Hi guys!
As soon as Google released the factory images for our GNex I downloaded the yakju one and flashed it. All was running fine.
Then I tried to root with Galaxy Nexus Toolkit option for yakju 4.2.2
SuperSU was installed but said no su binary available.
After searching for a while I saw the Chainfire's root method was doing the job for the Galaxy Nexus with 4.3, and applied it to my Nexus.
I can't remember exactly but I think the first restart was fine but I'm not sure.
Now my Nexus is stuck in a boot loop and it can't pass the boot animation. The phone start and show the Google logo, then most of the times I can see the boot animation but suddenly it restarts and the process start again.
Things I've tried before posting:
- Full wipes
- Installing CM10.1 and Gapps from CWM Recovery.
- Restore a backup from CWM Recovery
- Clean install of factory images (takju and yakju, 4.1, 4.22, 4.3)
- Restoring the factory image with ODIN as said in the HOWTO guide in this forum.
- Factory reset with factory images (tajku and yakju, 4.2.2, 4.3) with Galaxy Nexus Toolkit
- OMAP Flash trying to restore some flash memory issues?
By now, nothing works and I'm starting to think that there might be a hardware problem with my Nexus.
So, what you think? Can anybody help me?
Thanks in advance!
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
lovejoy777 said:
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, each Android stock version or custom ROM I've tried, was with it's bootloader.
I mean, bootloader #3 for 4.2.2 and #4 for 4.3
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
lovejoy777 said:
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you a lot, I read you in other posts from today and yesterday looking for a solution to my problem.
By now nothing solved it, but I'll keep on trying.
All your help is welcome, thanks!
Even after installing factory image takju jwr66v I'm stuck in the boot loop:
- Google logo -> boot animation -> restart.
- (sometimes) Google logo -> restart.
I've flashed it with flash-all.bat script and manually and nothing.
Any idea?
u tried odin flash? i
Sent from my Galaxy Nexus
paarthdesai said:
u tried odin flash? i
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes, I tried.
After 20 or more reboots, it showed the screen:
"Android is upgrading...
Optimizing app XX of XX"
And then, bootloop again.......
So extrange.
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
ledoweb said:
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
Click to expand...
Click to collapse
So sorry to read another case.
In mine I can see the bootanimation most of the times.
I really can't understand how the Nexus can't boot properly even after a full wipe or a factory reset using the official factory images (or after ODIN)
As I told before, I'm starting to think about hardware problems, caused or not by the 4.3 upgrade.
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
ashclepdia said:
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
Click to expand...
Click to collapse
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
||M^nnu|| said:
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
Click to expand...
Click to collapse
its sounding more and more like the time i accidentally left mine in a freezer(worked in a kitchen. set it down after using in an industrial freezer that goes -10F !! for over and hour. it just wouldnt boot. after warming up it was as if /data was corrupted. i couldnt do ANYTHING.)
i was pleasantly surprised when it just fixed itself after insane amount of tries of wipes, installs, restores.
good luck! i hope it gets back in working order.
(im also wondering if it might have something to do with the supersu install, as ive read that there has been issues with it and people not being able to get to the symlinked /data things such as the legacy symlink. have you checked to see if there is a "supersu removal" zip you can flash? just in case that helps? or maybe try to fastboot boot the 4.2.2 boot.img? wondering if installing cm10.1 and then fastboot boot the CM stock boot img just in case something isnt installing right with that)
Try fastboot erase commands instead of factory reset in recovery
Maybe this can sounds stupid but, did you check MD5 of the downloaded image? I don't know, just to discard some reasons
Sdobron said:
Try fastboot erase commands instead of factory reset in recovery
Click to expand...
Click to collapse
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
ashclepdia said:
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
Click to expand...
Click to collapse
Thanks haha..didn't think about anyone doing that but you never know lol.
MD5 check would be advised too.
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
OP what computer OS are you trying to do this from? I am wondering if something isnt flashing right due to a windows issue and as others like Sdobron mentioned check the MD5 of the tar.
lovejoy777 said:
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
i am using the shiny ota rom from baldwinguy
you can find it at rootzwiki. i dont know if its posted over here
i havent had any issues at all.(i am also now running faux kernel, he tweeted the 4.3 update just now. running awesome right now)
here is the link
http://rootzwiki.com/topic/36706-ro...tock-android-43-jss15j-no-bugs/page__st__4810
Related
So yea im stuck in a bootloop. My phone all of a sudden rebooted itself and it never went past the boot animation. I am able to boot into recovery and fastboot. When i do a factory reset and system restore then flash a the rom all over again it still bootloops. I dont have a nandroid backup cuz they got deleted from my sd car. Is there anyway to flash it to complete stock through recovery or use adb through recovery flash to stock. please any help would be much appreciated.
stacio88 said:
So yea im stuck in a bootloop. My phone all of a sudden rebooted itself and it never went past the boot animation. I am able to boot into recovery and fastboot. When i do a factory reset and system restore then flash a the rom all over again it still bootloops. I dont have a nandroid backup cuz they got deleted from my sd car. Is there anyway to flash it to complete stock through recovery or use adb through recovery flash to stock. please any help would be much appreciated.
Click to expand...
Click to collapse
I dont know what program u use but i use wugs toolkit and u are able to flash stock from fastboot ive done it plenty of times good luck my friend, oh and dont panic its just a bootloop, you will get it working again, hit the thanks if i helped.
Sent from my Galaxy Nexus using xda premium
leelaa said:
I dont know what program u use but i use wugs toolkit and u are able to flash stock from fastboot ive done it plenty of times good luck my friend, oh and dont panic its just a bootloop, you will get it working again, hit the thanks if i helped.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I used toolkit 5.4 and it worked like a charm Thanks for the advice and assurance buddy, i did panic a bit though. This never happened to me in all my time flashing, well ive gotten bootloops but a quick full wipe and reflash of the rom fixed it, not this time. Thanks again.
stacio88 said:
So yea im stuck in a bootloop. My phone all of a sudden rebooted itself and it never went past the boot animation. I am able to boot into recovery and fastboot. When i do a factory reset and system restore then flash a the rom all over again it still bootloops. I dont have a nandroid backup cuz they got deleted from my sd car. Is there anyway to flash it to complete stock through recovery or use adb through recovery flash to stock. please any help would be much appreciated.
Click to expand...
Click to collapse
Find the yakju Odin file on xda or Google it. Extract and run the exe. Put your phone in download mode (volume down + power) plug it in via USB and wait till it restores your phone. You will have a factory restored 4.0.1 Galaxy Nexus after. Once your phone is restored, you should be prompted for 4.0.2 OTA update.
Sent from my Galaxy Nexus using XDA App
stacio88 said:
So yea im stuck in a bootloop. My phone all of a sudden rebooted itself and it never went past the boot animation. I am able to boot into recovery and fastboot. When i do a factory reset and system restore then flash a the rom all over again it still bootloops. I dont have a nandroid backup cuz they got deleted from my sd car. Is there anyway to flash it to complete stock through recovery or use adb through recovery flash to stock. please any help would be much appreciated.
Click to expand...
Click to collapse
Good to c u solved it, just rember to always have a backup handy, and as long as u can get.into recovery or download mode u should b good,
Sent from my Galaxy Nexus using xda premium
I tried to flash to stock through odin mode and when it's rebooting it shows the Galaxy s3 logo, AT&T logo, and then it reaches the samsung logo and freezes. I'm thinking that the boot image is incorrect but I'm not sure. I tried to use the gs3 toolkit but every option in there requires USB debugging which I can't access since the phone wont boot. Help?
I also cannot find the CWM 5.8.4.7 recovery anywhere I can't restore my nandroid, it says "cannot restore /System" of the nandroid.
The only available CWM i have now is 5.5.X.X.
Nabbu said:
I tried to flash to stock through odin mode and when it's rebooting it shows the Galaxy s3 logo, AT&T logo, and then it reaches the samsung logo and freezes. I'm thinking that the boot image is incorrect but I'm not sure. I tried to use the gs3 toolkit but every option in there requires USB debugging which I can't access since the phone wont boot. Help?
I also cannot find the CWM 5.8.4.7 recovery anywhere I can't restore my nandroid, it says "cannot restore /System" of the nandroid.
The only available CWM i have now is 5.5.X.X.
Click to expand...
Click to collapse
I kept trying to flash the stock ROM and it finally worked so disregard this thread or delete it please.
For anyone's information this all happened after I flashed the Ultimatum ROM while I was on CM9 nightly.
The ultimatum rom flashed successfully and i rebooted it and then...nothing, it was a black screen.
I still had access to the custom recovery and odin mode but even after restoring a nandroid it wouldn't boot.
I don't know why it did this but my stress is your knowledge.
Thanks!
In the future, just boot into the factory recovery after flashing in Odin and do a factory reset.
Sent from my Samsung Galaxy S III
I'm having this same problem, stuck at the Samsung logo. This all happened when I was trying to restore to my backup after trying out a JB Rom, but it gave me an error when restoring system. I then tried to flash back to stock using Odin and here I am. Also I am trying to get to recovery but holding the 3 buttons isn't doing anything. Can anyone help me out?
nvm got it all fixed thank god
For anybody who flashes back to stock from ANY non stock rom. You must boot into recovery after the flash is done and clear your cache else you will get stuck at the Samsung logo
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I am also having a problem after trying to root the phone with Odin3. Here is the error message that I receive:
tz.mbn
boot.img
recovery.img
system.img.ext4
_XmitData_Read
XmitData Fail
Complete (Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I tried it several times and rebooted my computer but it still does not work.
Any idea?
ive looked all over for an answer but cant find anything. i tried to root my att s3 with odin. odin gave the successful message and when i unplugged my phone it only shows me either a samsung logo for a second or a drained battery. it cant be drained as i charged it to full before i started and it only took a few minutes. please help
Action Bob said:
ive looked all over for an answer but cant find anything. i tried to root my att s3 with odin. odin gave the successful message and when i unplugged my phone it only shows me either a samsung logo for a second or a drained battery. it cant be drained as i charged it to full before i started and it only took a few minutes. please help
Click to expand...
Click to collapse
Here is a quick fix... spent my 8 hours, so now I am officially PHD in stuck at boot fix. If solution work, kindly hit the thnx button:
This thread didnt help. However I was able to fix my phone. Since I was not able to boot the phone, I was not able to turn on USB debugging that many softwares inluding the link you have mentioned required. So this is what I did for the benefit of those who may face this in the future:
1. Booted into the download mode vol- + power+ home key
2. When in download mode, I installed clockwork recovrey for ATT Samsung S3 which can be found at many links. I cant paste her as I dont have the rights to post links yet. But the filename was CF-SGS3-CWM-v5.5-v1.0.tar. The file I downloaded had a .tar.md5 ext, I just deleted the.md5 extension so I was left with CF-SGS3-CWM-v5.5-v1.0.tar
3. Than I used Odin and selected the above file as PDA and left everything else at default
4. The phone rebooted but again was going to go into the unending samsung logo. So shutdown the phone.
5. Than I did vol+ + home + power key and THANKFULLY booted into recovery
6. Thereone it was simple, that is restore factory defaults, wipe cache, wipe delvik cache etc etc. and boom. I am back in my phone.
Thank god, almost had a mini stroke!!!
P.S. Had lost root upon reboot. Did many things but device would keep loosing root. I went to CWM recovery and selected "fix permissions" bang.. phone back to how I used to like it rooted and booted!
thank you magn2o
magn2o said:
In the future, just boot into the factory recovery after flashing in Odin and do a factory reset.
Sent from my Samsung Galaxy S III
Click to expand...
Click to collapse
omg thank you so much for that. purchased a rooted cynagenmod att s3. was not happy with it. so i flashed it back to stock rom with use of mobil odin. it was stuck on samsung screen while booting up. so i read and researched a bunch of threads. decided to download odin and another tar. samething happened. if i knew it was as easy as a factory reset it would have saved me some time. is there anyway to just post the fix earlier in the thread. or somehow make it come up as the first link when you perform a search? just asking for other people. just in case .thanks again xda. you guys always come through.
Ace_R1 said:
omg thank you so much for that. purchased a rooted cynagenmod att s3. was not happy with it. so i flashed it back to stock rom with use of mobil odin. it was stuck on samsung screen while booting up. so i read and researched a bunch of threads. decided to download odin and another tar. samething happened. if i knew it was as easy as a factory reset it would have saved me some time. is there anyway to just post the fix earlier in the thread. or somehow make it come up as the first link when you perform a search? just asking for other people. just in case .thanks again xda. you guys always come through.
Click to expand...
Click to collapse
Not working for me.
I'm stuck at Samsung Logo.
Tried to do the factory reset in stock recovery that's loaded after ROM install with Odin, no go.
Installed CWM recovery and tried to do reset / wipe cache/ wiped davlik/ no go
Tried to re-download ROM and tried again, no go.
Tried to load TeamWin recovery and do the same thing no go.
Still stuck at Samsung logo -
Waited good 15 20 min and still stuck
I just had the same problem. Flashing Samsung logo...thought that I was screwed. I tried to keep calm throughout the whole thing...(kind of helped) and did this. After Odin failed a few times I decided to restart my computer. After that it had to reinstall the drivers for the phone, ran Odin again, succeeded. Phone booted normally after that. I would suggest keeping the default settings in Odin as it appears (AutoReboot, etc) and do it that way. So:
1) If fails, restart computer.
2)Run Odin with defaults
3)Let the magic work
4) Enjoy your working phone, or start with number one again.
Hope this helps!
mookie_33 said:
I just had the same problem. Flashing Samsung logo...thought that I was screwed. I tried to keep calm throughout the whole thing...(kind of helped) and did this. After Odin failed a few times I decided to restart my computer. After that it had to reinstall the drivers for the phone, ran Odin again, succeeded. Phone booted normally after that. I would suggest keeping the default settings in Odin as it appears (AutoReboot, etc) and do it that way. So:
1) If fails, restart computer.
2)Run Odin with defaults
3)Let the magic work
4) Enjoy your working phone, or start with number one again.
Hope this helps!
Click to expand...
Click to collapse
PMing probably would have been more efficient. You've revived a 2 month old thread that the user probably is no longer monitoring.
Sent from my SGH-I747 using xda app-developers app
magn2o said:
In the future, just boot into the factory recovery after flashing in Odin and do a factory reset.
Sent from my Samsung Galaxy S III
Click to expand...
Click to collapse
does anyone have the s3 stock rom link? my phone also hangs on the s3 boot screen.
Cheers any help would be great!
wheelswisk said:
does anyone have the s3 stock rom link? my phone also hangs on the s3 boot screen.
Cheers any help would be great!
Click to expand...
Click to collapse
seriously? search the forum, dude. its in the android dev threads. cheers
need help
Tejh said:
For anybody who flashes back to stock from ANY non stock rom. You must boot into recovery after the flash is done and clear your cache else you will get stuck at the Samsung logo
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I will honestly buy you a beer if you can help. I have tried to get past the samsung logo for a while and am still unable to succeed. Please help.
charlielima43 said:
I will honestly buy you a beer if you can help. I have tried to get past the samsung logo for a while and am still unable to succeed. Please help.
Click to expand...
Click to collapse
Pm me if you need help
Sent from my SGH-I747 using xda premium
help
hcyplr29 said:
Pm me if you need help
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Still having problems getting past the samsung logo. Ive even tried to wipe the data and perform a factory reset but I am still getting stuck at the samsung logo. Any ideas?
charlielima43 said:
Still having problems getting past the samsung logo. Ive even tried to wipe the data and perform a factory reset but I am still getting stuck at the samsung logo. Any ideas?
Click to expand...
Click to collapse
Did you also wipe cache and dalvik cache (in advanced settings)?
reply
xBeerdroiDx said:
Did you also wipe cache and dalvik cache (in advanced settings)?
Click to expand...
Click to collapse
I wiped the cache, I cant find where the dalvik cache is located. the only things I can do are get to the download screen and the factory recovery. If the dalvik cache is in the factory recovery, then I havent been able to locate it.
---------- Post added at 10:28 PM ---------- Previous post was at 10:00 PM ----------
hcyplr29 said:
Pm me if you need help
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah could you help me out? I tried wiping the data and cache but im still getting the samsung logo.
charlielima43 said:
Still having problems getting past the samsung logo. Ive even tried to wipe the data and perform a factory reset but I am still getting stuck at the samsung logo. Any ideas?
Click to expand...
Click to collapse
I had this exact same situation when I tried to do a restore after i flashed cm 10. It failed on the system folder and the phone was no longer able to connect to computer. I just reflashed the cm10 and it came back to normal boot and would be able to be reverted back to stock threw Odin. If you flashed the stock firmware I'm surprised its not fixed . but I would just somehow flash a new ROM.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have Galaxy Nexus Maguro and I tried all ways to install jelly bean and it fails and stuck on Nexus logo ... I tried stock ROMs and kernels and Cocked one's but no success. The device work perfectly with all ICE Cream version. Any help or hint or tips will be appreciated.
Thanks in advance ...
alfkhr said:
I have Galaxy Nexus Maguro and I tried all ways to install jelly bean and it fails and stuck on Nexus logo ... I tried stock ROMs and kernels and Cocked one's but no success. The device work perfectly with all ICE Cream version. Any help or hint or tips will be appreciated.
Thanks in advance ...
Click to expand...
Click to collapse
Look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
no luck
efrant said:
Look at the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
More Info Required...
alfkhr said:
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
Click to expand...
Click to collapse
Are you unlocked and rooted?
Have you installed CWM?
If so, can you boot sucessfully to it?
Are you using the GN Toolkit?
Bit more info as to what you have done so far would be helpful...
unsuccessfully
I am very sad http://forum.xda-developers.com/images/icons/icon9.gif
alfkhr said:
First thank you for your response. I followed your procedure but the problem still exist. Stuck on Nexus logo.
Click to expand...
Click to collapse
You need to provide a bit more detail for us to help. Did you flash all the images (including the lc03 bootloader)? Did they flash successfully?
Sent from my Galaxy Nexus using Tapatalk 2
I did all scenarios ...
efrant said:
You need to provide a bit more detail for us to help. Did you flash all the images (including the lc03 bootloader)? Did they flash successfully?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
alfkhr said:
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
Click to expand...
Click to collapse
When you are booted in fastboot mode, does it indicate that you are on the lc03 bootloader and xxlf1 radio?
Sent from my Galaxy Nexus using Tapatalk 2
Hanging When Booting JB
alfkhr said:
All six img files were flashed successfully. Device rebooted and stuck on New Jellybean logo. To be sure what I did is right I did the same steps for ICS img files and it boots to ICS without any problem ,,,
before that I try to use recovery CWM but without luck.
Click to expand...
Click to collapse
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
yes
efrant said:
When you are booted in fastboot mode, does it indicate that you are on the lc03 bootloader and xxlf1 radio?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes boot loader version is lc03 and Radio is xxlf1
mlindema said:
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
Click to expand...
Click to collapse
Yeah it sounds like maybe you didn't wipe man.
Sent from my Galaxy Nexus using Tapatalk 2
Yes I do
mlindema said:
What happens when you boot into CWM?
If you have a JB ROM image on your flash then you should be able to completely wipe the phone (system, data and dalvik (under advanced options)), install the new ROM then boot it up.
Having a phone that hangs during boot is usually symptomatic of not having wiped the phone properly when flashing a new ROM.
Click to expand...
Click to collapse
I did all kind of wipe !!!
Try this: Make sure you have the JRO03C boot and system images handy (i.e., in the same directory as your fastboot.exe file), reboot into fastboot mode and type the following command in a terminal:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash system.img
fastboot flash boot.img
fastboot reboot-bootloader
fastboot reboot
EDIT: Note that it should take 5-10 mins to boot up.
Still
efrant said:
Try this: Make sure you have the JRO03C boot and system images handy (i.e., in the same directory as your fastboot.exe file), reboot into fastboot mode and type the following command in a terminal:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash system.img
fastboot flash boot.img
fastboot reboot-bootloader
fastboot reboot
EDIT: Note that it should take 5-10 mins to boot up.
Click to expand...
Click to collapse
Still nothing ...but there is something I should mention ... I was in JB before one month .. then I got back to ICS cos JB still in the first stages as custom Rom. Then I flags ics miui rom and work great then I flashed miui update and it was corrupted and get many problems till I fix it by going back to stock ICS. Now do you think this is the issue ???
alfkhr said:
Still nothing ...but there is something I should mention ... I was in JB before one month .. then I got back to ICS cos JB still in the first stages as custom Rom. Then I flags ics miui rom and work great then I flashed miui update and it was corrupted and get many problems till I fix it by going back to stock ICS. Now do you think this is the issue ???
Click to expand...
Click to collapse
Going back and forth should have nothing to do with it. But it really does sound like you're not wiping one of the needed things first which mixes your ICS and JB files.
I'd suggest that you download something like CM10 and AOKP build1, go to CWM and do ROM Wipe/Factory Reset, Wipe Cache, and Wipe Dalvik. These are the 3 you need to do. Then install zip from SD - your new ROM. Then install gapps for JB. Boot up. If you use Titanium Backup, don't restore any system data.
Yes I do
netbuzz said:
Going back and forth should have nothing to do with it. But it really does sound like you're not wiping one of the needed things first which mixes your ICS and JB files.
I'd suggest that you download something like CM10 and AOKP build1, go to CWM and do ROM Wipe/Factory Reset, Wipe Cache, and Wipe Dalvik. These are the 3 you need to do. Then install zip from SD - your new ROM. Then install gapps for JB. Boot up. If you use Titanium Backup, don't restore any system data.
Click to expand...
Click to collapse
still the same
Up
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
jakubmi9 said:
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
Click to expand...
Click to collapse
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here
https://developers.google.com/android/nexus/images#razor
Make sure your boot loader is unlocked
Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.
If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.
http://www.wugfresh.com
I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
If it is recognize in fastboot you should be good to go, and yes it will wipe you data unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
If adb is working then you can adb pull your files assuming the file path it not corrupted
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
LinearEquation said:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.
mdamaged said:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
Click to expand...
Click to collapse
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work
Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.
Nexus 7 LTE
Carbon Rom
Faux Kernel
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA
Nexus 7 LTE
Carbon Rom
Faux Kernel
Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,
Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
TWRP will work like that.
fastboot boot twrp-whaetver.img
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yes, so does Nandroid Manager.
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Officially these: http://developer.android.com/sdk/win-usb.html#download
This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
Sent from my HTC One S using Tapatalk
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.