Related
I have a G1 running cyanogen 5.0.8. Everything was going well until I wanted to add widgets to my left-side of the screen. Anytime I wanted to add a widget to the left-side of the screen it would force close. So I went to Rom Manger and fixed permission, cause it would help with my force closing issue. So I flashed my recovery to clockwork from RA-1.70. It was successful. Stupid me, was like, "You didn't need to flash clockwork recovery to fix permissions," so I flashed back to RA-1.70." That too was successful. Then I went to fix permissions. Fix permissions was successful. It prompt me to reboot, so I reboot. Now it got really ugly. My phone now stays at the T-Mobile G1 screen, I can't get into recovery, and the only thing I can do is get into fastboot. So in fastboot, it shows "No img. No img. No img. Then returns back to the fastboot screen, until my only options it to shut it down.
So I am screwed or it the hope?
Please help me
Thanks Matt
So is there hope is what I meant to say....my bad
If you can get into fastboot -then there is hope. I made the same mistake - and flashed two recoveries - and that is a problem.
What I had to do was get into fastboot - plug my phone into the usb cord, so that I could communicate with the phone from my laptop. I'm a newbie at this as well, but if you did not know, fastboot allows you to run command prompt from your PC - and send commands to your phone
Once I had fastboot running on the PC - I had to
Wipe the system, and then
flash my recovery image
Once my recovery image was flashed - I was able to
restore my last back-up without issue
others have reflashed their rom of choice
As noted - I too am a newbie, and your best tool will be to read and learn. I am not up to speed at this point as to commands in fastboot, etc - so do not want to write commands - or copy commands from other posts - in case I lead you in the wrong direction. I'm learning as I go along as well.
As noted, if you can get into fastboot mode - there is hope
Did you have to download ADB and SDK? I read some info on fastboot. And it seems like I have to download those programs and download drivers. Also where did you go to get the right commands?
Thanks for replying
I've seen that you have been involved in some of the other posts with similar issues. Yes, you need to download and install adb, and the drivers - check the sticky posts, all links are there for where to download - and how to get started
http://forum.xda-developers.com/showthread.php?t=532719 this is a good place to start
Good luck - take your time, I already bricked my first G1 and then transplanted a motherboard and started over again.
I now read twice, and make changes once - trying to learn from my mistakes, and not make them again
I think I have had the same problem. I fixed permissions via rom manager and then it prompted me to reboot. Now it is stuck at the G1 screen. I can load it up after holding "home+red power button" so that is good I guess. Is my only option to wipe and start over? I do have a backup but it is 1+months old and I dont want to lose everything in the last month unless absolutely necessary.. My mod info is in my signature.. Please help, my phone is out of commission right now and I need it back soon!
any solutions besides the 1 month old backup? or wiping and starting again??
attempted root and used superboot grj22 from modoco pphone is unlocked and after double clicking on indows bat file as directed phone is locked on boot x
this phone has just come back from htc with a new power switch installed and 2.3.4.
anyway could use some help daughter is upset I locked her phone.
can get to boot menu however can not get into recovery. I get a triangle with exclamation in it
thanks
Please read the Wiki, Rooting guide for unlocked bootloader.
Flash recovery through fastboot.
Flash whatever ROM you want from recovery.
You've flashed a wrong kernel (which is contained in "superboot"), that's why you can't boot.
another question
read wiki and followed instructions which said after loading passimg that this was an older version. searched more and found another thread that gave a new file that was supposed to load the older version of the rom and get around the error "older version"
still not working any other ideas will be appreciated
Just to make sure I understand right you tried the frg83 passimg file and you got "main version is older" error? If so then can I just ask you is your bootloader unlocked (at the X screen before the cyanogen mod logo do you see an unlocked padlock)?
hi
yes padlock on screen is unlocked tryed to flash again and get the same error version is older
thanks for trying to help kid leaves for school tonight and is freaking
more
also askes if I want to reboot device
It'll be long fixed by then don't worry
Boot into bootloader then from there select the recovery option. Once there tell me what you see if you see and android with a /!\ next to it then press power and vol+ power slightly before. Then you will get a menu select power down. If you go straight to the menu tell me what color the writing is.
hi
get the triangle white with a orange exclamation in it
Ok then you'll need to flash a recovery via fastboot. So since you bootloader is unlocked I assume you already have the SDK set up and the drivers installed if not then I can help you with that too, but now just download this file and place it in the same directory as fastboot on the computer and download this file and put it on the root of your sd card (not in any folders).
Then boot the phone into fastboot (hold down the trackball while powering up) then connect the phone to the computer via usb and open a command prompt in the directory where you have fastboot. Then input these commands:
fastboot devices (this should return the s/n number from your phone)
fastboot flash recovery recovery.img (where recovery.img is the name of the first file you downloaded earlier)
fastboot boot recovery.img (same thing here)
The phone should then boot into recovery from there use the trackball to navigate go to flash zip from sd card then chose zip and chose the second file you downloaded earlier (the one you put on the sd card), after that wait for it to flash then press vol- to go back to the recovery main menu then select reboot system now and your all good you have stock with root access, if you want to flash a custom ROM then just ask I can explain that too.
As I've said, follow the guide FOR UNLOCKED BOOTLOADER.
You didn't.
The guide for unlocked bootloader is in Unroot/Restore section, called "using fastboot".
Actually, the only thing you need to do is to install recovery. Go to "recovery" guide - again, FOR UNLOCKED BOOTLOADER - and install Amon_Ra's recovery.
Once you have it, you can flash whatever you want, including stock ROM.
ok
everything is good except that i tryed to flash downloaded zip from sd and got error that zip is signed wrong also zip verifacation failed
again thanks excited I got this far.
so after this gets fixed than will phone reboot and go to 2.3.4 that was on there before?
will I be good to go for a new rom and last but least like the miuis and recommendations from an expert?
funny I bought the sensation and forgot how to do all this probably the pressure of the child (oh my god you wrecked my phone) Forgetting of course it was dads to begin with DARN KIDS
me dumb as a box of rocks toggled zip verifacation and ra unzipped.
afraid to push any buttons.
should I reboot?
and then Its ok to load a rom?
thanks
radio should be ok as it was just loaded from htc?
Ya you should be good don't worry you can't brick it by flashing something to the system partition only to the recovery and hboot partitions. Just select reboot system now and all should work fine.
Sorry for the late response I was away from my computer
still stuck on nexus x screen ??
earlier someone posted that when I used superbot I got the wrong kernel?
not sure but still stuck
just tryed to boot into recovery and it wouldnt go
Oh right sorry forgot an important step you kind of need a ROM my bad ok so forget about su you're going to need to flash a ROM I suggest cyanogen mod as a first ROM but it's up to you if you want miui or something then go for it. Here's a link to cm7 http://dl.dropbox.com/u/31690913/android%20files/update-cm-7.0.3-N1-signed.zip
So to flash this simply boot into recovery then go to wipe, wipe all at least 2X I do 5X to make sure then just go to flash zip from sd card and flash the ROM.
In that case do like we did last time and reflash it through fastboot. Now sorry but I gotta go maybe someone else can come and help you if not I'll be back later tonight.
thanks
thank you so much for helping me with this got everything working including the new miui rom.
when you panic just a little you forget all the things you knew how to do before.
thanks again.
I have created this thread to give a step-by-step on how to flash a stock ROM build available on Google's developer site. (For those that are unaware, an unlocked bootloader is needed, and unlocking is part of the instructions below.)
I've also added a section on how to root for those that want it.
Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. See here for some further explanation.
So, without further ado:
How to flash a stock ROM
Step-by-step
Notes:
1) For the n00bs: read the entire post before proceeding;
2) MacOS-specific instructions: a) no drivers needed, and b) replace fastboot in the steps below with ./fastboot-mac
A. Install the drivers
1) Do not install LG drivers or the PDAnet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here or from here;
3) Install the drivers. See here on how to install them. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). (To enable USB Debugging, you first need to enable Developer options by going to Settings->About phone and tapping 7 times on the build number.) If you are using Windows 8, you will need to do this before installing the drivers.
B. Backup your data
1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
3) See here on how to backup your apps and app data if you don't have root.
C. Download the required files to your computer and extract them
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
3) Download the version of Android you want from here. Make sure you are using an occam image which is for the Nexus 4. Most old versions are not usually available on that site; however, there is a mirror on this site: Random Phantasmagoria.
4) Download the appropriate version (for your computer) of 7-zip from here and install it.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (which will obviously delete all your data & files in /sdcard...). Or do this.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: So far, only SuperSU v1.43 and newer currently work properly with JWR66V (i.e., 4.3). I've attached v1.51 below.
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: Only if you are running the z20i bootloader: the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
Notes:
1) Yes, you will receive the OTA update notification (when it is available) for the next update. WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the bootloader, radio, boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically.
2) There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
3) Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all. If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects. If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader. If you do want to lock your bootloader, the command is: fastboot oem lock
How to return to stock if your USB port is broken
I am adding this how-to in case people need it, for return their device to Google, etc.
This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.
Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.
1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;
2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;
3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;
4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.
5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.
6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;
5) Turn off your device and reboot into the bootloader;
6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.
7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.
8) Done. Now you are fully stock JDQ39 with a locked bootloader.
Reserved.
Awesome! Thanks again efrant!
Ok...
So I consider myself fairly good at this stuff. I've been rooting and doing custom stuff since the N1. I have messed up somewhere...
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc... It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
Ummmm... ****! I even rooted the Desire HD back when you had to do a bunch of weird terminal stuff. What happened? Little help?
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Jesus...
tomedic said:
So initially I used the "1-click" script method (I know) to unlock/root/BB/etc...
Click to expand...
Click to collapse
Yeah, you know I personally don't recommend that
tomedic said:
It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.
That ended up being unable to get passed the Google screen.
Click to expand...
Click to collapse
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
tomedic said:
I then used your method, which appeared to work...
First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.
I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!
EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....
Click to expand...
Click to collapse
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
efrant said:
Yeah, you know I personally don't recommend that
If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.
Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
Click to expand...
Click to collapse
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
tomedic said:
Ya, I did the format system out of habit because I usually did that when flashing ROM's.
So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!
I turned the phone off. I await your guidance...
Click to expand...
Click to collapse
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
efrant said:
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.
Ok, do you have data on your device you want to keep?
If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.
If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
Click to expand...
Click to collapse
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
tomedic said:
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...
Click to expand...
Click to collapse
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
tomedic said:
Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.
Any other suggestions? Your stuff works, it's just not booting...
Click to expand...
Click to collapse
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
efrant said:
Strange. All the images flashed fine (without errors) and it won't boot?
Can't think of anything else to try at the moment.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
evaradar said:
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.
Just verifying that's all.
Click to expand...
Click to collapse
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
tomedic said:
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...
I will try your method from the beginning again tomorrow.
I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
Click to expand...
Click to collapse
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
This is indeed strange, as steps D10 and D13 do exactly that: factory reset and wipe cache.
In any case, I will make a note of it in the first post.
efrant said:
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Maverick1707 said:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...
Hope it works for you too.
Click to expand...
Click to collapse
It worked! Thanks man!
And thank you efrant. Now to switch recoveries and get root! :laugh:
---------- Post added at 10:55 AM ---------- Previous post was at 10:40 AM ----------
evaradar said:
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
So just a heads up if anyone runs into this problem.
Click to expand...
Click to collapse
Yup, I just rooted and had to do the same thing.
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Thanks again all. These little hiccups make it interesting!
evaradar said:
By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.
Click to expand...
Click to collapse
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
evaradar said:
Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.
Click to expand...
Click to collapse
Again, interesting. Not sure why this is.
tomedic said:
I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?
Click to expand...
Click to collapse
Correct.
efrant said:
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.
Again, interesting. Not sure why this is.
Correct.
Click to expand...
Click to collapse
I'm assuming that like the GN we need to rename the recovery-from-boot.p file if we want our custom recovery to survive a reboot?
EDIT- never mind I just looked through your 101 thread and answered my own question- thanks!!
Thank you for making this thread over here. Glad to have you as a moderator. I hope every noob reads all of your threads.
Sent from my BAKED N7
Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?
Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]