Related
Hi Guys,
So I'd rooted the Nexus 4 by unlocking the bootloader and flashing the rooted kernel. I didn't flash a custom ROM after that. So what I had was a 4.2.2 Stock ROM with a rooted kernel so I could use the root functions. Now I get a system update notification after it downloads the new stock 4.3 on its own on my phone. But now since I don't have the stock recovery, selecting " Reboot and install update" after the system update downloads just leads me to the CWM recovery and obviously I don't have a custom update.zip to flash.
So my question is..How do I flash back the stock recovery and hence lose root and update to 4.3 without flashing the STOCK ROM back, thereby keeping my existing apps on 4.2.2. intact? So what I wanna do is flash the stock kernel which restores the stock recovery...Let the stock system update itself to 4.3 and then maybe Root the phone again..
Could someone kindly direct me to a solution?
Would appreciate a quick response
Cheers!
There's no way to restore to stock without wiping everything
Sent from my SGP311
https://developers.google.com/android/nexus/images
Download the factory images, you can find stock recovery inside. Flash the recovery.img in bootloader mode.
Code:
fastboot flash recovery recovery.img
Kernel and recovery is 2 separated partition in Nexus 4, so flashing kernel won't restore your recovery.
So I was trying to flash this rom (Originally from stock 4.2.2)
http://forum.xda-developers.com/showthread.php?t=2761322
As I was trying to flash it with RSD lite, the flashed failed. All i got was the splash screen and nothing else. I then downloaded the stock firmware and it failed as well. However, I can still get into the bootloader and my custom recovery TWRP. I have no idea what to do and i'm scared. Is there any way to safely flash my phone back to stock?
ozeyguy said:
So I was trying to flash this rom (Originally from stock 4.2.2)
http://forum.xda-developers.com/showthread.php?t=2761322
As I was trying to flash it with RSD lite, the flashed failed. All i got was the splash screen and nothing else. I then downloaded the stock firmware and it failed as well. However, I can still get into the bootloader and my custom recovery TWRP. I have no idea what to do and i'm scared. Is there any way to safely flash my phone back to stock?
Click to expand...
Click to collapse
If you read the OP from that post, you needed to be on 4.4.2 stock. Get the fxz for the stock KK and flash to it and then flash GPE.
Sent from my RAZR M xt907 (KitStalk) using Tapatalk
xKroniK13x said:
If you read the OP from that post, you needed to be on 4.4.2 stock. Get the fxz for the stock KK and flash to it and then flash GPE.
Sent from my RAZR M xt907 (KitStalk) using Tapatalk
Click to expand...
Click to collapse
The phone was already on 4.4.2 stock, along with a custom recovery (which was later removed in the process) and an unlocked bootloader. Each time I try to flash the original firmware, RSD lite will give me a sign that tells me that it failed. However, I think downgading RSD to 6.1.4 could have been the solution. When I tried to flash the GPE rom, it actually worked. But i'm having problems with the cellular data and wifi (wont turn on).
ozeyguy said:
The phone was already on 4.4.2 stock, along with a custom recovery (which was later removed in the process) and an unlocked bootloader. Each time I try to flash the original firmware, RSD lite will give me a sign that tells me that it failed. However, I think downgading RSD to 6.1.4 could have been the solution. When I tried to flash the GPE rom, it actually worked. But i'm having problems with the cellular data and wifi (wont turn on).
Click to expand...
Click to collapse
Did you flash to 4.4.2 stock before the new GPE flash? It does not flash the entire system, only the modified files, so it relies on many components being installed, probably including the radio
xKroniK13x said:
Did you flash to 4.4.2 stock before the new GPE flash? It does not flash the entire system, only the modified files, so it relies on many components being installed, probably including the radio
Click to expand...
Click to collapse
Haven't tried that yet. But since i'm on stock now, I might give it a go. I successfully restored my device by downgrading RSD to 6.1.4 and following the directions in this site.
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
FIRST THING FIRST, THIS IS DANGEROUS. DO IT AT YOUR OWN RISK.
Myself and one other person have successfully done this. If you have success as well, please post here. What you DO NOT want to flash, and is the cause of bricks is motoboot.img that is older than what you have now. Just dont mess with it.
What you can do, is flash gpt.bin to get the partition tables re-partitioned to get you back to be able to flash roms from CWM, TWRP, Philz, etc.
That being said, this is my PERSONAL experience, and am only sharing because it got me out of GPE lollipop hell, and I was terrified of the bricks, like everyone else. I will attempt to be more clear in my OP.
I have an XT1034 that I converted to GPE to flash 5.0 Lollipop OTA and it gave me the new bootloader 41.18. I couldnt get to CM12 due to Status 7, and I could only flash 4.4.4 stock, lollipop stock, or CM11, any flashing to CM12 always gave errors about Status 7. Others have reported not being able to wipe /data or /system or mount either in any recovery. The problem is the updated partition table and here is the solution:
IF YOU DO NOT FOLLOW THIS DIRECTION YOU WILL HARD BRICK. DO NOT RUN THE BATCH FILE IN THE DOWNLOAD. IT CONTAINS 4.4.2 motoboot.img and YOU WILL BRICK. ONLY RUN THE COMMANDS LISTED BELOW!!!
ALSO DO NOT use an older gpt.bin, it must be 4.4.2 or newer!! Use the link below to get a 4.4.2 XT1034 stock rom.)
I flashed a 4.4.2 GPT.bin from this: US_retail_XT1034_KXB20.9-1.8-1.4_CFC.xml.zip (http://motofirmware.com/files/getdow...-14-cfcxmlzip/)
If you want to try the same thing, you can extract gpt.bin from the zip and run this: (ONLY!!)
Code:
fastboot flash partition gpt.bin
then download philz here: http://fs1.d-h.st/download/00145/DEw...8.7-falcon.img
rename to philz.img
fastboot flash recovery philz.img
Hold vol - and power, to reboot into recovery, then
format /system
format /data
Download the latest nightlies and gapps and push them like this:
adb push cm-10-10-1000.zip /data/media/0
Reboot into recovery, and flash cm12 and gapps.
Marcus Lemonis!
I thought it had been established flashing the KitKat Partiton Table (gpt.bin) was the cause of downgrade hard-bricking.
It would appear the 4.4.4 Partition Table is specifically the cause.
People have been hard-bricking (now have to wait for full firmware images to fix) - because they flashed the 4.4.2 image and then applied the 4.4.4 OTA Update.
Perhaps you should mention that in OP.
I don't think a gpt.bin "4.4.2 or newer" is wise advice. Please correct me if I'm wrong.
lost101 said:
I thought it had been established flashing the KitKat Partiton Table (gpt.bin) was the cause of downgrade hard-bricking.
It would appear the 4.4.4 Partition Table is specifically the cause.
People have been hard-bricking (now have to wait for full firmware images to fix) - because they flashed the 4.4.2 image and then applied the 4.4.4 OTA Update.
Perhaps you should mention that in OP.
I don't think a gpt.bin "4.4.2 or newer" is wise advice. Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is possible to flash 4.4.4 gpt bin, bit it's not possible to OTA update to 4.4.4 from 4.4.2.
andogeek10 said:
It is possible to flash 4.4.4 gpt bin, bit it's not possible to OTA update to 4.4.4 from 4.4.2.
Click to expand...
Click to collapse
Exactly.
It's the same if you want come back from GPe to Retail Motorola STOCK, you need change GPe-partitions to Motorola-Partitions. There are some differents between both partitions:
GPE
Code:
'cache' -> 560,00 Mb
'system' -> 840,00 Mb
Motorola
Code:
'cache' -> 662,13 Mb
'system' -> 976,00 Mb
There is a partition with 2,28 Mb: In GPe is called 'metadata'; and in Motorola is Called 'padA'.
And there is a partition en GPE with 6,13 Mb called 'padC', but in Motorola didn't exists.
Any way, if you downgrade from LP, you don't must flash BL (motoboot.img), or you'll have a pretty brick.
updated op, I shouldnt have tried to walk anyone through that last night, i couldnt even understand my own english, apologies.
I just don't understand why peoples push 4.4.2 into phones when there is "safer" 4.4.4 that works perfectly and you must be retarded to brick phone when flashing 4.4.4 and doing anything after it. I will say for sure that 80% of hard bricks are caused by 4.4.2 android and updating to 4.4.4(which makes no sense at all) or doing anything after 4.4.2. Just. Stop. Doing. That.
Flash everything from last KITKAT except motoboot and everything will be fine.
how can I know my current bootloader version ?
P.s : ok sorry got it... it is in the bootloader mode (41.13)
http://forum.xda-developers.com/showthread.php?t=3002572
Tell me where to find the 4.4.4 stock xt1034 and I'll link it. My process works. No bricks. Sbf.droid developers is down, send me the 4.4.4 and I'll link it. It is not 4.4.2 causing bricks, it is 4.3!
Sent from my Moto G using XDA Free mobile app
The link is not able to be verified where that gpt.bin came from, that's why I linked the whole stock ROM and not just gpt.bin
Again, try it if you like, and if you don't, don't!
Sent from my Moto G using XDA Free mobile app
I am not suggesting that people flash the whole way back to 4. 4.2. I'm only saying that people need to flash the partition tables from 4.4.2 so then you can install recovery and move on to CM. Re read the op I tell you NOT to flash that rom, but to only update gpt.bin
Sent from my Moto G using XDA Free mobile app
Xt1032?
Do you think this will work for an XT1032 converted to GPE? I have been unable to flash any sort of custom recovery as of yet like it keeps on disappearing when I reboot the device and becoming stock recovery.
Fuchsie said:
Do you think this will work for an XT1032 converted to GPE? I have been unable to flash any sort of custom recovery as of yet like it keeps on disappearing when I reboot the device and becoming stock recovery.
Click to expand...
Click to collapse
Are you flashing recovery from fastboot? If you use fastboot, try flashing the recovery and using the button combo to boot into recovery from fastboot.
Do you have the 41.18 bootloader?
I have an 8 GB Telus xt1032 that I converted to GPE. While on GPE 4.4.4, I mistakenly allowed the 5.01 OTA update to install. Needless to say, it hung at the boot screen and I could do nothing.
I booted back into bootloader and noticed that my bootloader was now 41.18. I downloaded the stock Telus 4.4.4 ROM and manually flashed everything except motoboot.img (this is the bootloader image and is older than 41.18) and the phone booted without issue. I then installed TWRP and can flash pretty much any custom ROM.
I've heard it's possible to flash CM12 over Lollipop 5.0.2 official firmware. It was from 3 sources that peoples did it without problems
brainscollector said:
I've heard it's possible to flash CM12 over Lollipop 5.0.2 official firmware. It was from 3 sources that peoples did it without problems
Click to expand...
Click to collapse
It is possible but not on the GPE firmware. There are differences in the /system partition size and the update script doesn't expect this and hence the flashing fails.
audit13 said:
Are you flashing recovery from fastboot? If you use fastboot, try flashing the recovery and using the button combo to boot into recovery from fastboot.
Do you have the 41.18 bootloader?
I have an 8 GB Telus xt1032 that I converted to GPE. While on GPE 4.4.4, I mistakenly allowed the 5.01 OTA update to install. Needless to say, it hung at the boot screen and I could do nothing.
I booted back into bootloader and noticed that my bootloader was now 41.18. I downloaded the stock Telus 4.4.4 ROM and manually flashed everything except motoboot.img (this is the bootloader image and is older than 41.18) and the phone booted without issue. I then installed TWRP and can flash pretty much any custom ROM.
Click to expand...
Click to collapse
No no I have the 41.18 bootloader as it's a full conversion.
To get around the boot screen hanging I fastboot flashed a gpt.bin. Cheers for the advice though
d33dvb said:
FIRST THING FIRST, THIS IS DANGEROUS. DO IT AT YOUR OWN RISK.
Myself and one other person have successfully done this. If you have success as well, please post here. <snip>
Marcus Lemonis!
Click to expand...
Click to collapse
Finally!
It worked for me: UK Stock KK to GPE KK to GPE LP, on bootloader 41.18 and unable to flash CM12.
It didn't work exactly as you described, it only worked when I did teh following: flash stock v4.4.4 gbt.bin, reboot, flash philz, reboot to recovery, format system (unable to mount it otherwise), flash twrp, convert data from f2fs to ext4 (unable to mount it otherwise), format data, then install CM12, pagapps, and SU.
Thanks!
Does this downgrade the bootloader to 41.13? I'm on retail 4.4.4 with bootloader 41.18, tried flashing gpt.bin from 4.4.4 and it booted straight to bootloader with the message "fastboot reason: utag flash fail configured as fastboot", then I fixed it by flashing all the other files (except motoboot of course) However I'm still on 41.18..
I just want to get rid permanently of the ripple efect every time you reboot.
Motoboot.img is the bootloader file. Once on the 41.18 bootloader, you cannot flash an older bootloader.
The best method imo to flash custom ROMs on the 41.18 boot-loader is:
1) Flash the official Moto 5.0.2 firmwares for your respective devices
2) Flash the OFFICIAL TWRP 2.8.5.0
3) Wipe everything except internal storage. The first wipe will fail and the phone will reboot. Reboot again into the recovery and perform the wipe again. It will work this time.
4) Flash the ROM zip now.
PS: ADB sideload works for me but not MTP.
have rooted s5 on 4.4.4 nk2. Have been trying to install custom roms via safestrap. Apparently i am missing a step. I wipe data, try to install twi5ted Lollipop on custom rom slot....blank screen for over 30 min after reboot, phone gets real hot, take battery out. Try to install on stock rom slot, reboot then get stuck in boot loop and keeps booting into system recovery. I then saw through my hours of searching to format instead of wipe....so i format then try to install, get stuck again, take battery out, get back to safestrap dash now when i try to wipe/format/or even restore my backup it says unable to mount system. When i click reboot system it says no OS installed. After reboot, my custom slot gets erased.
I was about to try an odin flash back to stock but some how was able to get my phone back to a system restore. Why can i not get anything installed? Do i have to have odin to do a custom rom install?????? i know every rom is different but wtf. I have seen multiple videos and threads of people flashing zip via safestrap and rebooting into new rom without flashing kernals via odin or safestrap after rom install.
Also...my phone will not let me download zip files (ex. cm12.1) says unable to create download folder....how close to F'in my phone up am i? I have successfully rooted all phones in the past...s5 is giving me hell!
I just tried installing rom after format, then flash nk2 kernel from odin, still gives boot loop....ive tried everything i have found..never this much problem with custom rom..
When you try to install twisted it needs lollipop firmware which is flashed on odin, and based on your statement it says you're on NK2, a kitkat firmware. Try flashing a stock ncg tar and rerouting, downloading apps, etc. on the phone to see if that works. Also, I noticed you mentioned a cm 12.1 zip not downloading which, while unrelated to your current problem, will cause a bootloop when flashed due to the locked bootloader on the S5, so it isn't a smart idea to even attempt an install.
mrjiggywiggy said:
When you try to install twisted it needs lollipop firmware which is flashed on odin, and based on your statement it says you're on NK2, a kitkat firmware. Try flashing a stock ncg tar and rerouting, downloading apps, etc. on the phone to see if that works. Also, I noticed you mentioned a cm 12.1 zip not downloading which, while unrelated to your current problem, will cause a bootloop when flashed due to the locked bootloader on the S5, so it isn't a smart idea to even attempt an install.
Click to expand...
Click to collapse
thanks, i will try fresh from start ncg. so you have to be on the current kernel that you are flashing a rom for, whether its CM, Twi5ted, Alliance...etc i need to be on rooted 5.0 kernel then flash rom via safestrap?
i was having problems downloading from internet on phone, not downloading rom if thats what you thought i meant. I just tried installing zip for CM 12 via safestrap and got same issue. Phone reboots, goes to black screen and eventually heats up like crazy. .... I just noticed, after my restore ...again... it says safestrap disabled in red on the boot screen, why is that? it says installed and tried reinstalling.
FIXED
So i flashed ncg from odin on the messed up phone and got messed up worse. Ended up getting stuck on first boot image of samsung android s5 boot screen. Finally found original stock firmare file and used odin to complete install stock os and got rid of root. Now back to normal... luckily i figured it out my self! thanks to the 100's who viewed and didnt help and thanks to mrjiggywiggy for giving me some input to help out!
So I wanted to root my phone. Everything worked. Then I decided to factory reset my phone. Phone kept going in recovery mode. I wipe all (system,data,cache,dalvik) and tried to install stock rom from firmware center using RSDlite , but I couldn't. I keep getting "Failed flashing process. 3/23 flash partition "gpt.bin" "
I guess this because the stock rom is potentially downgrading the phone as there was a security update to the phone last month.
Other things I tried :
Wiped everything, tried custom rom (LineageOS) - Kept getting stuck in bootloader.
Please help
When you flash a custom rom, do you try to boot to system from the recovery? If so, boot into the bootloader right away from the recovery and select "qcom" and press the power button. This is what I have to do.
Try flashing another boot.img with a custom rom
Finally working
So, basically the problem was that the stock rom wouldn't install as my phone had been updated.
so whenever I tried to flash the stock rom using RSDlite it would fail at gpt.bin (which was the first operation).
Solution was to extract the xml.zip and edit the xml files to remove the operations that would flash gpt.bin .
Luckily the other files flashed successfully.
kuchbhinet said:
So, basically the problem was that the stock rom wouldn't install as my phone had been updated.
so whenever I tried to flash the stock rom using RSDlite it would fail at gpt.bin (which was the first operation).
Solution was to extract the xml.zip and edit the xml files to remove the operations that would flash gpt.bin .
Luckily the other files flashed successfully.
Click to expand...
Click to collapse
how do we do that to have it skip flashing gpt.bin? i tried erasing the line that said flash gpt but it still gives the same error
alexcass4 said:
how do we do that to have it skip flashing gpt.bin? i tried erasing the line that said flash gpt but it still gives the same error
Click to expand...
Click to collapse
Just use the updated firmware.