Okay so i received a new motherboard (NE2 firmware on 4.4.2) today and was rooting and installing a ROM when I got stuck on the att screen. I rooted using towelroot and installed CWM via ROM manger. Made a backup using CWM, then cause Im not used to the buttons to navigate I flashed phils touch. When i tried to flash another ROM i was getting status 7 errors, yes I did a full wipe, tried to toggle the signature but that didnt work either. My backup seems to hang on the att screen which i thought was odd since the CM screen was there after I installed CWM. Any help would be greatly appreciated. What can i do to fix this issue?
Factory reset and it should boot up fine. Need recovery.log for the status 7 error, but most likely either the recovery or the rom is old and won't flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
fixed
it appears that phils touch was outdated and causing the issue. Doing a factory reset from recovery didnt help but I used ODIN to flash a current twrp and its all good now. thanks
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.
So i attempted to root my gs3, i had succeeded in doing so. i had cm10 flash and was looking good but once i tried to flash gapps to my phone, i am now stuck right before the os boots up and get an error message saying that gapps has stopped working and must force close and unfortunately, setup wizard has stopped working. after attempting to recover using twrp, which failed, i tried to flash my recovery zip i had made from titanium backup. now i am still stuck at previously mentioned screen but twrp is now gone and when i boot into recovery mode it comes up with the stock mode. being dumb and thinking that the recovery from titanium would be enough i didn't make a back-up using nandroid. i can still get to download mode as well as recovery mode but i am not entire sure if usb debugging mode is still on or not. i have odin downloaded on my computer but am not entirely sure on how to go about restoring my phone. at this point i'd be happy just to get it back up and running stock. can anyone help?
Update:So i downloaded a stock rom and tried flashing it using odin and now i am stuck on the samsung splash screen. been waiting about 5 min. but would still appreciate any input if possible
Teeter89 said:
So i attempted to root my gs3, i had succeeded in doing so. i had cm10 flash and was looking good but once i tried to flash gapps to my phone, i am now stuck right before the os boots up and get an error message saying that gapps has stopped working and must force close and unfortunately, setup wizard has stopped working. after attempting to recover using twrp, which failed, i tried to flash my recovery zip i had made from titanium backup. now i am still stuck at previously mentioned screen but twrp is now gone and when i boot into recovery mode it comes up with the stock mode. being dumb and thinking that the recovery from titanium would be enough i didn't make a back-up using nandroid. i can still get to download mode as well as recovery mode but i am not entire sure if usb debugging mode is still on or not. i have odin downloaded on my computer but am not entirely sure on how to go about restoring my phone. at this point i'd be happy just to get it back up and running stock. can anyone help?
Click to expand...
Click to collapse
If you have Odin already you need to just download the stock rooted rom and flash it. Make sure when you flash a custom Rom that your recovery is up to date and you download the correct gapps package.
Ignore any file names. The video is just too get you accustomed to Odin.
https://www.youtube.com/watch?v=OqinDlH4hII&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Boot into stock recovery, the perform a factory reset. Reboot and enjoy.
Sent from my SGH-I747 using xda app-developers app
After flashing the stock rom in ODIN, boot into recovery and wipe data and & the cache. Reboot
Stock roms
Teeter89 said:
So i attempted to root my gs3, i had succeeded in doing so. i had cm10 flash and was looking good but once i tried to flash gapps to my phone, i am now stuck right before the os boots up and get an error message saying that gapps has stopped working and must force close and unfortunately, setup wizard has stopped working. after attempting to recover using twrp, which failed, i tried to flash my recovery zip i had made from titanium backup. now i am still stuck at previously mentioned screen but twrp is now gone and when i boot into recovery mode it comes up with the stock mode. being dumb and thinking that the recovery from titanium would be enough i didn't make a back-up using nandroid. i can still get to download mode as well as recovery mode but i am not entire sure if usb debugging mode is still on or not. i have odin downloaded on my computer but am not entirely sure on how to go about restoring my phone. at this point i'd be happy just to get it back up and running stock. can anyone help?
Update:So i downloaded a stock rom and tried flashing it using odin and now i am stuck on the samsung splash screen. been waiting about 5 min. but would still appreciate any input if possible
Click to expand...
Click to collapse
=====================================================
Sometimes when you search the for the stock rom they don't give you a good or the actual stock rom i get mine from sammobile.com
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
EgoTrip26 said:
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
Click to expand...
Click to collapse
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
soupysoup said:
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
EgoTrip26 said:
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
Click to expand...
Click to collapse
Just flash recovery then cm rom.
Sent from my SGH-M919 using Tapatalk 2
Thanks a million!
Thanks to both of you for prompt response, Used TWRP and at least got CM to flash and startup, so far so good. hope it works as well on the S2 as it does on my phone!
Thanks again
I've searched around for this specific problem and haven't found anything that will help me. I have the SPH-L710 model through Sprint that was previously running Android 4.4.2. That version killed the battery, so I attempted to root and install a custom ROM. I have rooted before, so superSU was already on the phone. I opted to follow the rooting directions from galaxys3root.com, which uses ClockworkMod Recovery v5.5.0.4. I did that and installed superSU again via a .zip file. When I rebooted the phone, superSU kept stopping. After some frustration, I found that there was an updated superSU v2.01 that I installed via CWM. Being an idiot, I figured I would just go right ahead and trying to install the custom ROM without checking anything. I then attempted to install the Carbon ROM 4.4.4 from galaxys3root.com without first making a backup of my existing version (again, idiot). There was some sort of error, and after that point, I was unable to boot up the phone...it would display the Samsung GS3 screen and then do a continuous bootloop.
I tried finding stock ROMS, but they usually have to be loaded from the SD card rather than through ODIN, and they so far haven't been working. I have downloaded more than one that claimed to be an MD5, but they turned out not to be. My wife has the exact same phone so I thought maybe if I use CWM to save a backup of hers to my SD card, perhaps I could restore that and boot up my phone. I got a bit farther this time and boot up made it through the Samsung GS3 and various Sprint 4g screens before getting stuck on the last Samsung screen.
If I can get the phone to boot up again, I've since learned that once you update superSU, you can have it disable knox, thereby allowing me to root, and thereby allowing me to install a custom ROM, but at this point I just need to get the phone to boot up so I can use it again.
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt
huntley said:
Summary:
Attempted to root using CWM v5.5.0.4
Did not properly disable Knox first and had an error loading custom ROM
Phone stuck in bootloop
Did not back up phone first but have a backup of my wife's exact same model
Used that backup and it gets stuck on very last Samsung screen
Any and all help is appreciated.
Matt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)
6th_Hokage said:
http://forum.xda-developers.com/showthread.php?t=2738533 <-----Odin stock ND8 rom use Desktop Odin
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5/ <------flash this recovery through Odin as well it gives you the option to root the stock ND8 rom under Philz settings choose option re-root(SuperSU)
Click to expand...
Click to collapse
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.
huntley said:
Thank you. That image worked perfectly, and the recovery is a newer version than I was trying to use earlier.
Click to expand...
Click to collapse
i know lol but its the best one for stock ND8 honestly
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.