Hello,
I am in serious problem and need your help asap
So this is the thing:
I got a nexus 4 running rooted srock 4.2.1 official ROM. I was trying to update to 4.2.2 with OTA update. The problem was it has an "assert problem (status 7)" with the file /system/app/PlusOne.apk. Maybe it was a mistake but I tried to format /system through the recovery. Again, I tried to install the update. this time, it has the same assert problem but with the build.prop file.
Since then, the nexus is stuck on the google logo and won't boot. I've tried to wipe dada/cashe/anything else and it didn't fix the problem. I also tried to install again the stock rom through the Nexus 4 Toolkit without any luck.
I have no idea what to do.. The only thing I can do is go in the fastboot/recovery menu, but can't boot in any way..
Please help me
Thanks in advance.
MasterLinuxer said:
Hello,
I am in serious problem and need your help asap
So this is the thing:
I got a nexus 4 running rooted srock 4.2.1 official ROM. I was trying to update to 4.2.2 with OTA update. The problem was it has an "assert problem (status 7)" with the file /system/app/PlusOne.apk. Maybe it was a mistake but I tried to format /system through the recovery. Again, I tried to install the update. this time, it has the same assert problem but with the build.prop file.
Since then, the nexus is stuck on the google logo and won't boot. I've tried to wipe dada/cashe/anything else and it didn't fix the problem. I also tried to install again the stock rom through the Nexus 4 Toolkit without any luck.
I have no idea what to do.. The only thing I can do is go in the fastboot/recovery menu, but can't boot in any way..
Please help me
Thanks in advance.
Click to expand...
Click to collapse
By formatting /system, you have effectively deleted Android OS. That's why your phone won't boot up. And without Android, you can't get into ADB (that's why the toolkit won't work. Reflash the stock images (guide can be found here: http://forum.xda-developers.com/showthread.php?t=2010312) and you should be fine.
Sent by carrier pigeon
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
Hi all,
For the past few days I've been trying to flash new ROMs. I'm a noon but have previously flashed probably 100 times with no problems at all.
Ive stuck with psx for about 3 months and live it, but as updates for the ROM have become a hasstke to get, I thought I'd try something else, but this time move on to KitKat custom ROMs instead of 4.3.
Now here's the problem. I'm doing everything the same as I usually would, d/l ROM, appropriate gapps, use latest twrp, factory reset, flash and then..... FAILED update : ( : ( Now I am a noobso am I missing something big time???, do I need to completely wipe phone when flashing from 4.3 to KitKat??, pls help, I'm sick to death of going through the fail/restore process
Thanks in advance : )
Are you updating the bootloader and radio when moving from 4.3 to 4.4? Did you try formatting the system before installing?
I transitioned from jellybean to KitKat too yesterday and had that same problem. From what i remember, what I did was when I got that failed update message in twrp, i first clicked home, then click reboot, then select to recovery. It should then warn you're about to reboot w/out a ROM/system. I swiped yes. Then it should prompt u to install supersu. Go ahead and swipe yes. It should then reboot u back to recovery and u can proceed to do your normal install routine. Now I'm adjusting myself to KitKat life!
Sent from my Nexus 4 using Tapatalk
I had that problem flashing ROMs with TWRP as well. I had to unmount the system, then everything flashed successfully!
Use cwrm instead , brotha from another motha twrp has issues with kitkat
Sent from my Nexus 4 using Tapatalk 4
You need a custom boot image for kitkat
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!
I recently rooted my (2012) Nexus 7 and installed CyanogenMod. All went well until I tried installing G-apps.
The installation process completed and then the tablet got stuck in a bootloop on the spinning CyanogenMod icon.
I followed the instructions here: http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/comment-page-1
but even after doing that the tablet goes back into the loop.
Has anyone got tips how to fix this?
Recovery , re flash ROM try different gapps.
rbeavers said:
Recovery , re flash ROM try different gapps.
Click to expand...
Click to collapse
I seem to be unable to do so from recovery mode.
I get as far as where it says flash ROM via side-load but it's not really clear to me what to do there.
I've been trying to flash my nexus 4 for anything past 4.2.2 it goes into bootloop.
ive tried flashing with twrp and adb sideload as well as flash-all.sh, from clean to dirty installs. even updating on 4.2.2 through system update to 4.3 causes bootloop as well. it always hangs on "Android is starting... Starting Apps"
this kernel log is from cyanogenmod 13 fresh install, I can provide different kernel logs if needed.
pastebin.com/BhpD1D65
edit:
in 4.2.2 imei/baseband version is unknown, but in bootloader it shows M9615A-CEFWMAZM-2.0.1700.48
onikii said:
I've been trying to flash my nexus 4 for anything past 4.2.2 it goes into bootloop.
ive tried flashing with twrp and adb sideload as well as flash-all.sh, from clean to dirty installs. even updating on 4.2.2 through system update to 4.3 causes bootloop as well. it always hangs on "Android is starting... Starting Apps"
this kernel log is from cyanogenmod 13 fresh install, I can provide different kernel logs if needed.
pastebin.com/BhpD1D65
edit:
in 4.2.2 imei/baseband version is unknown, but in bootloader it shows M9615A-CEFWMAZM-2.0.1700.48
Click to expand...
Click to collapse
I may be talking out of my ass here but I seem to remember someone else fixing this by wiping cache using stock recovery.
Sent from my Nexus 4 using XDA Labs
Looks like my system partition is corrupted, i'm unable to mount it through twrp.
onikii said:
Looks like my system partition is corrupted, i'm unable to mount it through twrp.
Click to expand...
Click to collapse
I'd just flash the Google stock nexus image, then flash the ROM you want.
http://forum.xda-developers.com/nexus-4/help/nexus-runs-jelly-bean-4-2-2-downgrade-5-t3314579/page1
Try looking in this thread. There someone else seems to have a similar problem to yours. There are several solutions suggested, and there is also links to other threads with similar problems.
Sent from my Nexus 4 using XDA Labs