not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
onicrom said:
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
Click to expand...
Click to collapse
No.
10chars
fastboot oem unlock
flash cwm recovery
nandroid backup
mount /system
flash the su-2361 zip
boot up
rename/delete /etc/recovery.sh (or whatever the exact file is)
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
reboot to recovery to make sure cwm loads properly and updated.
done.
nxt said:
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
Click to expand...
Click to collapse
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
distortedloop said:
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
Click to expand...
Click to collapse
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
unremarked said:
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
Click to expand...
Click to collapse
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
distortedloop said:
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
Click to expand...
Click to collapse
Works fine for me normally. I personally don't use rom Manager to do anything though. I manually reboot into recovery and do recovery stuff. I have not tried selecting reboot to recovery via ROM Manager. That might be the issue.
Related
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
also it says invalid "boot image header!" in red letters
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
P.Kosunen said:
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
Click to expand...
Click to collapse
Alright thankyou!
I got everything to work again but I still can't flash roms. They just bootloop :S
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
You do know flashing stock again removes root, so it has to be rerooted again ?
aradalien said:
You do know flashing stock again removes root, so it has to be rerooted again ?
Click to expand...
Click to collapse
Yes I am very aware and followed through with root with that outcome.
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
Click to expand...
Click to collapse
CWM doesn't work it. It boots up (Im used cyanogenmod) the cyanogenmod boot animation but just stays there.
P.Kosunen said:
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Click to expand...
Click to collapse
I've flashed twrp too and came out with the same outcome.
stuck in fastboot
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
Exactly i am also facing same problem....
mobile unable to instal firmware...
still i am searching for solution ...
guys plz help me
I thought I am the only one with this problem..After mailing the phone to SC and got it back after 2 months, the phone still looks the same, just like they did nothing to fix it.
can i fastboot flash a rom or other zip? i've run into a problem after flashing a rom that wont boot and twrp wont mount data or my internal storage so i cant flash anything else. any help would be appretiated
I dont know how to do it, but have heard you can use the sideload feature of the twrp recovery to flash a rom. Or you could try flashing the new twrp recovery if your not on the new one. The new twrp 2.8.0.3 recovery was released on 9-30-14 last I checked its not updated on xda yet but you can get it on the twrp recovery web site which its on the link below, its the newest one on the bottom of the list.
http://techerrata.com/browse/twrp2/m8_wlv
reaper420 said:
can i fastboot flash a rom or other zip? i've run into a problem after flashing a rom that wont boot and twrp wont mount data or my internal storage so i cant flash anything else. any help would be appretiated
Click to expand...
Click to collapse
worse case scenario, run the RUU, fastboot flash recovery recovery.img then install ROM in recovery.
Honestly, you might as well apply the whole RUU and get yourself back to a working stock before putting another custom ROM back on. Follow the OP in this thread: http://forum.xda-developers.com/showthread.php?t=2873144
I tried every method possible and none worked, I recently cracked my screen so I just took this as a sign and went ahead and got it replaced with insurance. Thanks for all the suggestions
did your recovery constantly reboot into a white htc screen ?
jxcorex28 said:
did your recovery constantly reboot into a white htc screen ?
Click to expand...
Click to collapse
Are you using the correct Vzw version of twrp or cwm?
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk
Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix
slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..
carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.
Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.
You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.
I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?
I don't recommend using CWM, only TWRP.
After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.
Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.
Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.
My understanding is, if you reboot out of twrp you'll bootloop? You have to flash twrp-installer-3.3.1-2-guacamole.zip to install twrp? My question is, why? In my OP6 I could flash things from fastbooting into twrp then reboot back to oos. I may be wrong.
Try flashing twrp with this. You should be fine to flash anything in the most updated version from here and reboot with no issues. (as long as you do everything properly)
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
Deleted
SysAdmNj said:
My understanding is, if you reboot out of twrp you'll bootloop? You have to flash twrp-installer-3.3.1-2-guacamole.zip to install twrp? My question is, why? In my OP6 I could flash things from fastbooting into twrp then reboot back to oos. I may be wrong.
Click to expand...
Click to collapse
In the guide (TWRP thread) linked previously, it says: "If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again"
What you are asking seems a little different. You proposing to only fastboot boot TWRP, then flash something (Magisk?). Not sure if that will work. Even if it did, you would not have TWRP installed as a recovery. I would not consider a modded phone without a custom recover to be a desirable state.
redpoint73 said:
In the guide (TWRP thread) linked previously, it says: "If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again"
What you are asking seems a little different. You proposing to only fastboot boot TWRP, then flash something (Magisk?). Not sure if that will work. Even if it did, you would not have TWRP installed as a recovery. I would not consider a modded phone without a custom recover to be a desirable state.
Click to expand...
Click to collapse
Thats exactly what I used to do on the my OP6.
fastboot boot TWRP
Flash something
reboot back into OOS, keeping stock recovery
SysAdmNj said:
reboot back into OOS, keeping stock recovery
Click to expand...
Click to collapse
But why? Stock recovery is close to useless. And not needed to flash OTA updates.