PLEASE READ Nexus 4 stuck in a bootloop (softbricked) - Nexus 4 Q&A, Help & Troubleshooting

This is my first time posting a thread, so I'm very sorry if its in the wrong place.
I've had my Nexus 4 for over a year now and over the past 1-2 weeks it has kept on randomly rebooting and freezing, so I decided to install a custom rom on it (prior to this I had not modified my phone in any way), this was something which i've wanted to do for a long time.
The last time I installed a custom rom and rooted a phone was on the samsung galaxy ace around 2-3 years ago.
the first thing I did was backup the data which I needed. Then I turned on USB debugging and unlocked my bootloader and rooted my phone (my phone is running android 4.4.2) this all went without a hitch. I turned on my phone and superuser ( the version of superuser was chainfire's 0.99) was there. Then I downloaded Paranoid Android, it was the third one down in the mako section of paranoid android. Then I downloaded gapps.
I watched a tutorial on how to flash a rom via cwm but the tutorial forgot to mention making a backup, and me being a bit of a noob it didn't occur to me. When I was installing Paranoid android it said something like "no folder context" and then it said installation aborted ( I had done a factory reset,wiped dalvik cache and wiped cache) gapps installed perfectly but my phone was now in a bootloop. It would turn on and get to the Google logo, where it would stay for a few minutes and then turn off again and do the whole thing again or it would turn on and go straight to cwm.
then I read a tutorial on how to flash the stock rom and followed it word for word but that ended up unmounting my sd card.
Then I read this tutorial:http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 and made sure I followed it word for word but at one point it said that there wasnt enough space but the installation still finished but did nothing, I tried again today with my phone in safe boot mode ( the one where you press volume down and power together) and it was all going fine until I got to step D.9 (fastboot flash system system.img) at this point my computer froze and cmd stopped working, I could not type anything into it even when my PC unfroze.
I tried this tutorial a number of times before and sometimes it would fail on some parts and keep going and on others it would fail and then say press any key to exit.
I hope I've provided enough information here and would be extremely grateful if someone would help me out as I really need my phone because I have exams coming up and i use my phone to plan my revision and to talk to people about the work etc. If anyone can help, please do, thank you very much for reading.

Have a look at these to put the rom in the sdcard partition and then flash it by recovery
http://forum.xda-developers.com/showthread.php?t=1392310
http://forum.xda-developers.com/galaxy-nexus/help/files-to-sd-card-fastboot-mode-t1542980
Sent from my Nexus 4 using Tapatalk

Related

[Q] Can't install ROM's on Wildfire, please help

Hey Guy's could somebody give me some advice here as i'm well and truly stuck with adding ROM's to my wildfire. . .
Right i'll try break this down as easy as i can, i bought my wildfire 3 days ago, and its running 2.2.1, i watched one of the latest video tutorials on how to root using Unrevoked (which i now know doesnt work), I installed HTC Sync to get the drivers, then uninstalled it. I then Added the modded Android USB Drivers. Run Alpharex to change my Hboot, and set to S-Off, Then tried running the latest version of Unrevoked, i got the dreaded "Is your firmware to new" message. . . I've always got debugging mode running and allow 3rd party apps!
I then mentioned this to somebody who told me of a different way around rooting my device so . . .
I then downloaded Gingerbreak.apk, then i got Astro off the Market and run Gingerbreak, my phone restarted and WAYHEY I've now got superuser access!
I got ROM Manager off the Market, then i downloaded Clockwork recovery mod 2.5.0.7, CM 7.03, Gapps 20110115, formatted my SD to fat32, put the zips directy onto the root of the SD card. . .
I made a flash recovery, go to install ROM from SD, phone restarts then i get the "Red Exclamation mark triangle"??? i've tried two different SIGNED versions of CM with no luck with either. I've tried running the Anonimo ROM and yet again i get the same red exclamation mark. . .
I've manually tried running recovery from hboot and yet again i get the same problem. . . .
I'm not doing nothing wrong here am i? As ive watched/read/researched dozens of how to's and followed every step exactly as it says!
I will be watching this post constantly as i'm itching to get rid of this nasty FROYO.
Thank you for your time.
I just had to reboot into recovery from hboot menĂ¹ and selected the zip I put there before (SD root)... If you're trying to istall cm then you don't need to use Rom manager, u can use the usual recovery.
I just tried to istall the latest CM Nightly Builds and 7.1.0 release candidate, I dind't have problems!
EDIT :
Oh dude, it seems you don't have recovery istalled, just follow this tips :
Put the file attached into root of your sd card, then power down your phone, and boot into hboot menu.
let the phone check for a "PC49IMG.zip" file and then press volume up.
after that remove the "PC49IMG.zip" from your sd card and put the rom you want to istall always into root of your sd card, then just istall the rom from there!
Install Clockworkmod Recovery on your NAND Memory. There are 2 ways to achieve this:
1) Using Fastboot: (My preferred method)
http://forum.xda-developers.com/showthread.php?p=14693680
2) PC49IMG
http://forum.xda-developers.com/showthread.php?t=1130044
If you face issues using the Fastboot technique (I haven't tried the other one), let me know, I'll help you sort it out.
WOW!!!!! It's actually doing it!!! You've both got a thanks vote off me but one thing now (sorry) . . . . ive rebooted my phone and its shown up the blue cyogen mod 7 screen with the blue circle, and it spins round a few times then shows the droid on the skateboard again and starts spinning again, its been doing this for way over 10 minutes now, is there something missing? do i have to boot Gapps from recovery off my sd card before i restart?
MC-ARNIE said:
WOW!!!!! It's actually doing it!!! You've both got a thanks vote off me but one thing now (sorry) . . . . ive rebooted my phone and its shown up the blue cyogen mod 7 screen with the blue circle, and it spins round a few times then shows the droid on the skateboard again and starts spinning again, its been doing this for way over 10 minutes now, is there something missing? do i have to boot Gapps from recovery off my sd card before i restart?
Click to expand...
Click to collapse
No, Its not necessary to flash GApps beforehand. What you are getting is a bootloop.
Reflash Cyanogenmod, but, before doing that, make sure you do a wipe. (Factory Reset / Data Wipe Option in Clockworkmod). Also make sure you wipe cache, dalvik cache (Under advanced), and format /system partition (Also under advanced)
After clearing all this, then reflash the CM Zip file and try again.
Thank you kind sir i did these exact steps just after i wrote my last post and i'm now VERY HAPPILY running 2.3.4
Only problem i've come across so far is the vibrate option for calls/texts in any status (silent etc) doesnt work whats a bit of a shame, but with the improvement in my handset i won't complain!
I could get used to this android business
MC-ARNIE said:
Thank you kind sir i did these exact steps just after i wrote my last post and i'm now VERY HAPPILY running 2.3.4
Only problem i've come across so far is the vibrate option for calls/texts in any status (silent etc) doesnt work whats a bit of a shame, but with the improvement in my handset i won't complain!
I could get used to this android business
Click to expand...
Click to collapse
Glad your sorted!
Sent from my HTC Desire using Tapatalk

Boot Loop and my efforts to fix it, all failed. Help?

Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.

I survived the Encryption Unsuccessful error unscathed?!

I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.
I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.
Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.
Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?

[Q] I accidentally deleted my OS

Hi forum, this is my first time here. So I will try to keep it short and simple. I bought a mint Nexus 7. The previous owner had it rooted and it was on 4.1.2. I Saw the 4.2 update and tried installing the update over the air. When the device tried restarting, instead of going back to booting normal, it went into this thing called team win recovery project. I have noticed some stuff:
1. It says my device has on OS.
2. Its stuck there in my TWRP thing and I cant access my OS
2. my PC wasnt recognizing the device (I fixed that though by downloading the driver from Asus's website)
So long story short, I just want my device to be back to normal and unrooted. If its possible. Please if anyone can spare me there busy time, I would really appreciate it
Just read up on this thread. Best collection of all the proper information.
http://forum.xda-developers.com/showthread.php?p=27963969
Sent from my Nexus 7 using xda premium
youve got a custom recovery, you cant install an ota. but you can manually flash a rooted stock rom if you want. twrp is a great custom recovery btw. you can boot up from its menu, or you can force reboot it by holding down the power button for about 20 seconds.

nexus 7 stuck on android is upgrading

i have a nexus thats completely stock( out of the box) worked fine for about a month, let the tablet die and has been unplugged for about a week. got it charged up and and would not turn on. using the nexus root toolkit i was able to get to turn on. unlocked the device( unlock logo below google icon on startup) was unable to get past that point. now finally i can get past the nexus boot logo but it gets stuck on aindroid is upgrading " optimizing app 1 of 11" i cant root using the root tool kit bc when i unlocked device it got rid of developer options ( by what the msg said before i unlocked). im simply trying to get my device to turn back on. i dont plan to root or install a rom, im fine with the stock rom. i just want to damn device to turn back on. when i was able to power on the device when i first got it i did upgrade to the newest jelly bean rom. any one can help me on this issue ??
thanks
Boot into temporary custom recovery using Nexus root toolkit(Advance menu). Now wipe cash and devlock than try rebooting into system. If it doesn't work you can try factory reset. Last but not the least will be Flash Stock + Unroot(Soft brick/boot loop).
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
dac2009 said:
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
Click to expand...
Click to collapse
If the factory reset doesn't work just go for the Flash. I don't think you are much worried about the data so it's not a big deal for you. and I'm quit sure this is gonna work. Best of luck.
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
dac2009 said:
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
Click to expand...
Click to collapse
Okay, that's weird!!!
Are you using Nexus Root Toolkit?? If yes are you using pre-downloaded android??
Try Automatically download + Extract.....
Last of all I'm really confused how there could be a problem when you got a fresh OS and Stock.
I agree with the messing thing that you told... Try checking and double checking everything... Check if you have selected the correct device or not.
And do a full wipe(including system) using TWRP before flashing again.
Edit: Make sure you are using the latest toolkit. You can get it from the link bellow.
http://forum.xda-developers.com/showthread.php?t=1766475
Try flash stock image throught toolkit.
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
dac2009 said:
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
Click to expand...
Click to collapse
I don't see a way how the problem still exists... :S
Whatever the problem is it's seems to be with android OS. But how it exists in completely new android. Sorry can't find a reason behind the problem. You can still try flashing any older android (like 4.1.2).
ok i got a zip of stock 4.1.2 and using the root tool kit i can install a zip via the twrp but it wont let me bc it says adb device not found and that developer options need to be turned on. im un able to turn it on bc i cant even get into the rom on the device.
thanks
ok i got it working. i was able to flash the older rom to my device and its working so far. no force closes yet.
thanks for everyone's help
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21%2018.37.24.jpg
dac2009 said:
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21 18.37.24.jpg
Click to expand...
Click to collapse
I can't just think of anything else. Just telling you the things that I'd have done if I were you.
* reinstall boot
* change kernel
* turn off the auto update of android.
* try some costume room.
Don't throw it out the window you call always donate it to me if you really wanna throw it or make a drop test video...
Last of all just don't lose hope keep trying. you'll find out something surely and share it with us.
Sent from my Nexus 7 using XDA Premium HD app
Daft question, but the few times you managed to get it running, was your Wifi on?
Sent from my GT-I9300 using xda app-developers app
yes my wifi was on and was able to stream . spotify among other things
Not the exact same situation, but I found certain Wifi router's would trip my nexus into reboots until I rooted
Sent from my GT-I9300 using xda app-developers app
Phone is stuck in "Android is upgrading. Optimizing application 1 of 1" HELP!!!!!!!!!
hey guys, my phone is stuck in "Android is upgrading. Optimizing application 1 of 1"
and all I can do is
1. apply sdcard/update.zip
2. reboot system now ( does NOT work coz it brings me back to optimizing apps )
3. apply update from external storage
4. wipe data / factory reset
5. wipe cache partition
6. apply update from cache
is there a way i can backup first all my files before factory resetting my phone (if thats the only option i have)????
help me please

Categories

Resources