Related
I don't really understand this.
When I enter the Hboot menu and navigate to Recovery and try to enter it I get a momentary flash of a HTC white screen and then it immediately goes into Fastboot instead of entering recovery.
I've tried Unrevoked, too. Nothing happens, it just reboots straight back all the way back in.
Any ideas how to get into Recovery mode or try to reset the bootloader sequence?
Hboot 0.80
Radio 5.09.00.08
Once it loads the bootloader do you quickly hit recovery or do you wait a little? Once in bootloader the HTC will prompt some checks about 10 seconds or so and then you should be able to enter recovery.
Have you tried doing it also from a PC? I dont remember well, but I think the adb programs can also put the HTC into recovery directly.
No, I wait until it does the checks.
Can anyone give me some exact info on how to adb to recovery?
My little sister's G2 has been stuck at the hboot screen every time the phone boots. Her phone is completely stock, with the most recent (that I know of) update, the one in PC10IMG.zip. She didn't do anything to damage it at all, it just started booting like this out of the blue.
When at the hboot screen, no buttons work at all, the only way to get out of it is to do a battery pull. I even tried using ADB but it wouldn't detect the phone.
Any suggestions?
first thing i would try is to somehow wipe the phone... push power & volume down to enter bootloader; choose recovery (a red triangle or something like that should appear) then push power & volume up (the recovery menu should appear); then wipe everything...
if this doesn´t work post here again
EDIT: sry, just recognized that i didn´t read your post carefull enough... if your buttons do not work, you probably have to flash a RUU
hoffmas said:
first thing i would try is to somehow wipe the phone... push power & volume down to enter bootloader; choose recovery (a red triangle or something like that should appear) then push power & volume up (the recovery menu should appear); then wipe everything...
if this doesn´t work post here again
Click to expand...
Click to collapse
i booted it with vol down+power, then i pushed vol up+power and it started searching for zips. I had pc10img on it and it found and tried to update with it, but it gave "main version is older! update fail! press power to reboot." and rebooting again brought me to the bootloader.
edit: i don't have any experience with ruu files, so if that's what i need to do, can you tell me how?
Search for a RUU which is similiar or higher than your actual version, download it and put it on your pc... on your phone push power & trakepad to enter fastboot mode, connect your phone with pc and start the .exe on your pc...
Before you do this remove the pc10img.zip from your sdcard and try what i posted before again...
Sent from my HTC Vision using XDA
hoffmas said:
Search for a RUU which is similiar or higher than your actual version, download it and put it on your pc... on your phone push power & trakepad to enter fastboot mode, connect your phone with pc and start the .exe on your pc...
Before you do this remove the pc10img.zip from your sdcard and try what i posted before again...
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
i tried doing this, but it failed, saying that my phone model wasn't right or something like that. but it did make the phone boot into the rom! and it appears to have all of its data still, hopefully everything works now.
rebooting will make the phone enter fastboot still. none of the ruu files i've tried work. is there a link to one that will work? i haven't found any.
ok, before you do the ruu thing, try to do a factory reset (either in the booted rom or through recovery)
here some links:
http://forum.xda-developers.com/showthread.php?t=1074391 (this is a pc10img.zip - you have to put it on your sdcard)
or
http://www.filefactory.com/f/b8dc837b1ed80be8/ (...all official ruu)
pls use the thanks button
htsger 3
i used the pc10img you linked me to. gives me: "main version is older! update fail!"
i tried the ruu files you linked me to and those failed as well. they kept telling me my phone image was wrong or something like that.
Try some from shipped-roms
You'll want to try the 2.15 rom
-Nipqer
Nipqer said:
Try some from shipped-roms
You'll want to try the 2.15 rom
-Nipqer
Click to expand...
Click to collapse
same error as above
I did some thinking and thought that getting it to boot by trying and failing to use an RUU, downgrading it, rooting it there, and then flashing another rom would solve my problems.
I managed to get to downgrading and rooting the phone, but after apparently flashing cwm through rom manager, I turned off the phone and tried to boot into recovery by vol down + power. Those are the buttons I use to boot my g2x into recovery, and through searching I didn't find any other combos for the g2.
That didn't work. I got sent to fastboot again, and no buttons work. I then tried RUU again, and this time it worked, booted. I turned it off and back on to see if it would actually load the rom this time. Alas, fastboot screen again. Still no working buttons.
I tried the PC10IMG.zip again. It flashed, but when it says <Press power to reboot> and I press power, I get sent to fastboot.
I pretty much consider this phone a lost cause, but if anyone has a suggestion that might help, please tell!
I can only tell you that I have same problem, just happened to me y/d and I am stuck on white HTC logo not having adb access and can not flash any stock rom for signature errors. not sure how to continue. thread is: http://forum.xda-developers.com/showthread.php?t=1614042, good luck for both to solve it
if you are stuck at samsung logo after flashing with odin
here's what you have to do:
1. While on Samsung logo. press power key + volume up and down + home button (all together)
2. When the screen is off. Press Power key + Volume Up + home button to enter recovery mode.
3. Wipe Data
4. Wipe Cache
5. Reboot to system
you should be fine right now ^^
cheers!
lexjay said:
if you are stuck at samsung logo after flashing with odin
here's what you have to do:
1. While on Samsung logo. press power key + volume up and down + home button (all together)
2. When the screen is off. Press Power key + Volume Up + home button to enter recovery mode.
3. Wipe Data
4. Wipe Cache
5. Reboot to system
you should be fine right now ^^
cheers!
Click to expand...
Click to collapse
I'm having that problem now. I followed your instructions and got to the recovery mode or "Odin Mode" and it's been saying it's downloading for about 10 min or so. Any idea on how long it should take ?
casual167 said:
I'm having that problem now. I followed your instructions and got to the recovery mode or "Odin Mode" and it's been saying it's downloading for about 10 min or so. Any idea on how long it should take ?
Click to expand...
Click to collapse
Actually I believe it's the download mode that I'm in. It doesn't seem to get to the recovery mode when I press the Volume up key and power button for some reason.. Am I doing something wrong
casual167 said:
Actually I believe it's the download mode that I'm in. It doesn't seem to get to the recovery mode when I press the Volume up key and power button for some reason.. Am I doing something wrong
Click to expand...
Click to collapse
Follow these instructions implicitly.
Hold POWER + VOL DOWN + HOME.
As soon as it restarts change to VOL UP while still holding the other buttons.
Do NOT let go of any of the buttons until recovery boots.
ashyx said:
Follow these instructions implicitly.
Hold POWER + VOL DOWN + HOME.
As soon as it restarts change to VOL UP while still holding the other buttons.
Do NOT let go of any of the buttons until recovery boots.
Click to expand...
Click to collapse
That's what I've been doing exactly but for some reason it just goes right back to the logo screen. I was able to get into the recovery mode one time out of 100 and I went through the process of factory reset but it didn't solve the problem. Now I can't get back into it. It's weird because I have no problem getting into the download mode pressing the volume down but volume up doesn't seem to work. Not sure why or what to do
I'd try reflashing stock recovery then try booting into it again.
If it flashes then you should be able to boot into it.
http://www.mediafire.com/?qyybs0m1yln443x
ashyx said:
I'd try reflashing stock recovery then try booting into it again.
If it flashes then you should be able to boot into it.
http://www.mediafire.com/?qyybs0m1yln443x
Click to expand...
Click to collapse
How exactly would I do that? I'm not to inclined when it comes to this stuff so any help you can give would be appreciated
Install Samsung usb drivers, put your tab into download mode, connect to pc, run Odin, load the file into the AP slot then click start.
http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613
i think i bricked mine...
These are the 2 screens i get whenever i try anything
joker616 said:
i think i bricked mine...
These are the 2 screens i get whenever i try anything
Click to expand...
Click to collapse
You haven't bricked anything, there could be any number of reasons why it won't boot past the logo.
Easiest way to resolve it would be to reinstall the stock rom.
The second image is download mode.
joker616 said:
i think i bricked mine...
These are the 2 screens i get whenever i try anything
Click to expand...
Click to collapse
That's the exact same situation I'm in. Every time I restart it I can't get passed that damn Samsung logo screen. I tried the whole flash with Odin process but I realized that when I connect the tablet to the computer, I get an "MTP Device Driver Failed" message so I'm assuming since the computer doesn't recognize it, even tried with KEIS and it doesn't, that I'm unable to complete the Odin job because that goes until 'Initialization' and stops there. Were you able to fix yours?
casual167 said:
That's the exact same situation I'm in. Every time I restart it I can't get passed that damn Samsung logo screen. I tried the whole flash with Odin process but I realized that when I connect the tablet to the computer, I get an "MTP Device Driver Failed" message so I'm assuming since the computer doesn't recognize it, even tried with KEIS and it doesn't, that I'm unable to complete the Odin job because that goes until 'Initialization' and stops there. Were you able to fix yours?
Click to expand...
Click to collapse
Are you saying you still can't get into recovery mode?
Also what is your device model?
ashyx said:
Are you saying you still can't get into recovery mode?
Also what is your device model?
Click to expand...
Click to collapse
No I can't. I've tried a thousand times in all different sequences of holding the three buttons and it just doesn't go. It's SM-T800. They screen shots on the first page is exactly what I get. Either the logo screen when trying to get into recovery or download mode which it has no problem going into.
casual167 said:
No I can't. I've tried a thousand times in all different sequences of holding the three buttons and it just doesn't go. It's SM-T800. They screen shots on the first page is exactly what I get. Either the logo screen when trying to get into recovery or download mode which it has no problem going into.
Click to expand...
Click to collapse
The two files below should boot you directly into recovery as soon as you start the tablet if you can flash them. Flash with Odin from the AP slot.
Make sure you put the device into DOWNLOAD mode first then connect your usb cable!
You can then do a factory reset and then try and flash the stock rom.
Stock recovery
Twrp recovery
.
ashyx said:
The two files below should boot you directly into recovery as soon as you start the tablet if you can flash them. Flash with Odin from the AP slot.
Make sure you put the device into DOWNLOAD mode first then connect your usb cable!
You can then do a factory reset and then try and flash the stock rom.
Stock recovery
Twrp recovery
.
Click to expand...
Click to collapse
Yeah I tried that too but when I connect the tablet to my comp, I get this 'Samsung Mobile MTP Device Failed' message so my comp doesn't even recognize the tablet. I even tried connecting with KEIS but that doesn't see it either because of that error. Idk if that's related to this issue that I'm having but I'm assuming that since the comp doesn't recognize the tablet because of that error, it won't finish the ODIN job. I get up to 'Initialization' and nothing after. I tried uninstalling and reinstalling the Samsung drivers and that didn't work either. Seems I can't catch a break here
casual167 said:
Yeah I tried that too but when I connect the tablet to my comp, I get this 'Samsung Mobile MTP Device Failed' message so my comp doesn't even recognize the tablet. I even tried connecting with KEIS but that doesn't see it either because of that error. Idk if that's related to this issue that I'm having but I'm assuming that since the comp doesn't recognize the tablet because of that error, it won't finish the ODIN job. I get up to 'Initialization' and nothing after. I tried uninstalling and reinstalling the Samsung drivers and that didn't work either. Seems I can't catch a break here
Click to expand...
Click to collapse
Mtp, kies and anything else is irrelevant, they are OS dependent.
Just put the tablet into download mode. Download mode works in boot loader mode. No need for the os.
ashyx said:
Mtp, kies and anything else is irrelevant, they are OS dependent.
Just put the tablet into download mode. Download mode works in boot loader mode. No need for the os.
Click to expand...
Click to collapse
Ok than Idk why it doesn't go passed the 'Initialization'. I tried multiple times and keep getting stuck on that
casual167 said:
Ok than Idk why it doesn't go passed the 'Initialization'. I tried multiple times and keep getting stuck on that
Click to expand...
Click to collapse
Ok we need to take this step by step as theres something amiss here.
DID YOU AT ANY POINT WHILE THE TABLET WAS WORKING ENABLE 'REACTIVATION LOCK'?
1. Ensure the Samsung drivers are installed (important) Samsung usb driver
2. Before connecting anything to the PC put the tablet in DOWNLOAD mode first.
3. Plug the USB cable into a USB 2 port
4. Wait for the 'ADDED' message (if you dont get this it wont work)
5. Load the tar file into the AP slot.
6. Click START
7. If it doesn't start to flash reboot the tablet directly back into DOWNLOAD mode without touching anything else then unplug and replug the USB cable back in.
8. If it still doesn't flash try ODIN 3.07 ODIN
9. Report back and post a screenshot (if it doesn't work).
ashyx said:
Ok we need to take this step by step as theres something amiss here.
DID YOU AT ANY POINT WHILE THE TABLET WAS WORKING ENABLE 'REACTIVATION LOCK'?
1. Ensure the Samsung drivers are installed (important) Samsung usb driver
2. Before connecting anything to the PC put the tablet in DOWNLOAD mode first.
3. Plug the USB cable into a USB 2 port
4. Wait for the 'ADDED' message (if you dont get this it wont work)
5. Load the tar file into the AP slot.
6. Click START
7. If it doesn't start to flash reboot the tablet directly back into DOWNLOAD mode without touching anything else then unplug and replug the USB cable back in.
8. If it still doesn't flash try ODIN 3.07 ODIN
9. Report back and post a screenshot (if it doesn't work).
Click to expand...
Click to collapse
I know for a fact that I never enabled the Reactivation Lock.. But you know, after literally days and hours including my entire weekend just searching the internet and trying every possible fix scenario that people have tried, I just gave in and sent it to Samsung this afternoon to have them fix it. Nothing I was doing seemed to work and I do believe I tried everything within my little knowledge to try. Let me ask you though, when I get it back in normal working order, would going through the steps to install the TWRP recovery and a ROM prevent me from being in this situation again or at least be able to actually fix it on my own?
If you dont mind tripping Knox and possibly warranty then I believe installing custom recovery is one of the best tools you can Install to a device.
It can get you back to a working state in minutes if you make a full backup.
It's a no brainer to install custom recovery if you intend to root and modify the device in any way.
Hi
I recently received my shiny new M9 and like I have with many HTC phones prior to it unlocked the bootloader installed TWRP (latest beta version) and installed my rom of choice (LeeDroid). For about 10 days now the phone has been great working well on the new rom and all was well with the world.......
Last night the phone rebooted on me and boot looped about or 6 times before finally booting correctly and then behaving normally. Today however the phone is constantly boot looping and failing to boot. I can access the bootloader menu via vol up and down and power button but if i select recovery or download mode the phone simply boot loops over and over. RUU mode also does this.
Once in a blue moon if the phone is left looping over and over it will actually boot into the rom and work ok but as soon as the phone is reset or runs out of juice its all aboard the boot loop express.
regards
Brian
Fastboot commands work however adb commands do not. I have fixed boot loops previously but on this occasion a solution appears to be evading me.
MightyRaith said:
Hi
I recently received my shiny new M9 and like I have with many HTC phones prior to it unlocked the bootloader installed TWRP (latest beta version) and installed my rom of choice (LeeDroid). For about 10 days now the phone has been great working well on the new rom and all was well with the world.......
Last night the phone rebooted on me and boot looped about or 6 times before finally booting correctly and then behaving normally. Today however the phone is constantly boot looping and failing to boot. I can access the bootloader menu via vol up and down and power button but if i select recovery or download mode the phone simply boot loops over and over. RUU mode also does this.
Once in a blue moon if the phone is left looping over and over it will actually boot into the rom and work ok but as soon as the phone is reset or runs out of juice its all aboard the boot loop express.
regards
Brian
Fastboot commands work however adb commands do not. I have fixed boot loops previously but on this occasion a solution appears to be evading me.
Click to expand...
Click to collapse
Sounds like a tricky one, you cant get to download mode to flash a new recovery and cant boot recovery. So if you can do fastboot commands do you mean at the bootloader? If so you are limited without s-off in what commands you can do from bootloader menu. I would be looking for an RUU based on your cid to get you back to stock at this point. You may have to wait. You say adb commands dont work.. have you enabled developer options and installer drivers on your pc?
gffmac said:
Sounds like a tricky one, you cant get to download mode to flash a new recovery and cant boot recovery. So if you can do fastboot commands do you mean at the bootloader? If so you are limited without s-off in what commands you can do from bootloader menu. I would be looking for an RUU based on your cid to get you back to stock at this point. You may have to wait. You say adb commands dont work.. have you enabled developer options and installer drivers on your pc?
Click to expand...
Click to collapse
Dev options have indeed been enabled and all drivers installed I can use adb on my partners phone with no issues. Fastboot commands as you say only work at the bootloader screen,
Sadly I cant even flash a RUU the moment i try it simply reboots the phone back into the bootloop :crying:
MightyRaith said:
Dev options have indeed been enabled and all drivers installed I can use adb on my partners phone with no issues. Fastboot commands as you say only work at the bootloader screen,
Sadly I cant even flash a RUU the moment i try it simply reboots the phone back into the bootloop :crying:
Click to expand...
Click to collapse
Try updating to very latest fastboot, I had to update my sdk a while back as fastboot wasnt working properly with newer phones. Worth a try
Still fubar
Once in a blue moon the phone boots into the rom fine and you can use the phone its very weird I literally am all out of ideas now.
Think im gonna bite the bullet and send it back to Vodaphone and pay to get it fixed. I cannot enter download or recovery mode by any method that I have been advised or have read about thanks to those who tried to help it was appreciated.
Well you can try this in the bootloader. Open up a cmd window with fastboot in the directory and type fastboot erase cache
then type fastboot reboot
Download an ruu for your device. Rename the file to 0PJAIMG.zip
Place it on a sdcard with lower than 32gb and flash it. Need to flash it twice. Directly after each other. All done in download mode
I can'r get into download mode sadly and I have tried many many methods from threads about how to do so. Recovery mode and Downlode mode are just not working hence I think It's going to have to be repaired :crying:
Tecardo said:
Download an ruu for your device. Rename the file to 0PJAIMG.zip
Place it on a sdcard with lower than 32gb and flash it. Need to flash it twice. Directly after each other. All done in download mode
Click to expand...
Click to collapse
worked for me, thanks
MightyRaith said:
I can'r get into download mode sadly and I have tried many many methods from threads about how to do so. Recovery mode and Downlode mode are just not working hence I think It's going to have to be repaired :crying:
Click to expand...
Click to collapse
That's not possible, do u press power and up volume for 10 secs so it restarts and then immediately volume down?
Tecardo said:
That's not possible, do u press power and up volume for 10 secs so it restarts and then immediately volume down?
Click to expand...
Click to collapse
I do indeed and the phone then either shows the battery indicator for about 5 or 6 seconds then reboots or simply reboots. If i selected recovery mode in bootloader the phone just reboots as well.
How did you get into boot loader?
You could choose download there, or reboot into ruu mode
Tecardo said:
How did you get into boot loader?
You could choose download there, or reboot into ruu mode
Click to expand...
Click to collapse
I can get into bootloader by holding power + volume up+down but If I select either recovery or download mode the phone simply reboots normally and commences boot looping again. If RUU mode is selected the phone DOES reboot into RUU mode but if you try and flash the RUU the phone simply reboots and boot loops.
Try placing the zip I mentioned above on SD card.
Still unable to enter download mode via any means so I think it's going to have to go in the freezer till it wont boot and I can send it back
Things I still CANNOT do
Enter Recovery (Phone simply reboots and commences boot loop)
Enter Download Mode (Phone simply reboots and commences boot loop)
If I try and charge the phone with it turned off as soon as it gets power it boots up and boot loops Once in every few hundred boot loops the phone will make it into the rom and will work ok untill eventually it decides to bootloop again after a few hours.
EDIT: For the solution to this particular issue, head to this post.
Hi, yesterday I successfully did a clean install of OOS 4.0, including Magisk and systemless root. I had everything set up as I wanted it.
Today, I tried the 4.0.1 OTA, after using a Canadian VPN server. It downloaded fine (the full zip), and I launched the OTA.
Phone reboots... into nothing. Now the phone won't boot into recovery mode, or start the system. I thought it was odd, so I flashed stock recovery again (which is what was installed). Still can't boot. Then tried just booting into recovery over fastboot mode. Still no luck.
Then I managed to boot into a modded TWRP. That's something... But tried flashing the OTA from its temp location in TWRP. A couple of "command log" errors, but appeared to patch nonetheless.
Reboot to system though: black screen of nothing, again.
Anyone know what might be the issue, and why it happened after just launching an OTA through the stock dialogue?
Cheers :/
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
abobobilly said:
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
Click to expand...
Click to collapse
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
ememeh said:
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
Click to expand...
Click to collapse
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
abobobilly said:
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
Click to expand...
Click to collapse
I can get to a point of backing up if I want to. Though at the moment, I don't know what I'd backup (maybe just the system partition? I dunno).
I have the same thing: Can get the white 1+ logo, both capacitative button backlights show, the android text logo, but then black screen. Very frustrating. Let me know if you have any luck! I'll update here too.
wierd
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
canceric said:
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
Click to expand...
Click to collapse
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
abobobilly said:
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
Click to expand...
Click to collapse
good thing it worked for you, it bugs me that i cant root the phone since the device doesnt get recognised in fastboot ,reinstalled all the drivers and all, nothing works
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
ememeh said:
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
Click to expand...
Click to collapse
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Shayded said:
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Click to expand...
Click to collapse
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
ememeh said:
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
Click to expand...
Click to collapse
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Shayded said:
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Click to expand...
Click to collapse
Weird. Could be a different problem...
Did you get the install success message?
ememeh said:
Weird. Could be a different problem...
Did you get the install success message?
Click to expand...
Click to collapse
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Shayded said:
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Click to expand...
Click to collapse
Can you still boot back into fastboot and/or recovery?
ememeh said:
Can you still boot back into fastboot and/or recovery?
Click to expand...
Click to collapse
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Shayded said:
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
Click to expand...
Click to collapse
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Shayded said:
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Click to expand...
Click to collapse
Just seen the edit. Okay, makes sense. Good luck :good:
ememeh said:
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Click to expand...
Click to collapse
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Shayded said:
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Click to expand...
Click to collapse
Luckily for you, it doesn't sound like a true hard brick. Sometimes power buttons are just funny like this. In my experience at least (I've come back from near death experiences in a similar way to you before).
In any event, well done! Always such a relief to get things working again.