I was talking about this problem over in the trickdroid thread, simply because it was trickdroid I was flashing but in fairness to that thread I don't want to clutter it with an endless amount of questions, repeating myself over and over, when people are simply there to review the rom/tweaks. I will give my issues in the correct order as best as I can remember, bottom line is I'm caught in a TWRP bootloop.
1) Picked up phone and unlocked bootloader and rooted via all-in-one toolkit. Confirmed root by downloading Titanium, so at this point I am stock rooted with zero issues.
2) Having installed latest TWRP at time of root I immiedietly backed up the stock rom, which I then copied to computer, so I do have this backed up and it's also visible (though unflashable) in TWRP under internal storage.
3) Flashed Trickdroid, which hung on 'install,' and I've since found out there is an issue with aroma installer. Tried 100 times (no exageration)since then to flash that rom and it gets to 30% installed and then reboots into TWRP. TWRP won't then let me do anything of substance. TWRP is also telling me I am now unrooted when I attempt to reboot into recovery from within twrp.The exact order is, flash rom - gets to 30% - reboots into a white screen (not recovery) that says HTC One, quietly brilliant, and then within 10 seconds it automatically reboots into TWRP.
4) On recomendation from rom developer, attempted to flash CWM via fastboot and it flashed fine, fastboot states the flash is sucessful but then when I reboot into recovery it's still TWRP. So CWM appears to have flashed but hasn't for some reason.
And that's where I am. Tried to flash CWM, tried to push rom to sd card, no luck.
Any ideas?
Try to flash without aroma... Replace the meta inf folder with the one linked in the op so it doesn't utilize aroma
Sent from my HTC One using Tapatalk 2
thesparky007 said:
Try to flash without aroma... Replace the meta inf folder with the one linked in the op so it doesn't utilize aroma
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Tried to do that yesterday and it wouldn't push. Trying again right now so I can give an exact error message.
What do u mean it wouldn't push?
Sent from my HTC One using Tapatalk 2
OK, I've followed the instructions and now have a zip ready to be pushed/flashed.
My question is, would you reccomend flashing it directly to device in fastboot or push to sd card and flash from there?
thesparky007 said:
What do u mean it wouldn't push?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Kept getting errors whenever I tried to flash or push to sd card
When u extract the meta inf folder what all do u see in the root of that folder
Sent from my HTC One using Tapatalk 2
losangeles100 said:
I was talking about this problem over in the trickdroid thread, simply because it was trickdroid I was flashing but in fairness to that thread I don't want to clutter it with an endless amount of questions, repeating myself over and over, when people are simply there to review the rom/tweaks. I will give my issues in the correct order as best as I can remember, bottom line is I'm caught in a TWRP bootloop.
1) Picked up phone and unlocked bootloader and rooted via all-in-one toolkit. Confirmed root by downloading Titanium, so at this point I am stock rooted with zero issues.
2) Having installed latest TWRP at time of root I immiedietly backed up the stock rom, which I then copied to computer, so I do have this backed up and it's also visible (though unflashable) in TWRP under internal storage.
3) Flashed Trickdroid, which hung on 'install,' and I've since found out there is an issue with aroma installer. Tried 100 times (no exageration)since then to flash that rom and it gets to 30% installed and then reboots into TWRP. TWRP won't then let me do anything of substance. TWRP is also telling me I am now unrooted when I attempt to reboot into recovery from within twrp.The exact order is, flash rom - gets to 30% - reboots into a white screen (not recovery) that says HTC One, quietly brilliant, and then within 10 seconds it automatically reboots into TWRP.
4) On recomendation from rom developer, attempted to flash CWM via fastboot and it flashed fine, fastboot states the flash is sucessful but then when I reboot into recovery it's still TWRP. So CWM appears to have flashed but hasn't for some reason.
And that's where I am. Tried to flash CWM, tried to push rom to sd card, no luck.
Any ideas?
Click to expand...
Click to collapse
Okay LA. One quick and very basic question? You said you rooted the phone and you know because you downloaded and installed Titanium. Titanium does NOT need root for simple backups so that is no way to make sure you have root. To verify root, when you boot into bootloader/recovery, make sure it says "unlocked" and "tampered" at the top. I know it is basic but nothing will work without it. If it shows that, we can work from there. You should be able to just copy the file over to your SD card on the phone if your computer sees it.
frodoboy said:
Okay LA. One quick and very basic question? You said you rooted the phone and you know because you downloaded and installed Titanium. Titanium does NOT need root for simple backups so that is no way to make sure you have root. To verify root, when you boot into bootloader/recovery, make sure it says "unlocked" and "tampered" at the top. I know it is basic but nothing will work without it. If it shows that, we can work from there. You should be able to just copy the file over to your SD card on the phone if your computer sees it.
Click to expand...
Click to collapse
Good points, and yes, i'm unlocked and tampered. What I actually meant was TB stated 'rooted.'
thesparky007 said:
When u extract the meta inf folder what all do u see in the root of that folder
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
The new meta.inf now contains: com folder, CERT.RSA, CERT.SF, MANIFEST.MF
losangeles100 said:
The new meta.inf now contains: com folder, CERT.RSA, CERT.SF, MANIFEST.MF
Click to expand...
Click to collapse
Make sure it zips up properly and try again. If that doesn't flash try flashing the original zip
Sent from my HTC One using Tapatalk 2
Hey, Mike
We can take this here from PMs
Not sure on the zip you are trying to do, but would still try to get off twrp 2.5.0.0.
and fastboot the 2.3.3.0 twrp image i sent you. then try flashing rom after all wipes in recovery, not aroma. and make sure you fastboot the boot image from command window right after you flash rom. then erase cache then reboot to bootloader then reboot system. usually after first boot I reboot again wipe caches then reboot system--
losangeles100 said:
Good points, and yes, i'm unlocked and tampered. What I actually meant was TB stated 'rooted.'
Click to expand...
Click to collapse
I take it that letting the battery drain didn't help? Does ADB find the phone now? by the way, without S-OFF, it is almost impossible to brick your phone so we'll get there eventually!
Rug, firstly, thanks for going above and beyond, you're a credit to XDA and I for one really appreciate your help.
Now the weirdness: flashed the TWRP image you gave me and erased cache and rebooted into recovery and it's the original twrp. It definetly flashed correctly, said 'flashed' 'ok' so that is really weird. It simply isn't sticking. And just to clarify, fastboot sees the phone and everything went as it always has, except the end result.
frodoboy said:
I take it that letting the battery drain didn't help? Does ADB find the phone now? by the way, without S-OFF, it is almost impossible to brick your phone so we'll get there eventually!
Click to expand...
Click to collapse
Letting the battery drain is easier said than done on this bad boy
I'm down to 45% and not charging at all so as soon as I get to zero I will let you know. I'm actually starting to pin too much god damned hope on that! lol
Ok when you flashed CWM in the bootloader you complained that it still booted into TWRP, did you try flashing it again and then erasing cache while still in fastboot then booting into the recovery?
losangeles100 said:
Letting the battery drain is easier said than done on this bad boy
I'm down to 45% and not charging at all so as soon as I get to zero I will let you know. I'm actually starting to pin too much god damned hope on that! lol
Click to expand...
Click to collapse
boy this is a stumper! Can you reflash the original stock ROM and relock the bootloader and see if you go back to at least a working phone? Then you can unlock the bootloader again choosing CWM this time and then try to reflash TrickDroid? Also, do you have Superuser installed? I think you said you did. Just see if you can start over to at least recover your phone. Something went wrong with the initial steps to cause it to freeze up like that.
When flashng zip without aroma I get this error in cmd:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bobruels44 said:
Ok when you flashed CWM in the bootloader you complained that it still booted into TWRP, did you try flashing it again and then erasing cache while still in fastboot then booting into the recovery?
Click to expand...
Click to collapse
I believe I did but you make a valid point.
frodoboy said:
boy this is a stumper! Can you reflash the original stock ROM and relock the bootloader and see if you go back to at least a working phone? Then you can unlock the bootloader again choosing CWM this time and then try to reflash TrickDroid? Also, do you have Superuser installed? I think you said you did. Just see if you can start over to at least recover your phone. Something went wrong with the initial steps to cause it to freeze up like that.
Click to expand...
Click to collapse
Superuser was installed but when I reboot into recovery I get a message from twrp saying 'you're not rooted, would you like to flash SU now.' When I swipe to flash it does nothing, although SU is on internal storage.
Just to add, the backup I made is visible in the TWRP folder in storage but cannot be accessed, and when I hit the restore button nothing is listed.
Regarding reflashing stock original, I'd pay 100 bucks to anyone in this thread who could get me back to stock.
Related
Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.
Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app
How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse
I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/
Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".
reflash twrp
flash a custom rom
Unlocking the bootloader shouldn't cause that message to show up. What were you expecting the toolkit to do? And do you know what it successfully did?
It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.
Consult the guy who made the toolkit that ****ed up your phone. You clicked his button, rather then run a short list of well known commands we could help you with, so we have no idea what you did right or wrong... Maybe you didn't click hard enough.
Alternatively, read one of the many many many guides here, and use the single command needed, and if there are any errors copy and paste the console output (using code tags) here and we can sort you out in a minute or two.
Caebron said:
It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.
Click to expand...
Click to collapse
What root are you using? That is probably the issue. If you use the older style root you need a modified boot image. I suggest the new systemless root.
So to fix this lets do this:
1 Use the toolkit to flash stock and unroot.
2 Flash TWRP
3 Copy the systemless root 2.65 to the !readytoflash folder. Delete the three files that are in there. The are from the old root way.
4 Reboot into TWRP and use it to flash the new root.
When you exit TWRP it will offer to root your phone. Say no. And stop after each step and make sure the phone is ok. So we can tell what went wrong if there are issues.
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.
Hi,
Had the same thing...
Really DONT know what the hack with with these wonderful people who developet these tools that do not mention ANYTHING regarding the issu in the main page of their tools here.
I think that you should follow the instructions:
1) Download shamu-mra58k => extract => take bootloader + radio + boot + cache + recovery + system + userdata => compy to platform-tools folder (under SDK).
2) Open CMD (open command prompt...) from platform-tools folder.
3) Type: fastboot devices (to know that pc recognized your N6) & than type the commands as shown at the attached screenshot.
That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu
Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.
Click to expand...
Click to collapse
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.
thinkingbrian said:
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.
Click to expand...
Click to collapse
Best and easiest method to root Marshmellow imo is to flash TWRP and CF`s latest systemless root zip 2.65.
dahawthorne said:
That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu
Click to expand...
Click to collapse
That's not the NRT log (just flahsed manually by fastboot without any script).
I think with up to 6.0.1 MMB29K(not included) there is no issues.
Just kidding...
I've been running MMB29K for a couple of weeks with no problems. I was just suggesting that if the OP was going to go to the effort of flashing then he/she may as wll use the most recent version. Or even hold off for a few days for the possible new one in January. Hey, that's today...
Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and
Click to expand...
Click to collapse
... it bricks your phone. Unless you know exactly what you're doing. But then you don't really need it anymore.
People, Marshmallow is already past the toolkits. It has an update once a month, and the toolkits don't have time to be updated fast enough. You'll be bricking your phones constantly if you don't learn your stuff.
Caebron said:
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".
Click to expand...
Click to collapse
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.
najoor said:
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.
Click to expand...
Click to collapse
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.
najoor said:
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
Click to expand...
Click to collapse
Just LOVE how you explain it!
Wish more users will explain these kinds of things in such an "user friendly" way
I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.
fyrmd said:
I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.
Click to expand...
Click to collapse
You have to flash back to stock first. Marshmallow is checking for system mods, so if you don't undo the previous changes it will trigger again. Flash stock, twrp then 2.65 chainfire.
Caebron said:
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.
Click to expand...
Click to collapse
... You don't need to root to install a rom.
In fact, while installing the rom you will likely wipe your /system partition and any other partition you mess with to root....
What is it you think rooting actually does? Why are you doing it? What part do you think it will actually play in you installing a rom? Don't just do random ****. Learn what things do, so you can do what you want. This is why people hate toolkits. They promote this kinda of mentality where you just do stuff you don't understand in the slightest.
So, after rooting my device, I used rom toolbox to delete some of the bloat ware. Well, in doing so, I lost the ability to customize my lock screen wallpaper by deleting the gallery app. This annoyed me, so I decided to just start over. I flashed the x526 stock firmware. I thought it was essentially the exact same rom. Well, it apparently killed my imei, baseband is unknown, don't know status of NVRAM. From what I understand, flashing back to x522 stock rom should rectify issue. I've exhausted all other avenues. I tried to force the IMEI using mobileuncle, tried mtktools, tried dialing the #*#* command (phone did nothing). I don't know what else to do.
X522 is a snapdragon 652 device. you wont be able to use mobile uncle or mtk tools as they are for mediatek CPUs. you are screwed for the time being until someone is able to extract a backup of the stock image. i have a completely unmodified LeEco S3 sitting right here, where i may be able to do a TWRP backup, but honestly i don't know how
TWRP > backup > select all the partitions > swipe. Should put a backup file on your device. Upload to like google drive or something. Would that not work?
Joneildu said:
TWRP > backup > select all the partitions > swipe. Should put a backup file on your device. Upload to like google drive or something. Would that not work?
Click to expand...
Click to collapse
interestingly, the S3 has an unlocked bootloader similar to the US LePro3 in that the bootloader will unlock temporarily until the next reboot. i was able to unlock the bootloader, boot into twrp, wipe my data, then backup system/boot. its a 1.9GB file that's uploading at the moment. it'll take a while due to my slow connection
You are a hero my friend. Bought the phone for my daughter to keep in touch with me using hangouts/google voice number for wifi calls and texts while she is at her mother's. (She's 9). Didn't really care to brick it. Hopefully it works. :good:
Joneildu said:
You are a hero my friend. Bought the phone for my daughter to keep in touch with me using hangouts/google voice number for wifi calls and texts while she is at her mother's. (She's 9). Didn't really care to brick it. Hopefully it works. :good:
Click to expand...
Click to collapse
no worries. i was going to get around to this sooner or later. the following backup is from TWRP with a completely stock, unrooted system/boot backup. unfortunately, i didn't realize until after i was uploading that i forgot to run the OTA first, so the backup is from 18S. unfortunately, TWRP wouldn't allow me to backup the recovery, the only options were - system/boot/cache/data/firmware??
here's the mega link. a mirror would be nice - LeEco_X522_TWRP_BootSystem_18S
https://mega.nz/#!voQTWJrA!lZaTKQyoBKuiYfYizpWkh-fOBTlldUUCDtiiVYHzwes
also, imo, you should learn fastboot and NOT use that toolkit that's floating around.
---------- Post added at 10:27 PM ---------- Previous post was at 10:18 PM ----------
for some reason the 19S OTA fails now, no idea what i did wrong considering i did a "fastboot boot twrp.img" and did no flashing of anything. gah
I have some experience flashing the contents using fastboot, as my last two phones were a nexus 5 and 5X. I do appreciate your time and effort! The OTA failing is really weird. I cannot recall if I installed TWRP before or after I did the OTA update initially.
Joneildu said:
I have some experience flashing the contents using fastboot, as my last two phones were a nexus 5 and 5X. I do appreciate your time and effort! The OTA failing is really weird. I cannot recall if I installed TWRP before or after I did the OTA update initially.
Click to expand...
Click to collapse
Flash the whole ROM from TWRP and select do not disable stock recovery replace (do note swipe). The OTA zip will be around 1.5-2GB
I've gotten the option to not disable stock recovery when flashing via zip. I did not get that option when loading the recovery from the recovery menu. Nonetheless, I ran the recovery through twrp, IMEI still empty, baseband still unknown . I've got no clue now.
Joneildu said:
I've gotten the option to not disable stock recovery when flashing via zip. I did not get that option when loading the recovery from the recovery menu. Nonetheless, I ran the recovery through twrp, IMEI still empty, baseband still unknown . I've got no clue now.
Click to expand...
Click to collapse
did you do a restore? you would have to copy the contents of the zip file i posted to your \sdcard\TWRP\BACKUPS\[deviceid]\
the device ID folder you can get by doing a simple backup of something, then put the system/boot backup that i uploaded also in that folder. in any case, i think we're screwed anyway unless someone does a full system image backup with TWRP mounted as "read only"
Yep. That's exactly what I did. Did a generic TWRP backup of what I have. Then added the folder you uploaded to the device folder in the twrp backups folder. Everything loaded into the phone fine, just the IMEI and baseband are still toast.
Joneildu said:
Yep. That's exactly what I did. Did a generic TWRP backup of what I have. Then added the folder you uploaded to the device folder in the twrp backups folder. Everything loaded into the phone fine, just the IMEI and baseband are still toast.
Click to expand...
Click to collapse
you're probably SOL until a full US ROM is posted. i can try to do a full TWRP "system image" for ya, but there's no guarantees. the backup i posted earlier was just the system and boot partitions. not sure what else the full system image contains though
I'm in a similar situation. I'm just trying to get back to 100% stock so that I can take the OTA. I was hoping this backup would do that for me. I can't seem to get it to prompt me to disable stock recovery replacement. I want it to put stock recovery back so that I can attempt the OTA. I'm restoring it from twrp, not flashing it. Attempting to flash it is throwing an error at me.
Hitokiri-Snake said:
I'm in a similar situation. I'm just trying to get back to 100% stock so that I can take the OTA. I was hoping this backup would do that for me. I can't seem to get it to prompt me to disable stock recovery replacement. I want it to put stock recovery back so that I can attempt the OTA. I'm restoring it from twrp, not flashing it. Attempting to flash it is throwing an error at me.
Click to expand...
Click to collapse
when you restored from my twrp backup, did you get the stock recovery back? double check by turning off the phone, then holding both power button and volume up until the screen turns back on. i'm going to try to dump the recovery partition tonight within twrp, but i'm seriously a noob at this. you won't be able to install the OTA until we also get someone with a 100% stock USA S3 to do a full system image backup while mounting twrp as read-only. i should be able to get another S3 to do this within the next week or two. unfortunately you'll have to wait until then
Is there an EFS partition that was able to be backed up? That's the partition that contains the radio information with modem_st1 and modem_st2
Joneildu said:
Is there an EFS partition that was able to be backed up? That's the partition that contains the radio information with modem_st1 and modem_st2
Click to expand...
Click to collapse
unfortunately no, the only selectable partitions to backup using the X520 TWRP were: boot/data/cache/system/firmware. the partitions could be different from the X520, so hopefully i have some time tonight to dump the partitions. i found this guide, and it seems to work on my oneplus3 http://forum.xda-developers.com/showthread.php?t=2450045
I have a full TWRP backup of the x522, its actually 7.6 GB
, when i was copying it over to the phone or a small usb drive, it went to 3.? gb, it seems one file is 4gb......
anyways, even at 3.?gb it restored, and booted up, but i was never able to take the OTA to 19s
i put the full 7.6gb TWRP on a 128 mb sdcard and restored, but when i pressed reboot, that was last thing it did...lol
I did a return as a faulty unit,and have a new one coming saturday....
my point is, if any use i could upload it somewhere, i also captured the 19s update file if that helps anyone..
will upload if someone wants
ExTREmE99 said:
when you restored from my twrp backup, did you get the stock recovery back? double check by turning off the phone, then holding both power button and volume up until the screen turns back on. i'm going to try to dump the recovery partition tonight within twrp, but i'm seriously a noob at this. you won't be able to install the OTA until we also get someone with a 100% stock USA S3 to do a full system image backup while mounting twrp as read-only. i should be able to get another S3 to do this within the next week or two. unfortunately you'll have to wait until then
Click to expand...
Click to collapse
When I restore you're twrp backup, it's not giving me stock recovery back for some reason, and it's not asking about the stock recovery override thing either. I made a backup of my own before I rooted originally, (system and boot, but not system image) when I restore that it restores stock recovery. It's strange, using my backup, I can get the device unrooted and with stock recovery, but the OTA still fails
britdude said:
I have a full TWRP backup of the x522, its actually 7.6 GB
, when i was copying it over to the phone or a small usb drive, it went to 3.? gb, it seems one file is 4gb......
anyways, even at 3.?gb it restored, and booted up, but i was never able to take the OTA to 19s
i put the full 7.6gb TWRP on a 128 mb sdcard and restored, but when i pressed reboot, that was last thing it did...lol
I did a return as a faulty unit,and have a new one coming saturday....
my point is, if any use i could upload it somewhere, i also captured the 19s update file if that helps anyone..
will upload if someone wants
Click to expand...
Click to collapse
the only way a full backup will keep the OTA going is if you booted TWRP in read only mode and did a full backup that way. i think a lot of us messed up and swiped away the lock screen that TWRP shows after you change the language from chinese to english.
Hitokiri-Snake said:
When I restore you're twrp backup, it's not giving me stock recovery back for some reason, and it's not asking about the stock recovery override thing either. I made a backup of my own before I rooted originally, (system and boot, but not system image) when I restore that it restores stock recovery. It's strange, using my backup, I can get the device unrooted and with stock recovery, but the OTA still fails
Click to expand...
Click to collapse
yea, i was looking through the OTA script and it basically does a checksum of the /system partition and if it doesnt match the one in the script, it fails right there. you can see it working by flashing the OTA's update.zip in TWRP. i dug a little further and opened up the OTA zip file and looked into the script and that's when i started googling and found out about the TWRP read-only vs read/write screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ExTREmE99 said:
the only way a full backup will keep the OTA going is if you booted TWRP in read only mode and did a full backup that way. i think a lot of us messed up and swiped away the lock screen that TWRP shows after you change the language from chinese to english.
yea, i was looking through the OTA script and it basically does a checksum of the /system partition and if it doesnt match the one in the script, it fails right there. you can see it working by flashing the OTA's update.zip in TWRP. i dug a little further and opened up the OTA zip file and looked into the script and that's when i started googling and found out about the TWRP read-only vs read/write screen
Click to expand...
Click to collapse
I dont usually use TWRP in read only mode, but like ya say, with TWRP being in chinese till ya figure out the language part anything is possible
so to do the full back up you have to be in read only mode and that will allow restore and ota to take?
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment recovery_twrp.zip
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
---reserved---
before you ask...
yes, of course, i have already tried to flash supersu, but unfortunately I had no luck so far. The script always aborts because it fails patching sepolicy of boot.img.
so if anyone knows a solution for this, feel free to help!
edit:
found another way to root, look here
Amazing! I never thought yb would have twrp. I've been looking for a way to install gapps since I bought yb. After my final I will definitely have a try.
Was it stable when you flashed some zip?
AndyVerne said:
Was it stable when you flashed some zip?
Click to expand...
Click to collapse
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
All right, I wil try to install supersu after take my final exam ,too .
I believe there will be a way to solve it .
(oh ,god , the root seems to have sloved , nice job!)
danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
Code:
fastboot flashing lock
if you are not sure, try to search xda for more information about relocking.
danjac said:
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
if you are not sure, try to search xda for more information about relocking.
Click to expand...
Click to collapse
Oh, I gave it up... Thanks
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
danjac said:
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment 3994659
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
View attachment 3994696
View attachment 3994697
View attachment 3994698
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
Click to expand...
Click to collapse
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
hajkan said:
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
Click to expand...
Click to collapse
to your first question:
1. well, here we are not talking about backing up your user data but your rom (stock rom so to speak). if anything goes wrong you can always go back to stock.
2. if you want to peform ota update you can't do it with modified system (ota will fail), so normally you must go back to stock, update, root again
to your second question:
it's just a warning that your bootloader is unlocked, nothing more. it shows with every boot and after 5secs just boots normally.
you can easily find out about the advantages and disadvantages of an unlocked bootloader e.g. here on xda.
I can't thank you enough for this. I live in China and was only able to buy the Chinese version of the Yoga Book, which doesn't come with Google Services installed. However, using this TWRP recovery I was able to flash Google Services (and get root) which makes my Yoga Book so much more useful! Thanks so much!
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
zamzenos said:
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
Click to expand...
Click to collapse
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
danjac said:
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
Click to expand...
Click to collapse
Left it overnight and tried again today. It's OK this time. I fiddled with settings, mainly to deselect the read-only system option. Each stage of this process has been pretty frustrating (I'm used to hacking sammy devices - this is first and last time with a lenny). Stuck now trying to get root - it will probably take until tomorrow! btw, ver is YB1 X90F (Europe/UK).
But thanks for taking the trouble to reply. And thanks for giving us the opportunity to hack the YB.
Worked on the wifi version too.
You may not be a developer but you are a pretty smart guy to be able to figure this out on your own, my hat is off to you. I rooted my wifi version of Yoga Book using your instruction and the only notable issue I ran into in the process was that i had to install new Android usb drivers in Windows to get the reboot-bootloader command to work, other than that little hiccup it worked like a charm. One other issue I ran into that was of my own making was that Titanium backup encouraged me to upgrade super user which led to a soft brick, thankfully I'd backed my book up and was able to restore it.
Thanks for taking the time to share this with us because rooting made this device a much better experience.
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
kakit78 said:
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
Click to expand...
Click to collapse
If you just want to install gapps, there is no need to root.
1. download gapps from opengapps.org. select x86_64 6.0 version. select nano or micro version if only want google play to be worked.
2. put the gapps zip file into your root of your YB.
3. just follow the instructions of this post to boot into TWRP
4. In TWRP, select install zip file from SD, then select the gapps to install
5. after finish, reboot to the system.
6. Done!
---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------
The problem is that I fail to OTA updated after booting into TWRP and install gapps. Anyone can helps?
@danjac Hi, did you keep the boot to bios option in the reboot menu?
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
bump pls
even bad news is appreciated
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Hmm.. does phone in TWRP works like USB storage?
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?
vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.
swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?
swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.
redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.
Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?