Related
Hey Guys,
I just rooted my i9505 via CF-Auto-Root and it worked like a charm. The next thing I did was to flash Philz Recovery, at first it auto reboot and it never went into recovery, so I followed the steps to re-flash it without the auto reboot and force it into recover. It loaded into Philz Recovery perfectly fine, now when I reboot, it gave me the option to disable auto flash recovery, so I selected yes.
After that I was never able to get into Recovery Mode ever again. All it does is says Recovery Booting in the top left corner and then restarts and loads into the OS. I followed the steps again to re-flash Philz with auto reboot unchecked and it still failed to get into recover. I then tried CWM and TWRP (via Odin), but all of these gave me the same problem and failed to get into recover.
I then tried SGS4 Flasher but still the same question.
Anyone here who has this problem before and know the fix or is able to recommend another method?
Was able to fix it. Had to flash the original stock Recovery back on and then re-flash a custom recovery. Not sure what happen but was able to install TWRP on without an issue, maybe something in Philz Recovery that stuffed it up.
OK! Looks like it is not working correctly. For me to get access to a custom recovery, I have to flash the stock recovery via Odin and then flash a custom recovery to get it working EVERYTIME. It will boot into Philz, CWM and TWRP only once, then you need to flash stock recovery and do the process all over again.
So it looks like the recovery gets over written each time even if you select "yes - disable flash recovery" in Philz Recovery. Anyone know of another way to disable flash recovery?
Z-Blade said:
OK! Looks like it is not working correctly. For me to get access to a custom recovery, I have to flash the stock recovery via Odin and then flash a custom recovery to get it working EVERYTIME. It will boot into Philz, CWM and TWRP only once, then you need to flash stock recovery and do the process all over again.
So it looks like the recovery gets over written each time even if you select "yes - disable flash recovery" in Philz Recovery. Anyone know of another way to disable flash recovery?
Click to expand...
Click to collapse
with a root explorer, go to system/recovery-from-boot.p and rename it to recovery-from-boot.p.bak
samersh72 said:
with a root explorer, go to system/recovery-from-boot.p and rename it to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Thanks for responding samersh. To lessen the pain of constantly flashing the recovery via Odin on my PC, I bought Mobile Odin Pro. However, it looks like when I flashed using Mobile Odin Pro, it fixed my issue.
I checked \System\ and there was no recovery-from-boot.p there. So it is confirmation that this has been fixed. Thanks again for responding.
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
common issue at this point. It appears recovery isnt sticking for some reason.
kokotron said:
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
Click to expand...
Click to collapse
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Click to expand...
Click to collapse
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
kokotron said:
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
A solution for auto swpan defualt recovery, the file is there only rename it
DJBhardwaj said:
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
Click to expand...
Click to collapse
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
Just Install a Custom Kernel with modified ramdisk. Install Hellscore kernel and then install SuperSU. You will be able to experience Root.
I think unleashed kernel has also been updated with the same, but I can only confirm it with Hellscore.
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
kokotron said:
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
Click to expand...
Click to collapse
It is weird. I am pretty much sure you're either missing something or using a corrupted img file. Confirm that the file has been downloaded completely by verifying the md5 checksum and I am sure it will mismatch
hp420 said:
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
Click to expand...
Click to collapse
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
kokotron said:
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
Click to expand...
Click to collapse
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
Ok thank you, this seems to have worked. When I booted back into Android though root didn't work any more. I re-rooted using your link (which was what I used the first time as well), and I guess I'll know how it goes the next time I reboot the phone.
hp420 said:
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
Click to expand...
Click to collapse
Not the boot loader because I have the new bootloader that came with L and TWRP working perfectly, so both can coexist.
The problem comes from within the rom as I said, the file is in /system/etc/install-recovery.sh is responsible to clear the custom recovery and return to default android recovery. The solution is to remove (or rename) that file, what I saw is that the TWRP and SuperSU (both try to) can not rename it, and the solution was to rename it manually from the file manager included in the TWRP (mounting /system as explained before).
The same problem to can not overwrite files (should be modified in any command in library ) prevents install from a flashable zip SuperSU, so the solution http://forum.xda-developers.com/nexu...- root-t2025274 initiating its own operating system booting own image solves the problem that can not be overwritten (or modified) files from the TWRP (at least until a specified version for L see the light).
Probably whoever the new bootloader prevents TWRP modify files in /system, but bootloader not erases the custom recovery. Surely people of TWRP is working to fix this issue (or sleeping sometimes you have to sleep) but the problem can be solved by keeping the new booloader.
Conclucion, I have stock L Last bootloader, root and TWRP everything working perfectly and hellsCore Kernel
sidVici0us said:
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
you installed via the SuperSU binaries from flashable zip in TWRP or use the method http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274 ?
With the CF-auto-root you should have no problems, I did so and I read that many people do so, use this method to root.
On the other hand, I was thinking that having a recovery that can not flash zip is not something useful
---------- Post added at 03:16 PM ---------- Previous post was at 02:52 PM ----------
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
You can not use the superSU flasheable zip, the recovery is not working to modify /system partition, use the other method.
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
CF autoroot works perfectly!! http://www.xda-developers.com/android/chainfire-releases-cf-auto-roots-for-nexus-line/
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
android_101_ said:
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
Click to expand...
Click to collapse
I only have the Twrp recovery.
Canukboy said:
I only have the Twrp recovery.
Click to expand...
Click to collapse
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
wang1chung said:
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
Click to expand...
Click to collapse
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Canukboy said:
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Click to expand...
Click to collapse
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Click to expand...
Click to collapse
Hy Wang.. I followed your guide - modified updater-script, but I can't install the stock rom .zip from TWRP.
It says "can't extract updater-binary", I tried few times thinking that the file is corrupt, but the result still same.
FYI, I use stock ROM "UL-ASUS_Z012D-WW-14.2020.1709.68-user.zip", and TWRP 3.1.1.
Please help me if you have experienced it before. Thanks
@rzahunn
I've never had that error before and you're on the latest version of TWRP so I'm going to guess it has to do with your modification of the updater script.
You edited updater-script not updater-binary, correct? There are two files with similar names
There's a detailed guide by @kyle_l88 on how to return to stock.
Here's the link: https://forum.xda-developers.com/zenfone-3/development/how-to-to-stock-rom-recovery-zenfone-3-t3666223
Do note that the original recovery link is dead. The updated link is: https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA
TWRP Bootloop
Sorry if my reply is irrelevant, but I need some helps.
I am also using Zenfone 3, but stuck in TWRP bootloop.
I cannot flash using fastboot (not detected on PC), reflashing ROM doesn't help either.
I've tried all the possible methods I found on Google, such as dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota method but still has no luck.
Restoring backup would end me in TWRP too.
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
wang1chung said:
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
Click to expand...
Click to collapse
I've managed to fix the bootloop after following the guide. I missed that somehow, thanks for pointing that to me.
I've thanked you (pressed the Thanks button).
dm verity
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
does it hangs on logo then start again? then reflashing the rom then flashing the dm verity zip again hope it works
Hello,
I dont get it done to reset my x527 to stock conditions.
I downloaded the 5.8.19S.zip and tried to flash it via TWRP. TWRP gives me Error 7 and "This zip is for Device 'le_s2_ww', your device is 'le_s2'"
I figured out that the stock ROM isnt flashable through TWRP, ok.
I wanted to also flash back the Recovery to stock. I downloaded the x526 Recovery to flash it via ADB/Fastboot.
ADB is working, Im able to start my x527 into bootloader. But from here the Commandline says "No devices" (fastboot devices), but the device is shown 'Fastboot Mode' on Display.
But the most important thing: Where I can download the original Stock Rom for my x527? All Links I found myself are for other x52? Devices, or seems suspicious.
Thank you for your help!
I got I worked to transfer the Stock Recovery and flashed it without problems.
Then I tried to flash the 5.8.19S.zip again with original Recovery. Now it seems to work. No Errors were displayed.
But know the device isnt booting. It onlyshows the LeEco Splashscreen for a couple of Minutes for now.
How do I transfer Data between PC and x527? Only Fastboot is working for now.
Ok I found a solution by myself:
- Put Device in Fastboot Mode (Power + Vol down)
- On PC start the command "fastboot boot <TWRP.img> (e.g. "fastboot boot recovery.img")
- Now you have a live TWRP and you are able to Sideload, Install, Wipe etc pp.
Now Im with RemixOS again.
To flash stock rom use the Chinese recovery! And after flash it will ask you to restore to stock recovery or not!
Or u can do it another way!
Rename the stock eui file by update.zip
Open any twrp recovery u have
Perform a factory reset and clean!
Copy the update.zip to phone
Goto fastboot mode
Flash stock recovery
Now the stock recovery will detect update.zip and will load the whole clean rom its a long process though u can give it a try in future!
Drooes said:
To flash stock rom use the Chinese recovery! And after flash it will ask you to restore to stock recovery or not!
Or u can do it another way!
Rename the stock eui file by update.zip
Open any twrp recovery u have
Perform a factory reset and clean!
Copy the update.zip to phone
Goto fastboot mode
Flash stock recovery
Now the stock recovery will detect update.zip and will load the whole clean rom its a long process though u can give it a try in future!
Click to expand...
Click to collapse
As you tell do factory reset and clean, what things should be cleaned to do it the cleanest way?
(And how do I just flash the recovery of the update.zip, will I be asked if I swipe to confirm flash of the update.zip? I am afraid it will already start a complete flash than.) Forget that
I just misunderstood the part of your description as I would have to go to fastboot, I think you just have to stay as you are already there all the time... or not?
FridrufHau said:
As you tell do factory reset and clean, what things should be cleaned to do it the cleanest way?
(And how do I just flash the recovery of the update.zip, will I be asked if I swipe to confirm flash of the update.zip? I am afraid it will already start a complete flash than.) Forget that
I just misunderstood the part of your description as I would have to go to fastboot, I think you just have to stay as you are already there all the time... or not?
Click to expand...
Click to collapse
Forget everything i just got a better way!
Goto fastboot n install chinese recovery available!
Open recovery then goto wipe and do a factory reset!
Then transfer the stock rom file! And flash it!
After the flash you will be asked to replace the recovery! If you want to replace it with stock then swipe to confirm!
Your stock os n recovery will be installed!
Just be patient it will take sometime on boot! N yes if it says some error like encryption n thing just don't get panic! The device will automatically restart in stock recovery and there you will get 2 option!
1st one is to update package via .zip
2nd is to clear data!
Since sometime it is shown in Chinese then just select the 2nd option and it will clear all the things and then will restart the device and will boot into clean stock rom!
Hey I think I will try it this way ...
https://forum.xda-developers.com/le-2/how-to/guide-how-to-flash-stock-rom-using-twrp-t3536122/post73219991#post73219991
Because I just want back 19s modem/firmware, which isn't working with the standalone files amd go back to los13 then.
So with their way I wouldn't have to change the recovery to chinese, to stock and back I guess.
Thx anyway