Related
HI all,
My nexus 4 just won't boot no matter how i flash any 4.3 version on it.
Tried google's factory image's bat file, efrant's guide, fota, ota file and some custom roms.
Tried each with wiping cache followed by factory settings.
I'm really lost, how could it be?
At which point does it stop?
bootloop, x screen.
You tried using the factory images from google's website? I had to wipe mine recently and flash the bootloader, reset fastboot, flash radio, reset bootloader, and then flash zip with the Boot/System/UserData/Etc in it and then once it was complete booted up fine. Might want to give it another shot, but don't forget to reboot the bootloader between flashes. It does help.
MisterRich said:
You tried using the factory images from google's website? I had to wipe mine recently and flash the bootloader, reset fastboot, flash radio, reset bootloader, and then flash zip with the Boot/System/UserData/Etc in it and then once it was complete booted up fine. Might want to give it another shot, but don't forget to reboot the bootloader between flashes. It does help.
Click to expand...
Click to collapse
I got stuck on this. I was really worried that I'd have to leave my brand new N4.
I ended up flashing Google's stock 4.2.2 images for everything, relocking bootloader then unlocking it. Then at that point, when you are in fastboot make sure you click start. It'll then show the android with a progress bar, just wait from there and it'll boot. I'm sure Google will fix these issues with 4.3.1
In this thread I got a great answer about how to fix a sizing problem with the data partition on my Razr M. You'll need this if you are running CMod, are encrypting, reformat your data partition with TWRP, and want to re-encrypt after the reformat.
There is only one silly problem. I am running CM 10.1, which is 4.2.2. I am also running TWRP 2.6. I can change versions of TWRP as easy as anything, but I cannot for the life of me figure out how to return to stock recovery. I really do not want to RSD, since Motorola has been working on how to relock the bootloader, and I don't want to give them that chance. And, of course, if I do RSD back to 4.2.2 stock, I'll have no way to get root back.
What I'd love to do is just to get the 4.2.2 stock recovery image, and flash it with fastboot. But I cannot for the life of me find the 4.2.2 stock recovery image. I have Matt's 4.1.2 stock recovery image, and I actually tried it with his utility, but...yeah. Android with exclamation point. It did not end well.
So, here's the question: is there any way to flash the 4.2.2 stock recovery without RSDing back to stock? Where is that darn disc image?
Thanks!
Brokkn said:
In this thread I got a great answer about how to fix a sizing problem with the data partition on my Razr M. You'll need this if you are running CMod, are encrypting, reformat your data partition with TWRP, and want to re-encrypt after the reformat.
There is only one silly problem. I am running CM 10.1, which is 4.2.2. I am also running TWRP 2.6. I can change versions of TWRP as easy as anything, but I cannot for the life of me figure out how to return to stock recovery. I really do not want to RSD, since Motorola has been working on how to relock the bootloader, and I don't want to give them that chance. And, of course, if I do RSD back to 4.2.2 stock, I'll have no way to get root back.
What I'd love to do is just to get the 4.2.2 stock recovery image, and flash it with fastboot. But I cannot for the life of me find the 4.2.2 stock recovery image. I have Matt's 4.1.2 stock recovery image, and I actually tried it with his utility, but...yeah. Android with exclamation point. It did not end well.
So, here's the question: is there any way to flash the 4.2.2 stock recovery without RSDing back to stock? Where is that darn disc image?
Thanks!
Click to expand...
Click to collapse
In my goodies. Stock recov & a prerooted restore method!
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Brokkn said:
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Click to expand...
Click to collapse
Normally when you boot into stock recovery , you wont be presented with a nice menu. It's almost a hidden menu that you have to pull up...
When you go in and get the Triangle or whatever is there, you will have to press volume + and - and power button to get the menu to display.
Try a few combinations, volume + and - then power, or power then + and -, or all three at the same time. Eventually it will come up.
Brokkn said:
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Click to expand...
Click to collapse
I was going to offer the xt897 stock recovery. It glides into action & has apply from cache. In goodies also.
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
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
So far there's only a small sample, but I think there's enough of a pattern to constitute an issue. I've tried to flash the latest of both pixel experience (unofficial) and havoc, and each one sends me directly to either recovery or fastboot, depending on the order which I flash/wipe/factory reset. It's been a couple months since I've flashed anything other than an open beta update, but I never had any issues flashing ROMs.
For both I've tried:
Flash OOS. 9.0.13 (or OB13) in both slots
Flashed Twrp installer
Reboot to recovery
Flash custom ROM
Flash Twrp installer
Factory reset (tried full wipe as well)
It's at this point where I attempt to reboot to recovery to flash gapps (for havoc, not PE) I get sent to recovery or fastboot, depending on whether I reset or wipe data.
I can flash OOS and boot stable or open beta and boot into them with no problems. I've even allowed it to boot to the OOS welcome screen and went back to recovery to flash the custom ROM with the same outcome, doing a factory reset before I flash, after I flash, reboot to recover after flashing to factory reset. I've tried a full wipe in place of factory reset and all different combinations, all with the same result...
What am I missing?
lordcheeto03 said:
What am I missing?
Click to expand...
Click to collapse
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
pbergonzi said:
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
Click to expand...
Click to collapse
Everywhere I've read says to flash OOS to both partitions so if there's an issue with the custom ROM there's a fallback.. I don't flash the custom ROM to both partitions, only OOS. Also, I've tried letting OOS boot to the welcome screen, then back to recovery; I didn't do any setup.
I have magisk installed in OOS, though I haven't tried flashing it when flashing the ROMs. When flashing ROMs I've always flashed the ROM and Twrp, reboot straight to recovery, and flash gapps/Magisk. In my experience, I've been able to skip rebooting back to recovery to flash Magisk and gapps and just boot straight to the barebones ROM.
To reiterate, I use the exact same process to flash OOS and it works flawlessly; can flash the stable or open beta, no issues. It's only non-OOS that refuses to work correctly.
I'm wondering if I need to use the unbrick tool and start from a 100% clean slate .. something may be borked that an unbrick may fix, it's about the only option left that I can think of...
lordcheeto03 said:
Everywhere I've read
Click to expand...
Click to collapse
Good luck whatever you do.
pbergonzi said:
Good luck whatever you do.
Click to expand...
Click to collapse
Thank you for the ideas
I ran the unbrick tool and still encountered the issues, but I did learn something, and also finally got havoc to boot, although I'm still unsure exactly what I did. I'm not saying I figured out exactly what is wrong, and I can't say I know the exact solution, but I CAN say I believe the solution lies somewhere within this wall I'm typing.,..
I noticed this earlier but it didn't actually click until I still got the same error after the unbrick tool... I would always boot correctly to OOS on slot b, so after every successful boot, I'd go into recovery and try flashing.. now taking into account the fact that I flashed OOS in both slots is important because on a successful boot, which would be slot b, I'd go into recovery, still on slot b, so that's the first slot to get OOS. Change slots, flash to slot a, then boot to OOS. If I'm remembering how a/b partitions go, since slot A was the last slot to flash, it would automatically fall back to slot b to boot. Hence the successful boot. Go back to recovery, flash havoc on b, it would attempt to boot from a, and fail.. go back to recovery, I'm back on slot b to start the process over.
After still encountering the problem after the unbrick, I really began paying attention to the boot slots. Once I was paying attention to that, I attempted to manually boot from slot a after flashing OOS to both slots and I got sent to a screen that says Qualcomm crashdump mode. Power +vol up/dn to force a reboot, then volume down until the bootloader unlocked splash screen to go to recovery.
Now this is what I think I did... After figuring out it was the slot, I believe I formatted slot a, and due to the way it fell, slot b then began being the slot to mess up so i made sure to flash havoc/twrp installer in the slot a and it booted right up. Went back to recovery to flash magisk and gapps, and finally a factory reset. Boot from slot a, and here I am.
There were times where I would get stuck in fastboot, boot to recovery or system would just send me to fastboot.. I guess that also meant I was booting from the bad slot. I tried fastboot boot twrp.img, it would send it, but fail to authenticate. Fixed that by doing fastboot --set-active=b then I could restart back to recovery no problem.