Hi there!
It would appear that my tablet is dead. I wiped the system partition in TWRP, expecting it to restore it to it's factory default (I edited the build.prop, and couldn't update using sideload, OTA, or install zip).
I need help, what do I do. TWRP says that there is no OS installed, so what do I do. I have a backup that includes /system, but will that do? I want to update to 4.4.2 from 4.4. I want to get rid of root, and all the changes to build.prop and any other changes made to my device, then flash stock recovery and lock the bootloader.
Download the toolkit boot into fastboot and install 4.4.2 via the toolkit and then unroot also via the toolkit.
Sent from my SGH-T679 using Tapatalk
Related
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
Hello all, I just had a quick questions for those of you who have unlocked / rooted your Nexus 10 and installed the factory image:
1. Did you all use the toolkit in the Android Dev Forum for Nexus 10 to achieve the root?
2. Once you flashed a custom recovery was installing the factory image as simple as downloading the zip from google (https://developers.google.com/android/nexus/images#mantaray) and then flashing it via recovery and rebooting AFTER you unlock the bootloader etc?
I was under the impression that once you Unlock / Root, you have no OS on your device, is this correct? Or can I root and Android 4.2.1 will still be there, albeit completely wiped of my user data from before.
Thanks for the help, don't wanna get started on this until I know what I'm doing! Don't want a $400 makeshift frisbee disk
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Fromako said:
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Click to expand...
Click to collapse
Thanks! I think I will go through with using the toolkit tonight and see if I can get it to boot into the factory image. Glad that it sticks around (hopefully) if not I can just flash 4.2 from google via TWRP...thats what I needed to know
So really all I need to root is this:
1. fastboot oem unlock
2. fastboot flash recovery [recovery.img]
3. Boot into recovery
4. Flash SuperSU.zip? --- Where can I download SuperSU.zip ?
5. Wipe Cache / Factory Reset via TWRP wipe data
6. Reboot
7. Profit?
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
TheEmpyre said:
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
Click to expand...
Click to collapse
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Fromako said:
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Click to expand...
Click to collapse
I just finished successfully rooting...got hung up after I unlocked the bootloader and flashing TWRP but all I had to do was Format the Data and wipe cache after to successfully boot into the OS. After that I was able to load SuperSU to my SDcard and then flashed it, reboot, did root-checker and I'm all good! Thought I was screwed there for a sec cuz I didn't pre-load SuperSU or the factory image in-case it hit the fan and I wasn't able to mount my SDcard storage via TWRP...Figured it all out though thanks for the help! Glad I was able to do it without the tool-kit!
Hi all!!
On my Nexus 7 2012 (rooted) I'm running android 4.3 rom and I'm trying to manually update it to the new 4.4. It's not letting me flash the update because I changed the boot animation, and (of course) I forgot to backup the stock animation before adding the new one. I downloaded the stock "X" animation from someone and replaced the old one with the stock animation, but it still comes up with an error. Is there any way I can get it back to it's unaltered state so the update won't flag it as a problem? Also, if that's the only thing I altered and I can get it back to normal, can I just wait for the OTA update?
Other info:
Running M-Kernel
Using TWRP
Thanks!!
Same here
Download the factory image for 4.4 and flash it over adb, can't go wrong with that. Only thing is you'll have to re-root and reflash TWRP after that.
Sent from my non-Apple device via XDA App
cr0wnest said:
Download the factory image for 4.4 and flash it over adb, can't go wrong with that. Only thing is you'll have to re-root and reflash TWRP after that ...
Click to expand...
Click to collapse
+1 on flashing the factory image via ADB - easy enough to re-install Custom Recovery & then Root by pushing SU v1.69
Otherwise, if running TWRP - look here, download the zip file and flash it from Recovery (first, full wipe - cache, dalvik & factory reset) - it will bring you to KitKat 4.4 (KRT16O)
There is a minor update (1.4MB in size) to KRT16S - flash it next once it's downloaded, and, then, reinstall TWRP and then root it.
Setup tablet, restore google account & customize home screen - enjoy.
Backup important files & data first, as always.
Hello, I have a 2012 WiFi Nexus 7. I recently read a post that has the link to the latest android lollipop 5.0 system image tgz file available which they extracted from the servers of Google, before they updated the website.
Excited, i downloaded the image, and tried to flash it via wugfresh's nexus root toolkit. (i was rooted). I extracted the tgz file and flashed the different partitions one by one via the toolkit. When i tried booting it, it stayed on the google logo. So went back to bootloader and tried to boot into recovery, but it said on the top left corner in small fonts that "could not boot"or something similar to that. worried, i flashed twrp via adb from the toolkit manually and rebooted normally into recovery. The log said it couldnt mount /system and /data. so i formatted the system and cache partition via adb and formatted /data from twrp. i somehow managed to push a slimkat ROM zip in the internal storage and install it. No gapps, no root nothing. its just like that, functioning normally. i have the original 4.4.4 tgz file. should i flash it via android sdk adb?
Can i be sure it wont give me such problems? and why did such a thing happen? please help me out
niranjan_23 said:
Hello, I have a 2012 WiFi Nexus 7. I recently read a post that has the link to the latest android lollipop 5.0 system image tgz file available which they extracted from the servers of Google, before they updated the website.
Excited, i downloaded the image, and tried to flash it via wugfresh's nexus root toolkit. (i was rooted). I extracted the tgz file and flashed the different partitions one by one via the toolkit. When i tried booting it, it stayed on the google logo. So went back to bootloader and tried to boot into recovery, but it said on the top left corner in small fonts that "could not boot"or something similar to that. worried, i flashed twrp via adb from the toolkit manually and rebooted normally into recovery. The log said it couldnt mount /system and /data. so i formatted the system and cache partition via adb and formatted /data from twrp. i somehow managed to push a slimkat ROM zip in the internal storage and install it. No gapps, no root nothing. its just like that, functioning normally. i have the original 4.4.4 tgz file. should i flash it via android sdk adb?
Can i be sure it wont give me such problems? and why did such a thing happen? please help me out
Click to expand...
Click to collapse
Don't use toolkits
Better flash the factory image from 4.4.4 and try again
GtrCraft said:
Don't use toolkits
Better flash the factory image from 4.4.4 and try again
Click to expand...
Click to collapse
So you mean i flash using the adb provided by google?
btw, i uninstalled the nexus toolkit but let the drivers be in the system. do i have to remove those too? if yes then how?
and r u sure my filesystem wont get corrupt again with stock adb? coz i never used the toolkit for my nexus 4 for as many times ive flashed; ive used stock adb.
why did this happen although?
Apparently a lot of people(including me) stuck in the boot animation while upgrading nexus 4 using the official OTA. Is it possible to upgrade to 5.0 without complete reset of the phone? I know I can backup everything, it is just kind of annoying and stupid. I have tried using fastboot command to flash everything but the user data img, and it will stuck as well. How did you guys upgrade yo 5.0?
You have to be 100% stock recovery, system, and kernel for the ota to work. If you're not flash the system, recovery and boot images from 4.4.4 in fastboot. Then try the ota again.
Sent from my Nexus 5 using XDA Free mobile app