Related
I have a kindle fire which has a CWM bootloader and it has CWM7 ROM on it. but, if i try to install CWM 9 or 10 ROM or Jelly Bean ROM it get stuck on splash screen. I will appreciate it if the gurus in the house can help me on how to install jeally bean on my kindle fire. thanks,
Install TWRP
[Edit:] or COTR
soupmagnet said:
Install TWRP
[Edit:] or COTR
Click to expand...
Click to collapse
My problem is i do no how to go about it. can you please put me through?
XDA member mlkjuggalo has provided a flashable zip here http://forum.xda-developers.com/showthread.php?t=1592681&page=24 in post #232 simply flash this zip from recovery and reboot recovery and you will have the newest twrp make sure you hit his thanx button for making this available. Also you can restore your backup and use smirkit http://forum.xda-developers.com/showthread.php?t=1500935
Thepooch said:
XDA member mlkjuggalo has provided a flashable zip here http://forum.xda-developers.com/showthread.php?t=1592681&page=24 in post #232 simply flash this zip from recovery and reboot recovery and you will have the newest twrp make sure you hit his thanx button for making this available. Also you can restore your backup and use smirkit http://forum.xda-developers.com/showthread.php?t=1500935
Click to expand...
Click to collapse
Please, can you give me a step by step guide on how to do it sir and what is the function of the smirkit? I appreciate Sir.
pelumiv said:
Please, can you give me a step by step guide on how to do it sir and what is the function of the smirkit? I appreciate Sir.
Click to expand...
Click to collapse
Smirkit is a great flashable zip created by XDA member Smirkis that you simply just flash in recovery, then install terminal to change your recovery or your bootloader read his op for full instructions they're fairly straight forward I believe. As far a TWRP flashable zip simply place the zip on your sdcard and flash it from recovery then select reboot no wipes needed very easy.
Thepooch said:
Smirkit is a great flashable zip created by XDA member Smirkis that you simply just flash in recovery, then install terminal to change your recovery or your bootloader read his op for full instructions they're fairly straight forward I believe. As far a TWRP flashable zip simply place the zip on your sdcard and flash it from recovery then select reboot no wipes needed very easy.
Click to expand...
Click to collapse
I have installed the TWRP bootloader and flash this ROM JB-aokp_otter_unofficial. But the kindle still get stuck on splash screen but when i reflash the CWM 7 the kindle boots normally. What should i do to use JB on my kindle, please help boss.
Wipe factory/data reset, wipe cache, wipe dalvik, wipe system, flash rom zip, flash gapps zip, reboot then system if prompted.
Thepooch said:
Wipe factory/data reset, wipe cache, wipe dalvik, wipe system, flash rom zip, flash gapps zip, reboot then system if prompted.
Click to expand...
Click to collapse
Please can you give me the link to the gapps zib? Thanks boss
It is in the OP of whatever rom your flashing.
Sent from my Amazon Kindle Fire using Tapatalk 2
Having same issue
Bootloader: FFF 1.4a
Recovery: TWRP 2.3
ROM: Stock Jelly Bean 4.1.2_r1 for the Kindle Fire
---------- Post added at 10:55 PM ---------- Previous post was at 10:47 PM ----------
Please help
Wipe factory/data reset, wipe cache, wipe dalvik, wipe system, flash rom zip, flash gapps zip, reboot then system if prompted. Initial boot of any new ROM takes a bit but should never exceed 10 mins and I'm rating that on the extreme high end it should be more like 3 or 4 mins. If you continue to have problems make sure you are doing md5 checks on your files and consider restoring your backup and return to twrp 2.2.2.1 .
subwoofer12 said:
Having same issue
Please help
Click to expand...
Click to collapse
The same issue? Really?
The issue in the OP was that he had CWM installed instead of TWRP. Clearly, your issue is completely different.
[url]http://forum.xda-developers.com/showthread.php?t=1644970[/URL]
I've tried with multiple recoveries same issue with all of them, and yeah it's been way past 10 minutes now, about 2 hours, and I always wipe everything including dalvik/battery stats etc everytime before flashing a new rom
Install TWRP 2.2.x
Wipe system and factory reset
Install your ROM or even a different ROM
Do this, and I'm positive you will have success, UNLESS...there are error messages in TWRP that you have failed to mention.
soupmagnet said:
Install TWRP 2.2.x
Wipe system and factory reset
Install your ROM or even a different ROM
Do this, and I'm positive you will have success, UNLESS...there are error messages in TWRP that you have failed to mention.
Click to expand...
Click to collapse
Thanks all for your input. I am now on TWRP 2.3.1.1 and i am still having the same problem.
Did you read what he said? He said use twrp 2.2.x
Sent from my GT-N7000 using Tapatalk 2
asf58967 said:
Did you read what he said? He said use twrp 2.2.x
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much all of you that has contributed to this thread. May God continue to empower you,give you wisdom and understanding. I installed TWRP 2.2.2.1, flash jandycane otter ROM V 1.8.0,flash Gapps, waited like 3mins and kindle fire booted with jellybean. Thanks all so so happy.
very glad it worked for you! and unless you read otherwise stay on that twrp version and you shouldnt have any trouble flashing whatever rom you like
Hi,
I was running 4.2.0 on a Takju Gnex. Attempted to update to 4.2.1 using the Takju link from the Android Police website using Clockworkmod Recovery. Gave me a "Status 7" error. I tried rebooting, and it hung on the Google logo for over 10 minutes. Restarted into Recovery, no longer have a USB mounting option, so cannot connect it to my laptop anymore. If I plug it into my laptop while it's stuck on the Google logo, my laptop recognizes it as an "Android 1.0" device, but won't do anything with it like it used to.
So I can only access the Recovery on my phone, but cannot get my laptop to recognize the device (this wasn't a problem before trying to update).
Any suggestions?
EDIT: I see I can transfer files to my Gnex using adb. Is my only option to just flash a factory 4.2 image and start over?
Same here
I have the exact same problem...
Help would be much appreciated.
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
This might help
mmuzzy said:
- If you get a status 7 error flashing a ROM, try making sure SYSTEM is unmounted in 'mount/unmount partitions' menu in recovery. Thanks to jroid for finding the tip.
Click to expand...
Click to collapse
NeoMagus said:
This might help
Click to expand...
Click to collapse
Could also be that the device is reading that the rom was meant for another model...
OP:
Post three of the guide in my Sig.
I had same issue so I wiped cache ad Dalvik cache and went to fastboot mode and flashed system.img and boot.img also I flashed CWM touch 5.# that is not recommended on 4.2.#
I have made Deodexed rooted ROM of 4.2.1 and it's for takju.. you can find it from GNex Android development section..
aDcOoL said:
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
Click to expand...
Click to collapse
I've done the same and has booted now .....just "upgrading applications" as I type
aDcOoL said:
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
Click to expand...
Click to collapse
you just have to mention that you have to reflash cwm
Also something that may interest you guys. From koush/CWM on twitter:
Holy crap. I just found and fixed the "Status 7" bug that I've been trying to locate for months.
Click to expand...
Click to collapse
aDcOoL said:
This is how I fixed my problem without wiping everything and starting over:
-retrieve system.img from stock 4.2.0 zip
-flash it to my Gnex using fastboot
-flash 4.2.1
-reflash SuperSU to get my root access back
No problems!
Click to expand...
Click to collapse
As a semi-noob who has a bigxie 4.2 with CWM and the stock 4.2.1 system.img file...
...do I boot into CWM recovery, and run just "fastboot flash system system.img"? It's my first time dealing with the .img files and I'm not entirely sure how they're handled yet.
Demon-Xanth said:
As a semi-noob who has a bigxie 4.2 with CWM and the stock 4.2.1 system.img file...
...do I boot into CWM recovery, and run just "fastboot flash system system.img"? It's my first time dealing with the .img files and I'm not entirely sure how they're handled yet.
Click to expand...
Click to collapse
learn how to use fastboot here:http://forum.xda-developers.com/showthread.php?t=1529058
basically you will need do it on command prompt on a windows PC while your phone is hooked up
chickentuna said:
learn how to use fastboot here:http://forum.xda-developers.com/showthread.php?t=1529058
basically you will need do it on command prompt on a windows PC while your phone is hooked up
Click to expand...
Click to collapse
I'm aware of that step, I'm just trying to verify that it's only the system.img file that needs updating, and not the four others (boot, recovery, userdata,radio) that were in the package, and that the command I believe to be correct is the only one that needs to be run to update/return to stock without wiping the phone completely back to empty.
As an update, yes, what I was asking about did work and got me to 4.2.1 with only the need to re-root and put a widget back.
I have the Galaxy S III SGH-i747m model on stock Jelly Bean 4.1.1 ROM on the Canadian Rogers network. (I live in BC)
I have been trying, unsuccessfully, to install a custom ROM. I have rooted and installed Super User, and have flashed the TWRP Recovery ROM v2.4.1.0 I still have the stock kernel and haven't mucked around in the permissions besides installing SuperUser SU app from Google Play store. Right now, I have managed to wipe out my entire internal storage. I have everything backed up on the google server, so I'm not too worried, but I have no OS right now. Regardless, I have tried many times with many different custom ROMs, and everytime I get a Status 7 error and a failed ROM flash. I have been trying for weeks to find out what I'm doing wrong, but can't seem to find anything that works. Can anyone please help me out with a step by step guide to install a custom rom? Heck, even to re-install my stock ROM would be better than nothing at this point. The last guide I tried to follow was Cyanogenmod 10.1. The file was called Liquid Smooth.
I currently have the ROM file and the gapps pakage on my external SD card, but, everytime I try to install it I get that Status 7 error.
Thanks in advance.
AuricPaulin said:
I have the Galaxy S III SGH-i747m model on stock Jelly Bean 4.1.1 ROM on the Canadian Rogers network. (I live in BC)
I have been trying, unsuccessfully, to install a custom ROM. I have rooted and installed Super User, and have flashed the TWRP Recovery ROM v2.4.1.0 I still have the stock kernel and haven't mucked around in the permissions besides installing SuperUser SU app from Google Play store. Right now, I have managed to wipe out my entire internal storage. I have everything backed up on the google server, so I'm not too worried, but I have no OS right now. Regardless, I have tried many times with many different custom ROMs, and everytime I get a Status 7 error and a failed ROM flash. I have been trying for weeks to find out what I'm doing wrong, but can't seem to find anything that works. Can anyone please help me out with a step by step guide to install a custom rom? Heck, even to re-install my stock ROM would be better than nothing at this point. The last guide I tried to follow was Cyanogenmod 10.1. The file was called Liquid Smooth.
I currently have the ROM file and the gapps pakage on my external SD card, but, everytime I try to install it I get that Status 7 error.
Thanks in advance.
Click to expand...
Click to collapse
did you just wipe data/factory reset or did you also format /system?
you're getting the status 7 error because you arent using the latest recovery version. hit me back
xBeerdroiDx said:
did you just wipe data/factory reset or did you also format /system?
you're getting the status 7 error because you arent using the latest recovery version. hit me back
Click to expand...
Click to collapse
Yes...stupidly... I formatted as well, thinking that that might solve the problem. Where can I get the latest recovery version? And, sorry, I'm new, so, not sure what you mean by "hit me back". But thanks for the reply.
AuricPaulin said:
Yes...stupidly... I formatted as well, thinking that that might solve the problem. Where can I get the latest recovery version? And, sorry, I'm new, so, not sure what you mean by "hit me back". But thanks for the reply.
Click to expand...
Click to collapse
in twrp, when you select "reboot" or "advanced", does it give you the option to reboot into recovery? i'm asking as i use CWM, not TWRP
thirty oniesl
xBeerdroiDx said:
in twrp, when you select "reboot" or "advanced", does it give you the option to reboot into recovery? i'm asking as i use CWM, not TWRP
Click to expand...
Click to collapse
Yes, I can reboot into recovery.
AuricPaulin said:
Yes, I can reboot into recovery.
Click to expand...
Click to collapse
make sure you have the correct ROM and gapps (compatible with your model). then i would try a different recovery.
you could download this flashable clockworkmod recovery zip and place it on your external sd card: http://d-h.st/8qP
it's not a touch version. you'll have to use the vol up and vol down buttons to navigate and the power button the select.
in twrp, mount external sd and then flash the CWM recovery like you would a rom. reboot into recovery.
make sure the external sd is still mounted and flash ROM & gapps twice. reboot
---------- Post added at 09:55 PM ---------- Previous post was at 09:49 PM ----------
hit me back is American for "reply back"
I can't seem to do anything now. Did I brick my phone?
Can you not get into recovery any more? If you can why dont you post the links for the rom you are trying to install and we can tell you if its the right one. Also do you have a external SD card to put the ROM and Gapps on
AuricPaulin said:
I can't seem to do anything now. Did I brick my phone?
Click to expand...
Click to collapse
Pbwizkid said:
Can you not get into recovery any more? If you can why dont you post the links for the rom you are trying to install and we can tell you if its the right one. Also do you have a external SD card to put the ROM and Gapps on
Click to expand...
Click to collapse
he has the rom and gapps on the external already.
if you can get into download mode, i'd try restoring via odin
http://forum.xda-developers.com/showthread.php?t=1968625&highlight=stock+firmware
1. Extract contents of the zip/rar archives
2. Wipe data-factory reset/cache/dalvik-cache
3. Plug phone into PC
4. Place the phone in Download Mode (vol dwn + home + power). Press volume up when prompted
5. Open Odin and ensure the COM box is highlighted, detecting your device
6. Uncheck the Auto Reboot option
7. In the PDA box, select the .tar.md5 file you downloaded
8. Flash the file by hitting Start
9. Once you get a Success message, pull the battery and then replace. Immediately go into recovery (vol up + home + power. release power button at Galaxy S3 logo and/or vibrate).
10. Select Wipe data/factory reset, then wipe cache. Reboot
you can then do some research and decide what files/procedures you want to try if you wish to root again and flash custom firmware
Thanks for the help guys. I am attempting to restore my phone right now. Will let you know how it went.
OK! Up and running! And I have it rooted with the latest TWRP recovery image installed. Now I just need to find a good custom ROM. Thanks againg guys!
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
knoll126 said:
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
Click to expand...
Click to collapse
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
dnewha sees
NyPlaya513 said:
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
Click to expand...
Click to collapse
I try to reflash but doesn't seem to work.
knoll126 said:
I try to reflash but doesn't seem to work.
Click to expand...
Click to collapse
USE TWRP!
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
beekay201 said:
USE TWRP!
Click to expand...
Click to collapse
Ok I guess I am just too confused. Downloading TWRP gives me an image file which I don't understand how to install, because I thought I need recovery to do it? When in fastboot I can select recovery but I get the error android.
knoll126 said:
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
Click to expand...
Click to collapse
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
beekay201 said:
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
Click to expand...
Click to collapse
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
knoll126 said:
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
Click to expand...
Click to collapse
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
beekay201 said:
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Mainly because I thought if I had rooted my device and done all this once, I should remember how to do it again. But through ignorance I thought I could and be able to remember the steps and what not. I'll read through it and figure it out, it was just a moment of panic of losing the option of recovery that I have had for a long time and not being able to use it means (or I think it means) I am just stuck of 4.3 for a bit and hopefully the ROM isn't too bad.
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.
Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.
oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes
FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!