Related
Update:
I was able to use this method to root the new ICS update. The thread has been edited accordingly.
----------------------------------------------
I was unable to find a single thread that detailed how to root the stock T-Mobile Springboard firmware and keep the boot and recovery partitions intact to allow future updates, so I have consolidated information from other threads and posts, as well as adding a little myself. Full credit goes to the users and thread OP's referenced in the post links below.
The usual warnings apply: Under no circumstances should anyone do this to their device. You are likely to brick your device and render it completey unusable. In addition, you will void your warantee with T-Mobile. So you will have an out-of-warantee brick instead of a nice, functional tablet. Turn back now while there is still time.
Before you begin, I obviously did this to my device without any problems. My device is running full stock T-Mobile Springboard firmware with the following:
Android version: 4.0.3
Baseband version: 314007
Kernel version: 3.0.8
Build number: S7-303uV100R002C201B035
I do not know if it will work on a device with any other version of the firmware. The following also assumes that you have fastboot and ADB installed and functional on your computer.
In describing how to boot into fastboot and recovery modes below, the description of the volume buttons is how they are while in portrait mode in Honeycomb....as this is where I first used this method. In other words, the volume button closer to the power button is volume up and the other volume button is volume down.
1. Download the CWM Recovery image from this post:
http://forum.xda-developers.com/showpost.php?p=23601045&postcount=7
2. Download CWM-SuperSU-v0.95.zip from this post:
http://forum.xda-developers.com/showpost.php?p=27678611&postcount=22
3. Copy the CWM-SuperSU-v0.95.zip file to an sdcard and put the card in your device.
4. Flash the CWM recovery image to your first recovery partition ONLY:
a.) Boot into fastboot by powering down the device and starting it back up by pressing the
volume up and power buttons at the same time. After the device vibrates, release the
power button but keep holding the volume button until it is booted into fastboot.
b.) Once in fastboot, flash the recovery image:
Code:
fastboot flash recovery recovery5.5.0.4.img
5. Press and hold the power key for 10 seconds to reboot the device. It will boot into the
T-mobile firmware.
6. Power down the device in the usual fashion.
7. Boot into recovery by starting the device back up by pressing the volume down and power
buttons at the same time. After the device vibrates, release the power button but keep
holding the volume button until it is booted into CWM Recovery.
8. Choose 'install zip from sdcard' -> 'choose zip from sdcard', then select the
CWM-SuperSU-v0.95.zip file you put on your sdcard above, then confirm installation.
9. Go back to the main menu and select 'reboot system now'. It will boot into the T-Mobile
firmware.
10. Shut the device down again in the usual fashion, then restart normally and boot into the
T-Mobile firmware again.
11. Now you need to get your stock recovery partition back and get rid of CWM recovery.
There are two copies of the stock recovery- one on each 'recovery' and 'recovery2'. You can
get back to stock recovery by extracting an image from 'recovery2' and flashing it back to
'recovery'. The following (using adb from your computer) will dump the image from recovery2
to your sdcard:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard2/recovery.img
12. Take the sd card out of your device and copy this file back to your computer, then flash the
first recovery partition with this image as in step 4b above, but with your new recovery.img file.
You are now rooted and your recovery partitions are returned to stock.
Once you are rooted, if you would like to remove some of the T-Mobile bloatware note that the apk files are not in the usual location (/system/app). I found them tucked away in the following directory:
/data/cust/app
Of course, you will need an app like Root Explorer to get to them and delete them...or you can just use adb. I deleted several of the apk files in that directory, rebooted, and everything is working just fine...with less bloatware.
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Just to add another bit of information - a list of what I believe are the internal partitions and their locations appears below. I got this from the output from 'cat /proc/partitions' and 'mount', as well as further inspection of the stock recovery image that I extracted from my device. As we don't have a functional CWM Recovery, and I am not sure that I would use any version that was built for the Mediapad (i.e. non-Springboard) for backup and restoring, this list should give Springboard users a way to back up their devices. Using the 'dd' command as in the coding box at the bottom of the OP for each of the paritions should result in a partition image stored out on the sdcard. Fastboot then should be able to flash these 'backed up' images back to the device as in step 4b of the OP...with the correct partition names and backup files substituted of course. I did do this for the recovery partition as I detailed in the OP, but have not tried it for the rest of the partitions.
Code:
/misc emmc /dev/block/mmcblk0p14
/vrcb emmc /dev/block/mmcblk0p16
/recovery emmc /dev/block/mmcblk0p17
/recovery2 emmc /dev/block/mmcblk0p18
/boot emmc /dev/block/mmcblk0p19
/system ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p22
/cust ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p27
/tmpdata ext4 /dev/block/mmcblk0p23
/persist ext4 /dev/block/mmcblk0p21
/tombstones ext4 /dev/block/mmcblk0p24
/firmware ext4 /dev/block/mmcblk0p1
Thanks
Many ty's for this.
Thanks you help me rooted my Springboard. Have you try the MediaPad Phone app can we use the tablet for calling? :good:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
---------- Post added at 06:11 PM ---------- Previous post was at 05:49 PM ----------
robkaos said:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
Click to expand...
Click to collapse
Also can I do it without PC?
Sent from my SpringBoard using XDA Premium App
Can I use the recovery image from the update that is still on my sd card,what is the difference between the I've springboard .rar, and the su files
Sent from my SpringBoard using XDA Premium App
robkaos said:
Do I have to do step 11 ?
......
Also can I do it without PC?
Click to expand...
Click to collapse
If you do not return your recovery partition to stock, then you will not be able to install future firmware updates from T-Mobile as their updates rely on the stock recovery. So no, you don't have to return your recovery partition to stock, but if you don't you will not be able to install future T-Mobile updates. As far as doing this without a computer - you can use a terminal emulator on your Springboard to create the recovery image from 'recovery2'....the commands should be the same. However, you need to fastboot flash that image back to 'recovery', which you must do from your computer with your device in fastboot mode.
robkaos said:
Can I use the recovery image from the update that is still on my sd card....
Click to expand...
Click to collapse
Yes, if you extract the recovery image from the official T-Mobile update package, you can use this image to flash 'recovery' back to stock when you are done.
Some people have reported that they are unable to boot into CWM recovery if it is flashed only to 'recovery' and not also to 'recovery2'. It is my experience that the device seems to alternate which recovery partition it boots into when you sequentially boot it into recovery mode. When I have CWM on 'recovery' and the stock recovery on 'recovery2', my device will boot into CWM every other time I boot into recovery mode. The other times it boots into the stock recovery. If you can't get CWM recovery to appear when you boot into recovery mode, you could do things a bit different than the instructions. Extract the stock recovery image from the official T-Mobile update package. Store this away on your computer. Then, instead of only flashing 'recovery' with CWM recovery, also flash 'recovery2'. Once you are done rooting the device, use your stored image of the stock recovery to flash 'recovery' and 'recovery2' back to stock.
Originally, I used this method to root Honeycomb. I did not have the T-Mobile update package for Honeycomb and so could not simply extract the stock recovery image from that package. You cannot use the 'dd' command as in step 11 above until you are rooted to dump the image of 'recovery2'. So, without a copy of the update package I could not get an image of my recovery partition without already being rooted. But to root, I have to overwrite my recovery partition with CWM recovery, thereby making it impossible to dump a copy of the stock recovery as I had wiped it out and replaced it with CWM. The solution was to only flash one of the recovery partitions and keep the other one as a backup until the device was rooted and the image could then be extracted.
robkaos said:
...what is the difference between the I've springboard .rar, and the su files
Click to expand...
Click to collapse
Not sure what you are asking here...please clarify.
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?there is not a one click Method like motor defy? My phone wasn't such a problem
Sent from my SpringBoard using XDA Premium App
robkaos said:
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?
Click to expand...
Click to collapse
I don't know about the root files for the Mediapad. I know there is a package that contains the su files and a Windows-based command file that contains a string of adb commands that is supposed to work to root both the Mediapad and the Springboard. I think what you are talking about can be found at either one of these locations:
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
I tried to use this, and got a 'premission denied' fail pretty early on. I run Linux on my desktop, so perhaps this works under Windows with the specific Springboard drivers and interface software installed, but it sure does not work in Linux. I came up with my method (or rather consolidated the information for 'my' method from multiple other sources) as a result of having this root method fail for me.
robkaos said:
...there is not a one click Method like motor defy? My phone wasn't such a problem
Click to expand...
Click to collapse
If the files that I linked above work for you, then this is going to be about as close to a 'one-click' method as you can get. Unless you modified it, your Motorola Defy is running Android 2.1 (Eclair). This version of Android can be rooted pretty much just by yelling 'ROOT!' at your phone. There is even an app in the market that can be installed and run on an Android v2.1 device that provides a one-click root without the use of a computer. All of the exploits that were used for these one-click root methods were patched in Android v3+. Pretty much every device needs its own unique root method now, and the only way it is a one-click method is if someone has constructed a command script to execute all of the needed commands for you, as in the linked packages above.
xdajunkman said:
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Click to expand...
Click to collapse
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Thanks for the clarification
Sent from my SpringBoard using XDA Premium App
cmstlist said:
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Click to expand...
Click to collapse
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Just finished rooting my MediaPad from t-mobile. I had to install into recovery one and two so now I have no original recovery but I don't really care, I've got the latest Android Ice Cream update beforehand. What usefull apps with root access do I need now? I've got ad free and ROM Toolbox. Was there a phone app that I could use now?
Failed updates and can't recover - PLEASE HELP!
xdajunkman said:
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Click to expand...
Click to collapse
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
knightpawn said:
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
Click to expand...
Click to collapse
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Any particular locations for the other files via fastboot?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
Wow! Thanks for the help! I unfortunately, don't have my other computer that has the proper drivers installed to recognize the tablet and to run fastboot on. So, I'll try the fix you are suggesting once I get home today. However, in the meantime, I had some questions with regard to where I should flash the other files.
I understand that recovery.img should go to the recovery and recovery2 partitions.
What about the others? Does boot.img go to a particular partition? Effectively, what would the command line look like? (eg fastboot flash boot boot.img?)
Sorry about the newbie questions. I've installed a number of custom ROMs on phones using CWM, but this is a strange beast.
With regard to your question of whether it boots, well, kind of...it does boot to the T-mobile Springboard screen, then it sits there. I will let it sit for 20-30 minutes and see what happens. Will report back...for sure!
Thanks a ton!
[UPDATE]
So, I had a chance to install the TWRP recovery with the CM10 ROM. I loaded the CM10 ROM with the TWRP which installed successfully. I turned the tablet on and let it sit there for about 10 minutes and sure enough, CM10 runs just fine. However, I did notice that I cannot receive any calls. I am able to make calls, but when someone dials my number, it just goes straight to voicemail.
So, now, I'm wondering, if I can get the stock ICS with International ROM running so that I can try to use this thing as a phone, data and texting tab. I'll try what you suggested when I get home as mentioned earlier.
CM10 has too many problems, why would you want to use it?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
That worked for me. After playing with vold.fstab I had rendered my Springboard unusable (got the encryption was unsuccessful screen!).
I really wanted to switch the apps installation path to the external sd card but did not succeed.
What am I doing wrong
I have not been able to root my springboard at all. It will go to a black screen that says enter fastboot and it just stays there. When I type to flash the recovery it says it cannot load it. I have adb and fastboot installed...could it be a driver issue? I now know that I am in the correct screen, just can't get this thing rooted. any help would be appreciated thanks.
Well I feel quite stupid. But figured out where I went wrong and for the love of God got my Springboard rooted. *whew*
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
ezugaru said:
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
Click to expand...
Click to collapse
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
Hi, this is what i used to downgrade : http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Hope it helps, i'm at the office now, so when i get home I'll check where i got the resources to downgrade since i used my personal computer to do it.
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
ezugaru said:
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
Click to expand...
Click to collapse
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
gypsydanger said:
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
Click to expand...
Click to collapse
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
ezugaru said:
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
Click to expand...
Click to collapse
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
gypsydanger said:
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
Click to expand...
Click to collapse
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
ezugaru said:
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
Click to expand...
Click to collapse
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
gypsydanger said:
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
Click to expand...
Click to collapse
Did you give terminal root permissions by issuing the SU command and then granting the permissions on the phone?
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
gypsydanger said:
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
Click to expand...
Click to collapse
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
roirraW "edor" ehT said:
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
Click to expand...
Click to collapse
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
gypsydanger said:
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
Click to expand...
Click to collapse
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
bweN diorD said:
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
Click to expand...
Click to collapse
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
is there a specific version of twrp I need for that nightly?
gypsydanger said:
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
I'm attempting to wipe recovery again and try CWM to see if that will work.
Click to expand...
Click to collapse
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
bweN diorD said:
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
Click to expand...
Click to collapse
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
gypsydanger said:
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
Click to expand...
Click to collapse
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
gypsydanger said:
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
Click to expand...
Click to collapse
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
roirraW "edor" ehT said:
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
Click to expand...
Click to collapse
it says update failed due to an error and you have to hit retry or it does nothing...unless I need to just do nothing.
edit: IT WORKS YAY...all I did was retry and retry (definition of insanity) and the /sdcard just appeared then the dd command worked and I'm in recovery now yayayayayay
edit: edit: I did take out my eternal SD card so I am going to guess and say that that was the problem from the get go...anybody have any thoughts on that??
Hoping to use this thread to help members who are having bootloops/wifi/etc. issues after flashing different kernels/system images.
If wi-fi is not working (A2017U B20):
bkores said:
Boot into TWRP, then connect your phone to your computer making sure adb is working then execute:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
This should be your output:
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst1 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst1': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001917 seconds, 1.0GB/s
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst2 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst2': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001829 seconds, 1.1GB/s
/dev/block/platform/soc/624000.ufshc/by-name #
Click to expand...
Click to collapse
You also need the crossed out boot.img from Here
If you're using an SD card, reboot your phone to TWRP. Make sure external SD is mounted in TWRP. On your PC, in the folder where your downloaded and extracted the boot.img, type:
Code:
adb push boot.img /external_sd/b20b_boot.img
adb shell if=/dev/block/sde12 of=/external_sd/boot_backup.img
adb shell if=/external_sd/b20b_boot.img of=/dev/block/sde12
adb reboot
Please post the steps you took to end up with bootloops/wifi issues, what exact issues you are having (wifi/bluetooth/cell/boot logo) as well as which recovery (stock/twrp) you currently have installed.
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.
http://forum.xda-developers.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
DrakenFX said:
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.
http://forum.xda-developers.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
Click to expand...
Click to collapse
Well, we got two sub-forums covered now. Let's see if anyone bites.
Well I did Draken's B20_Boot TWRP Backup Xposed+Root Edition Provided by DrakenFX , which cause a no boot situation, with no access to recovery. used tenfar's root without bootloader unlock to flash boot and recovery, then Draken's software image booted but no wifi. Still haven't fixed that one yet.
@thjoca3 do you know what system.img file you used? Is it a b20_boot system.img?
jkuczera said:
@thjoca3 do you know what system.img file you used? Is it a b20_boot system.img?
Click to expand...
Click to collapse
That I'm not sure, it's whatever system is packaged with Draken's backup
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Exactly what this thread says to do...http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
I downloaded the TWRP backup from that thread, and then downloaded Tenfar's tool from his own thread. I used his thread(Tenfar's) for the acquiring of the tool, as well as downloading a2017U B20 (since B20_boot unlocked is crossed out?). I then flashed the boot and recovery .img(using Tenfar's tool), then restored to the TWRP backup in TWRP provided by rcriderz. Afterwords, my phone booted up, but did not have Wifi access. That seems to bethe only feature missing... At this point I think I'd just rather wait for the first cyanogenmod release, but this is how I got to this point. I did this in the first place because I bricked my device by using GravityBox and rebooting so the settings would kick in. Device info: US Variant, unlocked bootloader via ZTE request form, TWRP installed
jkuczera said:
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Click to expand...
Click to collapse
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
jkuczera said:
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Click to expand...
Click to collapse
I know this is not my thread but having it little more info in the following form will help a lot lIssue
- Model :
- Previuos Version :
- Current Version :
- Issue / Problem :
- How happen :
That will help a lot figure things out.
DrakenFX said:
I know this is not my thread but having it little more info in the following form will help a lot lssue
- Model : A2017u
- Previous Version : locked bootloader, twrp, stock rom, was never able to get full root, and always had password needed in twrp, b20_boot
- Current Version : same other than using your system, from the B20_Boot TWRP Backup Xposed+Root Edition (still no root) had to flash boot and recovery from tenfar to get it to boot.
- Issue / Problem : no wifi, cannot copy anything over 5gb to sdcards... cant get back to stock
- How happen : flashed B20_Boot TWRP Backup Xposed+Root Edition via twrp, never lost wifi, till I flashed this.
That will help a lot figure things out.
Click to expand...
Click to collapse
zz
thjoca3 said:
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
Click to expand...
Click to collapse
The problem is likely the format of your SD card. It needs to be in a format that accepts files > 4GB. I believe exFAT or ext4 should work.
http://kb.sandisk.com/app/answers/d...rger-file-to-a-usb-flash-drive-or-memory-card
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
thjoca3 said:
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
Click to expand...
Click to collapse
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.
Do you know if warofhero's system image a b20 or a b20_boot?
jkuczera said:
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.
Do you know if warofhero's system image a b20 or a b20_boot?
Click to expand...
Click to collapse
I tried both on his, neither worked for me. Then I did this
Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from @rczrider‘s backup real stock b20 boot.img) and my wifi is back.
thjoca3 said:
I tried both on his, neither worked for me. Then I did this
Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from @rczrider‘s backup real stock b20 boot.img) and my wifi is back.
Click to expand...
Click to collapse
That's awesome, glad you got it fix.
So you have a full operational device now? Hope this solution help others.
DrakenFX said:
That's awesome, glad you got it fix.
So you have a full operational device now? Hope this solution help others.
Click to expand...
Click to collapse
Yes, appears everything is working now, with the modified boot.
I posted this somewhere else as well but here it goes again.
The booti.img and system have to match and be from the same set. So if you use stock B20 (not _Boot) boot.img then you have to use the same /system. In this case this would be
For locked bootloader use rcrider's boot(no root) + system or tenfar's boot(root) + rcrider's /system
For unlocked bootloader you would use B20_Boot boot+system like one jkuczera posted upthread
Do not mix and match files form different region's either, these are both from US A2017U model.
When bootlooping, there are multiple reasons why this could be:
- wrong modle boot.img
- unrotted boot.img and modded recovery or system while BL is locked
- /system flashed with unsuported SU or Xposed
- boot.img flashed with unsupported kernel/ramdisk patch
- junk in cache/dalvik
- junk in /data
- /data encrypted with key which cannot be decrypted due to altered cryptochain
The way to fix it most of the time is to flash proper boot and system and wipe all user partitions. tenfar's tools can restore boot and recoveries very painlessly. TWRP can take care of the /system and wipes. The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency. Hope this helps sort out the problems. I might try all this out once i am certain I'll keep the phone, it is currently in trial mode for few more weeks. The full "System Image" for B20_boot was posted here http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53 , (edit: jkuczera's is also System Image and same size). maybe rcrider can put up one for B20 Stock on his MEGA
peramikic said:
The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency.
Click to expand...
Click to collapse
Thanks for clarifying @peramikic.
For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
jkuczera said:
Thanks for clarifying @peramikic.
For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
Click to expand...
Click to collapse
This probably goes more for the B20 folks, since i doubt we will see an OTA from ZTE that will work on B2-_Boot. But in essence the System Image backups are supposed to produce bit level mirror image of the /system partition so that OTA update will properly hash it. Chances are very high that when you restore regular ext4 backups, while the files are the same they will not be laid out on the partition the same way. That's why /system is strictly read-only now. Even just enabling that RW access in TWRP can alter it. For instance the image you and swehes have posted differs slightly in first 4MB of the files (his has some stuff while your is all 0s) and then again in offset 69bd000 or so where one file is missing from your's i think it's the recovery-from-boot file. It is likely TWRP removed it so it would not get flashed over after reboot with stock recovery, if you allowed RW access to system.
M6E69X only for WI501Q
TWRP Backup & stockrecoveryM6E69X: uploaded by @Lrs121
【Version】
WI501Q _M6E69X
【Model Name】
ZenWatch 2
【Release Date】
???
【Release Note】
???
@RoyanArt
I won't be able to have access to adb till late tonight at the earliest, can you pull it using the following command?
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/
Those commands should copy the stock recovery IMG to your sdcard directory
Edit. Last command might be
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG
I think you have to specify the destination IMG file name
Sent from my ONEPLUS A3000 using Tapatalk
RoyanArt said:
MWD59 to M6E69N update.zip (adb sideload) : go to this thread
TWRP Backup : googledrive
Who can help to pull the stock recovery ? @Lrs121 , @slothdabski
【Version】
M6E69N
【Model Name】
ZenWatch 2
【Release Date】
2016/10/17
【Release Note】
1.Fix security vulnerabilities ( Update to Sep 2016 of Android Security Bulletins )
2.Fix issue "Watch could not pair with iPhone 7"
Click to expand...
Click to collapse
FYI: The stock recovery link is broken.
I can get to it in a couple hours. Out running errands and I've been meaning to make a backup
Here it is: Stock M6E69N recovery
slothdabski said:
@RoyanArt
I won't be able to have access to adb till late tonight at the earliest, can you pull it using the following command?
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/
Those commands should copy the stock recovery IMG to your sdcard directory
Edit. Last command might be
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG
I think you have to specify the destination IMG file name
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
sorry, i cant do it, because i've flashed twrp recovery :good:
Lrs121 said:
I can get to it in a couple hours. Out running errands and I've been meaning to make a backup
Here it is: Stock M6E69N recovery
Click to expand...
Click to collapse
Thanks for the stock recovery, ill put your post to top :good::good:
Want to root/twrp Zenwatch 2 m6e69n - ANY HELP would be GREAT!!!
I got my Z2 m6e69n about a week ago (10/16/16) and it's great but I want root & twrp like I have on my other Android devices. Don't know that it matters, I'm using LS990 (Sprint LG G3 on KK 4.4.2). I've been searching XDA and YouTube for clear, detailed info on how to root and get TWRP on the watch but not having a lot of luck.
What I have found is:
- I have activated developer options
- How to get into recovery, how to access bootloader, how to unlock bootloader (http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623) THANKS to arbitercu
...but nothing detailed about installing TWRP. Maybe I'm blind or just not understanding but any help would be great. I simply don't want to BRICK my Zenwatch.
- ALSO, VERY LITTLE EXPERIENCE with ADB and side loading which I think might be important to mention.
- Last thing, basically want to get some of the BLOAT off the device and get the most out of it.
Almost forgot:
- Zenwatch 2 m6e69n Sparrow (1.63")
Thanks in advance!
dsabine said:
I got my Z2 m6e69n about a week ago (10/16/16) and it's great but I want root & twrp like I have on my other Android devices. Don't know that it matters, I'm using LS990 (Sprint LG G3 on KK 4.4.2). I've been searching XDA and YouTube for clear, detailed info on how to root and get TWRP on the watch but not having a lot of luck.
What I have found is:
- I have activated developer options
- How to get into recovery, how to access bootloader, how to unlock bootloader (http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623) THANKS to arbitercu
...but nothing detailed about installing TWRP. Maybe I'm blind or just not understanding but any help would be great. I simply don't want to BRICK my Zenwatch.
- ALSO, VERY LITTLE EXPERIENCE with ADB and side loading which I think might be important to mention.
- Last thing, basically want to get some of the BLOAT off the device and get the most out of it.
Almost forgot:
- Zenwatch 2 m6e69n Sparrow (1.63")
Thanks in advance!
Click to expand...
Click to collapse
How about a little more googling. http://forum.xda-developers.com/zenwatch-2/orig-development/wip-unofficial-twrp-v2-8-7-0-t3321199/
Be careful what you remove. The watch won't function properly without some apps.
edit : no issue quick for wear
Thanks for the thread. :laugh::laugh::laugh:
Could someone provide fastboot flashable .IMG files?
I've ****ed up my watch quite hard by grabbing the wrong system image while the watch was still locked, now I can't even boot it anymore or restore a TWRP backup because the file system seems to be corrupt. I can't save anything in /sdcard without it getting wiped again after a reboot.
EpicLPer said:
Could someone provide fastboot flashable .IMG files?
I've ****ed up my watch quite hard by grabbing the wrong system image while the watch was still locked, now I can't even boot it anymore or restore a TWRP backup because the file system seems to be corrupt. I can't save anything in /sdcard without it getting wiped again after a reboot.
Click to expand...
Click to collapse
What happens when you boot twrp using fastboot? If you can get into twrp, with the bootloader unlocked you might be able to reformat the partitions.
On a side note I think you can format the partitions from fastboot mode
Lrs121 said:
What happens when you boot twrp using fastboot? If you can get into twrp, with the bootloader unlocked you might be able to reformat the partitions.
On a side note I think you can format the partitions from fastboot mode
Click to expand...
Click to collapse
Yeah, I've managed to repair the partitions by erasing and formatting them via fastboot, for whatever reason only formatting them didn't help... I have no clue why. Except boot I've erased + formatted every partition, then booted TWRP via "fastboot boot TWRP" and then was able to push TWRP backup files onto /data/media (/sdcard was broken still for whatever reason). After the first boot it somehow fixed /sdcard too tho it was missing all of its files on there. I simply did a factory reset of the watch after this and now it seems to be back and working again, tho I'm not fully sure because TWRP seems to have some problems still but that could be due to the wonky and, sorry, "****ty" port of TWRP 3.0 someone else made.
EpicLPer said:
Yeah, I've managed to repair the partitions by erasing and formatting them via fastboot, for whatever reason only formatting them didn't help... I have no clue why. Except boot I've erased + formatted every partition, then booted TWRP via "fastboot boot TWRP" and then was able to push TWRP backup files onto /data/media (/sdcard was broken still for whatever reason). After the first boot it somehow fixed /sdcard too tho it was missing all of its files on there. I simply did a factory reset of the watch after this and now it seems to be back and working again, tho I'm not fully sure because TWRP seems to have some problems still but that could be due to the wonky and, sorry, "****ty" port of TWRP 3.0 someone else made.
Click to expand...
Click to collapse
That's good you got it working. As for twrp if I remember right there were some issues with 3.0.0 regarding Android wear that were fixed in later versions. Ever since my galaxy s3, I've taken to building my own for the devices I have or have had. I make them available on my website.
Can anybody provide this for a Zenwatch 2 Wren? It would be appreciated a lot.
Can you help to pull the M6E69S stock recovery ? @Lrs121 , @slothdabski
RoyanArt said:
Can you help to pull the M6E69S stock recovery ? @Lrs121 , @slothdabski
Click to expand...
Click to collapse
Sorry had it pulled the moment the ota went out. I just didnt have it pushed to my server. Sparrow Stock recoveries
OP EDITED & UPDATED
M6E69S
-Version-
WI501Q _M6E69S
-Model Name-
ZenWatch 2
-Release Date-
2016/12/07
-Release Note-
1.Fix security vulnerabilities ( Update to Nov 2016 of Android Security Bulletins
Hey bud, watch just got an update today dec 29th, im rooted with twrp. Ill install a stock recovery sometime but in the mean time it would be nice to get that up for people to side load!
Dont know what the build is called, but i was running M6E69S when i got it.
Can you help to pull the M6E69V stock recovery ? @Lrs121 , @slothdabski
RoyanArt said:
Can you help to pull the M6E69V stock recovery ? @Lrs121 , @slothdabski
Click to expand...
Click to collapse
@RoyanArt Could you please upload the TWRP backup of latest firmware? It would be so appreciated ???
I recently messed up my V30 H933 badly and it'll only boot to TWRP now (not even Download Mode is working), so I'm looking for someone using LG official FW and who'd be willing to run the following command on TWRP on either Nougat or Oreo:
Code:
ls -l /dev/block/bootdevice/by-name
I'm hoping that, with said command output, I'll be able to manually flash some stuff around on my phone that'll get the system booting again. Should I be successful, I'll write down a guide to help people who run into the same problem as well.
Thanks in advance.
From my experience with past snapdragon devices (LG G Pro and OP2) that had that problem: misc partition was corrupted
Flash a kdz (should reset that flag there), or (didnt try this on a V30, but works on a G6, so... i dont guarantee anything, could even brick your device) via terminal (adb or twrp built in):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Safer method should be to flash a kdz though...
SGCMarkus said:
From my experience with past snapdragon devices (LG G Pro and OP2) that had that problem: misc partition was corrupted
Flash a kdz (should reset that flag there), or (didnt try this on a V30, but works on a G6, so... i dont guarantee anything, could even brick your device) via terminal (adb or twrp built in):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Safer method should be to flash a kdz though...
Click to expand...
Click to collapse
I can't flash a KDZ because the phone won't go to Download Mode, it will only reboot to TWRP.
And I tried that command, it did nothing for me except stopping the phone from booting up when I connected it to USB.
GryphonBR said:
I can't flash a KDZ because the phone won't go to Download Mode, it will only reboot to TWRP.
And I tried that command, it did nothing for me except stopping the phone from booting up when I connected it to USB.
Click to expand...
Click to collapse
If you reboot to TWRP, what happens if you flash a US998 ROM?
Have you tried Master Reset to wipe everything?
ChazzMatt said:
If you reboot to TWRP, what happens if you flash a US998 ROM?
Have you tried Master Reset to wipe everything?
Click to expand...
Click to collapse
How can I flash a US998 ROM (I'm assuming the KDZ) when I can't access Download Mode? And yeah, I tried doing a full wipe and then flashing a couple of different ROMs I found here (Lineage, WETA and Boombox), none worked, I could see under /system that information had been populated, but trouble is that it would seem as though I need to repartition the whole memory and reinstall the system from scratch before it works again.
So, breaking news: found a flashable ZIP that fixed my phone from the ground up. Managed to, luckily, get it back to working.
GryphonBR said:
So, breaking news: found a flashable ZIP that fixed my phone from the ground up. Managed to, luckily, get it back to working.
Click to expand...
Click to collapse
Good!
GryphonBR said:
So, breaking news: found a flashable ZIP that fixed my phone from the ground up. Managed to, luckily, get it back to working.
Click to expand...
Click to collapse
mind sharing where you found the zip? or the zip itself?
Just incase someone in the future has a similar problem
SGCMarkus said:
mind sharing where you found the zip? or the zip itself?
Just incase someone in the future has a similar problem
Click to expand...
Click to collapse
Absolutely! I used the ZIP I found on this thread to reflash the phone to stock ROM; I'm currently trying to get ahold of the guys who created the ZIP in the first place to try and figure out a way to do the same thing for my variant (H933), so I can reflash my phone with TWRP embedded since, apparently, lglaf can't be made to work with the V30 implementation.