[Noob Guide] How to recover from a brick - Asus Eee Pad Transformer Prime

First off, I would like to say that I've been rockin Android since Donut. So I wouldn't necessarily say that I'm a noob, but I'm definitely not an advanced user. I have rooted and unlocked a couple phones but this is my first tablet. My goal for this post is to come up with a noob friendly guide on how to unbrick the Asus Transformer Prime.
Disclaimer: Proceed at your own risk. I am only responsible for what I do, not what you do. This is just documentation of what I have done.
I rooted my Prime using Debugfs automated root. Then I unlocked it using the Asus Device Unlock App. I used ClockworkMod Recovery (came with the root) to flash various Jelly Bean roms (for some reason, I couldn't do it from Rom Manager so I had to boot it into recovery manually). Because of all of the button pushes and holds, I decided to install Team Win Recovery Project (TWRP). My Prime started acting strangely so I switched back to ClockworkMod. It was all down hill from there :crying:.
Ultimately, when booting up normally I get stuck on the start up screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I plug in to by computer via USB, Windows will recognize it. You can check in the Device Manager (on Windows XP Start --> Control Panel --> Switch Classic View if in Category view --> System --> Hardware --> Device Manager). Note: I am using the Naked Universal Driver.
Tip: If you hold the power/vol up buttons for about 10 secs it will show a black screen, vibrate, and then shut down (when it is not plugged into computer). When plugged in it will reboot back to start up screen, however, after it vibrates, if you let got of the power/vol up and then hold the vol down button it will reboot to "RCK" screen (just hold the power/vol down buttons to power on, then after vibrate, hold vol down button until you see the "RCK" screen, if starting from a shut down). Just let go of all buttons to go into fast boot selection. Remember, you have 10 secs to make a selection
Now here is a noob area for me. I don't believe I have ever worked in fastboot (if I did it was only once when I rooted my MyTouch 4G...did it the long way with detailed instructions). Once my Prime says "Starting fastboot USB download protocol" that is the end of the journey (for now ).
In all the forums, topics, and posts I've read with similar fastboot issues, they stated it was fixed by installing/reinstalling the drivers. Been there, done that, didn't work for me. It is being recognized in Windows.
Android Debug Bridge (ADB) is another noob area for me. Fortunately I had it on my computer already from the time that I previously rooted my phone so I just updated it. Like I said before, I used it probably only once before so when I read about using ADB, the light bulb is not lit . I know it is included in the Android SDK in the platform tools but other than that... .
Tip: I have a janky computer--got to upgrade soon--so here is a short cut to get to the appropriate path in the Windows Command Prompt. Setting up the short cut is easy but initially adds on a few secs to the process but is so worth it to me. From Windows XP, Start --> My Computer --> Tools --> Folder Options --> File Types --> select Folder, then Advanced --> New --> Action=Open in Command Prompt, Application=cmd.exe, then ok all the way back my computer. Navigate to android-sdk --> platform-tools --> right click on any folder and select Open in Command Prompt.
When I try to see if my device is recognized in ADB by entering ADB devices, it's a no go .
Update: I found a great guide on ADB/Fastboot. I learned that I can't use adb commands in fastboot. I'm tinkering with fastboot and will probably come out with a noob guide a little later...and here it is.
I can boot into Recovery just fine. Tip: Just as I had to do when it was stuck on the start up screen, I have to shut it down with the power/vol up buttons. To boot into recovery, hold power/vol down until you see the "RCK" screen. As soon as you do, let go and immediately hold the volume up button. Technically you have 5 secs.
Unfortunately, I think I wiped everything but the recovery from my Prime. When I try to: install zip from sdcard --> choose zip from sdcard --> clockworkmod/ --> it says no files found. So I downloaded Euroskank on my computer. You can download any ROM you want. It's just a matter of preference. List of ROMs and Kernels
I can see my device in Windows.
And this time I can see it in ADB .
For the sake of simplicity, I cut and pasted the downloaded ROM into C:\ (less to type and less likely to mistype). I also renamed it update. In the command prompt, I pushed the zip by entering adb push C:\update.zip /sdcard/ and gave it a few minutes to do it's thing.
In CWM Recovery, install zip from sdcard --> apply /sdcard/update.zip --> yes - Install /sdcard/update.zip
Once it's completed, reboot and Wah lah!
I hope that I have helped the noobies in a clear and concise manner. Just a word of advice moving forward...before asking a question in the XDA forums, please google it to see if there is an answer. Can you imagine hundreds of thousands of people asking you the same question even after you stepped up to the mic on live TV and gave the answer out? I imagine that's how these "know-it-all" feels :silly:. They can be a little testy, give you a tongue lashing, and then send you on your way. A lot of noobies are intimitated. If we all start documenting our own personal problems and solutions, as I have, then maybe we will get more noob guides.
BTW, I'm not a know-it-all so if you have a question feel free to ask. Just be clear and concise about what the problem is so I don't have to answer a question with a question...Just the answer to the question. If you are greatful for this noob guide, hit Thanks! :good:

Related

3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat

3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat
Ok, So you got your new Super Cheapo MTK8127 quad core Tablet from BestBuy or some other overpriced electronics emporium and want to install root and a custom recovery So it won't suck nearly as bad
Feeling hungry but don't wanna feed yourself??? Open wide......Here comes the airplane requesting permission to land
The Following procedure may "BRICK" your tablet and wipe your porn....You do so at your own risk, Neither Kneee or his lawyer claim to know ANYTHING about android....or anything else for that matter
THIS GUIDE WILL WIPE YOUR PORN!!!
If you've ever seen THIS:http://forum.xda-developers.com/chef-central/android/root-dl701q-install-twrp-touch-recovery-t2980339thread, You know that "iRoot/vRoot no longer works since updating to kitkat. I've BUNGLED my way into a solution, Hope it helps you too.....
THIS GUIDE ASSUMES YOU KNOW HOW TO USE ADB AND FASTBOOT (ENABLE USB DEBUGGING)OR AT LEAST KNOW WHAT THEY ARE AND DON'T SUFFER FROM GOOGLEPHOBIA
#1 Making a backup of this crap software when ADB , FASTBOOT and SP flash tool are working correctly is pointless (IMHO) (inm
Here's Everything you should need:
Stock ROM COURTESY...THIS DUMBASS https://drive.google.com/file/d/0B9DmzLnUt5tuaUtJS1FHcjNyX1U/view?usp=sharing
ADB_&_FASTBOOT_executables, no need to install, just extract the .zip to the directory of your choice and execute openCMD.bat with a right click + run as administrator. it will open a terminal window, you can run all your ADVB & FASTBOOT commands from there:https://drive.google.com/file/d/0B9DmzLnUt5tuM29vOTNHNEZya2s/view?usp=sharing
Driver installer & MTK_SP_FLASH_TOOL for MT8127 use this to install the drivers and flash the stock rom + custom recovery.img https://drive.google.com/file/d/0B9DmzLnUt5tudVlrSEtzSE1tWHc/view?usp=sharing
UBIFS_Modified_CWM FOR FLASHING UPDATE-SuperSU-v2.46.zip COURTESY Vampirefo: https://drive.google.com/file/d/0B9DmzLnUt5tueC04RDFVX3plTVk/view?usp=sharing
UPDATE-SuperSu-v2.46.zipflash this with vampirefo's modified CWM recovery image UBIFSRecovery4SuperSu.img" https://drive.google.com/file/d/0B9DmzLnUt5tuZjlmVm1Wc2tFUTA/view?usp=sharing
TWRP Setup.exe...Used to install TWRP recovery after flashing Stock ROM + Custom recoveryCOURTESY TWRP team & Protocol 9https://drive.google.com/file/d/0B9DmzLnUt5tuTVVJS2d2RERpbVk/view?usp=sharing
STEP 1: INSTALL THE DRIVERS INSIDE THE MT8127 SP_FLASH_TOOL.zip" file you downloaded It will install the mtk usb vCOM driver we need for the mtk8127. if u have questions PM vampirefo. after that, turn your tablet upside down, FIND THE reset hole and jam the nearest tiny object in there until the screen does something different (like go black) release the reset button, hold VOLUME DOWN and plug in the USB cord and the tablet should be reconized as a preloader USB VCOM Port device under "Ports" in Device Manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, the necessary driver to save this POS is at hand. after it's done installing the tablet will probably reboot and the remaining drivers will install. (EVEN WITHOUT THE OTHER DRIVER YOU CAN ROOT AND FLASH NOW)
Fire up the MT8127 SP flash tool (run as administrator) you downloaded and you should see this:
Click "Scatter-Loading" and select the scatter file located in the stock rom folder you downloaded and unzipped (you DID unzip it right?) and click the "RECOVERY" FIELD LOCATED HERE:
and select the recovery image you downloaded called "UBIFSRecovery4SuperSu.img......yay, you should be all set up and ready to go!
Make sure youve already unplugged the USB cable AND hit the reset button. HIT THE DOWNLOAD BUTTON (the program is now waiting for your device...no rush) HOLD VOLUME DOWN AND PLUG IN THE USB CABLE, the computer will detect the device, the program will proceed to shove a bunch of ones and zeros down the the tablets throat and it will reboot (hopefully to a mediatek logo).
If so, youre not as stupid as everyone says when u leave the room
Toss "UPDATE-SuperSU-2.46.zip" on a microSD, Power off the device, shove the SD in his home and hold POWER + VOLUME UP until you get prompted to select either RECOVERY OR FASTBOOT, we want recovery so make sure it's selected and press VOLUME DOWN to boot into recovery & install your SuperSU.zip and reboot
once the OS is fully running, run TWRP.exe as ADMINISTRATOR in AUTO mode, TWRP recovery should be installed and u should still have root, if not, you'll need to go into advanced, then mount system before re-installing from zip.
NOW learn ADB and fastboot so I can save my breath next time:
PS, all your GAPPS are gone....quit *****ing, I've got em here: htpa_gapps-modular-micro-4.4.2-20140608-signed.zip(pa_gapps-modular-micro-4.4.2-20140608-signed.zip 85.3MB) & HERE: https://drive.google.com/file/d/0B9DmzLnUt5tuSl9lME9VZnFJTU0/view?usp=sharing(pa_gapps-stock-4.4.2-20140608-signed.zip 267MB))
I have requested this thread be removed, you are using my stuff without permission, and even crediting yourself with the firmware, I took the time to download, you yourself have done nothing but take others work including mine without permission.

How to root the Homtom HT16

Hi there,
I recently got the Homtom HT16 for just 50 bucks. I've always rooted my phones with a one-click rooting app(kingoroot etc.), but it seems not to work. I did some reading and saw you need TWRP to root the device. Now there is no TWRP for the device, saw on xda there was for the HOMTOM HT7.
Anyone knows if I can use the TWRP for the HT7 or is there any other way to root my phone?
Sorry for late response. On Russian forum you may find way to install recovery with Flash tool, however that didn't worked for me. Their TWRP recovery is useful for rooting. This is 100% tested, I own HOMTOM HT 16.
1. Install adb-setup-1.4.3 to enable adb, fastboot and Google USB driver on computer..
https://www.dropbox.com/s/wvsyab1iakpsswu/adb-setup-1.4.3.exe?dl=0
2.Settings-Developer optons Enable USB Debugging and Allow OEM unlocking
3.Put on sd card SuperSU-v2.78-201609011115 (this version worked for me).
https://www.dropbox.com/s/84xm1m7rxerg6kt/SuperSU-v2.78-201609011115.zip?dl=0
4. Turn off the phone, press Power and Volume up. You'll see new menu. Move with Volume up, choose Fastboot and press Volume down. Connect computer and phone with USB cable.
5. Find the directory where adb and fastboot are installed and position itself there . Hold Shift, right-click and choose Open command window here. ( If you are not the administrator, Windows 10 Start, Command Prompt (Admin) and position yourself in directory where fastboot is installed with cd command).
Copy TWRP recovery (recovery.img) in that folder.
https://www.dropbox.com/sh/t26oax8n96izp60/AACq00Cgo1iMFOWPAT8leRXZa?dl=0
5.Type and execute commands:
fastboot devices (check if device if recognized, you'll see the serial number)
fastboot oem unlock (press Volume up to unlock bootloader)
fastboot flash recovery recovery.img (install new recovery on phone)
6.Pull out battery, push it back . Hold Power and Volume up. You'll see new menu. Move with Volume up, select Recovery and press Volume down.
7. Don't make attention to blinking and bad performance of Recovery. Select Install, find SuperSu on sd card and install. If everything is ok, you will see notification that superuser is successfully installed.
8. Reboot phone and check with Root checker application root rights.
(optional) If you need restore factory recovery and remove Superuser, to keep warranty valid.
https://www.dropbox.com/sh/s6dvqr8ge72otfu/AACgOQ7CgrVk94o0_K6ACXtIa?dl=0
Hi, all I received yesterday the z11 max. Install recovery with super your and comborom V6.2 all ok. Problem does not update ota, it tells me no updates. I have made to the wrong? Thank you.
Hi.
After step 6. I could not enter in the new recovery menu. I get some error messages (attached picture) then the phone is restarting. What could be the problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 06:41 PM ---------- Previous post was at 06:34 PM ----------
The image not visible, these are the error message:
'Could not mount /data and unable to find crypto footer'
`Unable to mount storage`
and so one....
pecs72 said:
Hi.
After step 6. I could not enter in the new recovery menu. I get some error messages (attached picture) then the phone is restarting. What could be the problem?
...
and so one....
Click to expand...
Click to collapse
I downloaded the original fw from needrom, then I put back the original recovery.img, so now it's as original, but without root...
I don't know what is the problem, this procedure worked on my phone.
Look here:
https://forum.xda-developers.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331
**** my phone factory resseted it self
No matter what I do, my phone doesn't allow to be found when I make "fastboot devices".
Can someone that have rooted the phone please do a readback of the entire rooted rom and upload for me?
I'm facing a lot of problem installing the recovery , so if someone can please post a rooted rom it'll be useful ...
Edit : can someone backup his nvram partition? I lost my imei and with this phone any trick wont work...
dani the hack said:
Can someone that have rooted the phone please do a readback of the entire rooted rom and upload for me?
I'm facing a lot of problem installing the recovery , so if someone can please post a rooted rom it'll be useful ...
Click to expand...
Click to collapse
Hi, for me the SuperSU from holocen (see above):
togeter with the TWRP image, flashtools v5 and the description from needrom worked for me (not every emailprovider can be used to create an account):
needrom.com/download/homtom-ht16-4/
Greetings Rikski
Solution found in here!!
Use TWRP for cyanogen after installing it with sp tools v5.
Put SuperSU v2.82 or above in the phone or sd memory card go to custom recovery and install the SuperSU v2.82.zip file. Reboot and that's it. It works like a charm. :good:
7. Don't make attention to blinking and bad performance of Recovery. Select Install, find SuperSu on sd card and install. If everything is ok, you will see notification that superuser is successfully installed.
How long does blinking take usually? It blinks all the time, I can't select Install ?!
This phone has now nearly 30 ROMs on needrom.com
Plus a non blinking custom TWRP recovery, go check it out:
needrom.com->Doogee->Homtom->ht16
I tryed to follow the guide of holocen (also used much of external information) but right now i'm stuck in a bootloop.
First of all i needed hours of reading and troubleshooting to get my adb "cmd" working proberly with the "bootloader mode" (cause of a driver problem).
After i was successful ("fastboot devices. fastboot oem bootloader) , i tryed serveral twrp recovery *.img's (officials first, holocen's later on), but i can't get the ht16 out of bootloop. Recovery flashing seems to be successfull though.
If i try "volume up + power" and start up the recovery manually, i got the twrp splashscreen, followed by a huge chunk of red "unable to mount xyz..." with a following bootloop (there are only seconds to see whats happening, an then the "HomTom" splashscreen reappears). I tryed "fastboot erase userdata" with no help. Was insecure about the "fastboot erase system" command though.
Maybe some of you guys are eager to help. I really tryed to read up as much information i could about this topic. I thank you in advance.
Target was to root the phone and to install some kind of lightwight custom rom (just to get rid of those frikk'n "trojans, bloatware-viruses, marketing horrors" which are messing with the stock rom. Hopefully everybodys know right now what i'm talking about).
I try to respond quickly, but i can't garuentee.
Thank you very much for reading.
Best regards
B4dLuck

Unbrick Asus MemoPad FHD 10 LTE (ME302KL)

Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working

Start Error in Pixel Experince, by Boot.img flashed by Fastboot (phone almost brick).

Hello friends, I hope you are well. I am writing to everyone to see if anyone can help me with this big problem.
Yesterday install the Rom Pixel Experience, all good, all the steps to perfection and others, had microSD at that time so flash the boot.img by Fastboot. It seems to install the Boot.img in the Recovery TWRP partition, or something like that. Because I do not have the Recovery either, when I try to go to the recovery, the window "Bootloader Unlocked" appears, but it does not take me anywhere, only to the boot of the rom, it is something very strange and the truth scares me. I clarify: I can not access the Fastboot, nor the download mode, nor the recovery, because it does not.
There will be another way: ????
PLEASE IF SOMEONE CAN HELP ME, FIND ANOTHER METHOD TO ENTER THE FASTBOOT OR DOWNLOAD MODE, THE SOLUTION THAT WORKS WILL PAY ME WELL TO THE PROPONGA, PLEASE, I DO NOT WANT TO LOSE MY MOBILE, I BUY IT WITH A LOT OF EFFORT.
Last night I dawned on the boot logo, until it was completely downloaded and at this moment it continues to do so ... By GOD!
When trying to enter the Fastboot or download mode, it takes me here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Image extracted from: https://www.tomshw.it
Then he starts loading the rom and stays there all the time .:
Image extracted from: https://www.tomshw.it
I can not access Fastboot, nor download mode, nor recovery, because it has disappeared. There will be another way to enter the Fastboot or download mode, because the phone actually woke up until I wake up today and was even charged. PLEASE.
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
ZestyManu said:
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
Click to expand...
Click to collapse
Hope this works for you @Yeriorlando. @gimpy1 had a similar issue when installing Havoc ROM. Part of the problem seems to be when installing the custom kernel?
gimpy1 said:
It was operator error (generally is) on my part, I'm sure. The only thing I did different that I can remember is installing the 9.0 boot image in twrp differently. I installed it in the recovery option first (intentionally, should not have), instead of ticking only the boot choice. I did not untick the recovery option (should have never ticked it in the first place, but I was trying to correct a problem on the ROM, and misread a post).
Click to expand...
Click to collapse
He was able to reinstall TWRP using fastboot.
gimpy1 said:
Thx, Chaz. I pulled out my printed instructions from your post, and once I was able to get my device recognized (that did take a couple of tries), reinstalling twrp was pretty easy.
I'm back in business thanks to you.:good:
Click to expand...
Click to collapse
IF you still can't after the suggestion at top, maybe @SGCMarkus or @runningnak3d have some tips?
Unless you have an H932, then if you get the error that: "Your device software can't be checked for corruption" then you have fastboot. It is literally impossible to have that message on a WTF rooted phone and NOT have working fastboot.
So, as @ZestyManu said -- make *sure* your phone is powered off. If you have to let, the battery die. Then hold vol down + plug in the USB cable (no need to touch the power button) and you will enter fastboot.
-- Brian
Thank you all. I have solved the problem in a super crazy way, to pure ADB, not fastboot .... Pure ****ing adb ... Hehehehe. Thanks to @ChazzMatt

ADB Pull possible on boot loop? (Should have been unlocked but maybe not?)

Hello everyone,
I've been googling this for the past couple days it's been driving me crazy. Stock 7 (I think), should have been unlocked but is showing locked.
1. My friend gave me the Nexus 9 which turned off one day, then wouldn't turn on again.
2. I plugged it in, and it turned on fine. Assumed bad usb port, he said keep it. I enabled developer options, then did "OEM [bootloader?] unlock" and "USB Debugging" toggles on (from memory, may not be right phrasing)
3. While trying to back up his data on it by ADB Pull, it would randomly stop. Using it, it would reboot unexpectedly.
4. So I went to Software Update.. bad idea in retrospect probably it rebooted during or something? It was fully charged and on AC power but I wasn't watching it.
5. I come back and it keeps bootlooping. Went into recovery, says "Device Locked" - Tried clearing cache, no difference. Tried sending bootloader unlock command with fastboot, says I have to delete all data to unlock.
The only lead that I have is that it might be possible to image TWRP to recovery, then boot into it so that I can get files off it (With OTG Flash drive or USB?) - I wanted to ask for help here first.
I did my best to search for this prior, but I've been out of the ROM game since 2012 cyanogenmod days.. Hope that it's possible to save my friend's data, and then also to flash a new ROM which will solve the reboot issue.. Thanks!
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
gk1984 said:
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
Click to expand...
Click to collapse
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Code:
PS C:\Users\User Profile\Downloads\platform-tools_r30.0.1-windows\platform-tools> .\fastboot flash recovery twrp.img
Sending 'recovery' (13254 KB) OKAY [ 0.838s]
Writing 'recovery' (bootloader) Device State : Locked
FAILED (remote: 'Can not flash any images while device state is locked!')
fastboot: error: Command failed
Thanks again,
luciant
luciant said:
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
I thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Thanks again,
luciant
Click to expand...
Click to collapse
You need to be in recovery for adb to work. The Android with belly open is recovery but you need to unlock it with a button combo. Fastboot won't work unless you unlocked the bootloader.
I may have the steps a little off for getting to recovery but I'm sure searching how to boot to recover for the Nexus 9 will find you the right steps. It's been a long time since I've used the stock recovery on this tablet.
For future bootloopers: Well in the end, I wasn't able to figure out how to pull files using the stock HTC Nexus 9 recovery. Since it was locked, I wasn't able to install or execute TWRP .img , and unlocking it meant losing the files. It was weirdly looping even in Recovery & Fastboot. I tried every mode, and different drivers in the device manager, but ADB couldn't connect. Maybe it's not meant to for security purposes.
If you're bootlooping even in recovery, try the following:
I gave up on trying to recover the data, and decided to just unlock the bootloader. booted to Fastboot (Pwr+Vol Down on start up, select Recovery, Pwr+Vol Up, should say "Fastboot") Then I used fastboot oem unlock, which unlocked the bootloader and Deleted ALL DATA. Then, I could flash TWRP, using fastboot flash recovery twrp.img. Once I flashed TWRP, I booted to twrp recovery using Pwr+Vol Up at boot, wiped all partitions. Then I went to TWRP Advanced -> ADB sideload. Issued adb sideload ota.zip, and this gave me a clean stock install.
Thanks gk for your advice.

Categories

Resources