Related
First let me start off by saying that I have read a lot of posts about issues with 4.2.2 but mine are different, I promise. If not, sorry.
I am unlocked/rooted and had a custom ROM installed. Decided to change to another so I went back to my stock backup (I really hated the ROM). When I went back to stock I received the notification to update to 4.4.2. I did. A bit later I tried to flash a ROM via goo.manager with no success. I then tried to flash with TWRP. I got the android with the red exclamation when I tried to go into recovery. I've also attempted to flash a recovery again with goo.manager and ROM Manager. I kept getting errors.
My dog chewed up my USB so I can't flash recovery since my nexus won't show on my computer with anything else. Is there any other way I can flash a recovery?
Again, forgive me for any redundancy and please help, I'm a serious noob. Being stuck on stock isn't the worst thing but I'd really like to flash another ROM.
Sent from my Nexus 7 using xda app-developers app
If your ROM is rooted, you can flash the recovery partition from a root shell using the "dd" command.
That is, from a terminal emulator:
$ su
# cd /sdcard
# dd bs=4096 if=name-of-recovery-image-file.img of=/dev/block/mmcblk0p1
good luck. I didn't understand everything you said in your post, but I got the part about the dog
buckwheat_shawt said:
First let me start off by saying that I have read a lot of posts about issues with 4.2.2 but mine are different, I promise. If not, sorry.
I am unlocked/rooted and had a custom ROM installed. Decided to change to another so I went back to my stock backup (I really hated the ROM). When I went back to stock I received the notification to update to 4.4.2. I did. A bit later I tried to flash a ROM via goo.manager with no success. I then tried to flash with TWRP. I got the android with the red exclamation when I tried to go into recovery. I've also attempted to flash a recovery again with goo.manager and ROM Manager. I kept getting errors.
My dog chewed up my USB so I can't flash recovery since my nexus won't show on my computer with anything else. Is there any other way I can flash a recovery?
Again, forgive me for any redundancy and please help, I'm a serious noob. Being stuck on stock isn't the worst thing but I'd really like to flash another ROM.
Click to expand...
Click to collapse
Are you still unlocked and rooted after the update to 4.2.2 ?
If not you must unlock and root your N7 again, but be careful, All root tools doesn't work for 4.2.2. and are not updated for 4.2.2
I unlocked my N7 normally, but I used CF auto-root (update) and now I'm unlocked and rooted with DirtyBox rom.
Thanks a lot. This will be my first time using the terminal emulator, should be a good learning experience
Sent from my Nexus 7 using xda app-developers app
I'm still unlocked and rooted. I just can't access my recovery after the update. This happened once with CWM on my GNex but I still had the oem usb so I just flashed it again with my computer. I don't have an oem usb for my N7. Btw, I was using twrp on the N7.
Sent from my Nexus 7 using xda app-developers app
buckwheat_shawt said:
I just can't access my recovery after the update.
Click to expand...
Click to collapse
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
bftb0 said:
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
Click to expand...
Click to collapse
I've tried that but I keep getting "cannot open for write: Permission denied". I guess I'm doing it wrong. And I can't boot to fastboot to try with my computer because I keep turning the damn thing off. My usb is iffy sometimes. This sucks.
buckwheat_shawt said:
I've tried that but I keep getting "cannot open for write: Permission denied". I guess I'm doing it wrong. And I can't boot to fastboot to try with my computer because I keep turning the damn thing off. My usb is iffy sometimes. This sucks.
Click to expand...
Click to collapse
Permission denied would only occur if you were not root.
Either your ROM is not rooted, or you forgot to run the "su" command first.
bftb0 said:
The 4.2.2 ota replaced whatever you had flashed into the recovery partition with a stock recovery.
Did you try the "dd" flash?
Click to expand...
Click to collapse
bftb0 said:
Permission denied would only occur if you were not root.
Either your ROM is not rooted, or you forgot to run the "su" command first.
Click to expand...
Click to collapse
You're right I wasn't. I just found out and I've rooted and installed my recovery. Thanks alot though, probably wouldn't have figured it out without you all. First time having to make a post to solve an issue. Thanks again! :victory:
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
Need help...
I installed the new PA AOSP 4.4 on Mako. I had not installed GAPPS. Started the phone up into 4.4, thought "don't like this", turned off went into CWM, went into recovery and was hit with a knocked over android with the red warning sign. I have tried multiple times without success to get into recovery.
I downloaded Flashify and it says I do not have SU permission on your device. Downloaded superSU and was greeted with the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
How do I get back to 4.3? is it possible? or do I have to wait for a root now? Is there any way just to get GAPPS or the Playstore?
Find efrant's guide on flashing back to stock using fastboot. It'll get you 100% back to stock, and teach you the right way to do it.
username8611 said:
Find efrant's guide on flashing back to stock using fastboot. It'll get you 100% back to stock, and teach you the right way to do it.
Click to expand...
Click to collapse
Can you do me a huge favor and find it, I have no idea which one I am looking at.
PhysicsNerd said:
Need help...
I installed the new PA AOSP 4.4 on Mako. I had not installed GAPPS. Started the phone up into 4.4, thought "don't like this", turned off went into CWM, went into recovery and was hit with a knocked over android with the red warning sign. I have tried multiple times without success to get into recovery.
I downloaded Flashify and it says I do not have SU permission on your device. Downloaded superSU and was greeted with the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
How do I get back to 4.3? is it possible? or do I have to wait for a root now? Is there any way just to get GAPPS or the Playstore?
Click to expand...
Click to collapse
so what happened is you did everything wrong. first off, you should have flashed the rom, gapps, and supersu 1.65(for root). and that android laying there is the stock recovery. you lost it because the rom replaced your recovery with the stock recovery. all you have to do is flash a custom recovery via fastboot, then flash supersu 1.65 in the custom recovery that you just installed. next time, figure out what you have to do before doing it.
simms22 said:
so what happened is you did everything wrong. first off, you should have flashed the rom, gapps, and supersu 1.65(for root). and that android laying there is the stock recovery. you lost it because the rom replaced your recovery with the stock recovery. all you have to do is flash a custom recovery via fastboot, then flash supersu 1.65 in the custom recovery that you just installed. next time, figure out what you have to do before doing it.
Click to expand...
Click to collapse
Thank you so very much, I thought I was downloading PA 3.99 just under a different name which is why it kind of shocked me when GAPPS 4.3 said it couldn't install.
I really appreciate your time, I was panicking here for a second.
PhysicsNerd said:
Thank you so very much, I thought I was downloading PA 3.99 just under a different name which is why it kind of shocked me when GAPPS 4.3 said it couldn't install.
I really appreciate your time, I was panicking here for a second.
Click to expand...
Click to collapse
na, this is a simple faux pas made by hundreds of thousands(it seems) over my android years. and its not even a big error, its easily fixed, but it does freak out way too many
simms22 said:
na, this is a simple faux pas made by hundreds of thousands(it seems) over my android years. and its not even a big error, its easily fixed, but it does freak out way too many
Click to expand...
Click to collapse
Happy that there is a solution. I'm having the same exact issue and i don't know flashing the recovery image in fastboot mode. If you could put up a link or a video on how to go about it , that would be great
Trying to push recovery.img using fastboot , but gettin "waiting for device"error. should have just let the 4.3 stay. damn. no gapps. no recovery .
747nemesis said:
Trying to push recovery.img using fastboot , but gettin "waiting for device"error. should have just let the 4.3 stay. damn. no gapps. no recovery .
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2015469 or other toolkit
PhysicsNerd said:
Need help...
Started the phone up into 4.4, thought "don't like this"
Click to expand...
Click to collapse
Just out of curiousity, why didn't you like it? You can always get a different launcher
Simplest way to fix it is DL one of the nexus tool kits. Me I use http://forum.xda-developers.com/showthread.php?t=2171332 and its that easy why make it harder than it is or read the full op
acultr said:
try this http://forum.xda-developers.com/showthread.php?t=2015469 or other toolkit
Click to expand...
Click to collapse
tried that . it is saying fastboot device not found. what to do now?
747nemesis said:
tried that . it is saying fastboot device not found. what to do now?
Click to expand...
Click to collapse
properly installed the driver?
Problem Flashing
Hi, i have a problem flashing rastakat. To Install in bootloader, appear: Error flashing zip. I download again the zip, but appear the errror again, What i can doing bad? tks
acultr said:
properly installed the driver?
Click to expand...
Click to collapse
FInally got it to work . Had issues with drivers i guess , so i connected my nexus 4 to a macbookpro(hate apple though ) and it was done in less than a minute
I am on the D801 for T-mobile.
I installed TWRP earlier today and as i get into my phone i was stupid enough to click the OTA update that occurs.
Now i bricked and only go into TWRP.
I have no idea what to do and dont know how to address the issue.
While it is like this i cant put stuff onto the device right? because my computer wont recognize it.
Please and thank you!
I would like to learn how to fix this. First time actually working with this stuff.
http://forum.xda-developers.com/showthread.php?t=2582142
Have you tried that?
exhibitA said:
http://forum.xda-developers.com/showthread.php?t=2582142
Have you tried that?
Click to expand...
Click to collapse
I have a recovery though. I did install TWRP onto my phone it is just i did the OTA update and it wont boot into the system now
Save yourself time and agony.... read the restore to stock threadsand go back to stock and then reroot. ..but do NOT take any otas.
Sent from my LG-D800 using Tapatalk
tdevaughn said:
Save yourself time and agony.... read the restore to stock threadsand go back to stock and then reroot. ..but do NOT take any otas.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
When i go into UpTestEx.exe it tells me to log in
2mustange said:
I am on the D801 for T-mobile.
I installed TWRP earlier today and as i get into my phone i was stupid enough to click the OTA update that occurs.
Now i bricked and only go into TWRP.
I have no idea what to do and dont know how to address the issue.
While it is like this i cant put stuff onto the device right? because my computer wont recognize it.
Please and thank you!
I would like to learn how to fix this. First time actually working with this stuff.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2451696
datechnerd said:
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I've tried that. I did the commands and reboot and nothing.
Okay guys so this is what is happening.
I have twrp 2.6.3,2
I am in a bootloop. I keep going to the recovery
I have ADB running and can push any zip files to it
I have tried pushing a version of paranoid to it.
Upon trying to flash i get this error:
error excuting updater binary in zip '/sdcard/pa.zip'
error flashing zip '/sdcard/pa.zip
So something is wrong with the binary?
2mustange said:
Okay guys so this is what is happening.
I have twrp 2.6.3,2
I am in a bootloop. I keep going to the recovery
I have ADB running and can push any zip files to it
I have tried pushing a version of paranoid to it.
Upon trying to flash i get this error:
error excuting updater binary in zip '/sdcard/pa.zip'
error flashing zip '/sdcard/pa.zip
So something is wrong with the binary?
Click to expand...
Click to collapse
Flash back to stock
doktor buknasty said:
Flash back to stock
Click to expand...
Click to collapse
Should that work with any stock rom?
2mustange said:
Should that work with any stock rom?
Click to expand...
Click to collapse
Find you device and read: http://forum.xda-developers.com/showthread.php?t=2432476
doktor buknasty said:
Find you device and read: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
Thanks i actually pulled that off last night!
IT was weird i couldnt get the flash tool to work for awhile and all of a sudden it worked.
Thank you!
Hi all,
I have an LG D802, was running standard ROM just rooted and with PhilZ recovery. Well I was silly and tried an OTA update, and got stuck at recovery...unfortunately I panicked, cleared everything and tried to flash another ROM but I'm still stuck at recovery.
I tried the instructions in the thread about being stuck after an OTA update but as I;ve formatted the sd partition it didn't work.
I want to go back to stock, I just have no idea how....I have ADB access though if that helps! I'm not really experienced in this kind of thing so please dumb it down for me!
Any help much appreciated!
Callum
calistheman said:
Hi all,
I have an LG D802, was running standard ROM just rooted and with PhilZ recovery. Well I was silly and tried an OTA update, and got stuck at recovery...unfortunately I panicked, cleared everything and tried to flash another ROM but I'm still stuck at recovery.
I tried the instructions in the thread about being stuck after an OTA update but as I;ve formatted the sd partition it didn't work.
I want to go back to stock, I just have no idea how....I have ADB access though if that helps! I'm not really experienced in this kind of thing so please dumb it down for me!
Any help much appreciated!
Callum
Click to expand...
Click to collapse
can you get into download mode either try the adb reboot download mode or turn phone entirely off and hold volume up(only volume up) and plug it into the pc usb, if you can use the back to stock guide to get your phone working again
XxZombiePikachu said:
can you get into download mode either try the adb reboot download mode or turn phone entirely off and hold volume up(only volume up) and plug it into the pc usb, if you can use the back to stock guide to get your phone working again
Click to expand...
Click to collapse
hi no I cannot get in to download mode by any means.
calistheman said:
hi no I cannot get in to download mode by any means.
Click to expand...
Click to collapse
have you tried adb pushing/sideloading a rom and flashing to see if it helps?
XxZombiePikachu said:
have you tried adb pushing/sideloading a rom and flashing to see if it helps?
Click to expand...
Click to collapse
Yes trued flashing a custom ROM, however in my haste to try and stop the OTA forcing me to recovery I may have formatted some partitions I shouldnt have.
Can I restore everything by downloading the kdz with all the correct IMG files in, converting to a flash able zip (saw a guide on here) and trying that?
calistheman said:
Yes trued flashing a custom ROM, however in my haste to try and stop the OTA forcing me to recovery I may have formatted some partitions I shouldnt have.
Can I restore everything by downloading the kdz with all the correct IMG files in, converting to a flash able zip (saw a guide on here) and trying that?
Click to expand...
Click to collapse
Yes that is possible to do I should know because we have something like that for d800
Sent from LG-G2 D800 on AEONFLEX 4.4.2