Related
So I am no noob and have unlocked and rooted 50+ androids in my day. I have personally done 12 Atrixs in the last 12 months. Today I got my hands on a free Atrix and decided I'd go ahead and do the norm.
I used the http://forum.xda-developers.com/showthread.php?t=1182871 method which I always do and proceeded as normal.
I ran the script like always and got the failed to boot 0x1000 error like always. Got the phone to run fastboot and ran the fix but on cmd for the first time ever I got the <waiting for device> message that never seemed to stop "waiting." I have never ran into this before and did everything as I normally do... I'm guessing I hard bricked it but have no idea how that could be.
Since I can get the phone into fastboot is there a way to recover the device and retry the method? If not no biggie as it was free and I could really care less as I have my Atrix, a S II and a Skyrocket lying around that I use regularly but would love to get this bad boy up and running. Please let me know ASAP if there is a fix...
Soo when you type cmd and choose your option
if it says "waiting for device " reboot it into "Fastboot mode
make sure u press volume Up
so then phone should read" Starting fastboot protocal" and type Fastboot devices your output should read
List of devices connected
then your device id like TA084327
something like that then type
fastboot oem unlock
ltdanno360 said:
Soo when you type cmd into pc go to your fastboot folder then type fastboot oem unlock
if it says "waiting for device " unplug phone reboot it into "Fastboot mode
make sure u press volume Up
so the phone will read Starting fastboot protocal Then plug into Pc
Click to expand...
Click to collapse
No no no... I run the script from http://forum.xda-developers.com/showthread.php?t=1182871 and I get to the point where it says "Starting fastboot protocal" and then the script tells me to plug in phone. I do and then I hit enter on script and it then says <waiting for device> ...... therein lies the problem.
*Solved
So I have a Telus version of the HTC One X+ 64GB. I have been pretty familiar with flashing roms on samsungs. Wasn't the case so much with the HTC. So I decided to unlock boot loader, root, and flash a custom recovery. Decided to flash this rom from this thread. http://forum.xda-developers.com/showthread.php?t=2219520 not understanding how the boot.img works well guess what I didn't flash that. Now I'm stuck on the Panandriod 3+ boot logo. The phone from my understanding don't seem to wanna charge. Just gets a slow blinking red notification light. When I was able to get into recovery when the battery had charge I was unable to get the ad card to mount so I could add the boot.img to the phone to get fast boot to flash it. I have all the drivers installed on the PC but unsure if maybe the reason that recovery is unable to mount is because of HTC Sync is installed on the PC as well?
The whole reason for trying to flash a rom on this HTC is because I have the HTC One Developer Edition on the way and I wanted to learn as much about flashing HTC as I could so I wouldn't mess up and brick my HTC One when it came. Nowwwww I'm not so confident.
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem. I was able to get some charge thru to the phone when I selected recovery and it went to a black screen with the notification light pulsing red. It seems like its not fully bricked. I tried to use Cmd in windows to try and communicate and see if he phone would respond to the fast boot commands but to no lunch Cmd cannot find the phone. Do anyone know where I could start? Is there a tool kit that can send me back to stock? It was running 4.1.1 any help in the right direction would be great. Thank you guys.
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Hey thanks for replying
I downloaded the pizza boot.img but the issue I'm facing is charging it seems either very very slow on black screen or maybe it's not charging? But main issue is that PC cannot find the One X+ I will try this command but where do I place the pizza boot.img on windows?
The only thing is getting me is I'm getting the sound from windows when you connect a device when I plug the phone in USB but the cmd so far that I have tried even the All in one toolkit don't seem to see that the phone is connect USB in fast boot or boot loader mode. Think this is due to not enough charge? Plus should I just leave it in custom recovery to charge which is a black screen due to it says not enough charge to flash to charge my device?
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
fastboot erase cache
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Corrected.
Gene1985 said:
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem.
Click to expand...
Click to collapse
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Do you have the latest TWRP
Lucky Thirteen said:
Corrected.
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Click to expand...
Click to collapse
Thanks Lucky, I noticed tonight I went thru everything in issues and I noticed that I didn't correctly have SDK set up right on my windows. Hopefully that this is the issue and that when I set it up right that I can fix this problem. This has been far different then Samsung to fix hahaha thanks again and kinda my bad for posting the question. But hopefully that works.
sixcarnage said:
Do you have the latest TWRP
Click to expand...
Click to collapse
No I don't have TWRP I have the recover that came in the noob tool kit. The none touch screen one lol. But I understand a fair bit on what I should have done. I'm gonna try and follow luckies link for the SDK set up and see if I can send the zip file to the phone then flash it in recovery. Just I hope the thing can charge. I had it on the charger for 4 hours today and it still said that there was not enough charge to flash I tried charging it in the boot loop and in recovery.
So I guess the issue is worse. The phone won't charge at all the red notification light blinks red but it don't seem to be charging at all I have looked for fixes and it says flash latest compatible recovery but it won't even discover the phone connected to windows with proper HTC drivers installed
Is your phone capable of booting in bootloader mode?
Lucky Thirteen said:
Is your phone capable of booting in bootloader mode?
Click to expand...
Click to collapse
Yea I am able Lucky. But what I tried today was to get RUU to recognize the phone to do that but no go. So tomorrow I'm gonna do a fresh reinstall on a new laptop of windows and install drivers again and all that. But as for boot loader mode it boots. I click recovery and I get a black screen. I can fast boot USB but I'm not quite sure about USB debugging is still turned on. If it where I'm sure I wouldn't have an issue with the PC not seeing the phone connected.
OK try this in bootloader mode with the USB plug
fasboot devices
Do you have a confirmation serial number?
Will do Lucky. Thanks for your time and patience. I will try this over the night. I really like to try and get this fixed and to understand how the htc works with installing roms and tweaks. I really don't wanna mess up my Develeper Edition of the HTC One that's on the way.
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
Thanks Lucky. I will try this first thing in the A.M I hope that works.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
worked like a charm Lucky. thanks i followed all the steps now im up and running. thanks again.
Great! This is a good news!
Please take the time to edit your OP and change your title to this : [SOLVED] BAD FLASH!!!! NOOB. Possible Brick HELP THANK YOU.
Happy flashing now!
Please help me, I had the ROM from here:
http://forum.xda-developers.com/tmo...-lg-v10-h901-10c-debranded-debloated-t3277305
Then I started playing around with adb and relocked my bootloader without installing anyhing and just running "fastboot oem lock" command
Now my V10 trapped in a loop of security error and wont boot
I can go to the fastboot mode with pressing down "volume down" while I'm connecting the phone to laptop, also have the 3 ".img" files from here
http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
But I don't know how to fix this!
Never Mind, I fixxed it with running commands from bat file inside the KlicKiTool, thanks to ted77usa
Dear Community,
I got my Note 3 Pro Snapdragon Version today and I tried unlocking the bootloader, installing root and TWRP.
Unfortunately after I installed TWRP, WiFi didnt work anymore so I wanted to go back to where I was before.
i tried flashing the GlobalRom with the MiFlash Tool but somehow I'm now stuck with a bootloop.
The phone starts up and shows the MI Logo but doesnt go on. I tried booting TWRP temporarily via fastboot commands so that I can try to flash flashable zip files
but it doesnt let me execute "fastboot boot xyz.img" anymore because my device is locked.
I would really love to hear any solutions or ideas. I dont want any root or something anymore. If someone has an idea Im very happy!!!
thanks a lot in advance and tell me if you need any more infos
Paul/shisaya24
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Alex3oe said:
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Click to expand...
Click to collapse
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
search miui forum for unbrick, there is 2 or 3 method without opening your device
exp: http://en.miui.com/forum.php?mod=viewthread&tid=257227
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
shisaya24 said:
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
Click to expand...
Click to collapse
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Dharani_V said:
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Click to expand...
Click to collapse
Can I do the test point thing myself or is it risky?
What kind of service center? A general mobile phone repair shop or a Xiaomi special one?
shisaya24 said:
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
Click to expand...
Click to collapse
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
I will try that this evening when I am at home again and report. Thanks
Alex3oe said:
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
Click to expand...
Click to collapse
Unfortunately this doesnt work. Phone reboots and shows MI Logo but red light doesnt blink and MiFlash doesnt recognize any devices.
Do you have another idea? :/
How did you unlock the bootloader, via official permission or that unofficial hack?
Sent from my Moto G using Tapatalk
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
shisaya24 said:
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
Click to expand...
Click to collapse
Only options you have right now are:
1) using test points method which is a but cumbersome and voids warranty if you care about that.
2) go to a xiaomi service center of you have any nearby.
It is hard bricked.
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
shisaya24 said:
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
Click to expand...
Click to collapse
Apparently, no! Whenever using unofficial methods, read precautions carefully and you missed all as I can see. Wait if someone can help you out.
apply official unlock. then unlock your device from fastboot mode.
asaharaSK said:
apply official unlock. then unlock your device from fastboot mode.
Click to expand...
Click to collapse
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
shisaya24 said:
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
Click to expand...
Click to collapse
Does anyone know this?
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
smiley1960 said:
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
Click to expand...
Click to collapse
out of sheer desperation I tried MiPhone again and after a few tries, MiPhone started updating the OS. My phone now works again and I have an unlock code as well.
I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!