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.
Related
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
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Did u try doing factory reset from boot menu
Sent from my MB855 using xda app-developers app
Yes i did try that along with every other option given system still not booting up... but another strange thing ive noticed is that the android recovery is now letting me choose what zip i want to install from my sd card although i cannot because everything keeps failing the signature check. Has anyone been in this same situation?
I think i flashed the ap20bl.img with sv1 but i havnt flashed the microboot because i didnt know what command to issue in fastboot mode. for the bootloader i typed something along the lines of "fastboot flash rdl3.bin rdl3_unlocked.smg" then i think it restarted to only the moto logo was there and i typed fastboot devices it showed my phone so i took the cg file from derpunlock and typed a command like fastboot flash boot cg42_000somthing.smg it said ok finished... ???
sunny530 said:
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Click to expand...
Click to collapse
are you saying you're on 2.3.5? if you are, your bootloader is permanently locked. it won't do any good to try and unlock it, unless you don't mind bricking. otherwise i have never seen this error before.
if you are on 2.3.5 i'd recommend flashing the electrify 2.3.5 sbf method to hopefully unbrick and return to stock.
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
sunny530 said:
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
Click to expand...
Click to collapse
with 2.3.5 you aren't unlocking anything. can almost guarantee it! it's going to take a miracle! i'd say just restore it with the SBF if possible and continue on with life haha. i rooted like a year ago so i don't remember anything about it at this point haha. the only thing that was important was unlocking the bootloader! we need a breakthrough on that for these locked users. that miracle hasn't happened yet. or even gotten close.
Try flashing signed boot.img. This seems to me like failed to boot 2 in other words.
You can flash almost anything into the phone, the signature is checked after reboot, so "flashing ok" in fastboot is normal feedback, sometimes even if it's not ok (radio).
Also with recovery, you can choose whatever zip you want, but when you hit install, signature is checked.
Well you see i receive no failure to boot 1-4 i just get stuck at the moto dual core screen with nothing written at the top. Is it possible that i flashed the bootloader sucsessfully and did not flash the microboot? i didnt know the command to issue to flash microboot. The unrecoverable bootloader error seems interesting to me how would i find out what kernal i should/can flash and what would be the command would it be in fastboot? can i install a system.img via recovery or install bootstrap through fastboot or stock recovery?
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
hey everyone. trying to OEM unlock the TWRP bootloader. When I type "fastboot OEM unlock" it will reboot into TWRP bootloader, and nothing unlocks. I know this because when I type "fastboot oem device-info" it says "unlocked FALSE".
I have OEM unlock and USB debugging enabled.
This is a phone with previously successfully installed CM13, and now I'm trying to revert to stock/unrooted. I can't seem to flash the recovery at all here because I can't get the damn thing to unlock.
Any ideas?
Did you lock the bootloader ? If your flashing Roms and custom recoverys imagine its already unlocked. Bootloader won't lock itself. If you want full stock just flash any OS2 firmware with twrp. You can worry about stock recovery after. I would just leave the bootloader unlocked won't hurt anything.
I had the same issue not long ago. Finally, i used the mega unbrick guide, but warning, all the data is lost
Ps: Sorry for bad english
hey, thanks for the response. I have been following the following tutorial (and others similar for installing CM13):
(great, website won't let me post it here... it's the unlockr oneplus x guide)
so yes, I originally flashed the stock recovery and replaced it with the one from the tutorial. There were a few hiccups during setup, which may have affected why I can't easily update nightly now, so now I'm trying to revert to the unrooted stock state so I can try from scratch, hopefully fixing the issues I'm seeing now. The problem is that I can't flash the recovery using the stock recovery... I can't even update the damn recovery because it's locked. Is this what is meant by a 'soft brick' ?
Hello ! So I got this one max, it suddenly started to bootloop out of no where. So I decided to unlock bootloader and flash a stock rom.
However, after flashing the unlocktoken, the screen on my one max asks if I'm sure I want to proceed, I select yes but the phone just restarts and the phone doesn't unlock.I said to myself maybe if i flash a firmware it will work, i typed "fastboot oem rebootRUU" but the phone just restarted instead of giving me the black screen with grey HTC logo
HTC DEV website is where you need to go and follow on-screen instructions to completely and successfully unlock your bootloader.
For stock rom flashing you don't need to unlock bootloader unless you're planning on Rooting and installing Custom Recovery, at this point it seems that you're stock. You need to either adb a custom recovery and flash a firmware or you're stuck and only need to adb over stock IMG file perhaps or something of the sort. I would recommend googling this and see what you find.
I myself have a problem... I cannot seem to re-lock my bootloader, I have followed every single guide in the entire world... Including Scotty's Guide here on XDA. I even tried to GURU Zip Aroma Installer, didn't work either. It's a waste of time.
Sometimes you get stuck bad. GL