Stuck in TWRP after pushed upgrade 28s - LeEco Le Pro3 Questions & Answers

This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.

Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium

mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?

Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.

In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658

marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium

No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that

Related

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind

Nexus 10 does not boot after Update

After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.

Trouble reflashing ASUS stock ROM for ZE551KL

I accidentally tried doing a factory reset, and flashing an incorrect rom. So I lost the stock rom, and have no other rom to use. I tried using TWRP to flash ASUS's stock firmware from asus's support website, under firmware. Using firmware file: "UL-Z00T-WW-1.16.40.763-user.zip"
but TWRP tells me "E:Error executing updater binary in zip '/sdcard/TWRP/Stock.zip'
Error flashing '/sdcard/TWRP/Stock.zip"
I still have access to both adb, fastboot, and TWRP but I cant get an OS to install.
Any help with this would be greatly appreciated, haven't even had this phone a day yet, and already may have broken it.
I don't have an answer to your question , just got this phone yesterday and am in the process of figuring out how to root and install a custom recovery for this specific device.. I have found many methods to root but none for my specific model. I think you have the same model as I do and was hoping you could lead me to the place that will give me the files I need.. the box my phone came in has the model as ASUS_Z00TD (ZE551KL).. Sorry I wasn't of any help to you, hope you manage to figure out how to flash something that will get your device running again!
tmjm28 said:
I don't have an answer to your question , just got this phone yesterday and am in the process of figuring out how to root and install a custom recovery for this specific device.. I have found many methods to root but none for my specific model. I think you have the same model as I do and was hoping you could lead me to the place that will give me the files I need.. the box my phone came in has the model as ASUS_Z00TD (ZE551KL).. Sorry I wasn't of any help to you, hope you manage to figure out how to flash something that will get your device running again!
Click to expand...
Click to collapse
I used @rczrider 's post in this thread, and was able to get root. http://forum.xda-developers.com/zenfone-2-laser/general/wip-root-ze550kl-1-16-40-763-t3275760/page3, good luck!
willrox15 said:
I accidentally tried doing a factory reset, and flashing an incorrect rom. So I lost the stock rom, and have no other rom to use. I tried using TWRP to flash ASUS's stock firmware from asus's support website, under firmware. Using firmware file: "UL-Z00T-WW-1.16.40.763-user.zip"
but TWRP tells me "E:Error executing updater binary in zip '/sdcard/TWRP/Stock.zip'
Error flashing '/sdcard/TWRP/Stock.zip"
I still have access to both adb, fastboot, and TWRP but I cant get an OS to install.
Any help with this would be greatly appreciated, haven't even had this phone a day yet, and already may have broken it.
Click to expand...
Click to collapse
Happy to know that it works for you.
Whenever you got stuck in this situation, just flash stock recovery & you will able to flash stock rom again.
rajlko said:
Happy to know that it works for you.
Whenever you got stuck in this situation, just flash stock recovery & you will able to flash stock rom again.
Click to expand...
Click to collapse
Do yo mean this stock recovery? http://forum.xda-developers.com/showpost.php?p=64441364&postcount=9
How do I flash it? just "fastboot flash recovery stock_recovery.img" ?
If so, I've tried that, and TWRP still boot when I try to enter recovery. Also, once I've flashed the stock recovery, do I just place the firmware on the root of the sdcard as 'update.zip' and try to install it from there?
Thanks for your help already, and sorry about the repetitive questions!
willrox15 said:
Do yo mean this stock recovery? http://forum.xda-developers.com/showpost.php?p=64441364&postcount=9
How do I flash it? just "fastboot flash recovery stock_recovery.img" ?
If so, I've tried that, and TWRP still boot when I try to enter recovery. Also, once I've flashed the stock recovery, do I just place the firmware on the root of the sdcard as 'update.zip' and try to install it from there?
Thanks for your help already, and sorry about the repetitive questions!
Click to expand...
Click to collapse
This is not stock recovery, this one is twrp recovery.
once you flashed stock recovery, flash stock rom as you do it.
This one is stock recovey
http://forum.xda-developers.com/showpost.php?p=64440791&postcount=8
rajlko said:
This is not stock recovery, this one is twrp recovery.
once you flashed stock recovery, flash stock rom as you do it.
This one is stock recovey
http://forum.xda-developers.com/showpost.php?p=64440791&postcount=8
Click to expand...
Click to collapse
Thank you! That worked perfectly!!

WiFI wont work after root

I should start this off by saying that i have no idea how to root a device and i am now currently aware of how stupid my actions were.
I've searched the forums for about 2 hours now and i've yet to find a solution to this problem which is stressing me out like you wouldn't believe.
about i year ago i tried to root my Moto X Pure edition but i failed miserably so i returned to stock and lived without. This morning i decided i would try to root again but it isn't going so well.
I followed this guide: http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380 And everything worked fine until i noticed that my wifi wasn't working.
I then decided to flash back to the original boot image which i found from this site: http://androiding.how/systemless-root-moto-x-style-marshmallow-mph24-49-18/ But my wifi still refuses to turn back on
By now I'm a bit stressed out and not thinking straight. I then recalled that device encryption can screw with the rooting process so i decided to factory reset (how stupid can i get.)
So now im sitting at the welcome screen and my XT1575 cant find a wifi network so im going to have to restore my device over cellular data.
What do i do!?!?!?!?!!?!?
EDIT: i just realized the first link i posted was for the XT1572. I feel so stupid. how do i restore original functionality to my device?
I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms
dj_ooms said:
I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms
Click to expand...
Click to collapse
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)
UC_Nightmare said:
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)
Click to expand...
Click to collapse
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.
UC_Nightmare said:
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.
Click to expand...
Click to collapse
The only app I am aware of without root is Helium. I haven't tried it personally but I think you need to have an app running on your PC and the phone connected to it. I personally use TWRP with Nandroid Manager and Titanium Backup. These both need root though. You could always make a backup through TWRP prior to flashing the pre-rooted ROM, then flash the ROM as always recommended. If you run into issues, just restore the backup through TWRP, then flash the stock recovery back through fastboot/ADB to be backup to your original state.
HTH,
Ooms
dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?
UC_Nightmare said:
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?
Click to expand...
Click to collapse
I think i can answer my own question now. TWRP is a "custom recovery" and after i use TWRP i can flash something over it so that i can be stock. The terminology around these parts is quite confusing
i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?
UC_Nightmare said:
i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?
Click to expand...
Click to collapse
When rooting, there is always a risk. I have been flashing phones for over 10 years and it is always a learning experience. Even now i have occasionally done something and thought I've completely mucked up my phone. You just need to make sure you follow exactly what is stated as the procedure and if you run into problems, there is always someone at hand to help in this great forum.
Out of curiosity, did you follow the standard procedure for installing a new ROM? You will lose all data doing the standard procedure but can restore most stuff from your Nandroid backup. The steps I always do is:
1. Make a backup
2. Wipe data, system, dalvik/art and cache partitions
3. Flash your ROM
4. Wipe dalvik/art and cache again
5. Reboot
Click to expand...
Click to collapse
That is the standard recommended procedure for flashing all ROMs in TWRP. I have an EU XT1572 and have successfully used this ROM on my phone. The ROM contains everything you need including the modem. The modem is for the US XT1575 but worked fine on my phone. For sanities sake, I flashed the EU modem after and still had everything working.
Just another point, your phone needs to have been updated to Marshmallow before you can run one of these ROMs. If you are on Lollipop you may run into issues, especially from a radios perspective.
Another thing to point out is that all ROMs are started that you flash at your own risk. Developers will not be held responsible for anything going wrong. As long as you follow the guides and don't flash a ROM for a completely different device, you shouldn't run into any issues and more often then not can bring your phone back to a functional state if you do.
HTH,
Ooms
Flash twrp
Make backup
Flash su 2.62-3
Done.
Or...
1. Flash the factory image
2. Flash TWRP
3. Flash this attachment in TWRP, which will force install SuperSU 2.78 SR-1 systemless-ly. I've shared and posted about it before in this thread.
Nothing's changed with the attached zip here, except it has the latest version of SuperSU included as of this post.

Cannot get TWRP on Oreo, only on Nougat, phone keeps rebooting.

Hi,
I have a S8+, SM-G955F and I cannot have Android Oreo and TWRP (and then root). I only can have Android 7 and TWRP (and then root).
Current situation is: I have Android Oreo, Build G955FXXU1CRB7 is installed. Once I go to Download Mode and flash TWRP, I can boot into TWRP, but my device is not booting into Android anymore. It starts up, shows me the Samsung logo and reboots, then it shows samsung logo again and reboots.
It reboots and reboot and reboots...If I go to TWRP and make a factory reset or format data, it does not help, it only reboots when trying to start Android.
Even if I restore an older backup of boot, systems partition, it does not work...
So what do I do? I flash original Android Oreo firmware once again via Odin and get it back working, but: I loose TWRP again (and cannot flash SuperSU).
Any idea? I would like to have latest Oreo as well as TWRP recovery
Many thanks!
tobyffm said:
Hi,
I have a S8+, SM-G955F and I cannot have Android Oreo and TWRP (and then root). I only can have Android 7 and TWRP (and then root).
Current situation is: I have Android Oreo, Build G955FXXU1CRB7 is installed. Once I go to Download Mode and flash TWRP, I can boot into TWRP, but my device is not booting into Android anymore. It starts up, shows me the Samsung logo and reboots, then it shows samsung logo again and reboots.
It reboots and reboot and reboots...If I go to TWRP and make a factory reset or format data, it does not help, it only reboots when trying to start Android.
Even if I restore an older backup of boot, systems partition, it does not work...
So what do I do? I flash original Android Oreo firmware once again via Odin and get it back working, but: I loose TWRP again (and cannot flash SuperSU).
Any idea? I would like to have latest Oreo as well as TWRP recovery
Many thanks!
Click to expand...
Click to collapse
Hello, which instructions did you follow to flash again the firmware? ( i assume the firmware was the official )
StonebridgeGr said:
Hello, which instructions did you follow to flash again the firmware? ( i assume the firmware was the official )
Click to expand...
Click to collapse
Yes, it was the official one. Just searched the site, but cannot find it anymore. However, flashing the firmware does not need many steps. DOwnload the zip, extract the .tar files in it, open ODIN, load .tar files into Odin and click flash. Then it was flashed and Android was booting again.
tobyffm said:
Yes, it was the official one. Just searched the site, but cannot find it anymore. However, flashing the firmware does not need many steps. DOwnload the zip, extract the .tar files in it, open ODIN, load .tar files into Odin and click flash. Then it was flashed and Android was booting again.
Click to expand...
Click to collapse
you are right, when you flashed the official firmware, on odin did you select the Home_CSC or the CSC ?
StonebridgeGr said:
you are right, when you flashed the official firmware, on odin did you select the Home_CSC or the CSC ?
Click to expand...
Click to collapse
I think it was the CSC, but as far as I remember, I also tried the HOME_CSC in the past (not today) but the behaviour was also the same.
As far as I know difference is that with one of these files internal storage is wiped, with the other one it isn't, correct?
But what could this have to do that I get a restart-loop when flashing TWRP? I dont have a problem to flash original firmware, it works. But once I flash TWRP I cannot start Android anymore and have to reflash Android firmware again.
tobyffm said:
I think it was the CSC, but as far as I remember, I also tried the HOME_CSC in the past (not today) but the behaviour was also the same.
As far as I know difference is that with one of these files internal storage is wiped, with the other one it isn't, correct?
But what could this have to do that I get a restart-loop when flashing TWRP? I dont have a problem to flash original firmware, it works. But once I flash TWRP I cannot start Android anymore and have to reflash Android firmware again.
Click to expand...
Click to collapse
which guide did you follow to flash TWRP?
also yes the CSC not the HOME CSC wipes the internal storage
StonebridgeGr said:
which guide did you follow to flash TWRP?
also yes the CSC not the HOME CSC wipes the internal storage
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But also not much to follow...Download correct TWRP for S8+, load into Odin and click flash. TWRP is correct version and it works for me. But at same time, phone is not booting into Android anymore. This is why I end in reflashing original Android firmware again. I am in a loop :silly:
tobyffm said:
I followed this guide: https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But also not much to follow...Download correct TWRP for S8+, load into Odin and click flash. TWRP is correct version and it works for me. But at same time, phone is not booting into Android anymore. This is why I end in reflashing original Android firmware again. I am in a loop :silly:
Click to expand...
Click to collapse
Dude thats guide to flash and root S8 not S8+.. thats why you get bootloop, make sure to follow the correct guide next time
Here is the best guide i found for you https://www.androidinfotech.com/2018/02/root-samsung-galaxy-s8-plus-sm-g955f-oreo.html
StonebridgeGr said:
Dude thats guide to flash and root S8 not S8+.. thats why you get bootloop, make sure to follow the correct guide next time
Here is the best guide i found for you https://droidfeats.com/root-galaxy-s8-plus-variants-android-8-0-oreo-cf-auto-root/
Click to expand...
Click to collapse
thanks, but I dont think so.
From the thread I mentioned, yes, I can download TWRP for S8, not S8+, but I went to TWRP site and downloaded correct TWRP for my device. Loading into odin and flash is the same, doesnt matter which device I have.
CF Autoroot does not work for me as it is not available for Oreo firmware. I checked all this previously, I am not a that stupid guy :laugh:
tobyffm said:
thanks, but I dont think so.
From the thread I mentioned, yes, I can download TWRP for S8, not S8+, but I went to TWRP site and downloaded correct TWRP for my device. Loading into odin and flash is the same, doesnt matter which device I have.
CF Autoroot does not work for me as it is not available for Oreo firmware. I checked all this previously, I am not a that stupid guy :laugh:
Click to expand...
Click to collapse
then follow this guide, i am sure you did a wrong on the instructions, follow then without stress and do not rush . I never said you a stupid guy
https://androidjungles.com/root-samsung-galaxy-s8-plus-install-twrp-recovery-android-oreo-sm-g955f/
Download this TWRP image for your S8PLUS(twrp-3.2.1-0-dream2lte.img.tar 38.2M 2017-12-09 03:01:59 ES)
https://dl.twrp.me/dream2lte/
StonebridgeGr said:
then follow this guide, i am sure you did a wrong on the instructions, follow then without stress and do not rush . I never said you a stupid guy
https://androidjungles.com/root-samsung-galaxy-s8-plus-install-twrp-recovery-android-oreo-sm-g955f/
Download this TWRP image for your S8PLUS(twrp-3.2.1-0-dream2lte.img.tar 38.2M 2017-12-09 03:01:59 ES)
https://dl.twrp.me/dream2lte/
Click to expand...
Click to collapse
I used exactly that TWRP version today.
The only difference between my steps and the steps mentioned in your mentioned guide is that they use an older Odin version. But I already used different Odin version too
Ok, aynway, I will try it again with this guide tomorrow and will let you know about the result tomorrow. Thx so far
tobyffm said:
I used exactly that TWRP version today.
The only difference between my steps and the steps mentioned in your mentioned guide is that they use an older Odin version. But I already used different Odin version too
Ok, aynway, I will try it again with this guide tomorrow and will let you know about the result tomorrow. Thx so far
Click to expand...
Click to collapse
alright i will be waiting for you reply to my post here !!
StonebridgeGr said:
alright i will be waiting for you reply to my post here !!
Click to expand...
Click to collapse
Hi again,
I got an OTA Update this morning, so current build on phone was G955FXXU1CRC7.
I now downloaded the TWRP file you mentioned and followed the guide you mentioned.
TWRP was installed using latest Odin Version 3.13, then I tried to install SuperSU, but this failed, red error messages like failed to mount /data, unable to mount storage.
same for factory reset, does not work. I formated data, it worked. then I installed Super Su, it was possible. then I rebooted device and what shall I say, it booted into Android
Dont know what I did different now, maybe not trying to boot up Android before installing supersu.zip?
However, Now I have latest Oreo with TWRP and phone is rooted
Now I will go on and install xposed framework :good:
Many thanks for your help.
tobyffm said:
Hi again,
I got an OTA Update this morning, so current build on phone was G955FXXU1CRC7.
I now downloaded the TWRP file you mentioned and followed the guide you mentioned.
TWRP was installed using latest Odin Version 3.13, then I tried to install SuperSU, but this failed, red error messages like failed to mount /data, unable to mount storage.
same for factory reset, does not work. I formated data, it worked. then I installed Super Su, it was possible. then I rebooted device and what shall I say, it booted into Android
Dont know what I did different now, maybe not trying to boot up Android before installing supersu.zip?
However, Now I have latest Oreo with TWRP and phone is rooted
Now I will go on and install xposed framework :good:
Many thanks for your help.
Click to expand...
Click to collapse
Update: Just tried to flöash xposed framework via TWRP but it fails because of unable to mount data. Do you know why this appears?
tobyffm said:
Update: Just tried to flöash xposed framework via TWRP but it fails because of unable to mount data. Do you know why this appears?
Click to expand...
Click to collapse
Hello dude, u are gonna need to flash dm-verity 5.1 find it on google , flash it and then flash immediately flash Xposed , if the error appear again then format data, and there is a option to wipe cache and Data, wipe them too, flash dm-verity and flash immediately the Xposed, if I helped you please press thanks buttons
StonebridgeGr said:
Hello dude, u are gonna need to flash dm-verity 5.1 find it on google , flash it and then flash immediately flash Xposed , if the error appear again then format data, and there is a option to wipe cache and Data, wipe them too, flash dm-verity and flash immediately the Xposed, if I helped you please press thanks buttons
Click to expand...
Click to collapse
Hi,
I had to format data, then I wiped Cache and Data again. Tehn, I flashed dm-verity, directly after that SuperSU again and directly aafter this I flashed xposed.
Finally, all works
Many thanks for your kind help!
tobyffm said:
Hi,
I had to format data, then I wiped Cache and Data again. Tehn, I flashed dm-verity, directly after that SuperSU again and directly aafter this I flashed xposed.
Finally, all works
Many thanks for your kind help!
Click to expand...
Click to collapse
I told you you were missing something with the instructions, I am happy now everything is fine

Categories

Resources