Related
Tried to return my wif xoom to stock with the official images and ran into a problem. Followed the steps :
adb reboot bootloader
fastboot flash boot boot.img < this flashed Ok
fastboot flash system system.img < adb stuck waiting for xoom .. had to manual reboot the xoom.
Never got to the remaing steps.
Tried several times with the same result, almost. One time after manual reboot
came up with "RSD mode support 3". Had to do a hard reset to recover.
I ended up flashing Tiamet v1.4.0 again.
Maybe I'm doing something wrong here.
RSjagman said:
Tried to return my wif xoom to stock with the official images and ran into a problem. Followed the steps :
adb reboot bootloader
fastboot flash boot boot.img < this flashed Ok
fastboot flash system system.img < adb stuck waiting for xoom .. had to manual reboot the xoom.
Never got to the remaing steps.
Tried several times with the same result, almost. One time after manual reboot
came up with "RSD mode support 3". Had to do a hard reset to recover.
I ended up flashing Tiamet v1.4.0 again.
Maybe I'm doing something wrong here.
Click to expand...
Click to collapse
Are you sure it froze up I mean the system.img does take longer to do than the boot.img.
Have tried RSDLite 5.0? You might want to look into it.
I waited about 10 minutes before the manual reboot. Is 'adb' required before the flash command? The 1st step took about 14sec and based on the size of the files, the system image should flash in less than a minute.
I'll research RSDLite 5.0. Thanks.
UPdate: Today I tried it again and was successful, Xoom now stock and locked.
For info:
boot.img took 15sec to flash
system.img 17 minutes
Recovery.img 20sec
Userdata.img 4 min
erase cache 1.5s
Hope this helps someone.
Hello,
I have the MZ601 (Xoom UK 3G) and had EOS Everest JB stable on it.
Now I wanted to go back to stock. I downloaded the original firmware from Motorola, flashed the img files with adb and everything was fine (I did not relock the bootloader). The first OTA went fine too, now I am on Android 3.0.1 (H.6.1.-38-1).
It now detects the next OTA (about 44 MB, 63.5.25.en.EU), downloads it, tries to install it but at about 1/3 of progress the green bot of ! appears. I reflashed the stock firmware several times now, same result.
Then I googled, flashed Tiamat CWM recovery, rooted the device and then did:
adb remount (got message: succeeded)
adb shell rm /system/recovery-from-boot.p (message: no such file or directory)
adb shell rm /system/etc/install-recovery.sh (no message, so guess it worked)
Now I have no idea what else to try. I'd like to get back to stock ICS.
edit: reflashed back to stock once more. This time I entered recovery mode before I applied the very first OTA and the green bot of ! already appears, what's wrong here?
Hi,
It looks like your problem is not big deal. Just try flashing again all the files and principally DON'T FORGET TO FLASH RECOVERY! And I don't see why wouldn't you lock bootloader , if you really wants it unlocked and go to stock ICS I'd recommend you to flash stock, lock bootloader and then you update, after you get to the version you want unlock again :thumbup:
Wish you the best luck
Any problems please give me an up!
​Thanks for your reply!
I think I flashed recovery with the specific adb command (see below), not sure, not really an expert. :/ I even wiped dalvik cache and factory reset in cwm recovery before flashing back to stock.
Here's what I did in detail when reverting to stock:
I downloaded MZ601_H.6.1-38-1_Retail_Europe.zip from the official Motorola website, extracted all files and used these commands in adb:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Also, I noticed the green bot of ! appears after reboot when I enter recovery mode even before I flash the very first OTA (so just after flashing the stock files and reboot). Looks like recovery is somewhat broken or so?
I didn't want to relock the bootloader simply because I might want to root the device once I am back on stock ICS. Basically, I just wanted to get away from a custom ROM (Team EOS).
Would locking the bootloader make a difference for my success? According to google it doesn't but I am no expert to judge it right.
Yea, it looks like something is going wrong there...
Try downloading the files again, and then flash recovery. If you have no success try locking your BL, maybe it can works. The two times I went back to Stock I relocked my BL and had no problems to update via OTA. Then you relock your BL and use LordAIOTool to root again, which can easy your work...
Also you should try erasing system, recovery, cache and data before flashing, but it looks like what you did is fine.
Good luck
Thanks! I will give that a shot and post the result here.
By the way, that is one thing I read about and didn't dare to try yet: formatting system.
From what I read, after formatting /system the tablet will no longer be able to boot into android. In that case, how can I perform adb commands still? Afaik USB debugging has to be on but I will not be able to get into settings (due to lack of boot) and turn it on (and it will be off after reflashing afaik).
When you format system you can't boot in Android, but you can still flash things via fastboot, which uses a different protocol from adb. There was one time I had to format system to fix a cellphone, but if you don't want to try that, no worries , it may turn out without risking
I believe in order to upgrade you need to lock the BL. Once you update you can unlock it again.
Okay, downloaded the image again, this time via XDA. Suprisingly, all files were flashed in less than a min each (sometimes flasing system.img took half an hour or longer). Same result though. Since I forgot to lock the bootloader I flashed everything again after reboot:
Code:
>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 49.293s]
writing 'boot'... OKAY [ 2.155s]
finished. total time: 51.477s
>fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (remote: (00120003))
finished. total time: 1196.176s
Not sure why it failed here, worked dozens of times. So I simply decided to reflash system.img once more in the same run:
Code:
>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.391s]
writing 'system'... OKAY [ 14.744s]
finished. total time: 40.136s
Worked fine apparently, then continued from there as normal:
Code:
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All went well this time, no error messages on the latest full reflash or locking bootloader. Then rebooted, and now it is stuck at the Motorola boot screen:
Code:
Failed to boot LNX 0x0004
Starting RSD mode 2
(charger information bla bla here)
Not sure why this happened and what this actually means? It won't boot up and since the bootloader is locked I can't enter recovery or anything. What do I need to do now?
Man... You forgot to flash the kernel (boot.img)!!! And it's probably appearing because of this small mistake!!! Now that you're on RSD Mode 2 you have to fix it another way... I never went to it (only went twice to mode 3), so sorry, I can't help you this time , I will search a little and see what I can do for you.
My mistake on posting, I did flash boot.img before that, corrected my previous posting.
Now I am stranded. And I can't even turn off the device on boot screen.
edit: rescued it, thanks to this posting:
Pushed power + vol up for reboot, waited 5 sec, then held vol down until fastboot appeared (kept pressing the button for about 17 sec until fastboot showed up).
Once there, I unlocked bootloader successfully again to flash all stock files. Xoom booted up bravely afterwards, phew.
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Landorin said:
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Click to expand...
Click to collapse
Glad you made it
Congrats!!
Hey guys, I have a 64gb OnePlus One and it's seems to be stuck on an infinite bootloop(soft-brick). I am able to access both fastboot mode and recovery. My phone's bootloader is unlocked and I have the stock cyanogen recovery presently.
I had run into this issue several times earlier, and was quickly able to resolve it... Either by flashing a different custom rom or factory resetting the phone using TWRP recovery and it all worked out, but this time, nothing seems to work. After reading several guides and watching many videos, I frequently came across that flashing the stock(cm12.1 factory image) would fix the bootlooping issue once and for all, and it turns out and it did work, but only momentarily and it was quite weird infact... After the fastboot flashing process was done, the phone started bootlooping once again and I let it happen for 5-10 mins, after which I gave up and turned it off. But after leaving it off for sometime and then turning it on later, it did boot up once for sometime to the initial boot setup screen, only to start rebooting again.
I gave it some more time to be turned off and the next time I turned it on, it booted normally and everything seemed to be working fine... I installed whatever apps I needed, downloaded music and everything looked great, but then it started crashing into random reboots once again, at random instances, but using the temporary power off technique I talked about earlier, I made it work somehow, until even that stopped working.
I've tried literally every method, even locking and unlocking the bootloader and then flashing stock again... Also... using the single command method mentioned which fixed persist partitions on that phone, and even that was in vain.
Infact, now my phone is in an even worse condition, it won't even make it past the 1+ logo, just keeps on rebooting there. Any help with this issue would be greatly appreciated... Thank you.
Sounds like the exact final stage issue that my friend was having. Finally his phone even bootlooped in fastboot when he was on holiday.
I had the phone with me for a couple of hours when he returned and nothing worked. I couldn't even connect to the pc in the end. I personally think his memory had an issue.
Seems like you tried all you could. Does it stay on in fastboot?
In the end I had my friend rma his phone and Oneplus said the warranty was void because one sticker was slightly red .... complete bull story since the phone was never ever in contact with water or other liquid stuff and they would not answer a single question in regards to that. So my advice if someone else doesn't have a hocus pocus solution is to check if you have warranty and see if you can't see these moisture indicator through the headphone jack and try to go for warranty repair.
Download the latest fastboot signed ROM from here: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
Hi , I just screwed up when I was trying to flash TWRP recovery on my OnePlus 7 Pro. I accidentally wrote "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img" and now my phone wont boot into anything but the bootloader. How can I fix this issue? Thanks heaps!
Edit: Ok, it looks like I need the boot.img from stock firmware. Could someone provide that for me? My download speed is super slow (like less than 100 KB/s) so downloading the stock firmware is gonna take me 7 hours D: (Yay for living in the middle of nowhere!!)
fastboot boot twrp.img shouldn't have messed anything up. That should just have booted the recovery without installing it, and this is the command you should use.
If you want help getting the boot image you should probably post what build and version you are using, since there are quite a few to pick from.
Didgeridoohan said:
fastboot boot twrp.img shouldn't have messed anything up. That should just have booted the recovery without installing it, and this is the command you should use.
If you want help getting the boot image you should probably post what build and version you are using, since there are quite a few to pick from.
Click to expand...
Click to collapse
Well my phone won't boot now, so it did something wrong haha :'( When I go fastboot boot twrp.img, the phone hangs on it's splash screen of the 1+ logo, with powered by android at the bottom.
As for build, I think it was the latest version out 11.0.0.2.GM21AA, thank you!
Also, typing fastboot flash boot twrp.img then trying to reboot to recovery just takes me back to the stock bootloader, so I don't know what's going on there :\
Also, fastboot gives this as it's outupt about why it can't flash twrp to the phone, using fastboot flash recovery twrp.img:
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
Aqyx said:
Well my phone won't boot now, so it did something wrong haha :'( When I go fastboot boot twrp.img, the phone hangs on it's splash screen of the 1+ logo, with powered by android at the bottom.
As for build, I think it was the latest version out 11.0.0.2.GM21AA, thank you!
Also, typing fastboot flash boot twrp.img then trying to reboot to recovery just takes me back to the stock bootloader, so I don't know what's going on there :\
Also, fastboot gives this as it's outupt about why it can't flash twrp to the phone, using fastboot flash recovery twrp.img:
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
Click to expand...
Click to collapse
I feel your pain on download speed. Took me two tries, finally had to zip it I will try to upload boot.img for op7p 11.0.2.1, OnePlus7ProOxygen_21.P.38_OTA_0380_all_2107172338_49e62 build which I believe is the latest. Use at your own risk. It would be good to know for sure what build you're on.
Phoenix 15 A said:
I feel your pain on download speed. Took me two tries, finally had to zip it I will try to upload boot.img for op7p 11.0.2.1, OnePlus7ProOxygen_21.P.38_OTA_0380_all_2107172338_49e62 build which I believe is the latest. Use at your own risk. It would be good to know for sure what build you're on.
Click to expand...
Click to collapse
Thank you mate!
i tried arrowos and havocos (the only ones that worked for me) and they both takes roughly 15~20 minutes to boot
Phone: Oppo A5s Rooted with unofficial TWRP (encryption and mtp do not work)
i flashed the rom with fastboot
fastboot erase system
fastboot flash system (arrow-havoc-os).img
fastboot -w
fastboot reboot
Khalyl22 said:
i tried arrowos and havocos (the only ones that worked for me) and they both takes roughly 15~20 minutes to boot
Phone: Oppo A5s Rooted with unofficial TWRP (encryption and mtp do not work)
i flashed the rom with fastboot
fastboot erase system
fastboot flash system (arrow-havoc-os).img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Any newly flashed android operating system takes 10-20 mins to boot. As android grows bigger with new software improvements over time, this isn't going to change anytime soon.
Droidriven said:
Any newly flashed android operating system takes 10-20 mins to boot. As android grows bigger with new software improvements over time, this isn't going to change anytime soon.
Click to expand...
Click to collapse
ah okay make sense it just annoying to try a lot of gsi roms when u gotta wait 20 minutes for it to boot for every single one of them