Hi,
I've never posted here before because I've always been able to find info via searches up until this point, but it seems I am the only one who's had this problem?
THE PROBLEM:
I upgraded to JB 4.2 this morning on my GSM Galaxy Nexus. I had CWM recovery. I've never had a problem with it before. I needed to re-root my device so I tried using the tool found here (http://forum.xda-developers.com/showthread.php?t=1392310) and various other methods. None worked.
Furthermore, I noticed that every time I went into recovery it just showed the android lying on his back with a red error symbol above him. I tried re-flashing CWM recovery, then tried TWRP recovery, then even tried re-flashing stock recovery, and all of them give the same result.
Can anyone shed some light on this situation for me? I'm an app developer and I need to have my phone rooted (and I'd like to get the recovery sorted out too), but unfortunately I'm relatively noob when it comes to the inner workings of android.
Any help would be much appreciated!
How are you flashing the recoveries? Fastboot? I had to go back to 4.1, flashing latest recovery with fastboot, and then flash a custom/stock 4.2 using the recovery to achieve root on 4.2.
djluis48 said:
How are you flashing the recoveries? Fastboot? I had to go back to 4.1, flashing latest recovery with fastboot, and then flash a custom/stock 4.2 using the recovery to achieve root on 4.2.
Click to expand...
Click to collapse
Yeah I used fastboot, and I believe that toolkit uses it as well. Did you have the same problem as me?
How did your method work? Did 4.2 make changes to the fastboot, which is what you were getting around? I don't understand why that's a problem that other people don't seem to be having.
Related
I'm totally boggled here, I've never had problems like this. I've rooted my T-999, no problems there, but when I install CWM, either the non-touch or touch versions, it doesn't boot into that recovery. When you recovery boot, either manual or through ROM Manager, it just boots to the stock recovery. I've tried re-installing through ROM Manager and through Odin, to no avail. I'm pulling my hair out...help!
Just use the the root 66 method and then use goomanager to install twrp recovery. Did this process for my brothers S III last night over the phone.
I had the same problem before. Tried multiple ways but the cwm recovery will not stick, even though it appears working in Odin. Only way I got cwm recovery to install is by going back to an earlier version os.
You need to find an earlier version of factory stock jelly bean or better yet ics and flash it with Odin. Make sure it's a factory image. After that just root and install cwm recovery with Galaxy s3 toolkit. Then just install whatever rom you like.
Sent from my SGH-T889 using Tapatalk 2
Ok, trying out these methods and will report back. Thanks.
whatsitsnamenow said:
I had the same problem before. Tried multiple ways but the cwm recovery will not stick, even though it appears working in Odin. Only way I got cwm recovery to install is by going back to an earlier version os.
You need to find an earlier version of factory stock jelly bean or better yet ics and flash it with Odin. Make sure it's a factory image. After that just root and install cwm recovery with Galaxy s3 toolkit. Then just install whatever rom you like.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Why do all that when you can flash the latest through ODIN; and get the correct partition tables setup, and that has root, and then install the recovery via an app? Seems more logical to me.
mt3g said:
Why do all that when you can flash the latest through ODIN; and get the correct partition tables setup, and that has root, and then install the recovery via an app? Seems more logical to me.
Click to expand...
Click to collapse
I was not aware you can install the recovery through an app. I'm not familiar with the process so maybe you can talk the op through it.
When I had my problem with the cwm recovery not sticking from Odin, it was when the jelly bean update was just release for T-Mobile. Just letting the op know that I had the same problem and how I got it working.
Sent from my SGH-T889 using Tapatalk 2
Okay I thought I was missing something. Ya the new update surprised me as well last night with ODIN not working to flash a recovery. It's available in CWM app ROM manager I prefer TWRP though which is available in GooManager via menu>Install OpenRecoveryScript>yes> so long as it says "2.4.1.0" and "D2TMO" then yes and boot recovery to install from there.
I followed mt3g's advice and did the root66 method and then installed via ROM Manager and I had success. Flashing a new ROM now. Thanks!
Cool bro.
Sorry if this is a repeat question, but after searching I still can't seem to find a solution (that I can understand anyway.) I relatively new, having only rooted this phone once before, successfully, but a year ago. I've been reading up for the past two days, but I can't seem to find the soft-brick solution to the new Knox problem.
Short history: Rooted 4.2 a while back, but the speakers stopped working (constant headphone mode) so I thought a software update was finally in order. Did the 4.3 update (not knowing about Knox) to see if that fixed the headphone issue (it didn't) then installed TWRP and tried to install the 4.4 OMNI nightly. After install, it hangs on Samsung logo (soft brick?). Restored to backup, but still hangs. Tried installing SlimKat 4.4, but the install fails. Unsure where to go from here.
Phone still powers up, goes into both Download and Recovery mode. TWRP is the current bootloader(?)/recovery(?).
So, is there a simple reason I'm soft-bricked? I read that Knox is in the bootloader, so is it because I'm using TWRP that it hangs? I find it odd that after restoring to previous settings it still doesn't function. Also, I don't care about the warranty bit, so anything is on the table for me.
Much love to those who spend the time to help out, please link to any resources for me and others who have the same problem. I'll append the working solution to this post for quick access in the future!
Ripptor said:
Sorry if this is a repeat question, but after searching I still can't seem to find a solution (that I can understand anyway.) I relatively new, having only rooted this phone once before, successfully, but a year ago. I've been reading up for the past two days, but I can't seem to find the soft-brick solution to the new Knox problem.
Short history: Rooted 4.2 a while back, but the speakers stopped working (constant headphone mode) so I thought a software update was finally in order. Did the 4.3 update (not knowing about Knox) to see if that fixed the headphone issue (it didn't) then installed TWRP and tried to install the 4.4 OMNI nightly. After install, it hangs on Samsung logo (soft brick?). Restored to backup, but still hangs. Tried installing SlimKat 4.4, but the install fails. Unsure where to go from here.
Phone still powers up, goes into both Download and Recovery mode. TWRP is the current bootloader(?)/recovery(?).
So, is there a simple reason I'm soft-bricked? I read that Knox is in the bootloader, so is it because I'm using TWRP that it hangs? I find it odd that after restoring to previous settings it still doesn't function. Also, I don't care about the warranty bit, so anything is on the table for me.
Much love to those who spend the time to help out, please link to any resources for me and others who have the same problem. I'll append the working solution to this post for quick access in the future!
Click to expand...
Click to collapse
TWRP is your recovery. How were you wiping in between flashes? Sounds like the phone wasnt wiped correctly, causing it to hang. You should be able to flash any ROM zip, because ROM zips dont flash the bootloader, they just flash the system and the kernel. You can flash 4.3 stock tar file in ODIN, but you cant flash anything under 4.3 in ODIN, because tar files flash all parts including the bootloader. If you flash a 4.2 stock tar in ODIN, you will brick instantly.
joeyhdownsouth said:
TWRP is your recovery. How were you wiping in between flashes? Sounds like the phone wasnt wiped correctly, causing it to hang. You should be able to flash any ROM zip, because ROM zips don't flash the bootloader, they just flash the system and the kernel. You can flash 4.3 stock tar file in ODIN, but you cant flash anything under 4.3 in ODIN, because tar files flash all parts including the bootloader. If you flash a 4.2 stock tar in ODIN, you will brick instantly.
Click to expand...
Click to collapse
I used ODIN to flash TWRP, then wiped using TWRP, factory reset/dalvik cache. It seems that the problem was actually with TWRP, however. Apparently it doesn't install 4.4 KitKat ROMs correctly, from another post that I read. I installed PhilzTouch Recovery instead, and it installed just fine. Phone is working just fine running the latest SlimKat, however I still have no audio output.. So, still gotta figure that out.
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.
I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.
An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!
Please help:
I rooted my new HTC One M8 using Hansoons All-In-One Toolkit and was able to success unlock the bootloader and flash TWRP recovery.
I can now enter bootloader and boot into recovery.
The problem is that I cannot seem to flash a ROM..any ROM and have tried 3 different ROMs off the forum but all fail or quickly go back to the main recovery page.
I think I have wiped all the data off my phones internal memory in my desperate efforts to get something flashed so that I can use my phone to make calls.
Where do I go from here? I have tried searching the forum for similar threads but seem to be getting myself even more confused.
Thanks in advance if you take the time to help me. In my case a 'little knowledge has been a dangerous thing'
Bob
fastboot erase cache
Then flash the latest TWRP using fastboot. If you used the toolkit to flash TWRP, the toolkit has not been updated in a long time, so the old TWRP versions might be the problem. Or just a bad TWRP install.
Thanks Red - that sorted it out and I now have Cyanogen installed and running perfectly.
Thank you so so much for you advice and timely help.
Bob :good:
Awesome. And you're very welcome.
Never fails to amaze me how many recovery or flashing problems can be solved by simply flushing cache and re-installing recovery.
bob939563 said:
Thanks Red
Click to expand...
Click to collapse
BTW, there is a button for that.
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.