Related
The nopudding4u download that someone posted doesn't work and gives Fail to boot 2 errors to everyone who tries it out.
Could one of you please make a pudding remover that works? I would like to relock my bootloader, so that way my 4G will work. I don't want to reflash an entire sbf as I want to keep my data.
I just relocked my bootloader with the pudding remover... it says that it's failed... but it works.. make sure you flashed the stock recovery before you relock... but I kinda did it backwards... but it works...
I would get Fail to boot 2.
I had to reflash pudding to get my phone to boot.
I really want to remove pudding and the steps provided don't do much.
Sent from my MB855 using Tapatalk
antgly said:
I would get Fail to boot 2.
I had to reflash pudding to get my phone to boot.
I really want to remove pudding and the steps provided don't do much.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
me too I can't relock with pudding remover even with flashing back the stock recovery i'd still get the failed to boot 2 error.
Cwm backup, sbf, bootstrap, cwm restore=profit
Sent from my MB855 using XDA App
+10 char
jokersax11 said:
Cwm backup, sbf, bootstrap, cwm restore=profit
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
I'm wondering as to what exactly is the problem with nopudding4u that makes it fail to work properly.
I believe that Failed to boot 2 error means that your battery is below 50% charge. The RSD softeware on the phone won't let to flash if you're under 50% battery.
I got that error and then put my Photon on the AC charger. Tryed again 20 minutes later and the boot worked.
what does Failed to boot 4 mean?
Work it does not, rsd you must do.
skyungjae said:
what does Failed to boot 4 mean?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
antgly said:
I would get Fail to boot 2.
I had to reflash pudding to get my phone to boot.
I really want to remove pudding and the steps provided don't do much.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
Make sure you guys have the right nopudding.sbf I had the failed to boot 2 a while ago when I flashed an electrify.sbf by mistake and It nearly terminally bricked my phone. I have locked and unlocked multiple times using the correct nopudding I believe there is also a stock sbf that will relock, but I'm not sure where to find it, I would assume try googling it.
FanBoy_Hunter said:
Make sure you guys have the right nopudding.sbf I had the failed to boot 2 a while ago when I flashed an electrify.sbf by mistake and It nearly terminally bricked my phone. I have locked and unlocked multiple times using the correct nopudding I believe there is also a stock sbf that will relock, but I'm not sure where to find it, I would assume try googling it.
Click to expand...
Click to collapse
Go to the dev section or check my sig
To Other MoPho Users:
I'm not quite sure what's going on as I root-unlock-relock a couple times a day on a dev day with no issues. There seems to be a flood of OMGWTFBBQ posts regarding this process. What threads are you guys reading for instructions?
Fanboy, PM me with how you managed to get rid of the electrify sbf. I am stuck in the same predicament with .235.
As for Lokifish, I thank you many times over for putting the files together.
medic233 said:
Fanboy, PM me with how you managed to get rid of the electrify sbf. I am stuck in the same predicament with .235.
As for Lokifish, I thank you many times over for putting the files together.
Click to expand...
Click to collapse
Working right now and I have to do some research to remember how I did it (been a while) , but most definitely. I'll get back to you on it tonight. where I'm at it's almost 1 so it'll be about 9 When I can pm u
I unlocked a while back to check out ICS. I then flashed back to stock using the 198_7 sbf and did a factory wipe. My phone no longer said unlocked during boot and everything was good. However, a couple days back I decided that I wanted to unlock again to try some new cool things. During the unlock process, I flashed the pudding sbf and when it reboot it said unlocked. I didnt have to go through the cmd steps and enter my unique ID. So that has me wondering if I was ever really relocked. I definitely had the stock recovery. So, even if my phone does not say unlocked during boot, should I flash the nopudding4u sbf? I ask because I will be traveling to a wimax area soon and want to make sure that I can use it.
Thanks guys.
my2cents said:
I unlocked a while back to check out ICS. I then flashed back to stock using the 198_7 sbf and did a factory wipe. My phone no longer said unlocked during boot and everything was good. However, a couple days back I decided that I wanted to unlock again to try some new cool things. During the unlock process, I flashed the pudding sbf and when it reboot it said unlocked. I didnt have to go through the cmd steps and enter my unique ID. So that has me wondering if I was ever really relocked. I definitely had the stock recovery. So, even if my phone does not say unlocked during boot, should I flash the nopudding4u sbf? I ask because I will be traveling to a wimax area soon and want to make sure that I can use it.
Thanks guys.
Click to expand...
Click to collapse
u only have to put in the unique I'd once. Its like unlocking the door that allows u to open and close it. I believe with 198_7 u don't need to use no pudding, but I have been on cm9 a long time and my memories a little foggy. U can however flash it just to be safe.
Sent from my MB855 using xda premium
I don't read well, apparently, and flashed the Electrify 2.3.5 file in hopes of unlocking my bootloader.
Has anyone else (I have read that a handfull of people have been stupid like me) had any luck unbricking the device?
I have access to RSD protocol and Fastboot.
Thanks in advance.
EDIT: The only thing my phone says now is:
SUF: 108:1:2
Failed to boot 3
----------------------------------------------------------------------
EDIT #2: Downloaded someones CWM flashable kernel and flashed to boot.img via moto-fastboot. Not I have an "Failed to boot 2", which people have recovered from. I am currently flashing (198_7)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf and it's 55% completed, which is higher than it got before........
EDIT #3: It failed.... waiting for re-enumeration...
Have you tried this?
http://www.youtube.com/watch?v=J94VcWk-CJc
I fixed it by flashing the electrify 2.3.5 rom thru rsd.
Now all I have to do is get it back to Sprint.
Sent from my A500 using xda premium
npaulseth said:
I fixed it by flashing the electrify 2.3.5 rom thru rsd.
Now all I have to do is get it back to Sprint.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not gonna happen until the new boot-loader is cracked... Sorry
Flashing ROMS Via Bootstrap doesnt work.
Its not that big of a deal. Everything works except 4G and MMS.
I can wait.
Sent from my Motorola Electrify using xda premium
npaulseth said:
Its not that big of a deal. Everything works except 4G and MMS.
I can wait.
Sent from my Motorola Electrify using xda premium
Click to expand...
Click to collapse
Try go sms pro. Put mms settings in advanced settings. Should make mms work.
now just a clarification but is it possible to, without Motorola files, to unlock the boot loader our selves? Is there any coding work to unlock this boot loader on our own?
Sent from my Full Android on Wingray using xda premium
You have to flash something to gain the abilty to unlock the bootloader thru fastboot.
npaulseth said:
I don't read well, apparently, and flashed the Electrify 2.3.5 file in hopes of unlocking my bootloader.
Has anyone else (I have read that a handfull of people have been stupid like me) had any luck unbricking the device?
I have access to RSD protocol and Fastboot.
Thanks in advance.
EDIT: The only thing my phone says now is:
SUF: 108:1:2
Failed to boot 3
----------------------------------------------------------------------
EDIT #2: Downloaded someones CWM flashable kernel and flashed to boot.img via moto-fastboot. Not I have an "Failed to boot 2", which people have recovered from. I am currently flashing (198_7)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf and it's 55% completed, which is higher than it got before........
EDIT #3: It failed.... waiting for re-enumeration...
Click to expand...
Click to collapse
I haven't found the file yet, but apparently right now the only way to fix this is to flash the 2.3.5 Electrify rom.
http://forum.xda-developers.com/showthread.php?t=1394982&highlight=stuck+in+fastboot
http://forum.xda-developers.com/showthread.php?p=20713504
Edit #2: confirmed working. I made a small tutorial for those on this same situation here: http://forum.xda-developers.com/showpost.php?p=21015556&postcount=6
Have a good life!
firtermish said:
I haven't found the file yet, but apparently right now the only way to fix this is to flash the 2.3.5 Electrify rom.
http://forum.xda-developers.com/showthread.php?t=1394982&highlight=stuck+in+fastboot
http://forum.xda-developers.com/showthread.php?p=20713504
Edit #2: confirmed working. I made a small tutorial for those on this same situation here: http://forum.xda-developers.com/showpost.php?p=21015556&postcount=6
Have a good life!
Click to expand...
Click to collapse
Just a quick question: Where you able to flash back to:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf
or are you runningL 2.3.5?
Thanks,
RJR
rrusek said:
Just a quick question: Where you able to flash back to:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf
or are you runningL 2.3.5?
Thanks,
RJR
Click to expand...
Click to collapse
I haven't personally tried it, but as far as I know you can't. You are stuck on 2.3.5 until someone releases a new bootloader unlocker.
firtermish said:
I haven't personally tried it, but as far as I know you can't. You are stuck on 2.3.5 until someone releases a new bootloader unlocker.
Click to expand...
Click to collapse
That's what I figured.. I quess it is better to be stuck unlocked than to be stuck locked!
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
Has anyone been able to get the Sprint data profile pulled down on this so I can use on Sprint?
I had a similar problem this weekend I flashed electrify 2.3.5 on my photon lost root and recovery and was able to get both back. First I flashed the sunfire 2.3.4 thru rsd then one click root and then bootstrap app to flash cwn and am able to flash roms again.
Sent from my MB855 using Tapatalk
js11222 said:
I had a similar problem this weekend I flashed electrify 2.3.5 on my photon lost root and recovery and was able to get both back. First I flashed the sunfire 2.3.4 thru rsd then one click root and then bootstrap app to flash cwn and am able to flash roms again.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
Are you currently locked or unlocked? If I lock my device I will get the Failed to Boot 1 error. If I unlock then everything works.
When I flashed the 2.3.5 rom It locked my phone u have to re unlock it
Sent from my MB855 using Tapatalk
rrusek said:
Are you currently locked or unlocked? If I lock my device I will get the Failed to Boot 1 error. If I unlock then everything works.
Click to expand...
Click to collapse
After flashing the 2.3.5 rom it locked my phone I had to re unlock it I used the unlock sbf thru rsd I am currently unlocked back on jokers stock rom
Sent from my MB855 using Tapatalk
js11222 said:
After flashing the 2.3.5 rom it locked my phone I had to re unlock it I used the unlock sbf thru rsd I am currently unlocked back on jokers stock rom
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
But if you wanted to re-lock your phone to get 4g could you do it or would you also get the Failed to Boot 1 error?
Point being is that I think it relocks your phone and does not allow for a downgrade.
rrusek said:
But if you wanted to re-lock your phone to get 4g could you do it or would you also get the Failed to Boot 1 error?
Point being is that I think it relocks your phone and does not allow for a downgrade.
Click to expand...
Click to collapse
Yes it did lock my phone then I unlocked it again and am on stock 2.3.4 so I did downgrade
Sent from my MB855 using Tapatalk
js11222 said:
Yes it did lock my phone then I unlocked it again and am on stock 2.3.4 so I did downgrade
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
If you would not mind can you please outline what you did?
This is what I did:
1. Installed regular pudding
2. Installed cwm recovery
3. Installed 2.3.5 for Electrify/Photon via cwm
Then did:
1. Installed stock recovery
2. Installed nopudding4g
After that I started getting the Failed to Boot 1
No matter which locked 2.3.4 I try to flash via RSD it fails on first flash pass when it tries to put the phone into BP bypass.
First to get my phone back to normal in rsd mode I flashed the sunfire sbf then to unlock my phone I used pudding unlock sbf then to get recovery I had to do the one click root then got the bootstrap app to flash cwm zip then I installed jokers stock rom
Sent from my MB855 using Tapatalk
after this thread http://forum.xda-developers.com/showthread.php?t=2105017 i used one of the sbf in this sites http://www.das8nt.com/sbffiles.html
and flash it with RSD now i am trying agin to use fastboot and flash once more cwn and i get this message 'error cannot load recovery.img'
and when i tryd to erase and then flash and i got the same thing.
moreover when i start the phone somehow after i flash the sbf the tuch screen works funny (its not dead pixel) its like the touch screen moved one half inch lower
After flashing sbf, in order to flash a custom recovery, you first need to flash a pudding sbf file to unlock the bootloader. After unlocking the bootloader, running the command "fastboot oem unlock" and then repeating the command with your device's ID, you can flash CWM to your recovery.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
After flashing sbf, in order to flash a custom recovery, you first need to flash a pudding sbf file to unlock the bootloader. After unlocking the bootloader, running the command "fastboot oem unlock" and then repeating the command with your device's ID, you can flash CWM to your recovery.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
did it still dont work
igalc87 said:
did it still dont work
Click to expand...
Click to collapse
Seeing as your device is a non-ATT device, did you flash a pudding sbf or the IHOP sbf?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Seeing as your device is a non-ATT device, did you flash a pudding sbf or the IHOP sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i flashed to my original sbf Partner (Orange) Israel 2.3.4 / 45.33.0
Ok. After you flash that, you have to flash another sbf file over that one. http://forum.xda-developers.com/showthread.php?t=1136261 will get you to the instructions on what to do. Since Orange is what is considered international, you need the IHOP sbf on the page.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Ok. After you flash that, you have to flash another sbf file over that one. http://forum.xda-developers.com/showthread.php?t=1136261 will get you to the instructions on what to do. Since Orange is what is considered international, you need the IHOP sbf on the page.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i got a message its already unlock
and it still dont let me flash with fastboot
so do you any answer?
After seeking advice from a dev, this is the response i was given:
Could also be the recovery is in fact in that directory but is not named recovery.img. Or, if fastboot actually managed to load the file but still reports that error, it could be that his bootloader is either not unlocked or is having issues (the fastboot protocol is implemented in the bootloader AFAIK).
Sent from my MB860 using xda app-developers app
palmbeach05 said:
After seeking advice from a dev, this is the response i was given:
Could also be the recovery is in fact in that directory but is not named recovery.img. Or, if fastboot actually managed to load the file but still reports that error, it could be that his bootloader is either not unlocked or is having issues (the fastboot protocol is implemented in the bootloader AFAIK).
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i looked agin my i got in the left up corner message unlock(i did all the steps after flashing the sbf)
i redownload recovery and put it in the same dirctory
and still i got errors when i try to flash recovery.img (or system.img boot.img)
so maybe my bootloader fuked how do i fix it?
and tell me if i will flash other sbf file iy will make it worse?
I'm not sure what the heck is going on with your phone or how to fix it, but I'm going to advise you to stay far far away from SBFs from now on.
ravilov said:
I'm not sure what the heck is going on with your phone or how to fix it, but I'm going to advise you to stay far far away from SBFs from now on.
Click to expand...
Click to collapse
ok will do but i will be glad to find an answer
igalc87 said:
i looked agin my i got in the left up corner message unlock(i did all the steps after flashing the sbf)
i redownload recovery and put it in the same dirctory
and still i got errors when i try to flash recovery.img (or system.img boot.img)
so maybe my bootloader fuked how do i fix it?
and tell me if i will flash other sbf file iy will make it worse?
Click to expand...
Click to collapse
I'm going to recommend you ask one of the devs about how to fix it. You can flash another sbf file, but make sure it is the same version as what you have. So if you flashed a 2.3.6 sbf, you need to flash a sbf that is 2.3.6 or risk bricking your phone.
Sent from my MB860 using xda app-developers app
---------- Post added at 09:47 AM ---------- Previous post was at 09:34 AM ----------
One other thing. I'm about to head off to basic training and will be offline for about 10 wks starting next wk. Any one of the atrix dev's should be able to help you further with your phone. I'll do what i can until i leave.
Sent from my MB860 using xda app-developers app
---------- Post added at 09:50 AM ---------- Previous post was at 09:47 AM ----------
ravilov said:
I'm not sure what the heck is going on with your phone or how to fix it, but I'm going to advise you to stay far far away from SBFs from now on.
Click to expand...
Click to collapse
I didn't see this post when i first logged in. Seeing as this comes from one of the atrix devs, i'm going to stand behind this bit of advice, but i still will stand behind what i said before, ask the devs for help.
Sent from my MB860 using xda app-developers app
I had a unlocked bootloader, rooted rezound running AOKP JB rom. Now after trying to flash a differnet kernel (stupid me) I can't get past the bootloader screen. I was able to relock my bootloader but now on Hboot screen it says ***tampered*** *****relocked**** and ****security warning**** I am completely stuck. Am I SOL or is there a chance to fix this? Any help would be greatly appreciated.
bluerez79 said:
I had a unlocked bootloader, rooted rezound running AOKP JB rom. Now after trying to flash a differnet kernel (stupid me) I can't get past the bootloader screen. I was able to relock my bootloader but now on Hboot screen it says ***tampered*** *****relocked**** and ****security warning**** I am completely stuck. Am I SOL or is there a chance to fix this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Get back into fastboot. Unlocked your phone. You can just go back and flash the boot.img that was on your original rom
Flyhalf205 said:
Get back into fastboot. Unlocked your phone. You can just go back and flash the boot.img that was on your original rom
Click to expand...
Click to collapse
I tried. I went through the htc.dev and it all went ok until i tried to submit it. It said "unlocking bootloader failed"
bluerez79 said:
I tried. I went through the htc.dev and it all went ok until i tried to submit it. It said "unlocking bootloader failed"
Click to expand...
Click to collapse
You s-on or s-off?
Might as well install the RUU again...
Flyhalf205 said:
You s-on or s-off?
Might as well install the RUU again...
Click to expand...
Click to collapse
S-on
Can I flash with a locked bootloader?
Sent from my Galaxy Nexus using xda app-developers app
bluerez79 said:
Can I flash with a locked bootloader?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You won't be able to flash a rom or kernel if your s-on and locked. The only thing you can do is try and unlock bootloader or run RUU and restart from scratch
I can't unlock boot loader. Went thru the process and it said the token was too long. So I guess I'll look for the RUU and give it a go.
Sent from my Galaxy Nexus using xda app-developers app
bluerez79 said:
I can't unlock boot loader. Went thru the process and it said the token was too long. So I guess I'll look for the RUU and give it a go.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
At what point did it say that? When you are trying to get it from the HTC site? If that's it you are just copying too much. Make sure you don't copy any extra characters at all.
If it's when you are flashing the unlock token bin file then I agree that you should just run the RUU and get back to fresh stock then try again.
Use the RUU that is the .12 version rather than the global leak, unless you have already run the global leak one, if you want to be able to take the newest OTA.
I tries to flash ruu from my pc. The command prompt said “access denied"
Sent from my Galaxy Nexus using xda app-developers app
And your bootloader is locked? You talked about getting the unlock token, did you unlock it again before RUUing?
It needs to be locked to run the RUU.
bluerez79 said:
I tries to flash ruu from my pc. The command prompt said “access denied"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
How are you flashing it?
Fastboot flash and then the name of the ruu
Sent from my Galaxy Nexus using xda app-developers app
It was locked when I tried to flash ruu
Sent from my Galaxy Nexus using xda app-developers app
Try this:
fastboot oem rebootRUU
fastboot flash zip {nameofruu}.zip
Or place it on your sd card and flash it in hboot
If it's an exe file you need to double click on that on your pc while the phone is connected.
Sorry they are a dumb questions , i don't know.
I unlocked bootloader and installed cwn , and rooted my rom.
I have two questions:
1. Can i have root and cwn with locked bootloader? (guess not .. but not sure)
2. Can i lock again bootloader? say if I flash stock ics via lg tool or..
please don't laugh or something.. i'm new here and curious. (after i rooted my phone and tried a few roms i end up to the conclusion that it's better with bootloader locked and root only)
skate4life said:
Sorry they are a dumb questions , i don't know.
I unlocked bootloader and installed cwn , and rooted my rom.
I have two questions:
1. Can i have root and cwn with locked bootloader? (guess not .. but not sure)
2. Can i lock again bootloader? say if I flash stock ics via lg tool or..
please don't laugh or something.. i'm new here and curious. (after i rooted my phone and tried a few roms i end up to the conclusion that it's better with bootloader locked and root only)
Click to expand...
Click to collapse
I think you can have only root without ul bl,bu there is not known method for locking bl again
Sent from my LG-P760 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2173465
u can root with locked bootloader....
u cannot unlock bootloader again
I have unlocked my bootloader, bricked my device and had to flash the uboot and xboot through fastboot, my bootloader is locked up tight, oem-unlock does not unlock it I would have to go through the whole process again
Sent from my LG-P769 using xda app-developers app
jlirgg said:
I have unlocked my bootloader, bricked my device and had to flash the uboot and xboot through fastboot, my bootloader is locked up tight, oem-unlock does not unlock it I would have to go through the whole process again
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
You just temporally locked it back, it's still unlocked.
Sent from my LG-P769 using xda app-developers app
If it's "temporarily locked" why can I not unlock it without flashing 20b again and going through the whole process again?
Hidden menu says locked - s/w update does not indicate unlocked bootloader
And I still cannot get into fastboot without running the fastboot.Bat through windows
Sent from my LG-P769 using xda app-developers app
jlirgg said:
I have unlocked my bootloader, bricked my device and had to flash the uboot and xboot through fastboot, my bootloader is locked up tight, oem-unlock does not unlock it I would have to go through the whole process again
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
How exactly did you do that? I mean, in noob terms
Go to this post http://forum.xda-developers.com/showthread.php?p=37213010
Flash the ics xloader and uboot then Kdz back to 10g phone seems stock to me and anyone else that's not a computer programmer, normal person would never know it's ever been unlocked
Sent from my LG-P769 using xda app-developers app
jlirgg said:
Go to this post http://forum.xda-developers.com/showthread.php?p=37213010
Flash the ics xloader and uboot then Kdz back to 10g phone seems stock to me and anyone else that's not a computer programmer, normal person would never know it's ever been unlocked
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
what is an xloader and uboot? i tried to follow the tutorial but it didnt work
jlirgg said:
If it's "temporarily locked" why can I not unlock it without flashing 20b again and going through the whole process again?
Hidden menu says locked - s/w update does not indicate unlocked bootloader
And I still cannot get into fastboot without running the fastboot.Bat through windows
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
You don't have to install the 20B again, all you need is it's u-boot.img. If you don't have the u-boot.img, just extract it from the kdz. Open this thread in a browser, and look at my signature.
Sent from my LG-P769 using xda app-developers app