Related
Hi
I am on stock 4.1.2 unlocked and rooted and I was on TWRP recovery then I changed to CWM 6.0.1.0 because there are some problems in it an yesterday I flash the new TWRP 2.3.1.0 with goo manager and rebooted to TWRP and I did a backup of the rom and rebooted the tablet and I trasfer the paranoidandroid rom to my SD card and open the goo manager and select reboot recovery , it didn't reboot to recovery i I don't know why I did it a couple of times the tablet just rebooted normally like there are no recovery and I go to flash the CWM 6.0.1.0 and it is the same the phone rebooted normally it didn't rebooted to recovery
Somebody help me please
Sent from my Nexus 7 using xda app-developers app
Anybody
Sent from my Nexus 7 using xda app-developers app
You should be able to use fastboot to flash a recovery img or use a toolkit.
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
You should be able to use fastboot to flash a recovery img or use a toolkit.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I did but it is the same it is reboot normally
Sent from my Nexus 7 using xda app-developers app
sharjackmission said:
I did but it is the same it is reboot normally
Click to expand...
Click to collapse
Did you remember to change the recovery-from-boot.p file after you did the 4.1.2 update?
iElvis said:
Did you remember to change the recovery-from-boot.p file after you did the 4.1.2 update?
Click to expand...
Click to collapse
Yes after I update to 4.1.2 OTA those problems came
And now I managed to reboot to CWM by wug's toolkit but I can't enter to recovery from the bootloader
Sent from my Nexus 7 using xda app-developers app
sharjackmission said:
Yes after I update to 4.1.2 OTA those problems came
And now I managed to reboot to CWM by wug's toolkit but I can't enter to recovery from the bootloader
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is a problem many Nexus 7 owners are experiencing since the 4.1.2 update, whether by OTA or flashed from sd card. There apparently is an issue with the bootloader (version 3.43). One solution that I have seen on t his forum and on another is to flash the last version of bootloader (3.31 I think). I have tried every conceivable method to get into either stock recovery or custom recovery to no avail...flash, 2 different toolkits, ROM Manager, TWRP...you name it, I've tried it to no avail. I have not tried to flash back to the old bootloader though...just doesn't sound like a good idea...although I have not heard of problems being encountered by those who have flashed the old bootloader...yet. There are a couple thread in this sub forum on the subject if you want to read the 100 different ways users have tried to get a recovery.
jpcalhoun said:
This is a problem many Nexus 7 owners are experiencing since the 4.1.2 update, whether by OTA or flashed from sd card. There apparently is an issue with the bootloader (version 3.43). One solution that I have seen on t his forum and on another is to flash the last version of bootloader (3.31 I think). I have tried every conceivable method to get into either stock recovery or custom recovery to no avail...flash, 2 different toolkits, ROM Manager, TWRP...you name it, I've tried it to no avail. I have not tried to flash back to the old bootloader though...just doesn't sound like a good idea...although I have not heard of problems being encountered by those who have flashed the old bootloader...yet. There are a couple thread in this sub forum on the subject if you want to read the 100 different ways users have tried to get a recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32918876
I found this and I didn't tried it because it may not work see for your self
I just wondering when the android 4.2 will be released to solve all those problems
Sent from my Nexus 7 using xda app-developers app
I think my bootloader is 3.41 and I have no issues but I flashed the factory image from Google because my touchscreen didn't respond after the 4.1.2 OTA.
Try flash the bootloader and see if it works and if not then flash the factory image.
Just note that if you use the script/batch file to flash it all automagically it will wipe your SD so flash each image separately and don't flash userdata.img
flashing factory fixes any software problem, its the best thing about owning a nexus.
Sent from my Nexus 7 using xda premium
found it
if you are on the latest bootloader vesion
reboot to booloader
fastboot erase cache
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot
thank you all
Either from the bootloader or from the Nexus 7 Toolkit, this stupid thing won't boot to recovery. I flashed from CM10.1 to cm10 after wiping cache and dalvik...now I cannot get to recovery. System boots after going back to stock and even after the CWM flash, but recovery seems to be non-existent. Using the toolkit mentioned I flashed CWM, and I cannot boot to this.
Does adb reboot recovery work
Sent from my HTC Vision using Tapatalk 2
Try downloading ROM Manager from the play store. It will install recovery CMW for you and then you can boot to it. If you are trying to boot directory to recovery using the key press it will not work unless you have the tab plugged into a computer.. the N7 is funny that way.
Sent from my Nexus 7 using xda app-developers app
Have you tried upgrading the bootloader to 4.31? That fixed my problem.
Sent from my Nexus 7 using Tapatalk 2
I've already done the upgrade to Android 4.2 when I was on stock. CWM I had from the Nexus 7 Toolkit. Even when I boot to custom recovery via that it just skips over it. When I had CWM installed I could boot to recovery via the reboot menu though so I dunno what the issue is.
agentfazexx said:
I've already done the upgrade to Android 4.2 when I was on stock. CWM I had from the Nexus 7 Toolkit. Even when I boot to custom recovery via that it just skips over it. When I had CWM installed I could boot to recovery via the reboot menu though so I dunno what the issue is.
Click to expand...
Click to collapse
What version of CWM did you flash? Perhaps try downloading CWM 6.0.1.9 and flashing it via fastboot
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
I don't think I need to do all that. Do I need to re-lock the bootloader, flash stock, unlock and flash CWM again or something? Trying to figure out why this device is such a pain in the ass. Even from the bootloader I can't boot to recovery after flashing it!!!
swieder711 said:
Have you tried upgrading the bootloader to 4.31? That fixed my problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
So how do I do this? My bootloader is version 3.34.
Pretty sure I bricked it. Just says booting failed. Friggin overmarketed P.O.S.
Anyone want to buy this?
agentfazexx said:
Pretty sure I bricked it. Just says booting failed. Friggin overmarketed P.O.S.
Anyone want to buy this?
Click to expand...
Click to collapse
Dang man calm down before you stroke out. Unless you did something seriously stupid it's not bricked.
And your ROM/flashing problems have nothing to do with the device itself.
Instead of rants, more details would help get you better answers.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - MKernel+ a19
Sure ill buy it, these things are hard to brick... what you want for it?
Sent from my HTC Vision using Tapatalk 2
It's booting now. Somehow flashing the stock ROM while locked soft bricks it.
So back to the drawing board, how do I get CWM back on here? This whole "adb push fastboot" yaddayadda is Greek to me.
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Sent from my HTC Vision using Tapatalk 2
demkantor said:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Yeah no idea how to input that into my Nexus.
agentfazexx said:
Yeah no idea how to input that into my Nexus.
Click to expand...
Click to collapse
Follow the directions here.
http://www.talkandroid.com/guides/u...ot-guides/how-to-unlock-and-root-the-nexus-7/
Here's one with a video.
http://www.droid-life.com/2012/07/17/how-to-unlock-the-nexus-7-bootloader/
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
How bout instead of learning about it you just sell it to me on the cheap... no more headaches for you!
Sent from my Nexus 7 using xda premium
Hi all,
I'm freaking out here. I was trying to install a kernel on my N4 using the Toolkit and somehow it said it was done successfully but then my phone got stuck on the Google screen and was never able to start up again.
I do have a Nandroid back up but unfortunately it's on my computer and not on my phone.
I tried using the toolkit AND adb to push the files to my phone but I get the same message: "failed to copy to sdcard: No such file or directory".
I'm completely stuck now and am panicking. Somebody please help!
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Might also be helpful if you specified which kernel you flashed. As long as you didn't flash a kernel for a different device (e.g. nexus 7) you can definitely recover. To reiterate what others have mentioned, fastboot is your friend. There are numerous tutorials on his to install and use it. Check the stickies.
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My main problem is I need to get my Nandroid backup onto my phone. For some reason, because it's stuck on the Google screen, it's not able to write to the sdcard. Can someone please help me get my files from my computer to my phone?
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Unjustable said:
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your help. I've successfully follows the instructions and got back to Android 4.2.2.
I still want to restore my previous Nandroid though. Although I have placed it in the Clockworkmod backup folder, it's not being seen by CWM recovery. I tried backing up a new nandroid just to test and CWM sees the one it backs up.
Anyone know how I can get CWM to recognize the Nandroid which was done through the toolkit?
Thanks!
darkwolf1789 said:
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Click to expand...
Click to collapse
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Crisisx1 said:
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I realize that now. But any idea how to get CWM to recognize my Nandroid that I did with the toolkit? Anyone?
joshnichols189 said:
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
skezza said:
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
Click to expand...
Click to collapse
Ok well to solve the problem I did download the stock images and flash them according to Effrants guide:
http://forum.xda-developers.com/show...php?p=34552123
Then the reason that CWM wasn't recognizing my Nandroids was because I had them in /sdcard/clockworkmod/backups, but they should be in /data/media/clockworkmod/backup.
I recovered everything and I'm back! Thanks for your help everyone.
I was on stock 4.2.2 with TWRP installed and I took the OTA to 4.3. Now whenever I try and access my recovery it dispays the Android mascot lying on its back, chest open with a red triangle with an exclamation mark above. I tried flashing TWRP 2.6 via fastboot twice but I still get the same error. How can I fix this? Thank you!
What Fastboot command did you do?, toolkits can't help on 4.3.
The android getting operated on is a security feature so criminals cannot get your data, it is Volume up and power to access the stock recovery on that screen.
Sent from my Nexus 4 using Tapatalk 4
Same exact situation. Stock 4.2.2 with TWRP installed (version 2.6) and then did the OTA. Losing TWRP and root in this situation is normal. I also could not reinstall TWRP the normal fastboot way, and then I saw the following on several forums, and it installed jut fine:
fastboot-windows -c "lge.kcal=0|0|0|x" flash recovery recovery.img
pjc123 said:
Same exact situation. Stock 4.2.2 with TWRP installed (version 2.6) and then did the OTA. Losing TWRP and root in this situation is normal. I also could not reinstall TWRP the normal fastboot way, and then I saw the following on several forums, and it installed jut fine:
fastboot-windows -c "lge.kcal=0|0|0|x" flash recovery recovery.img
Click to expand...
Click to collapse
I managed to fix this after trying a variety of things. All I had to do was rename the downloaded TWRP file and flash using "fastboot flash recovery twrp.img" and it worked flawlessly.
andyabc said:
What Fastboot command did you do?, toolkits can't help on 4.3.
The android getting operated on is a security feature so criminals cannot get your data, it is Volume up and power to access the stock recovery on that screen.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
What do you mean by toolkits cant help?!
I still can root my 4.3 JB via toolkits like wugfresh etc?! Right?!
And i too got the same problem couple of days back while rooting manually, so finally had to flash stock.
Sent from my Nexus 4 using xda premium
ssbnasa said:
What do you mean by toolkits cant help?!
I still can root my 4.3 JB via toolkits like wugfresh etc?! Right?!
And i too got the same problem couple of days back while rooting manually, so finally had to flash stock.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Rooting your device running 4.3 by booting a unsecure 4.2.2 kernel?, not really what I had in mind and not really recommended what so ever...
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Rooting your device running 4.3 by booting a unsecure 4.2.2 kernel?, not really what I had in mind and not really recommended what so ever...
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No not about booting an unsecure kernel, i'm talking about using toolkits for rooting 4.3 via toolkit :|
They're goog to go right?!
Sent from my Nexus 4 using xda premium
ssbnasa said:
No not about booting an unsecure kernel, i'm talking about using toolkits for rooting 4.3 via toolkit :|
They're goog to go right?!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well the kernel may contain something which allows support and causes no damage so yes.
Sent from my Nexus 4 using Tapatalk 4
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
wrong advice, my mistake... thanks for the reminding simms22.
But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app
You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken
Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks
darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.
Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app
will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.
simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk