Related
I had my phone on and it locked up last night. I took out the battery and put it in and the diamond wouldn't turn on.
I plugged it into my computer and the Touch Diamond logo appears for a few seconds, then goes away, then reappears again then goes away. this continues endlessly.
i got my phone to go to the red/green/blue screen which shows my spl number and such. i tried to reinstall a rom, which seemed to work.
after it clears 100% it shows the "touch diamond" logo and redoes the loop mentioned above.
im lost and need my phone badly. any ideas?
CoreGMRConMan said:
I had my phone on and it locked up last night. I took out the battery and put it in and the diamond wouldn't turn on.
I plugged it into my computer and the Touch Diamond logo appears for a few seconds, then goes away, then reappears again then goes away. this continues endlessly.
i got my phone to go to the red/green/blue screen which shows my spl number and such. i tried to reinstall a rom, which seemed to work.
after it clears 100% it shows the "touch diamond" logo and redoes the loop mentioned above.
im lost and need my phone badly. any ideas?
Click to expand...
Click to collapse
Hi
Did you see tri colour bootloader? what are the reading on the tri colour screen?
Without more details we cannot help
Give more details about the spl version and the rom you are flashing
Good luck
diam100 mfg 64m
spl-1040olinex
microp-diam led v11
psox-diam stage_pvt 0x30
i got to here by doing the bootloader button code. it did not just go to tri-coulr
1 more thing. it only will turn on if plugged in.
Well the good news is .....It's not Bricked
Does it say USB at the bottom when plugged into PC?
yes mam!?????
I had this kind of problem with a WINGS. It was a battery fault, not having enough power to fully run the phone at startup. Worked ONLY connected, but with endless reboot. No way to start without connection.
I 've sent the device to HTC (without battery, as usual) and they send it back asking to change the battery. And worked!
sergiopi said:
I had this kind of problem with a WINGS. It was a battery fault, not having enough power to fully run the phone at startup. Worked ONLY connected, but with endless reboot. No way to start without connection.
I 've sent the device to HTC (without battery, as usual) and they send it back asking to change the battery. And worked!
Click to expand...
Click to collapse
i dont think thats the problem. i might put this on the car charger in a bit.
threw it on the dc charger. no luck. i might drive around a bit to get it charged. any other ideas?????
with it turning on hard reset im sure its possible with the device actually turn on try and enter into bootloader mode and flash it to the stock rom...
as i say im not to sure but worth a try.....
to get to tri-coloured screen, just reset and press the volume down key down flash the default stock rom should be fine!!!
I just got to bootloader and tried updating the ROM. it finishes but after install it renters the loop.
fixed!!!!!!! one of the gold prongs on the battery connector was bent. bent it back n it works now.
I told you, It was the BATTERY!
usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...
FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up
hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)
Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA
Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.
Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/
So, I've been seeing A LOT of threads regarding bricked devices (be it soft or hard bricks). So, I decided to create this thread, so everyone with bricked devices post here for help, instead of filling our forums and XDA servers with a load of topics with the same stuff.
If someone knows of a general unbricking thread, please PM me or tag me with a link so I can post on this post.
I will PM a mod to pin this thread to top.
To all brickers,
Before posting, try this thread:{RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick
Remember to give the author thanks
Xperia S Return Back To Stock!
Pre-Requisites
For All The New Users..
If You Did Something Wrong
If nothing is working out
Not Able to Fix
Need to Return Back To Original Firmware?
Here is the Guide For You
Click to expand...
Click to collapse
Return Back To Stock
GUIDE for Better Understanding With Pictures And Images For New Users
Explained Step By Step
Click -- [HERE]
Just a tip: Try downloading Sony Update Service and following the instructions if you get a green LED blink on your phone, which is way simpler to recover without any problems.
Guys My ION LT28h got bricked during a recovery using CWM.
First It was a soft brick, i did something , random pressing of buttons made it worse. its on HARD BRICKED STATE now. Its been more than 5 weeks.
So after some research i found out that my Kernel is ****ed up. My phone is Boot loader Locked, so i cant flash the Kernel separately.
Now few of our fellow xda members told me to unplug the battery cable from the motherboard.
I have successfully disconnected the battery cable from motherboard, i kept it disconnected for one whole night.
Whats the next step ?
Will i be able to flash it with flash tool after connecting the battery to motherboard back ?
Will i be able flash the busted Kernel to a working stock kernel ?
Accidentally messed up and soft bricked Ion- LT28h.
xperia Ion LT28h
ROM: JB 4.1 Pure CyanogenMod Based on CM 10 FXP 218
kernel: GI Kernel v3 or v5
Recovery: TWRP and CWM
Rooted and Unlocked Bootloader
Hi guys, above mentioned were my previous settings. Had occassional reboots and sometimes it was kinda laggy that's why i decided to flash it to another ROM - supposedly to ParanoidAndroid. After following steps to install PA, my phone was on bootloops, was in a hurry then freaked out, i tried soft and hardreset, and tried booting on recovery both on twrp and cwm to flash properly as what was instructed however i may have flashed the wrong zips interchangeably with other roms and kernels resulting to a total messed up ion. i could have restored immediately to a saved CWM or TWRP backup right away however, i only stopped resetting when my phone suddenly stopped responding, no Sony logo, no Xperia logo, no boot, just backlight on, does not turn off, soft and hard reset no nothing. i guess until the battery went dead, then i charged it the whole night.
after reading most threads on recovering softbricked phone, mainly this {RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick thread, and after a couple of days of red led, i constantly charged, i patiently waited(2days) still no green led, however i found out that i can access fastboot. (blue led).. i managed to get to this fastboot mode(blue led) ONLY after i soft reset or power+vol.up/1 vibrate the phone once the backlight lits up- on&off - for about less than a minute then it goes back to red led. (i'll be calling that stage as backlit-on&off-then-back-to-solid-red-led cycle) but then again if i go to fastboot, it will stay in fastboot mode during flashes and it stays there until the battery runs out and goes back to red led. then i charge my phone again, but
during fastboot mode, i have tried flashing the kernel, system and boot image. all via Fastboot command prompt.
and all were successful. there were combinations like, flashing only the kernel, tried flashing kernel and system, tried boot image only, tried all the same time, tried system only, tried different kernels, system and boot img, BUT STILL my phone wont even give me the sony logo screen.
then i thought i may need to wipe cache and userdata so i also erased cache and userdate a couple of times via fastboot mode command prompt. and yes fastboot does detects my phone. it can reboot to bootloader or just the normal fastboot reboot. so i have no issues regarding phone and pc via using fastboot command prompt. and Same thing - all flashes were successful,
i have flashed i think more or less than a total of 50 times, flashing different combinations. Still it goes back to brick mode.. backlit-on&off-then-back-to-solid-red-led cycle.
i'd like to add that i have also tried flashing via fastboot mode using Flashtool. (thunder icon+selecting 'fastboot mode'). i have flashed the kernel and system, tried kernel only, tried both same time, tried system with boot.img tried flashing kernel with boot.img too, tried different combinations. again, all were successful, but still same result.
it only goes back to backlit-on&off-then-back-to-solid-red-led cycle.
a couple of days after it went to green. flashmode finally! thinking everything will now be alright, i decided to flash it using flashtool via flashmode. I connected phone to pc, after the solid red led and after backlit-on&off-then-back-to-solid-red-led cycle. and the it goes back to red led then the backlit on&off cycle, after observing my phone for hours i then knew that after, i guess about a hundred cycle of backlit on&offs it really does go to green led by itself and if i'm connected to the pc and flashtool it stays on green led or flashmode, however if im connected only on a wallcharger it goes to green led but will only stay there for like 1-2 seconds then goes back to red led and then the backlit on&off cycle.
then i thought just maybe my battery really needs to die as mentioned, since upon plugging my phone on to a wall charger it goes immediately to red led and there's really no response on the phone except only if you gonna wait for the backlit on&off cycle the n press power + vol up then it will respond and go to fastboot mode or power+vol down which goes to flashmode. then i decided to reset the battery by carefully unplugging the ribbon cable and i did. well, initially it did (led was off for a moment then changed to blinking red then solid red) but i have to go to work that time and had to continue only after coming home from work, and that did not resolved it.
i may have flashed my ion a hundred times or so to this date, still no luck. i have finally decided to re-locked my bootloader- and yes it is successfully locked now. - thinking PCC/SEUS/SUS would get it back to life but i'm wrong - it just cant detect my phone. PC companion detects it as Phone/Tablet only then after selecting Ion on the phone list it always says my device is upto date and no available software. (sad)
I also noticed that flashtool does not detect my phone as LT28h. It only says that it is connected to flashmode. Is that an issue too. I have tried diff versions of flashtool from 9.6 to 9.11 all same. i have also installed fastboot and adb as well as flashtool drivers, it sayas all were successfully installed however if im connected via flashtool flashmode, none seems to be detected on device manager, tried reinstalling and manually installing the sony sa0103 adb interface driver however after installing i get an error unable to start device. even if my phone is connected still the device on devicemanager still has an excalamation point. i'm using windows 8. i have flashed successfully before when my phone was in good state, however now that im on brick mode it seems that all flashes i've done did not push thru. also those times that i have flashed my ion via flashtool it says something like:
phone should be connected with usb debugging on and enabled install on unknown sources. i have tried flashing it using win7 pc phone was not detected still, however flashtool stated and detected my device was connected on usb debugging mode, but have has errors during flashing though.
since my bootloader is now locked im unable to flash now via fastboot. before bootloader status says- rooted now bootloader status is- ROOTABLE.
i previously owned xperia neo and have managed to flash it successfully without any issues, also this is the 3rd time i had bricked my ion and managed to fix it before..
i also want to ask regarding flashing back to stock - does that mean any stock firmware can be selected? can be .233 / .68 /.20 or the latest ICS 6.1.E.3.7? coz i have basically tried to all of those mentioned. also is the reason that my flashes were not successful is it because i was currently on 4.1 JB ROM and im flashing 4.0 ICS stock? I also have TWRP and CWM backups on my PC and on internal SD card, is there a way for me to flash or restore those backups via flashtool?
I'm running out of options, i'm desperate and on the verge of giving up.
i dont want to believe that i have totally messed up and hard bricked my phone. I do believe that there is a solution to this, and my phone can be recovered without sending it over to repairshop.. Today is the 3rd week and still struggling to get my phone back to life (even just the sony logo) . any suggestions before i unlock again my bootloader? please help. Any help will be gladly appreciated, and many thanks to everyone for spending time on reading my messed up and soft/hardbrick ion experience.
If you brick your device while flashing kernel and device do not respond any way then follow this little difficult but 100% sure method.
- Dissemble your phone.
- Disconnect battery ribbon from motherboard.
- Reconnect battery ribbon.
- Fastly connect USB cable while holding vol +/-
- Flash Kernel or FTF FW.
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Droiiiiiiiiid said:
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Click to expand...
Click to collapse
Did you try SUS ? Official update service ?
Droiiiiiiiiid said:
Just looking for some direction on my Xperia Ion that recently got bricked while attempting to update to JB software.
Currently, it has no response except for plugging into charger giving a solid red light. I am unable to get it into flashmode and have already disassembled and disconnected/reconnected the battery to reset it.
Im gonna guess that the kernel is royally efed up at this point, Im unable to get it into a bootloop either.
What is the next step to solve this issue? Any help is greatly appreciated!
Click to expand...
Click to collapse
I think that you should charge it more to be able to go into flashmode. Maybe until the red light will go off or it'll turn into green. Then try to go into flashmode. Good luck
MozzieZ said:
Did you try SUS ? Official update service ?
Click to expand...
Click to collapse
I was going to but that requires my device be in Flashmode.
Droiiiiiiiiid said:
I was going to but that requires my device be in Flashmode.
Click to expand...
Click to collapse
Read this, maybe it will help you.
http://forum.xda-developers.com/showthread.php?t=2344896
This is my first time got hard brick on my phone. I'm flash wrong ROM (it made for S but I flash it on SL) now my phone totally dead. When I put on wall charger it show constant red led and off several minutes later, try disassemble phone and disconnect and connect ribbon doesn't help to get flashmode and fastboot mode. Any help would be very appreciated.
EDIT: After disconnect ribbon battery I got notification on flashtool "device connected with usb debugging off" but led remains on constant red. Should I try rubber band tricks?
ahlulnugraha said:
This is my first time got hard brick on my phone. I'm flash wrong ROM (it made for S but I flash it on SL) now my phone totally dead. When I put on wall charger it show constant red led and off several minutes later, try disassemble phone and disconnect and connect ribbon doesn't help to get flashmode and fastboot mode. Any help would be very appreciated.
EDIT: After disconnect ribbon battery I got notification on flashtool "device connected with usb debugging off" but led remains on constant red. Should I try rubber band tricks?
Click to expand...
Click to collapse
After disconnecting and connecting back the battery cable , you wont get access to flashboot/flashmode instantly. disconnecting the cable will reset the phone.
If you are getting red led means , its charging on low power. You should keep on wall charging for some hours , say 12 + hours.
After that try flashing the kernel alone , first . you will have to hold the flash mode button for sometime. say 5-10 minutes. then if u have enough charge in your phone it will flash the kernel alone. if u are successful in flashing the kernel, then charge again for some hours , 2-4 hours then try to flash the entire ROM.
Read the Thread Recovering Bricked Phones. This will help. I recovered my phone following the method shown in that thread.
Be patient bro, you can recover your phone, just that it will take some time
Captain Droid said:
After disconnecting and connecting back the battery cable , you wont get access to flashboot/flashmode instantly. disconnecting the cable will reset the phone.
If you are getting red led means , its charging on low power. You should keep on wall charging for some hours , say 12 + hours.
After that try flashing the kernel alone , first . you will have to hold the flash mode button for sometime. say 5-10 minutes. then if u have enough charge in your phone it will flash the kernel alone. if u are successful in flashing the kernel, then charge again for some hours , 2-4 hours then try to flash the entire ROM.
Read the Thread Recovering Bricked Phones. This will help. I recovered my phone following the method shown in that thread.
Be patient bro, you can recover your phone, just that it will take some time
Click to expand...
Click to collapse
Thanks for your fast reply, but I'm already put on wall charger 1 day, and the red led got turn off (no led at all). I think I'll try rubber band trick tonight and leave it till morning.
Hey guys I'm having a problem with my Acro S... It's bootloader is unlocked.
It was soft bricked due to a command I ran on Terminal Emulator (dd if=/dev/zero of=/dev/block/mmcblk0). After inputting that command I safely turned off the phone (Long press Power button, Choose Power off). After turning off, phone was completely dead, no response. It was on 80% battery for sure. It happened last week Saturday (July 20). I then charged my phone for 2days+. On the first day (July 21), no red LED appeared, on the 2nd day (July 22), constant red LED appeared, 3rd day (July 23), red LED disappeared. I then prepared my flashtool for flashing the JB firmware .211 KERNEL ONLY. So I plugged in my phone with volume down pressed, I pressed it for 15mins! My finger was f*cked, after 15mins... nothing happened, RED LED just disappeared and I just heard the Windows USB sound. Flash process didn't start, phone didn't give me a GREEN LED. I tried it again and again and miserably same thing happens, can't go to flash mode. Tried the same with volume up button for fastboot mode but still nothing happens, the RED LED just disappears!
Should I just leave my phone charging on the wall socket even if the RED LED disappeared? To get green LED?
SOMEBODY PLEASE HELP ME! I NEED MY PHONE SO BAD! :crying:
i was installing the prerooted/deodexed stock lt28h rom through cwm in the middle of instalation my phone rebooted and came into a sony bootloop i forced it shutdown by pressing power and volume up now its not starting not even charginig what to do please help :crying::crying:
Flash Tool
Be calm and sit back now put your phone to charger for whole night and then next day download flashtool and a firmware for you device and fladh it your device will breath again.......
tejasvi1 said:
i was installing the prerooted/deodexed stock lt28h rom through cwm in the middle of instalation my phone rebooted and came into a sony bootloop i forced it shutdown by pressing power and volume up now its not starting not even charginig what to do please help :crying::crying:
Click to expand...
Click to collapse
we have desame problem my phone is not charging no ligths/led and cant power on after pressing power and up because im stuck in boothllop after afgrading via OTA.
theprint said:
we have desame problem my phone is not charging no ligths/led and cant power on after pressing power and up because im stuck in boothllop after afgrading via OTA.
Click to expand...
Click to collapse
thks for sharing but i have alraedy solved my hard brick problem my phone is back and running normally
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
bmx4lfe said:
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
Click to expand...
Click to collapse
Hold down the power button and vol down until your phone reboots. It'll take 20 seconds or so, and the capacitive button lights should flash until it reboots.
That should take you to download mode where the RUU.zip on your SD can be flashed.
If that doesn't work, try power + vol up + vol down, then switching to power + vol down when the screen goes black. I think I remember having to do that once when I first got the 10 for a different problem, but it could have been a different device
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Hi
to get to another mode you need to have the phone connected to a PC or Mac, so plug it into the usb and power off, once it is off hold volume down, this should make it go into download mode from there follow this link ( https://forum.xda-developers.com/razer-phone/help/razer-phone-os-t3772424 ) and you should get back to stock and you can retry to root from scratch or leave your phone as stock
Hope this helps
adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
If you got it to download mode but cannot communicate with the phone check your fastboot and drivers. You need Google USB drivers and the absolute latest fastboot. There are other posts here that can help you find the right stuff
adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
tabletalker7 said:
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
Click to expand...
Click to collapse
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
incinandseril said:
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
Click to expand...
Click to collapse
Hi follow the link from my comment above and give yours a try, don't think yours is toast just think it's in a boot loop cycle
My comment is second one down
incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
I´ve got this Screenproblem with the Oreo Update with sideload, it flash but then only this Screen, i found my mistake.
My solution was to do an critical unlock for Bootloader, than install 7.1 and than sideload 8.1 OTA, now it works very fine and much smother than before
[EDIT] After letting the battery run dry again last night, plugging my phone back into my laptop booted into download mode, again with the same display as below. Fastboot again recognised the device & after doing some searching, I'd seen another suggestion somewhere else I hadn't yet tried, which was forcing the phone to partition a (to be honest I couldn't even remember which partition I'd left it in from the attempted root)
The command is "fastboot set_active a && fastboot reboot"
I did this as soon as I was able to, rather than leaving it charging (this may be unrelated, but worth considering if you're still stuck)
after this, I got to the Razer logo screen lock (instead of the blank screen lock below), I was then able to follow Razer's instructions - which are linked in one of the comments on the link from the 2nd post here (hope that makes sense)
Now I'm happy to report everything is working, back to factory
I hope this can help someone else [EDIT]
I'm unfortunately in the same position, did you have any luck flashing back to factory?
I also tried following the guide from the 2nd link, these were the steps I took:
(I can confirm my bootloader is unlocked & critical also unlocked)
1. allowed battery to run dry
2. plugged into laptop whilst holding volume -
3. phone now in download mode with battery charge symbol on screen, I left it some time to charge but noticed it got stuck as per the screenshot (for approx. 6 hours)
4. device not recognised by adb, but recognised by fastboot
5. phone not accepting any fastboot commands, when attempting 'flash_all.bat' just hangs on the first line (flash partition:0 gpt_both0.bin), I have to close command line & reopen to try anything else, however whatever I try I get the same result, so basically the only responses I'm getting from fastboot are that it is aware of the device and confirms the bootloader incl. critical is unlocked
My next thought was the perhaps the phone attempted to boot once it reached the picture charge level and therefore locked in the same way it had initially on the razer logo. Should I attempt flashing the factory image immediately once the phone enters download mode, rather than allowing it to continue charging until it's flashed? Any ideas would be greatly appreciated!
Cheers
Been a while since anybody posted, I know... but did anyone who had this problem end up figuring it out? I am in the same situation and am freaking out a little bit, I JUST got this phone...
Just try this and should solve your problems
https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip