Hi all,
it's now a month since I downloaded the 4.4 update crashed my Nexus 7.
I have been trying several tool and solutions but nothing worked. I know there are many posts for this problems but I may need specific help.
Current status is I have a working TWRP recovery but every ROM I try to install I get "failed" without further explanation.
Before I was "Unable to mount system" but now it seems sorted out.
I also tried to flash the various components one by one using fastboot. Everything fine for boot, recovery and userdata, but when I try to flash system it gets stuck there. I waited for a few hours but nothing happened.
Any suggestion?
Thanks!
Related
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
IchStelleDummeFragen said:
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
Click to expand...
Click to collapse
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
As long as you have access too fast boot everything can be fixed at least w.r.t software.
Red Devil said:
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
Click to expand...
Click to collapse
It worked!!! Thank you so much.
Still wondering why it didnt flash the factory image as a whole while flashing every part step by step worked perfectly fine...
Red Devil said:
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
Click to expand...
Click to collapse
Yes, tried booting, but the device just restarted and returned to fastboot mode.
many thanks again
help plz
this is where I am at as well how do you get out of this. kinda a noob at this so a step by step would be great thanks
I've never had problems like this and I've been flashing custom roms and recovery since HTC G1 days. Maybe you chaps can enlighten me a bit.
I can boot into all partitions of my device just fine, regular system, recovery, bootloader all okay. My daily rom (Vanir), however, has been getting a little bogged down lately so I'm trying to do an update.
I transferred my rom and gapps files to the sdcard and boot into twrp 2.6.3.1 to update, but lo and behold, the files are now missing. All my other files are there, just not the rom or the gapps. Not too worried yet, I'll just use the sideload method instead.
Start up sideload and watch it transfer over the new rom (MIUI at this point, and I factory reset before hand). From the cmd line I can see it going over just fine and the device seems to be accepting it as well. It gets to 100% and starts a quick error free install on the device, but when I reboot, nothing has been changed and I'm back in Vanir. Okay...I'll update the recovery and see if a new one works.
So I boot into the fastboot to update the recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-grouper.img
Looks good, no error messages, cmd line shows it has been written, so I reboot into my new recovery, only its not new, its still twrp 2.6.3.1 and everything still doesn't work.
Long story long, I also tried installing CWM instead of TWRP -- didn't work, using adb push to move the files and that didn't work, and every time I seem to just lose the zip files after a reboot or update attempt. In fact, when I boot back into Vanir, all my regular files are there, but even though I haven't removed them none of the rom or gapps zips are anywhere. I am sure they have successfully transferred multiple times, but they never seem to make it through a boot sequence.
At this point I'm stuck, and wondering about my boot partitions being messed up. Any help you can provide is much appreciated.
Update, with new information.
I tried to do a complete wipe a la the guide that's stickied in this forum, and it's led me to a bit of new information. It seems that my bootloader is repeatedly failing to update from version 3.23 every time giving either the "InvalidState" error, or when I use older bootloaders that are supposed to work like the JWR66V bootloader mention in this post, it doesn't say "InvalidState" but still fails just the same with a blank where it would say "InvalidState".
I've also realized that none of my changes to my tablet are persisting through a boot sequence. If I download a new app, it is gone upon restarting. In fact, every time I power it up, it downloads the same 3 app updates to the device. Perhaps that can help narrow the problem down a little bit? Sounds like a data wipe is happening every time, but only for changes since I began to try to update the tablet a few days ago, all my files from before the update attempt are never removed or altered at all.
Lastly, according to Rom Manager, I have both TWRP and ClockworkMod as recovery. Actually, that makes me think it might be a boot.img issue. If anyone has any ideas at all, I am open to try any of them at this point. Thanks for reading and for your suggestions in advance!
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.
The first issue I started to notice after rooting via Odin & TWRP was when trying to flash the iOS and WP ROMs from this thread, http://forum.xda-developers.com/android/software/3oss-project-samsung-galaxy-tab-4-7inch-t3081478 , it would fail. I was able to successfully flash the Google ROM from same post. I believe it was with one of the other ones that it even said successful yet when i went to reboot said no OS installed. So, I figured update my TWRP to newest version, maybe that was the problem. Well after updating, now when i go to wipe/factory reset it either says unable to mount or it doesnt even make it that far and reboots system. I tried flashing PIT file with Odin and issue persists. Everything still works smoothly but any help fixing this issue would be much appreciated as I do not want to dirty flash anything. Thanks in advance.
So now...after flashing stock firmware, it boots all the way to nook screen (right after samsung logo) and stops. I can boot into TWRP but it still says unable to mount data. Also, in TWRP when i click mount, the only one already checked is cache. I can manually select all others except data. When i go to install, the internal sd has absolutely nothing on it...really hope i didn's completely mess it up, sometimes my eagerness to learn gets the better of me. Thanks again for any help!
I have the same issue, im stuck
Hi guys,
so I am running into a strange issue: I can't flash any ROMs in recovery anymore.
I switched to Pixel Experience Q from xiaomi.eu's MIUI ROM ~1 week ago without wiping internal storage, so I ended up not being able to use TWRP as I was faced with a password prompt that accepted none of my passwords (current, previous or default_password, etc.). So when an update for PE came I thought "okay let's get this over with now" and did a complete wipe including /data/media from OrangeFox recovery - so far so good.
Now I transferred back the new ROM zip and wanted to proceed flashing it.
Result: Error 7 Failed to update system image (E1001)
Confused by this I went back to the previous version's zip, but the same error comes up.
Even more confused I downloaded all kinds of ROMs and every single one comes up with this error.
I tried
another full wipe
mounting/unmounting system before flashing
MIUI, Android 10, Android 9 ROMs
Different versions of TWRP and OFR
Even different firmware packages
Removed assert and abort lines in the updater-script (which results in skipping the flashing of the system image and then failing at vendor)
Flashing by adb sideload
So the only thing getting me back to a working phone is flashing a fastboot ROM. That works.
Even after doing that, flashing back TWRP/OrangeFox, wiping and flashing a ROM the same error comes up again. I also checked the MD5 hash for my files. They are fine.
I am at a loss of ideas at this point and no solution I found helped. I hope you guys can help me. Thanks in advance. :-/
Well, scratch that, I guess.
After hours of troubleshooting somehow it's working again now.
So for anyone who gets this issue:
Flash a fastboot ROM and...go to sleep and try in the morning.
I'm facing the same problem now.. I think after trying many times its a flash problem, because when I flash over fastboot sometimes stick on 5/7 and others 3/7 etc.. well its a xiaomi is something to expect.
Format Data partition, not just wipe, this should fix those kind of issues.
This.
After more xiaomi devices and more flashing I can definitely say this is the fix.
This.
After more xiaomi devices and more flashing I can definitely say this is the fix.
Try transferring the ROM using a USB 3.0 port. Worked for me...
I am facing the same problem. Can you help me?