Im stuck with CM 10.2, cant revert to stock 4.4. - Nexus 4 Q&A, Help & Troubleshooting

Hi, like a month ago I Installed 10.2 CM but now I want to go back to stock 4.4 but everytime I try to do smoething, I encounter another problem.
I found a 4.4 stock ROM so I thought I will just install it, Wipe date and cache, and then just flash the rom, But It didnt work for some reason. I thought the problem was my outdated TWRP so I tried to install the latest TWRP but then I understood that I formated my computer so the fastboot drivers are not installed, so I tried to install them, but no matter what I do, It just doesn't work. I dont really know what to do so If someone can tell me stage by stage what should I do to revert back to stock, I'd be happy to hear because I Dont really know
Thanks!

Related

[Q] Stuck on bootlogo after flashing custom rom

I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...

A nightmare for my lovely nexus 7

After installing kitkat ~1 month ago my tablet was fast. But then a week before it started being slow as hell, so i finally decided to install a custom rom. I installed revolt but the home button didnt work. Then i tried installing PA3.99 but in the recovery menu it said failed. I tried a couple of other roms but they also failed(all 4.3 roms). Then i thought it was because of 4.4 and installed factory 4.3 by using the bat inside the image. It formats userdata. Everything gone(but i got a backup of apps so it doesn't matter too much). Tried installing a few roms. Again mistakes. Then finally installed stock 4.4 rom and everything works. My question is why is this happening? (my recovery is twrp 2.6.3.1) I want to install other roms
P.S. has anyone else had these kinds of problems?

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

[SOLVED] What recovery should I use with CM 10?

I got bored today and decided to pull out the old N7, 2012 version. I update recovery to TWRP 2.8.7.0, installed CM 12.1, realized this tablet crawls with any version of Android other than shipped version, so I went and got CM 10 and GApps for JB, wiped and flashed them back on. I didn't see any errors when flashing them, but when rebooting after, it just boot loops. I see the Google logo with the unlocked icon at bottom, then reboot and back to Google/unlocked again. So I wipe and reflash cm12.1 and it's GApps and all boots and works fine, other than being slow. I'm assuming the recovery is the problem as I've run into something similar before on another device, but in that case, the recovery was too old and needed updated, but it makes sense that a recovery could be too new as well.
Am I correct that the recovery is the problem? If so, what should I run for CM 10 to flash and work?
Try cwm recovery
iwjosi said:
Try cwm recovery
Click to expand...
Click to collapse
I don't' know if it was using CWM or that I also tried CM 10.2 at the same time, but it's working now. On CyanogenMod's own page, there was no MD5 for CM10, but there was for CM10.2, so it's possible my copy of CM10 was a bad download. Either way, it's working now, so thank you good sir, or madam, or person on no specific gender.

How can I revert to factory state in my Leeco Le s3 (x522 US variant)

Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!
Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?
Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?

Categories

Resources