Hi there,
I have a N7 (2012) with an issue.
First, I am familiar with fastboot, adb, etc. The tablet bootloader is locked (unfortunately), there is a stock recovery, and the tablet is running the stock rom (4.3, forgot the build number).
It has been working fine for months, but now when turning it on it goes to a black screen with just the google logo. It never displays the boot animation (the x).
I know for sure I could reflash the stock rom, but the tablet is my brothers and he really wants to somehow save his game progress (in games such as Jetpack Joyride, Temple Run 2, Iron Man 3, and one other).
I can’t…
….. flash any partitions (such as reflash system, boot, recovery, etc.)
….. boot a custom recovery (that has adb so I can do a adb backup)
…… boot the tablet to turn on usb debugging
…… do an adb backup from stock recovery.
I did however wipe cache from the stock recovery to no avail.
Before anyone says “check the drivers”, both fastboot devices and adb devices (fastboot in bootloader, adb in recovery, after selecting sideload update from adb) display the tablet.
Anyone have any ideas (or know if these games backup to play games somehow?) on how to save his game data?
Anyone have any ideas on how this happened? Since stock android should only be able to write to cache, userdata….. and not system, boot, etc… which partition has the issue?
Thanks in advance for all the help.
Bump
Related
Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?
Solved: it was my TV. So check your TVs! plug your Q's to regular computer monitors instead
Hi guys,
today i finally bit the bullet and got myself to install cm10.1 on my Q. I'm no stranger to adb and fastboot, and consider myself a fairly advanced user, but i cannot figure this out.
I fastboot oem unlock_accept the ball, fastboot boot recovery using koush's official cwm image and adb pushed cm10.1-20130228 and gapps to the Q, wiped cache, dalvik, factory reset and then flashed both zips, but the Q won't boot.
It stays with the blue ring on, the TV says "no signal", and there's no adb logcat whatsoever
I also tried flashing an older nightly (20130218) without flashing gapps, but it won't work either.
I've waited for it to boot for around 20 minutes, so I figured it's not that I had to wait for it.
any experiences to share? does cm10.1 take that long on the first boot or i really screwed up something?
I used these instructions http://wiki.cyanogenmod.org/w/Install_CM_for_steelhead
Hi, after researching for the 3rd day straight I'm ready to make a post about this. Hopefully someone has some information I may have overlooked that can help me.
I have a completely stock, not rooted, boot loader locked Nexus 4 that was on the latest 4.4 OTA update (received OTA from Google). It was completely stock until I decided to enable the ART java runtime in developer options. The phone then updated my applications, rebooted and now displays the KitKat four circles boot animation for an unlimited amount of time (I've let it run for up to 30 minutes so far).
My question is: Is there any way to recover my pictures?
Every method I've looked into involves a step that requires wiping the phone and deleting my pictures. I've researched the ADB pull command and it appears that I can't run it successfully without being rooted, and I can't root without unlocking the boot loader, and unlocking the boot loader always wipes the phone (which deletes my pictures).
-USB debugging is not enabled
-I can boot into fastboot and I can load stock recovery.
-I downloaded the latest 4.4 full OTA zip file and sideloaded it ("adb sideload update.zip") but my phone still will not continue beyond the KitKat loading animation.
-I have tried wiping the cache and had no improvements.
-When I boot into recovery and use the command "adb devices" it reports my phone's serial number with the message "sideload" next to it.
I am uncertain about exactly how to use adb pull but the following attempts result in the message, "error: closed"
adb pull /data/media c:\android\backup
adb pull /data/media c:/android/backup
I have Wug's Nexus Root Toolkit v1.7.9 but it says that in order to use the "backup data/media" tool on Android 4.4 my boot loader must be unlocked (which will wipe my pictures).
Does anyone have any suggestions or advice? The pictures were recently taken and I delayed a little too long on backing them up.
Thanks for your time!
Android-SV650 said:
Hi, after researching for the 3rd day straight I'm ready to make a post about this. Hopefully someone has some information I may have overlooked that can help me.
I have a completely stock, not rooted, boot loader locked Nexus 4 that was on the latest 4.4 OTA update (received OTA from Google). It was completely stock until I decided to enable the ART java runtime in developer options. The phone then updated my applications, rebooted and now displays the KitKat four circles boot animation for an unlimited amount of time (I've let it run for up to 30 minutes so far).
My question is: Is there any way to recover my pictures?
Every method I've looked into involves a step that requires wiping the phone and deleting my pictures. I've researched the ADB pull command and it appears that I can't run it successfully without being rooted, and I can't root without unlocking the boot loader, and unlocking the boot loader always wipes the phone (which deletes my pictures).
-USB debugging is not enabled
-I can boot into fastboot and I can load stock recovery.
-I downloaded the latest 4.4 full OTA zip file and sideloaded it ("adb sideload update.zip") but my phone still will not continue beyond the KitKat loading animation.
-I have tried wiping the cache and had no improvements.
-When I boot into recovery and use the command "adb devices" it reports my phone's serial number with the message "sideload" next to it.
I am uncertain about exactly how to use adb pull but the following attempts result in the message, "error: closed"
adb pull /data/media c:\android\backup
adb pull /data/media c:/android/backup
I have Wug's Nexus Root Toolkit v1.7.9 but it says that in order to use the "backup data/media" tool on Android 4.4 my boot loader must be unlocked (which will wipe my pictures).
Does anyone have any suggestions or advice? The pictures were recently taken and I delayed a little too long on backing them up.
Thanks for your time!
Click to expand...
Click to collapse
u can use adb while unrooted, but the error: closed is because the device is in fastboot mode. u can try to backup /data/media while on stock recovery.if it dosent work, then just sending to jtag, so they dump the nand.
Your adb command is right but that's only for custom recovery. ABD is not allowed in stock recovery for good reasons, otherwise it's a huge security risk.
There really isn't a way to back up your data of you have stock recovery and locked bootloader. You'll have factory reset to lose everything and see of it boot or unlock and install factory image.
Next time sync your photos with Google or DropBox, or leave the bootloader unlocked so you can not into recovery and retrieve the data.
sent via tapatalk
hey, there is jtag dump BUT, some ppl say that if u clear cache on stock recovery,then restart and connect to pc u can backup your things because of adb being enabled.other says that on boot with cleared cache it will mount on pc as normal.u can try that.
so i feel like Ive tried everything.
tried to flash a rom and gapps in twrp and phone booted to warning screen with the yellow triangle.
passes that and then goes to google splash screen with unlock icon. and then repeats to the cycle.
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
my phone is unlocked.
computer can see it as fastboot devices
computer CANNOT see it under abd devices
i am able to install and get into TWRP using skipsoft tookkit.
i feel like i am running out of things to flash onto the device haha
any help is appreciated.
barrackOBAMA said:
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
Click to expand...
Click to collapse
First, I'd recommend staying away from Toolkits, as you can't really see what's happening and diagnose issues. Since you've used fastboot/ADB commands, you know they are faster anyway. When you say your PC can't recognize your device in ADB, was your device in recovery? Make sure you're in recovery and you're ready to receive ADB commands. If you CAN see your phone with fastboot that means you're in the bootloader, whereas you have to boot into recovery to see your device via ADB.
Also, you didn't outline anything else you may have done. Did you restore from a nandroid with a buggy version of TWRP? Your issue sounds like the TWRP EFS restore bug (3.0.2-2). It effectively bricks your device, but there is a thread here that discusses it. Effectively you need to be recovery ADB mode and run a couple commands to delete your EFS partition and that will fix the issue.
More info here: http://forum.xda-developers.com/nexus-6p/help/im-stuck-google-logo-stop-reboots-twrp-t3452842
Make sure you've also installed the updated 3.0.2-3 TWRP as it will work with encrypted data and doesn't have the EFS bug.
Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).
Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate
unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself