Hopefully this helps people in my situation.
So on the first day of having my nexus 7 i found a way to have no OS and 0MB internal storage showing in TWRP. Yah i suck.
I tried tons of things but knew a system image was needed.
HOW: I was about to flash the superuser root for 4.3 newly released and forgot to put it on nexus so i then proceeded to exit TWRP, however upon exiting TWRP the recovery detected i havent installed supersu and asked do i want to install superuser? I though why the hell not!
I confirmed to install superuser and then tried to reboot but for 20 minutes device could not boot. TWRP showed 0MB internal storage and pushing adb files in this state yielded nothing as there was no directory
This is how i managed to have a working tablet again
1. FORMAT DATA in TWRP - after doing this your internal storage should be back and not show 0MB
2. reboot to the bootloader
3. On your computer download this file kindly given to us by phuduong and uploaded by Nburnes
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
Credit to Nburnes http://forum.xda-developers.com/member.php?u=2918596[/QUOTE]
4. Once downloaded move that system.img file to your adb directory
5. With you nexus 7 in the bootloader, adb open, and file downloaded copy and paste this command into adb terminal
fastboot flash system system.img
6. Now you have an OS but it still would loop and wouldnt start
7. Boot into recovery and Format Data again, because for me 0MB interal storage was back again
8. Then Factory Reset
FINALLY YOUR DEVICE SHOULD BE BACK TO ITS ORIGINAL STATE!!!!!
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
plbelanger said:
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
Click to expand...
Click to collapse
Google has yet to release the official factory image for the new N7. However, a kind user was gracious enough to make their own. It is likely to be almost identical to what Google will eventually release and should work the same way.
Thank you! Thank you!
good stuff OP. glad you got it working again
You all are life savers! 1000X Thanks!
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
petersellers said:
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
Click to expand...
Click to collapse
So you first tried to restore the OLD nexus 7 factory image? Probably gonna have to wait for factory image or exchange yours
Sent from my Nexus 7 using xda app-developers app
jporter396 said:
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
THANK YOU!!!
This worked perfectly! I had a wiped system folder (no ROM), and obviously no USB debugging enabled. And with the lack of a factory image, I've been counting seconds to seeing somebody post this!
Just follow the instructions carefully. Thank you guys!
petersellers said:
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
Click to expand...
Click to collapse
You can flash old and new image through fastboot. I did 2 times ^_^
This is boot.img for who need
BOOT.IMG HERE
It gives me a fail when I try to wipe data.
Edit: never mind
jarjar124 said:
It gives me a fail when I try to wipe data.
Edit: never mind
Click to expand...
Click to collapse
How did you fix it? I still cant wipe data.
Balsta said:
How did you fix it? I still cant wipe data.
Click to expand...
Click to collapse
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
jporter396 said:
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can't, get an error with that too
Sent from my SCH-I545 using Tapatalk 4 Beta
OP and nburnes saved my butt!
I did this and now it seems my device is booting and it shows up as N7 when I attach it to my PC. But the display shows nothing at all. It just goes blank after the Google screen. Any ideas?
After flashing everything I could think of and banging my head and the device against the wall for two hours, I finally got it to work. Not sure how exactly but the last thing I did was reflashing bootloader. So if anyone has the same problem, try that.
Thank you.
Note:
Give step 6 a little time be patient.
All main JSS15J .IMGS here: http://forum.xda-developers.com/showthread.php?t=2381438
Glad this helped some of you guys!
Related
I tried to install a new rom after updating TWRP 2.3.0.0. after all was complete it stuck on the boot screen. I then tried with the Nexus Root Toolkit to use a restore from backup. Same problem. I then tried to flash stock and unroot. Same problem. I then tried a number of things through TWRP from backups I had their. Same problem. At present I have no OS and I can only boot into TWRP, turn if off or look at the GOOGLE screen. I have run out of ideas and would appreciate any help offered.
If you have tried everything else (flashing a ROM zip etc.) Then you should flash the factory image from Google.
Don't use the script/batch file as that will wipe your internal storage.
Just flash system and boot.
Sent from my Nexus 7 using xda premium
Sometimes a rom takes a long time to boot for the first time, please be very patient. Also, try wiping everything from /system, and then re install a custom rom from your /sdcard partition. also make sure your roms are for the nexus 7 not galaxy nexus or other similar devices. ONE MORE THING 4.1.2 wont flash with 4.1.1 bootloader.
jmtend said:
I tried to install a new rom after updating TWRP 2.3.0.0. after all was complete it stuck on the boot screen. I then tried with the Nexus Root Toolkit to use a restore from backup. Same problem. I then tried to flash stock and unroot. Same problem. I then tried a number of things through TWRP from backups I had their. Same problem. At present I have no OS and I can only boot into TWRP, turn if off or look at the GOOGLE screen. I have run out of ideas and would appreciate any help offered.
Click to expand...
Click to collapse
There was a bug in TWRP V2.3.0.0 use fastboot to flash V2.3.1.0 and then reflash the rom
Sent from my BAKED Nexus
spaceman860 said:
There was a bug in TWRP V2.3.0.0 use fastboot to flash V2.3.1.0 and then reflash the rom
Sent from my BAKED Nexus
Click to expand...
Click to collapse
Got it working. Thanks all for your suggestions.
jmtend said:
Got it working. Thanks all for your suggestions.
Click to expand...
Click to collapse
How did you fix it? I have no OS and my internal SD card was erased too I don't know how to flash from fastboot
Adb push a ROM.
-Brought to you by Marino's Nexus 7-
AshleyPem28 said:
How did you fix it? I have no OS and my internal SD card was erased too I don't know how to flash from fastboot
Click to expand...
Click to collapse
I know many people hate the talk about toolkits but I was in the same situation and I used Wug's toolkit and it saved me. I downloaded 4.1.2 image directly from Google, as the toolkit only has 4.1.1.
I tried to return to stock on my own and it just went from bad to worse. I would of spent more time trying to fix it on my own but I was on a very tight time constraint. It will unroot your device but it is easy to root again.
Sent from my Nexus 7 using xda app-developers app
Billchen0014 said:
Sometimes a rom takes a long time to boot for the first time, please be very patient. Also, try wiping everything from /system, and then re install a custom rom from your /sdcard partition. also make sure your roms are for the nexus 7 not galaxy nexus or other similar devices. ONE MORE THING 4.1.2 wont flash with 4.1.1 bootloader.
Click to expand...
Click to collapse
THANK YOU the "ONE MORE THING" is all I needed to know for the same problem!
After i rooted/unlocked my phone I booted it up and it got stuck on the nexus splash screen. I did find a solution to the problem which was to put it back to factory settings. alright, great, problem solved, but when i go to do the reset i come across errors as seen in the picture. Anyone know how to fix?
I had that issue when downloading the file through the toolkit. I went and manually got the images from google, placed them in the correct folder within the kit and flashed successfully.
Sent from my Nexus 4 using xda premium
dont use a toolkit. do it manually like what ^^ said
I recommend flash SuperSu zip file via CWM Recovery.
It's totally easy and safe.
I had this issue. Factory reset/clear caches should fix it.
Sent from my Nexus 4 using Tapatalk 2
sporez said:
I had this issue. Factory reset/clear caches should fix it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
factory resetting clears your cache, as well as dalvik cache.
Not sure what I did wrong.
Backed up phone
unlocked phone
downloaded CWM
put SU on phone
went into put loader and flashed ( I think ) CWM
then when I go into recover mode the phone gets stuck on google logo.
Cleared cache etc. but nada.
Downloading factory image now....on a very slow connection and will take 3 hours. Any way around this? What are my options.
I'm totally stuck here too. I have the exact same as the OP.
I've manually placed the stock image in the folder structure. It's starts to do stuff, reboots and then the toolkit says Waiting for Device (forever).
Nothing happens after this.
This all occurred while I was installing my Google Apps. I stupidly installed Chainfire3D, and installed the drivers. It restarted and this never ending cycle happened. I only read that they weren't compatible with ICS or Jellybean afterwards
Any help is greatly appreciated. :crying:
Hi guys
I am stuck on the google logo, I have cleared dalvik etc unmounted / mounted system but cannot get to data partion
I have wiped the SD card now I cannot connect to copy a rom back to the device... it just hangs on Google logo.
I can access recovery but still cannot access data partition to add rom.
any ideas?
thank you
ace9094 said:
Hi guys
I am stuck on the google logo, I have cleared dalvik etc unmounted / mounted system but cannot get to data partion
I have wiped the SD card now I cannot connect to copy a rom back to the device... it just hangs on Google logo.
I can access recovery but still cannot access data partition to add rom.
any ideas?
thank you
Click to expand...
Click to collapse
flash stock recovery.IMG clear caches and boot
Burroveo said:
I'm totally stuck here too. I have the exact same as the OP.
I've manually placed the stock image in the folder structure. It's starts to do stuff, reboots and then the toolkit says Waiting for Device (forever).
Nothing happens after this.
This all occurred while I was installing my Google Apps. I stupidly installed Chainfire3D, and installed the drivers. It restarted and this never ending cycle happened. I only read that they weren't compatible with ICS or Jellybean afterwards
Any help is greatly appreciated. :crying:
Click to expand...
Click to collapse
There is a file contain in the factory image download called flash-all.bat Double click on this file while your phone is connected in bootloader mode and it should automatically flash the stock image for you
Sent from my Nexus 4 using Tapatalk 2
i also have this problem.
I tried to flash stock factory image with the .bat file but no success. I am stuck at the nexus bootlogo...
Can still enter recovery and fastboot.
Edit:
solved my problem. I went to CWM Recovery, and checked in "mounts and storage" that none of the partitions were mounted. Cache was mounted in my case. I unmounted Cache and rebooted.
Phone boots fine now!
Hi everyone,
So I have never ran across this issue before. I haven't had any problems with my device and yesterday I wanted to test out the new Jelly Bam update rom from their site. The rom would not boot pasted the "Google" spash screen so I rebooted in to recovery and did a full wipe and restored via backup to my previous rom just like normal. Well then I noticed that normally when I connect my phone to my computer I see my internal memory drive pop up which I am able to click on and then access my files, but this time when I accessed it I have a hand full or folders like 0, twrp, android, etc and I had to double click on o folder to access my memory with all my files. I thought that was weird so I went on about my day. Later I tried to do a fresh install of my current rom PACman but even after doing a fresh install the phone will not boot passed the Google spash screen, and now twrp doesn't even see my backup file because its being directed to this new partition with all the folders I was talking about. I even tried using the file manager in twrp to move the backup to that twrp folder but twrp doesn't even see it.
So as of right now I can get in to twrp but I can not boot my device pasted the google splash screen. I also can't access my memory through my pc since nexus does not allow it with twrp. What do I do? My thoughts are that something got screwed up with the partitions when I flashed the Jelly Bam rom so I will need to go back to stock, does that sound about right? I was thinking of following these instructions to go back to stock and then move on from there, any thoughts or alternatives? http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Thank you
Trying this method to return to stock: http://www.wugfresh.com/nrt/
If no one has any input I will assume I am following the right path.
I flashed factory images a couple weeks ago and in order for TWRP to see the nandroids I copied back to my phone I put them in the following path: /sdcard/TWRP/BACKUPS/stringofrandomnumbersandletters/
Are your TWRP backups in a similar location?
If you've decided to go back to stock, I'd suggest using the following guide by efrant... http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda app-developers app
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
It looks like twrp is now looking at my twrp folder in my sd card 1 not sd card 0 where I have had my backups and all my files. After trying again, I moved the TWRP backup to the sd card 1 twrp folder, twrp recognized it and I restored from backup....but when I reboot I am still stuck on the Google screen. Not sure what to do.
Underground_XI said:
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Since I can't move anything to my memory, any suggestions?
If you've got adb and the proper drivers installed on your PC you could try:
Code:
adb push ROM.zip /sdcard/ROM.zip
from the command prompt. Obviously use the name of the actual ROM.
Edit: ignore that, just read the post where you managed to restore! D'oh!
Have you tried clearing both caches?
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
synergeticink said:
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
Click to expand...
Click to collapse
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that's were I am stuck right now. I am not a pro at using adb commands, never used it till I got my nexus 4. Right now when I launch the cmd it shows "C:\Users\My User Name\Desktop>", not sure where to go next. I guess I am not sure what I should be pushing at this point either.
Oops...it seems I was editing my post at the same time you were responding to it...take a look at my previous response again
I'm fairly new around here but I can help with the adb commands if you need. Hang in there
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I tried wiping cache/dalvik/system/factory reset and then both restoring from backup or flashing the latest PACman rom which is in my sd card. Right now I am reading the http://forum.xda-developers.com/showthread.php?t=2018179 guide to see if I can use adb to flash my rom or another recovery. Makes sense if its the recovery not letting me flash anything, but i'm not a dev. At least I am able to get in to recovery to begin with, good sign I guess.
If you can boot into bootloader and recovery there are many options to help get you up and running again. That guide by Jubakuba is really good but if wiping and restoring your backup from within TWRP didn't work I would highly suggest reading efrant's guide on returning to stock...I posted the link in an earlier reply.
Sent from my Nexus 4 using xda app-developers app
I was able to flash cwm using adb, now trying to do a fresh install
Nope, doing a fresh install didn't work. Now its time to restore to stock. ......
One problem:
"
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;"
UPDATE; Got it, instructions were not clear.
synergeticink said:
UPDATE; Got it, instructions were not clear.
Click to expand...
Click to collapse
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its weird adb will not work on the computer unless the files are in the platform-tools folder in androi sdk. trial and error, just finished flashing system....
should I do this command, I really don't want to lose my stuff:
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Well, I didn't and finished the process...did a reboot when I was done...now its on the Google screen...just waiting....I'm seeing a Nexus X splash screen!!!...
Update: Its taking a very long time, hopefully it works...going to give it another 10 mins
And we have BOOT... thank you everyone! Now I have to root this sucker!
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
bflatmajor said:
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
Click to expand...
Click to collapse
How long did you let the boot go for? The first boot takes a REALLY LONG time.
over 15 minutes..
Im rebooting it now.. lets see what happens
after more than 30 minutes, still no change in behavior
bflatmajor said:
over 15 minutes..
Im rebooting it now.. lets see what happens
after more than 30 minutes, still no change in behavior
Click to expand...
Click to collapse
You wouldn't happen to have an old ROM on your device would you? If so, maybe flash that and see if you can at least boot. If you can't even boot you may have to do a full wipe.
bflatmajor said:
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
Click to expand...
Click to collapse
I noticed this has happened to me before when I would flash all the images (except userdata) and elect to only erase cache, and not flash the cache image. It would be stuck in the bootanimation forever. Once I started flashing the cache image when upgrading, I've never had an issue since. So my advice to you is to flash the cache image from the factory image and see if that fixes it. All your data will still be intact.
charesa39 said:
I noticed this has happened to me before when I would flash all the images (except userdata) and elect to only erase cache, and not flash the cache image. It would be stuck in the bootanimation forever. Once I started flashing the cache image when upgrading, I've never had an issue since. So my advice to you is to flash the cache image from the factory image and see if that fixes it. All your data will still be intact.
Click to expand...
Click to collapse
How did you do this exactly? My phone is in that exact cycle...
gundamslicer said:
How did you do this exactly? My phone is in that exact cycle...
Click to expand...
Click to collapse
You may also need to wipe dalvik if you have not tried that already.
The factory cache image is in the same zip file with system.img, boot.img, etc. You need to boot back to fastboot and do
Code:
fastboot flash cache <path_to_cache_image>
I recently upgraded to 5.1 by flashing only system.img and boot.img and wiping only cache and dalvik and I didn't have any issues.
gundamslicer said:
How did you do this exactly? My phone is in that exact cycle...
Click to expand...
Click to collapse
I usually follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Obviously, just make sure you have the correct factory image files for the Nexus 10. MAKE SURE NOT TO FLASH USERDATA. If you do, you will wipe your device and you will lose all your data. So I always just skip that command when I'm flashing the image files. After you're done flashing the cache image, just unplug your device and select "Start" from the bootloader menu. It will boot up normally and then you will see the "Android upgrading app ## of ##" message. That means everything worked.
Same problem happened with me. After applying the ota update for 5.1, I got locked in the boot animation.
Tried to reinstall the 5.1 manually, same thing happened.
I also tried to downgrade to 5.0.2 and 5.0.1 with no lucky. Now the tablet is useless.
Anyone else is experiencing this problem. Any suggestion to solve it?
luizm.jr said:
Same problem happened with me. After applying the ota update for 5.1, I got locked in the boot animation.
Tried to reinstall the 5.1 manually, same thing happened.
I also tried to downgrade to 5.0.2 and 5.0.1 with no lucky. Now the tablet is useless.
Anyone else is experiencing this problem. Any suggestion to solve it?
Click to expand...
Click to collapse
How are "reinstalling 5.1 manually"? Are you following the steps (Method 2) in the link I posted in the post above yours?
No. I ran the batch on the original rom downloaded from google.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
No. I ran the batch on the original rom downloaded from google.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Ah. That's what I had thought. That could be your problem right there. Unfortunately, the batch process hasn't worked properly since 5.0. Not sure if Google fixed this with 5.1, but I doubt it. Try flashing all of the images manually. DON'T FLASH USERDATA, unless you don't care about losing your data.
charesa39 said:
Ah. That's what I had thought. That could be your problem right there. Unfortunately, the batch process hasn't worked properly since 5.0. Not sure if Google fixed this with 5.1, but I doubt it. Try flashing all of the images manually. DON'T FLASH USERDATA, unless you don't care about losing your data.
Click to expand...
Click to collapse
I followed the method 2 and flashed everything except userdata and radio (bootloader, system, boot, recovery and cache). Still locked in the boot animation.
I noted that before accepting any flash command I sent, Nexus screen displayed "FASTBOOT STATUS - FAIL Invalid Partition". But at the end of flash it was displayed "FASTBOOT STATUS - OKAY"
luizm.jr said:
I followed the method 2 and flashed everything except userdata and radio (bootloader, system, boot, recovery and cache). Still locked in the boot animation.
I noted that before accepting any flash command I sent, Nexus screen displayed "FASTBOOT STATUS - FAIL Invalid Partition". But at the end of flash it was displayed "FASTBOOT STATUS - OKAY"
Click to expand...
Click to collapse
Hmm. That invalid partition message is odd. Were you stock before? Did the command window show "OKAY" after each image was flashed? I'm wondering if your userdata partition is messed up as well. Not sure if all your stuff is backed up, but I would probably flash everything again, including userdata to start fresh. Obviously, you would lose all your data.
I never had unlocked the bootloader before in this device.
Yes, I got an OKAY after every flash. But also the invalid partition message at the beginning.
I'll try to flash everything again, including user data and let you know.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
It worked! However I lost all my data. I thought the new lollipop cloud backup would restore the app data but it was a fresh install for everything including the Google Now launcher.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
It worked! However I lost all my data. I thought the new lollipop cloud backup would restore the app data but it was a fresh install for everything including the Google Now launcher.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
That sucks about losing your data... But at least you have a functioning N10 now. :good: I'm thinking the data partition may have somehow got corrupted, which is why it wasn't completing the boot process. Glad it worked out for you in the end though.
I was flying yesterday, and noticed that the phone went into a bootloop when I took it out of my pocket during the flight.
My phone is on purenexus with TWRP installed already. When I got back home I tried clean flash the latest Feb ROM update, wiping all partition besides storage partition before the flash. Also flashed the latest vendor image. I did not see any error during the flash process.
No matter what I try, the phone would not get past the google screen and reboots just before it gets to the boot screen.
I am now backing up data on my phone via TWRP. It's going to be a PITA if I need to RMA the phone as it was bought in the US but I am now using it overseas.
Any magical fix to this issue?
Prior to the phone had issue, it was running Nougat Purenexus rom Jan 2017 version.
I got it yesterday. Try to flash the factory image in this post https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 (Step 10)
Add some more steps before the above:
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
It will works. Try it.
nhatminhng said:
I got it yesterday. Try to flash the factory image in this post https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 (Step 10)
Add some more steps before the above:
It will works. Try it.
Click to expand...
Click to collapse
As I do not want to format internal storage, I tried option 11 - How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
I followed all the steps and phone is still in bootloop.
Just backup your internal storage to somewhere in your PC and then you're free to go. Why dont try?
nhatminhng said:
Just backup your internal storage to somewhere in your PC and then you're free to go. Why dont try?
Click to expand...
Click to collapse
I haven't seen any evidence of wiping the internal storage will fix this issue.
Me. Yesterday. It's up to you to try.
nhatminhng said:
Me. Yesterday. It's up to you to try.
Click to expand...
Click to collapse
Just tried step 10 and format userdata - does not work. Phone is still stuck in bootloop.
The fact that you have access to the recovery means you have a high chance of getting the phone back to the should. The real BLOD only has boot loader available but nothing else besides the bar code screen.
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
The fact that you have access to the recovery means you have a high chance of getting the phone back to the should. The real BLOD only has boot loader available but nothing else besides the bar code screen.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have access to bootloader, and recovery (TWRP). Problem now is finding a solution to boot the phone past the google screen without going into a loop.
fustyler said:
I have access to bootloader, and recovery (TWRP). Problem now is finding a solution to boot the phone past the google screen without going into a loop.
Click to expand...
Click to collapse
Format your sytem, userdata and cache partitions then flash the latest full stock image using flash-all.bat.
v12xke said:
Format your sytem, userdata and cache partitions then flash the latest full stock image using flash-all.bat.
Click to expand...
Click to collapse
I have formatted every partition, and flashed latest full stock image. Still the same, google, google, google. Even tried the solution to format EFS partition and still bootloops.
So you have TWRP access still, and you have used the flash-all.bat method through the boot loader and it's still boned??
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
So you have TWRP access still, and you have used the flash-all.bat method through the boot loader and it's still boned??
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I followed step 10 in this guide (which is the same as doing flash-all.bat, and it is still bootlooping. I then reflashed TWRP into recovery.
https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2