Database Users

HELP : No Recovery

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

[Q] Recovery issues after OTA update to 4.3

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

Need help on OTA update with Nexus 7 2012 Rooted

Hi,
My Nexus 7 3G 2012 was rooted, stock rom 4.3 but I've deleted some APK in the system partition. Now my Nexus 7 received an OTA update for the KitKat. What is the quickest way to safely update to the 4.4 while maintain all of the installed apps and userdata?
Thanks

1. Download the official KitKat image files from Google
2. Extract system.ing and boot.img from it
3. boot into bootloader
4. fastboot flash system system.img
5. fastboot flash boot boot.img
6. reboot your system
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
1. Download the official KitKat image files from Google
2. Extract system.ing and boot.img from it
3. boot into bootloader
4. fastboot flash system system.img
5. fastboot flash boot boot.img
6. reboot your system
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tks for your reply.
So all data and installed apps will be inact?
Sent from my Nexus 7 using Tapatalk

Yes, I am doing it always in that way, because I have a rooted system and normally there are often problems with applying the OTA. Flashing boot and system will keep your data and apps which are located on the data partition. If you want to be really sure to have a clean system, I would also flash a custom recovery, boot directly into recovery and wipe dalvik-cache, but this is not really needed.
Sent from my Nexus 7 using xda app-developers app

This is interesting and really new to me.
Could you please precise, which tools you use? A little how-to would be very helpfull to get along with the bunch of possibilities coming with TWRP and/or wugfresh´s toolkit.

I am using no tools / toolkits as I want to have full control on the flashing process. Probably you might want to have a look at my blog. Here I described the update process already some time ago (not to go to 4.4, but the steps and the mechanism are the same).
Sent from my Nexus 7 using xda app-developers app

Ok tks for your response.
However my friend confirmed that he updated successfully to 4.4 via OTA while rooted.
Sent from my Nexus 7 using Tapatalk

I have used this method every update. Only takes about 5 minutes.
It amazes me all the convoluted methods and bricked devices that you see, when if people would do a little research and had a little understanding of what they are doing it would save them a lot of grief.
All I can say is thanks to the person who wrote this simple how-to.
Now I will get off my soap box.

[Q] Nexus 7 (2012) - TWRP No OS Installed - Are you sure you want to reboot? Bricked?

Hi, I booted into TWRP recovery mode to attempt updating my rooted Nexus 7 from 4.2.2 to 4.3. I wiped system, dalvik cache and cache. I also (stupidly) wiped data and internal storage too. Now I cannot turn on my Nexus 7 fully, it only shows the Google insignia with the unlocked boot loader icon below it.
I can boot into recovery mode and I can USB host, I tried copying a zip of the stock 4.2.2 ROM for Nexus 7 wifi onto my flash drive and tried flashing under the "install" section on TWRP but it always fails (I do not know why).
I cannot connect my Nexus 7 to the computer. Can anyone help me out, please?

Use adb side load in advanced settings
adb sideload nameofrom.zip
adb sideload gapps.zip
Reboot
Profit
Sent from my Nexus 4 using XDA Premium 4 mobile app

Either flash a custom ROM from recovery or use the Wugfresh toolkit to flash a stock ROM.
Sent from my IdeaTab A3000-F using xda app-developers app

dimbo33 said:
Either flash a custom ROM from recovery or use the Wugfresh toolkit to flash a stock ROM.
Sent from my IdeaTab A3000-F using xda app-developers app
Click to expand...
Click to collapse
Agreed, the toolkit works like a charm.
I had also deleted the whole Os and fixed it with the help of the toolkit.

Not sure why folks keep telling you to flash a custom rom when you ha e clearly stated that it fails. So, heres my two cents......
Since you already wiped the internal memory and there is no chance of data loss, just download the stock image and fastboot back to a fresh system. And for gods sake, dont use wugs. Just use good ole fastboot. There is a very easy how-to in the stickies of this section. This forum is full of problems arising from toolkits, that could have been easily avoided by fastboot.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Toolkit to Rescue
dimbo33 said:
Either flash a custom ROM from recovery or use the Wugfresh toolkit to flash a stock ROM.
Sent from my IdeaTab A3000-F using xda app-developers app
Click to expand...
Click to collapse
I SECOND that use the toolkit from wugfresh for this.
ADB sideload and Fastboot is a real pain with TWRP don't know why the file does not get pushed at all.
Save yourself time and just use the toolkit if it's a Nexus device if Samsung find a similar toolkit tool
The site for toolkit is wugfresh . com ( no urls so the space )
Hope this helps someone
Good luck
Martin

brenmartin said:
I SECOND that use the toolkit from wugfresh for this.
ADB sideload and Fastboot is a real pain with TWRP don't know why the file does not get pushed at all.
Save yourself time and just use the toolkit if it's a Nexus device if Samsung find a similar toolkit tool
The site for toolkit is wugfresh . com ( no urls so the space )
Hope this helps someone
Good luck
Martin
Click to expand...
Click to collapse
Why are you necro'ing old threads to spam wug's website?
Sent from my Nexus 5

Nexus 7 2012 stuck in safe mode

When I restart Nexus 7 it always boot up to safe mode. Tablet first shows bootloader menu and when I choose to start, it boot in to safe mode. It looks like volume down button is always pressed on but it don't work - does nothing in bootloader menu, and in safe mode.
I don't use it for some days. I don't remember the tablet being flooded or hit. It just appears. First I thought that it was caused by some bug in LineageOS. I made factory reset, and when it does nothing I set u Android 5.1 again but that also didn't work.
Do you have any idea why this is happening?

You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?

AndDiSa said:
You mean you are always booting into recovery when starting up the device? This may happen if there is no valid boot.img / system.img installed. How did you install the current system on your device? Do you have an unlocked bootloader? Do you have the latest bootloader (4.23) installed on your device?
Click to expand...
Click to collapse
Last thing I did is option Flash Stock + Unroot in Nexus Root Toolkit.
Yes I have bootloader 4.23.

Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
Sorry, but I don't know what the toolkit is doing and whether everything went as expected .. that's the disadvantage of using toolkits.
Best would be to learn how to install and to use fastboot and after that you can decide either to flash stock factory image again or to upgrade to one of the custom ROMs available for the Nexus 7.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I think you don't understand me. Nexus Root Toolkit have nothing to do with this. It works 3 years with my Nexus 4 and 1 year with Nexus 7. This problem appeared long after installation of LineageOS.
Ok, I installed Android 5.0 manually and I still have this problem.

Did you notice any error messages while flashing the stock image? Did you do a factory reset after returning to stock?
I am still thinking that your bootloader is closed and you are not really flashing / changing the ROM, but flashing fails and you are remaining in the same state as before. Just as an idea ...
Sent from my Nexus 7 using XDA Labs

I would do one step at a time assuming fastboot and adb work. Search for adb minimal. Download stock zip to same directory. Run fastboot oem unlock. Unzip stock zip and try running flash-all.bat it flashes compatible bootloader and stock zip. If that doesn't work img files are inside stock zip and can be flashed separately.
Sent from my Nexus 6 using Tapatalk

Sorry for leaving you like that.
I took the risk and ordered flex cables with volume buttons. Now the tablet works fine. I'm sorry for the trouble.