I don't think it's called that anymore, i couldn't find it so I'll give what i think it is.
Upvote
0
SO here is my problem. I have an LG Tribute 2 (boost), . i rooted with kingroot and all was fine. I installed Super-SUME to install supersu and remove kingoroot. rebooted as it told me to do, and it is stuck at the boost boot logo. you cant get into fastboot on this phone, only download mode and stock recovery. stock recovery wont let you flash .img files only sideload option.
Any help would be appreciated. i have the stock system.img
PS i tried this:
http://forum.xda-developers.com/android/development/guide-how-to-root-lgls770-5-1-1-t3184649
people say this works on LG phones. i did it, didnt work either
Looks like I just repeated your mistake. If you find some way to unbrick, please share...
Try online nandroid by h3r3tic, just need Root perms and will give you a cwm/TWRP backup of your choice..^ That's what I thought. Anyway, I'd like to back up my ROM before I do anything else. TWRP and CWM don't have the Tribute 2 listed. How can I backup the ROM?
Will be following this thread as well, as I just got this phone for the second time, after bricking it earlier today
By the way, here's how I bricked it:
1) Rooted with KingRoot, no problems
2) Phone worked fine for a week
3) Downloaded F-Droid market, and the app Ad Away
4) Ran Ad Away
5) BRICK
So...don't run Ad Away!
Gonna do the smart thing and backup my ROM first this time. Which version of TWRP do I need?
EDIT: Went to the two websites linked in the post above mine, but it went to some BS survey, so I'm guessing it's all fake. All the user comments on those two sites are from people with generic white guy photos and English-looking names, who all make the same grammatical errors...the type of mistakes a native English speaker wouldn't make. @ELGee, did you actually USE the links you posted?
It is 30 bucks to switch to it(downgrade)Unrelated, but I did a factory reset on my (new) phone, and got stuck in a loop on the activation menus. When I managed to get past it, my home screen was flashing black and grey. In my settings, there was no default Home screen, so I selected the one that was there, and that got me back to a normal home screen. But now the Home button doesn't work, and other random little things are freaking out. All of this happened while on the phone with Boost Mobile support, so they told me to go get another phone from a store.
I didn't even root this phone! I shoud've got a Moto E or something...
Will be following this thread as well, as I just got this phone for the second time, after bricking it earlier today
By the way, here's how I bricked it:
1) Rooted with KingRoot, no problems
2) Phone worked fine for a week
3) Downloaded F-Droid market, and the app Ad Away
4) Ran Ad Away
5) BRICK
So...don't run Ad Away!
Gonna do the smart thing and backup my ROM first this time. Which version of TWRP do I need?
EDIT: Went to the two websites linked in the post above mine, but it went to some BS survey, so I'm guessing it's all fake. All the user comments on those two sites are from people with generic white guy photos and English-looking names, who all make the same grammatical errors...the type of mistakes a native English speaker wouldn't make. @ELGee, did you actually USE the links you posted?
WARNING: DO NOT FLASH ANYTHING TO BOOT OR RECOVERY. IT WILL NOT WORK. BUMP WILL NOT WORK. NO EXPLOIT IS AVAILABLE RIGHT NOW. TEMP ROOT IS THE BEST THING YOU HAVE.
Hello, everyone. Let this serve as a guide for the LS665 (boost mobile). This is about the only info out there as the device is a month old. I have put all of the findings I have gone through below. Smack the thanks button around if you find it helpful.
Device Codename: LS665
Android Version: 5.1.1
Kernel Version: 3.10.49 (Source)
Baseband Version: MPSS.DPM.2.0.c11-00021-M8936FAAAANUZM-1
Build number: LMY47V
Software Version: LS665ZV3
Root is available on LS665ZV3
Root: King Root
Vulnerable To:
- CVE-2015-3828 (start stagefright)
- CVE-2015-1539
- CVE-2015-3824
- CVE-2015-3829
- CVE-2015-3827
- CVE-2015-1538 (end stagefright)
- CVE-2015-3636 (ping pong)
PartitionsCode:lrwxrwxrwx root root 1970-01-01 00:20 DDR -> /dev/block/mmcblk0p23 lrwxrwxrwx root root 1970-01-01 00:20 aboot -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 1970-01-01 00:20 abootbak -> /dev/block/mmcblk0p11 lrwxrwxrwx root root 1970-01-01 00:20 boot -> /dev/block/mmcblk0p18 lrwxrwxrwx root root 1970-01-01 00:20 cache -> /dev/block/mmcblk0p37 lrwxrwxrwx root root 1970-01-01 00:20 carrier -> /dev/block/mmcblk0p35 lrwxrwxrwx root root 1970-01-01 00:20 drm -> /dev/block/mmcblk0p31 lrwxrwxrwx root root 1970-01-01 00:20 eksst -> /dev/block/mmcblk0p26 lrwxrwxrwx root root 1970-01-01 00:20 encrypt -> /dev/block/mmcblk0p25 lrwxrwxrwx root root 1970-01-01 00:20 factory -> /dev/block/mmcblk0p29 lrwxrwxrwx root root 1970-01-01 00:20 fota -> /dev/block/mmcblk0p30 lrwxrwxrwx root root 1970-01-01 00:20 fsc -> /dev/block/mmcblk0p21 lrwxrwxrwx root root 1970-01-01 00:20 fsg -> /dev/block/mmcblk0p20 lrwxrwxrwx root root 1970-01-01 00:20 grow -> /dev/block/mmcblk0p39 lrwxrwxrwx root root 1970-01-01 00:20 hyp -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 1970-01-01 00:20 hypbak -> /dev/block/mmcblk0p9 lrwxrwxrwx root root 1970-01-01 00:20 laf -> /dev/block/mmcblk0p17 lrwxrwxrwx root root 1970-01-01 00:20 metadata -> /dev/block/mmcblk0p14 lrwxrwxrwx root root 1970-01-01 00:20 misc -> /dev/block/mmcblk0p12 lrwxrwxrwx root root 1970-01-01 00:20 modem -> /dev/block/mmcblk0p33 lrwxrwxrwx root root 1970-01-01 00:20 modemst1 -> /dev/block/mmcblk0p15 lrwxrwxrwx root root 1970-01-01 00:20 modemst2 -> /dev/block/mmcblk0p16 lrwxrwxrwx root root 1970-01-01 00:20 mpt -> /dev/block/mmcblk0p32 lrwxrwxrwx root root 1970-01-01 00:20 pad -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 1970-01-01 00:20 persist -> /dev/block/mmcblk0p13 lrwxrwxrwx root root 1970-01-01 00:20 persistent -> /dev/block/mmcblk0p34 lrwxrwxrwx root root 1970-01-01 00:20 rct -> /dev/block/mmcblk0p27 lrwxrwxrwx root root 1970-01-01 00:20 recovery -> /dev/block/mmcblk0p19 lrwxrwxrwx root root 1970-01-01 00:20 rpm -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 1970-01-01 00:20 rpmbak -> /dev/block/mmcblk0p10 lrwxrwxrwx root root 1970-01-01 00:20 sbl1 -> /dev/block/mmcblk0p1 lrwxrwxrwx root root 1970-01-01 00:20 sbl1bak -> /dev/block/mmcblk0p7 lrwxrwxrwx root root 1970-01-01 00:20 sec -> /dev/block/mmcblk0p24 lrwxrwxrwx root root 1970-01-01 00:20 sns -> /dev/block/mmcblk0p28 lrwxrwxrwx root root 1970-01-01 00:20 ssd -> /dev/block/mmcblk0p22 lrwxrwxrwx root root 1970-01-01 00:20 system -> /dev/block/mmcblk0p36 lrwxrwxrwx root root 1970-01-01 00:20 tz -> /dev/block/mmcblk0p2 lrwxrwxrwx root root 1970-01-01 00:20 tzbak -> /dev/block/mmcblk0p8 lrwxrwxrwx root root 1970-01-01 00:20 userdata -> /dev/block/mmcblk0p38
Partition dump backup:
DOWNLOAD IT HERE (System rooted, but can uninstall)
Getting into "Download Mode"
- Power off
- plug usb in
- hold power and volume up at the same time
Getting into Recovery Mode
- Power off
- plug usb in
- hold power and volume down at the same time
Boot / Kernel info
Code:page size : 2048 kernel size : 7997632 ramdisk size : 2375543 dtb size : 182272 base : 0x80000000 kernel offset : 0x00008000 ramdisk offset : 0x02000000 tags offset : 0x00000100 dtb img : dt.img cmd line : console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=c50 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 vmalloc=504m
fstab
Code:# Android fstab file. # The filesystem that contains the filesystem checker binary (typically /system) cannot # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK #TODO: Add 'check' as fs_mgr_flags with data partition. # Currently we dont have e2fsck compiled. So fs check would failed. #<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags> /devices/soc.0/7864900.sdhci/mmc_host /storage/external_SD vfat nosuid,nodev wait,voldmanaged=external_SD:auto /dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait,check /dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,encryptable=/dev/block/bootdevice/by-name/encrypt /dev/block/bootdevice/by-name/persist /persist ext4 nosuid,nodev,barrier=1 wait,check /dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,barrier=1 wait,check /dev/block/bootdevice/by-name/drm /persist-lg ext4 nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait,check /dev/block/bootdevice/by-name/sns /sns ext4 nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait,check /dev/block/bootdevice/by-name/boot /boot emmc defaults defaults /dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults /dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
Battery Cover Pin Out
Did you know you dont need the battery cover on to manipulate power on, off, volume buttons.
Here is the pin out:
bottom right - common ground
bottom left - Volume -
top right - Power
top left - Volume +
To turn on power, youd get a paper clip and connect the bottom right with the top right. If you want power and volume down (recovery) youd connect the bottom left, bottom right, and top right pads together.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.