Hello,
as I said in another thread, I bricked my tablet while trying to root it, and made it worse while trying to fix it: it's in a bootloop.
Fastboot mode works still, but no recovery I tried does anything. So I might have fried the bootloader by doing something stupid like "fastboot flash boot <file.img>". I can't remember whether I did this during my desperate attemps of getting out of the bootloop, but if I did, how would I find out?
As far as I understand the boot process (now ), there is a piece of code that initializes the device and then loads the actual bootloader into memory. When I'm in fastboot mode, am I already within the bootloader or still inside that piece of initial code?
When I chose "recovery" or "normal boot", is it first then that the bootloader is started? Or is it already the bootloader that shows those options ("recovery", "normal boot" and "fastboot")?
When I do a "fastboot getvar all" I do get a lot of variables all starting with "(bootloader)", mostly "partition-size" and "partition-type". So is my bootloader still ok and if not, how do I find out whether it's the bootloader broken or the recovery I'm trying to flash, and which one is causing the bootloop?
Thanks for any hints.
Related
So I was on my way to unlocking my boot loader and rooting the phone when i ran into this issue. (i am on AT&T)
The phone is stuck on a Red Exclamation Point and then it reboots to a white HTC screen every minute or two.
Where I was at in the process my bootloader was "unlocked", "tampered" displayed. I had even backed up with TWRP. The thing was I couldnt get the USB Debugging turned on. I turned it on before I started the process and was having trouble finishing with superuser and rooting the device. I had been trying forever to setup the S-OFF Feature to NO AVAIL.
Once I unlocked on HTCdev and then setup TWRP I just could never get the phone back to normal.
Once again this is the INT'L Version of the HTC ONE MAX and I just don't know where to turn next.
Please help. I am without phone and just purchased yesterday.
TIA - Mark
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
shaggydiamond said:
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
Click to expand...
Click to collapse
heres my question how do i know what RUU to search for? how do i figure out which version i need based on my phone?
Thanks in advance.
Mark
Well you say you have the international version? but you got it from at&t so it's carrier branded right?
but first things first, you have to be able to access the bootloader to start the ruu. So can you access it?
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
Then it will tell you the CID. this code is needed when receiving updates from your carrier.
You will need to find the ruu for your CID, any other ruu won't work.
If you find an international ruu for your phone, you can use that one, but you have to have SuperCID.
You can get superCID after you s-off..
If you have SuperCID you can flash any ruu for your device, be careful though, I bricked my htc one s with a wrong ruu.
Goodluck!
the phone is not sold by ATT but is GSM
i cannot access boot loader.
I cant get past the RED EXCLAMATION (so am I bricked?)
this is the phone...
http://www.amazon.com/HTC-One-Max-F...92559809&sr=8-3&keywords=htc+one+max+unlocked
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
also i did find the TRWP backup if that matters or helps....
i tried both commands and it says fastboot is notrecognized as an internal or external command
operable program or batch file.
Well if you cannot access the bootloader, then you can't use fastboot commands..
Can you tell me what button pressing combinations you have used to enter bootloader?
Can you try to power the phone off completely and then just hold volume down?
The twrp backup can come in handy when your phone gets a working recovery, don't delete that
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
i have not been able to power down completely
dankduke said:
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
Click to expand...
Click to collapse
I'm pretty clueless here, If i were you i would keep trying to get in the bootloader. I have had a similar soft brick on my htc one and after half an hour of pressing every key combination it ended up in the bootloader. If that doesn't work I would let it get replaced on warranty
Okay so now I need some HELP.
I took out the SD Card and the SIM Card and the Bootloader screen comes up.
My choices are FASTBOOT, RECOVERY FACTORY RESET, SIM LOCK etc.
What do I do. I feel like I got one chance at this!
And here is my boot loader
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
dankduke said:
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
Click to expand...
Click to collapse
okey here's what you do, you don't have to have usb debugging enabled. that's only for adb purposes. You need to try and access the twrp recovery from the bootloader. If it doesn't work. try and look for the boot.img file of a twrp recovery for your device and flash that through fastboot
So,
I wanted to install a new recovery because i want to try out multirom (http://forum.xda-developers.com/oneplus-x/orig-development/mod-multirom-v32-t3316937).
But when i wanted to flash the recovery I found out that the bootloader is again locked.
I tried to unlock if again but the fist problem was, that it said "error: device offline" every time i did "adb reboot bootloader".
So i just bootet into fastboot myself and did "fastboot oem unlock". Then the program said that it finished and my phone launched TWRP.
I heard that you need to press "Yes" in your recovery but nothing showed up. The phone is still locked and i can`t figure out what to do/ what i do wrong.
I hope you guys can help me,
Andy
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck
Hi,
I tried to install twrp on my device and must have done something wrong. I then tried to use one of the fastboot roms to go back to stock. However, this didnt work and i was unable to boot past the fastboot bootloader. For some reason i then decided to run 'fastboot oem lock' and have locked the bootloader. I understand that was stupid and now i'm stuck at a screen that says 'Your device is corrupt. It can't be trusted and will not boot'. Is it possible to fix this or have i permanently bricked this. Thanks for any answers and i'll happily get any other information you need.
Also i have seen the thread that says to use the msm tool to reflash the stock firmware/unbrick but i can't get the device to go into EDL mode. Every time i hold the volume + and - buttons while booting the device shows up on my pc for about 5 seconds before disconnecting. Sorry if i've misunderstood these instructions but i've tried it so many times and it just doesn't seem to go to EDL mode.
Keep trying with MSM tool. It can be very finicky from what I've heard.
Try different usb ports, maybe different cable or computer.
Since you can start your device it's not really hard bricked and you should be able to restore it completely.
Sent from my OnePlus7TPro using XDA Labs
No need to worry.
Flashing the stock rom with fastboot did not work because you have relocked the bootloader. Unlock the bootloader again with fastboot oem unlock and then flash the fastboot stock rom. It would work just fine and you would be able to boot into stock rom.