Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
The only way to unlock bootloader at this time is flashing pudding and then running fastboot OEM commands
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Really? Huh- I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
SevenandForty said:
Oh, really? I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
Click to expand...
Click to collapse
if you're running the ota update, then you don't have an unlockable bootloader. you need to flash a pudding sbf to get one, which you can find instructions to on either the general forum or the dev forum.
Oh, I see. Thanks!
same problem
I also have the same problem but I have a stock 2.3 atrix does it make a difference?
I had to flash the 4.5.91 pre root sbf Via rsd lite then run that fastboot command.
Sent from my MB860 using XDA App
You need to flash the unlock sbf first. Just remember that if you're on 2.3.4, after you flash the sbf, the phone will reboot and soft brick - that's normal. Be ready to fastboot flash RomRacer's CWM recovery, and have the two 2.3.4 Fruitcake builds on your external sdcard beforehand.
Once you've flashed RomRacer's recovery successfully, pull the battery, put in your SIM and sdcard again, boot into recovery, and then install both fruitcake builds.
After that, your phone will boot and you can root it at your leisure.
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
same problem
i have the same problem
1. i did use the sdf. but in the end it says FAIL in RSD
2. cant continue
3. still searching for answer:crying:
---------- Post added at 06:18 PM ---------- Previous post was at 06:07 PM ----------
hammerlock13 said:
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
Click to expand...
Click to collapse
sir, could you kindly pls. give the codes step by step, it will help a lot, i can not use my Atrix Thanks in Advance
OEM unlock is not implemented
I also have this issue
I am desperately looking for a solution without luck for my rooted
Atrix 4G Buld 4.5.2A
GB 2.3.4
If someone can point me to a solution I will be very glad
Thanks
Eli
i'm in the same situation....
help please
FIXED it and now my phone is unlocked
you have to flash the phone with RSD this file http://diamantephoto.com/IHOP_Bell.rar
and rerun the command to give you the phone ID
hope it helps for you
So Guess who got an Atrix today? me! Guess who also probably bricked their atrix today? me!
So here is what happened:
1: I have an unlocked, rooted Atrix 4G from AT&T running 2.2 1.5.7 I believe.
2: I wanted to flash some roms, so I so I attempted to flash tenfar's CWM, but that didn't work, it said install succeeded but I could not get into CWM ( I tried everything, believe me, I'm no noob)
3: I then attempted to flash CWM from Rom Manager and so I did and I flashed the Atrix version, I then hit boot into recovery from within Rom Manager.
4: What I got next is a screen that says "failed to boot 2, starting RSD mode", now I cannot get passed that screen when it powers up.
5: Worst of all, using MSU (moto sw update), it says device is connected but not what kind, meaning I can't restore it, probably because I had adb mode turned on previosly.
update: after attempting to flash a new SBF, the phone told me it failed because the phone did not re-enumerate. Now I have the same problem, but with a new error message on the boot screen: Battery to low to flash!
I have searched everywhere, now I need to resort to you, xda community, Thanks So Much!!!
If you can get into RSD , check to see if fastboot is an option. If you can get into that I would advise to start over by erasing recovery. Command is fastboot erase recovery, then flash romracers recovery thru fastboot. Once you have recovery reboot into it and flash any ROM like Alien, Aura whatever you like.
Alien Atrix
See the thing is, fastboot is not an option , it immediately goes to RSD mode. I may have found a fix, and I am now flashing a new SFB with rsdlite
That's another option, noticed you were on 1.5.7 so I would advise 1.8.3 fruitcake sbf. Make sure you battery is fully charged, if your battery gives out during sbf flash you will hard brick your phone.
Alien Atrix
while I was flashing the sfb, the device failed to reenumerate and now it gives me a low battery warning, with no way to charge it, regardless, I have a friend who will let me borrow his battery tommorrow then Ill try to flash again, really I should use the 1.8.3? I just tried to flash the 1.2.6, so Your saying its ok to go forward with a SFB flash? I come from a world of Samsung's so these are all new to me besides the time I had a backflip for a week (ugh).
Are you sure your unlocked the bootloader? If you successfully unlocked you would have unlocked on top right corner of boot screen and have fastboot also.
Alien Atrix
I'm not sure if I have there is nothing that says "unlocked" at the top of the screen, and I could previously access the recovery and fastboot before this. I did not get this phone new, it came from the AT&T dev center or something like that. My dad works there.
You need to charge the battery. I stripped an old USB cable down and used the red with the positive side of the battery and black with the negative using tape to hold them in place then inserted the battery in the phone and plugged the USB in the computer. This allowed me to flash a ROM and unlock bootloader. Etc.
Warning this could harm you're phone. If you cross the wrong wires or touch more then just negative or positive areas of the phone and or battery. Although I didn't have any trouble with it you might.
If in doubt do it the right way buy a battery charger for your battery, use someone's battery or phone to charge yours.
Sent from my MB860 using Tapatalk
Ok Im at my computer, If you are unsure of unlocked bootloader I now recommend you RSD either 1.8.3 with unlocker & preinstall or the newest is 2.3.4 with unlocker & preinstall read this thread about 3 times first http://forum.xda-developers.com/showthread.php?t=1136261
Unlock using fastboot, after you get phone to boot for first time, ADB commands for preinstall root, after root use Root Explorer app then delete "install-recovery.sh" @ /system/etc.
Now you are ready to install the newest recovery by Romracer 3.2, Tenfars is outdated and no support from the developer. Read this thread 2 times http://forum.xda-developers.com/showthread.php?t=1204500 I recomend flashing this recovery thru fastboot per Romracer.
Now you are ready to flash your choice of ROM, follow proper procedure to flash new ROMs thru Recovery.
Also check out the unlocked sim codes thread in general, unlock sim.
If I helped click the thanks button
what Im confused on is what exactly i should flash if I am stuck in a kind of RSD mode bootloop/soft brick?
On your first post you said you were on 1.5.7 correct?
Atrix first released with 1.2.6 then updated to 1.5.7 then updated again to 1.8.3
Bootloader was unlocked with the 1.8.3 update
I updated to 1.2.6>1.5.7>1.8.3 then followed this tutorial http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader[/UR
ok thanks very much! Ill get back to you later once I get a fresh battery.
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
iCracked said:
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
Click to expand...
Click to collapse
yes, that's what you should have done in the first place. you can't do anything with "ROM" in its name without unlocking your bootloader which is why you're in this predicament. unlocked phone (maybe you mean SIM unlocked, free to use on any carrier) is not the same as an unlocked bootloader.
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
defnow said:
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
pukemon said:
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
Click to expand...
Click to collapse
haha thanks guys, yes I am SIM unlocked and everything just said unlocked so maybe I thought the reason they where specific to carrier locking was the radios? haha but I was wrong
Getting the Failed to boot 3 error.
I've been working at this for days now trying to reflash an sbf image to the phone to no avail. Every single time RSDLite (5.6) gives me the error saying it failed to re-enumerate the device no matter which sbf file I use. I am running as admin, and have all the drivers installed. Any help on this would be VERY much appreciated. Any info you need, just ask.
Hows the charge on the battery.
Sent from my MB855 using xda app-developers app
Well, I keep trying to get it to flash so it runs out a lot but I have a battery charger and I periodically charge it for a few hours. There's no way for me to tell how much of a charge it has but I assume it's somewhere around 75%.
"SVF: 108: 1: 2
Failed to boot 3
Starting RSD mode"
is what is says on the phone.
Always gets stuck on "Waiting for re-enumeration" in RSD Lite.
I get this error:
Phone did re-enumerate after RAM downloader was sent. (0x703e). Phone connected.
This is not much info, we need to know, if you were unlocked, locked, what sbf did you flashed last before this, if you flashed some OTA update, or radio, which sbf are you flashing now, if you can boot into fastboot after this error, and anything, that you think might be important to know.
But if you didn't do anything special, first try redownloaing the sbf.
I never successfully unlocked my bootloader, and I think this is where the brick occured so as far as I know it is locked still. I never flashed any sbf prior to this, I was trying to install a different ROM (I don't like blur very much). As far as I know I am able to boot into fastboot (power + volume up button) and it says fastboot on my phone and when it is plugged into my computer RSD lite displays it as fastboot mode but I can't flash anything to it, it'll give me an error in fastboot. When I hold power + volume down, it says something about NVFlash which I believe is an NVidia tool except the phone just shuts off almost immediately after this. The SBF I am flashing is the Sprint 2.3.5 version, and I've tried downloading and redownloading it from about 4 different locations to no avail. I purchased an external battery charger so I can keep trying different things, so the battery is almost always at a 100% charge. As of now I believe the phone to be unrecoverably bricked, and it's pretty sad because I had the photon for all of maybe 10 hours. Safe to say I've learned my lesson about flashing non HTC devices. My EVO 4G was so easy to do, I guess Motorola really doesn't like people messing with their devices.
Edit: If there is anymore information you think would be helpful let me know.
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
peetr_ said:
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
Click to expand...
Click to collapse
Yes I am able to get into RSD lite, and it recognizes my phone just fine everytime with no trouble. I believe it starts flashing, or it at least creates the image but everytime it gets stuck on "waiting for re-enumeration" and it fails there with an error like "phone did not re-enumerate" or something along those lines. I've tried flashing a 2.3.4 sbf as well but it gives me the same error as if I were to flash one of the 2.3.5 files.
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
peetr_ said:
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
Click to expand...
Click to collapse
Pudding unlock in fastboot gives me the error "Failed flashing process. Unable to retrieve interface handle(0x7027) phone connected."
Deblur gives me the same error as before, "failed to re-enumerate".
The link to the third method is really hard for me to understand. I understand the basics in which he speed hacks it, but I don't understand which files I will need to put in and where to get those files and which ones are correct etc.
I've found the directory with all the .smg files that I'm assuming is the image. Which files would I need to speed hack to have a chance at saving this thing?
Also, my phone fails to flash anything. I'm pretty sure it doesn't actually get anything done except to create the image.
In the command line when I type in "moto-fastboot oem unlock" it says INFOOEM unlock not implemented so I take it that means I'm still locked for sure.
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
bdotr said:
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
Click to expand...
Click to collapse
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
mof9336 said:
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
Click to expand...
Click to collapse
Well it would never get far enough to let me flash a recovery. I'm not able to flash any .sbf's through RSD lite either. The error it gives me every time is "device failed to re-enumerate".
I'm trying it through the ramloader now. I'm pretty sure I'm stuck on an bum electrify install. When I use the electrify ramloader it reboots to a blank screen with the motorola logo on it and when I try to flash derpunlock over through command line it doesn't say anything past "writing 'boot'".
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
****, now I noticed that, you should never ever flash electrify ramdownloader there. You changed rdl signature version. Now you have only the last chance. Download and flash full electrify sbf. But you will have no 4g, no more ota, and I am not sure if it flashes electrify radio or not, so maybe you will have no service.
If you really want, you can try some combination with creating custom sbf for recovering, but you need to read the whole thread in dev section and get much more familiar with that situation.
peetr_ said:
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
Click to expand...
Click to collapse
It now says fail to boot 2. I'm going to try the speedhack when I get home from work today and I'll let you know how it goes. No 4G I can do without, no ota as well I'm fine with. The radio thing might bug me though. So do I drop pudding's CG42 file into the 2.3.5 image while it's being created? Or do I flash just the CG42?
You cannot get unlocked anymore with cg42 from pudding, even with speed hack. You must read whole how to make custom sbf thread if you want to try custom combinations. If nothing will help, your only solution is flashing Electrify 2.3.5 sbf or wait, if some similar photon sbf comes out (I doubt).
I'm really out of ideas to what's causing this so I could use some help.
My tablet has been fine for a long time and has had many roms on it previously. I have been on rooted stock however for over a year now and decided to try a rom again....
However I have tried 3 different roms now all with catastrophic problems. I install them fine through twrp along with gapps then reset Tablet but get a black screen with just a blinking charge light if it's plugged in. No boot logo or anything.
I managed to revert back to stock about 5 times today through flash mode and flash tool but I don't know what's going on.
I rooted, turned on debugging and reflashed twrp but it keeps happening across different android versions too. I thought maybe I had relocked bootloader so I tried to check through adb oem but it freezes, so I ran the unlock command just in case through adb and it was fine but still freezes.
Any ideas?
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
SabertoothTitan said:
To add to this I just downloaded a dialer app on stock to check bootloader unlock status.
It says bootloader can be unlocked but nothing about its actual status. I'm more or less certain this is the issue now so can anyone advise what to do? I manually tried unlocking bootloader and it just restarted like everything was fine but nothing changed.
Click to expand...
Click to collapse
I'm not an expert to be honest but I would try that:
put your tablet in fastboot mode, connect it to your pc and in fastboot type
"fastboot flash boot twrp.img"
Now you should have TWRP.
If this work your bootloader should be unlocked otherwise I think you should see some error in fastboot
Once you have twrp I suggest you to flash resurrection remix 5.7.0 (android 6.0.1). I suggest it just because it worked without problem with my tablet Z.
Something not clear to me: you started just with a rooted stock ROM or you unlocked bootloader, flashed TWRP and then your ROM?
I started with rooted stock rom, I am using dual recovery that seems to be working fine (it was faster since its just a bat file). I originally rooted using kingroot on stock which I used to flash stock rom prerooted with supersu with twrp.
If I try the same process with anything that isn't stock it's black screen on reboot. No Sony logo or anything.
Ive tried changing recovery to newest twrp, changing sd card to a different one, different ROMs including the one you mentioned because that's the one I wanted to try. I also tried with and without black kernel. None made any difference. Black screen boot everytime with just a blinking light on side like its got no OS installed at all.
Just to clarify, my bootloader should be unlocked. I've checked but if I run the adb command to check it just freezes like it's eternally loading. Using dialer go check it doesn't even display anything about it aside from the fact it can be unlocked.
what command do you type? "fastboot oem device-info"?
ok so I have an update, something is definitely messed up with my bootloader.
I tried to relock bootloader from fastboot but its also stuck in a loading cycle for no reason. It seems on some level my bootloader is unlocked because I can flash recoveries fine, but when I come to put a new ROM on the device it won't let me and black screens.
From fastboots I used the commands 'fastboot oem lock' and I just get '...' forever underneath. If I use 'fastboot devices' my device is listed, if I use 'fastboot -i 0x0fce oem unlock 0xbootloadercodehere' it fails the first time, then works the second time and says ok but its clearly done nothing when the device reboots. 'fastboot oem device-info' also leaves me with the '...' on command prompt forever too.
I have no idea what to do if bootloader is screwy at all.
-Pepe said:
what command do you type? "fastboot oem device-info"?
Click to expand...
Click to collapse
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
SabertoothTitan said:
Yup that's what I used. I'm pretty sure bootloader is borked somehow though. I tried reinstall from Sony software too which hasn't changed anything.
Click to expand...
Click to collapse
I just tried with my XTZ and "fastboot oem device-info" just froze, it had 3 dot and nothing else. In my OPO it worked.
I'm gonna search something else...
Whats weird is my tablet also won't install anything on TWRP, I just tried installing SuperSU from it to see if it would work (having to use Kingroot atm) and it just does nothing.
I think this is the issue since I'm factory resetting before installing a ROM, which is therefore wiping my system and when I come to reset because TWRP isn't installing anything its acting like there isn't a system installed.
I can install via ADB fine, just when it comes to recovery... system says no. Its weird because its like its got a locked bootloader or something but even though I reinstalled using Sony software its still the same. If I try unlock bootloader again, I get an error first time then it says OKAY and does nothing.
SabertoothTitan said:
bootloader can be unlocked
Click to expand...
Click to collapse
According to an other post this should mean that your bootloader is locked but can be unlocked via Sony's code. At the same time I've read in the same post (can't find it) that people with unlocked bootloader still have "bootloader can be unlocked" even if they successfully unlocked it...
Unfortunately I can't try it myself because I'm on RR and the code *#*#7378423#*#* (this should be the code you used) doesn't do anything.
I have the code and have used it previously I have also retried it just to make sure.
When I type the dialer code above I get 'bootloader can be unlocked: yes' but nothing mentioning the actual current state of bootloader.
This is what's leading me to think it's a bootloader glitch because all posts I've seen should say 'bootloader unlocked: yes' or 'bootloader unlocked: no'. I get neither.
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
SabertoothTitan said:
Been a few days and had no suggestions. Anyone got any ideas at all outside what I have mentioned? Getting pretty desperate because wifi is really bad on stock, getting constant slowdowns and stalls for no reason. I'm gonna end up trying to sell second hand if I can't do anything.
Click to expand...
Click to collapse
Sorry, I'm out of ideas
The only thing I can tell you is what I did to my XPZ, but I doubt it may help you:
1) Unlock bootloader using Sony's guide
2) XPZ in fastboot mode → from pc "fastboot flash boot twrp.img" (assuming you have the proper TWRP image named twrp in the same folder of fastboot)
3) flashed RR 5.7.0 and Gapps
4) RR change the rocovery to CMrecovery but I "easily" changed back to twrp using a guide under RR thread.