Hello everybody !
I wanted to install a new "ROM" on my device. I installed the "ROM" with "RCW" and everything went well.
But when I turn on the device again, the following message appeared:
"Failed to boot 2"
"starting mode rsd"
What should I do?
I tried to reinstall a "ROM" in "SBF" but the process to stop after a while and says "failed".
I also tried with "fastboot". Everything seems to be fine but the device shows the same message.
Any idea? Have i to unlock the "bootloader" again?
My device is an "AT&T" from "United States" and used in France. The latest version of "android" that I used was the official 2.3.4 updated "in the rules" with Motorola.
I just wanted to install a "ROM" more Sympathic. Until now I had just root the device and unlock the bootloader.
Thanks for all !
P.S: I searched around and tried many things. So I'm sorry if there is a post that I have not seen about it.
galadiel said:
Hello everybody !
I wanted to install a new "ROM" on my device. I installed the "ROM" with "RCW" and everything went well.
But when I turn on the device again, the following message appeared:
"Failed to boot 2"
"starting mode rsd"
What should I do?
I tried to reinstall a "ROM" in "SBF" but the process to stop after a while and says "failed".
I also tried with "fastboot". Everything seems to be fine but the device shows the same message.
Any idea? Have i to unlock the "bootloader" again?
My device is an "AT&T" from "United States" and used in France. The latest version of "android" that I used was the official 2.3.4 updated "in the rules" with Motorola.
I just wanted to install a "ROM" more Sympathic. Until now I had just root the device and unlock the bootloader.
Thanks for all !
P.S: I searched around and tried many things. So I'm sorry if there is a post that I have not seen about it.
Click to expand...
Click to collapse
If the boot screen shows unlock on the top of the screen than u don't have to unlock the bootloader again.
You should check if you get the "unlocked" message on the top left side of your screen to ensure it is unlocked or not.
If it doesn't show anything, you should try to unlock the bootloader again.
Just be careful to not flash any rom through SBF before make sure you are not downgrading your Kernel version, or you will hardbrick your phone.
The Pudding (http://forum.xda-developers.com/showthread.php?t=1136261) thread and the Brick thread (http://forum.xda-developers.com/showthread.php?t=1160408) should give your more insights about this.
I'm searching for some screens and a thread explaining how to unlock the bootloader in the safest way. As soon as I find I'll edit my post.
Thank you for the answer.
I'm also looking on my side. The first is that the announcement to another.
Thanks again ;-)
Hey folks,
So i got my Atrix from RMA today, it has a new mainboard, had WLAN errors before. Tried to unlock it with ihop_bell.sbf, like last time, but it failed. Now it says failed to boot 1, the bootloader is still locked, because fastboot does not know oem unlock.
I can enter fastboot mode. If I start and press volume down it says something about nvflash for 0.5 secs and turns off. RSD detects it as SE Flash Olympus and I can start flashing, but it always fails at "Switching to BP Pass trough mode".
So what now, is it hardbricked?
Before flashing did you check your FW version (i.e. Build number/version) to see what type it was, sometimes after installing new parts they will turn it on and test it to see how it works and may hit update while at it to make sure it is ready to go out of the box
Should be the German Retail 2.3.4, did not check it though. Just made sure the WiFi Error is gone.
Uh, you might have wanted to check. You always want to ensure software revision numbers before attempting the unlock. Even some retail updates can have minor build changes that could result in your bootloader unlock bricking your phone.
So moto-fastboot is not responding to the CMD "oem unlock"? I am just going over all the info to see if I can help, I have had the "Failed to boot #" issue with a multitude of Moto's (CDMA and GSM, and my global Photon) I have also been able to fix them. Was your device fully charged before attempting the SBF flash? that will kill an SBF flash and possibly the phone.
---------- Post added at 01:29 PM ---------- Previous post was at 01:20 PM ----------
It would also appear that FTB 1 is related to not having atleast 50% charge available during the flash. You may want to get a battery charger for it and charger the phone and attempt a flash from there. This thread has a little info in it (if you read the on topic stuff) http://forum.xda-developers.com/showthread.php?t=1491788 . Good luck my friend, I know how it feels, If you have any questions let me know.
Edit: If you can get fastboot to atleast give you info on any bootloader variables (fastboot getvar <variable request>) then you may be able to find out if their was a software revision, i am unsure at this time
OMG!
After I tried flashing the international unlock like 5 times more again and the same error ocurred, I tried to unlock in fastboot after ur last post and IT WORKED
TBH I am a little bit confused, because 1 hour ago it(the unlock) did not work and really can not understand what was wrong before. Still on the same battery.
Now it is unlocked and the message is gone, I can enter e.g. the RSD mode or the recovery.
Maybe it had to do with battery indeed, I dont know, just happy that it works again. Thanks for posting mate!
Haha, That's good. Hope it stays going well for you. I hated when I flashed pudding and it failed then ran the OEM unlock code just to see if it would continue, sure enough it did. Glad to hear it is fixed
So here is the thing: I'm from Brazil, and HTC does not sell devices here anymore. I ended up buying an AT&T HTC One M8 from Amazon - a friend of mine brought it for me.
I had to unlock it to use with the carriers around here. I have been using the device just fine for months. For some reason, my device never updated - it was always at Kitkat 4.4.2. This week I decided to try to fully unlock and put a ROM in the M8 to get the most recent OS. I went for the ARDH, the most recent one - with Android 5.0 and Sense 7.
I used Sunshine to bootload and s-off my device. Everything worked perfectly and then I installed the ARDH ROM. However there is one small problem that I stumbled upon since then: my wifi, from time to time, just stops working, and usually comes back when I restart or turn off/on my device. It usually works fine for a few hours, and then just suddenly stops working.
Can anyone help me with this problem? I read some articles saying that maybe the problem is related to the OS not being updated to 4.4.4., but I'm not sure how I could go back now. Can I just download the ROM in HTC website and try to install it over the current one?
I humbly ask of you to try and explain things as easily as possible, since I'm not too familiar with "jargons"
Change your cid to BS_US001,BS_US002 And flash developer version ruu...no need to change mid as they are the same device and then youll have a clean device,no carrier bloat from ATT AND get your updates from HTC. You will never get updates from ATT due to not being on their network.
haimondlafis said:
So here is the thing: I'm from Brazil, and HTC does not sell devices here anymore. I ended up buying an AT&T HTC One M8 from Amazon - a friend of mine brought it for me.
I had to unlock it to use with the carriers around here. I have been using the device just fine for months. For some reason, my device never updated - it was always at Kitkat 4.4.2. This week I decided to try to fully unlock and put a ROM in the M8 to get the most recent OS. I went for the ARDH, the most recent one - with Android 5.0 and Sense 7.
I used Sunshine to bootload and s-off my device. Everything worked perfectly and then I installed the ARDH ROM. However there is one small problem that I stumbled upon since then: my wifi, from time to time, just stops working, and usually comes back when I restart or turn off/on my device. It usually works fine for a few hours, and then just suddenly stops working.
Can anyone help me with this problem? I read some articles saying that maybe the problem is related to the OS not being updated to 4.4.4., but I'm not sure how I could go back now. Can I just download the ROM in HTC website and try to install it over the current one?
I humbly ask of you to try and explain things as easily as possible, since I'm not too familiar with "jargons"
Click to expand...
Click to collapse
Thank you for your help. Unfortunately, I did not understand what you asked for me to do - like I said, I'm not too familiar with the names.
Could you maybe try to explain a few steps?
haimondlafis said:
Thank you for your help. Unfortunately, I did not understand what you asked for me to do - like I said, I'm not too familiar with the names.
Could you maybe try to explain a few steps?
Click to expand...
Click to collapse
S-OFF ONLY! How to get supercid
1. Have adb and fastboot set up. There are guides all over xda and google
2. Connect phone to PC and open terminal
3. Type "adb devices" to make sure phone is connected to PC
4. Type "adb reboot bootloader"
5. Once in fastboot type "fastboot devices" to make sure fastboot sees your device
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111" (has to be 8 one's)
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!
Be warned you can do some bad things to your phone with super cid if you don't know what you're doing. I'd head over to the international forum for the m8 and do some reading up on it.
Credit to: skulldreamz at http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
SO, i followed a guide the other day to get lollipop on my wind huawei mate 2.
but now i want to switch back to the original android that came with the phone because i want to unlock the phone, and the lollipop one on the guide i followed doesnt show the unlock code entry screen when i put in a different sim card.
the issue i am having?
when i flash the stock recovery file that i found on here, that boots fine, then when i try to install B128 wind firmware, it says a bunch of error codes along the size of
oemsbl write failed something or other then it also said update_vendor.app install failed - invalid package
i'm hoping someone can help me because my phone will not go past the huawei logo at this point.
i do have access to fastboot mode though thank god.
if anyone can help me with the proper files to download and such that would be great!
mikeogden1981 said:
SO, i followed a guide the other day to get lollipop on my wind huawei mate 2.
but now i want to switch back to the original android that came with the phone because i want to unlock the phone, and the lollipop one on the guide i followed doesnt show the unlock code entry screen when i put in a different sim card.
the issue i am having?
when i flash the stock recovery file that i found on here, that boots fine, then when i try to install B128 wind firmware, it says a bunch of error codes along the size of
oemsbl write failed something or other then it also said update_vendor.app install failed - invalid package
i'm hoping someone can help me because my phone will not go past the huawei logo at this point.
i do have access to fastboot mode though thank god.
if anyone can help me with the proper files to download and such that would be great!
Click to expand...
Click to collapse
With NO stock backup i doubt it.
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05