So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Please, could someone write a good step-by-step newb-friendly manual on how to get the Jelly Bean on this tab? I am seriously considering throwing this thing out of the window right now as I spent the whole evening trying to get this working with no results.
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
oh_delay said:
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
Click to expand...
Click to collapse
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
oh_delay said:
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Click to expand...
Click to collapse
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
AW: Recovery doesn't boot! Help!allready
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
feraay said:
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Click to expand...
Click to collapse
Well, yeah, apparently. I have stock 4.0.4 installed.
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
What exactly should I do? IDK what that means, "Fastboot flash recovery recovery.img
fastboot reboot recovery".
As I said, I am almost a complete newb in this.
pruano said:
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
Click to expand...
Click to collapse
I did adb reboot recovery, and it booted the stock recovery. Maybe I should use another recovery image? I used the one linked in the CM's instructions.
Ok, so basically what happens now is I flash recovery.tar.md5 through Odin, then it reboots in OS and I reboot it to recovery through terminal. The recovery says 'Android system recovery <3e>', so I assume it's the stock one?
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Ok i figured out how to use fastboot command. Still I don't understand, which recovery.img should I flash? I don't have this file, at least not in an .img format, it's format is .tar.md5
So I guess my next question is, where can I get recovery in .img format?
OK, so I figured this out.
I downloaded the recovery.img for the Galaxy Tab 10.1 from the official CWM site (NOT 10.1v, cause they don't have it for this version. It worked fine).
then I loaded in bootloader, used ./fastboot boot <path to downloaded recovery.img>, I just dragged the img to terminal window.
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
So yeah, thank you for your posts and thoughts, you helped me figure this out.
oh_delay said:
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
Click to expand...
Click to collapse
Yes, if you use "fastboot boot [recovery image]" instead of "fastboot flash recovery [recovery image]", you can boot to a custom recovery like CWM without flashing.
oh_delay said:
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
Click to expand...
Click to collapse
Fastboot only accepts .img files, Odin only accepts tar.md5 files; however, tar.md5 files are just archive files, if you rename the file to remove the .md5 extension and use a program like 7-zip which can read .tar files, you will find one or more .img files inside, which you can extract for use with fastboot.
oh_delay said:
So yeah, thank you for your posts and thoughts, you helped me figure this out.
Click to expand...
Click to collapse
Great that you managed on your own (even with some tips), best way to learn.
---------- Post added at 12:12 PM ---------- Previous post was at 12:07 PM ----------
oh_delay said:
Well, yeah, apparently. I have stock 4.0.4 installed.
Click to expand...
Click to collapse
Its the last stock release for this tablet.
---------- Post added at 12:45 PM ---------- Previous post was at 12:12 PM ----------
oh_delay said:
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
Click to expand...
Click to collapse
One last thing: those instructions do not include adding root, as indeed you can use most of the functionality of Cyanogen without root (and possibly exposing your device to malware).
However many useful functions and apps DO require root; to check if you have root, either install this app, or do "adb shell" + "adb su", which should change the prompt from a $ to a #
For root the best way is probably to flash both zip files (ARM version) with CWM at this point (so you get the latest version); dont forget to hit the "Fix Permissions" CWM option afterwards to prevent any potential problems.
AW: Recovery doesn't boot! Help!
Noo dont take 10.1 recovery take the recovery from droidbasement.com
P3 7100 only this
And do this
Adb reboot bootloader
If not work press power and volume +
Or may
power and volume -
Should Boot into bootloader click not in download modus for Odin just take the other icon and Connect to PC
Fastboot flash recovery recovery.img
Thats all
Gesendet von meinem HTC One X mit Tapatalk 2
Related
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Seleren said:
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Click to expand...
Click to collapse
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Lucky Thirteen said:
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
Click to expand...
Click to collapse
I have the International model.
jbharbin said:
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Click to expand...
Click to collapse
Tried that already, nothing changed at all, TWRP logo shows up and then the phone reboots to ROM. CWM works partially as I said, it reboots when I tell it do do anything (backup/wipe/flash) and the phone is unaffected.
Bump. Help please, I tried flashing another kernel but that didn't help. I can't even wipe or flash another ROM in CWM.
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Try redownloading the recovery and rewriting it. It may be a bad download.
Sent from my One X+ using xda premium
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Flash the kernel and then the recovery with fastboot and see what happens.
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
@Seleren I would be interested to know if the above worked for you? Also useful if anyone else gets this problem
Lucky Thirteen said:
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
Click to expand...
Click to collapse
I've already tried that numerous times, I can get to erasing cache etc but once I try to boot into the recovery ... I'm done. TWRP won't boot even after erasing cache. CWM fails at wiping/backuping/flashing and just reboots without any notice at all. I'm really out of ideas now.
Sorry for a bit late answer.
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
Seleren said:
Hello there,
... A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery....
Click to expand...
Click to collapse
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Lucky Thirteen said:
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Click to expand...
Click to collapse
Yes, I am correctly rooted, I've rooted numerous phones, I unlocked using the official HTC method. I could say I'm not a complete noob to Android. I wouldn't even post here if I didn't try all the standard procedures.
I flashed the Non-touch CWM yesterday and nothing changed (not that I expected it to). I decided I'll try flashing the bootloader in the end but I have to back up my whole SDCard before that ...
Bump.
SALVATION
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
hukel56 said:
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
Click to expand...
Click to collapse
wut?! TWRP = Recovery
boot.img = KERNEL
Seleren said:
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Click to expand...
Click to collapse
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Lloir said:
wut?! TWRP = Recovery
boot.img = KERNEL
Click to expand...
Click to collapse
Yea idk. But this happens
Lloir said:
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Click to expand...
Click to collapse
I wish that was the problem, I tried quite a few versions, including the one from ALL IN ONE toolkit, an older version that previously worked, the latest version and the ViperX version. Trust me, that was not the problem.
hukel56 said:
Yea idk. But this happens
Click to expand...
Click to collapse
What Lloir meant to say was that the boot.img has nothing to do with the recovery, so flashing a boot.img will NOT change your recovery to so-said TWRP.
TWRP is being flashed by a different command namely 'flash recovery' instead of 'flash boot' like previously mentioned boot.img
Just got the phone, unlocked through HTCDev, installed recovery through Toolkit, but can't actually boot into recovery. I tried all of the recoveries available (TWRP, CWM, CWM Touch) but once I select reboot into recovery, it reboots, gets to the HTC logo screen, something appears on the top edge of the screen, it reboots and boots normally. Did I do something wrong?
Try one of the other methods to flash recovery.
[/COLOR]Try
http://forum.xda-developers.com/showthread.php?t=2182792
Sent from my HTC One X using Tapatalk 2
joshuadjohnson22 said:
Try one of the other methods to flash recovery.
[/COLOR]Try
http://forum.xda-developers.com/showthread.php?t=2182792
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I just tried flashing TWRP manually (fastboot flash recovery recovery.img) and it still does the same. I renamed the img file to recovery.img, so it's not that.
Try redownloading the file from the url above. Maybe it was a bad file download?
Also try different micro usb cables and usb ports. Reinstall the drivers just things like that
Sent from my HTC One X using Tapatalk 2
Tried flashing stock recovery from here, no dice: http://forum.xda-developers.com/showthread.php?t=2224752
jcracken said:
Tried flashing stock recovery from here, no dice: http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
have you tried rebooting while holding power and the down volume key? maybe that is the way you need to enter it
also more info would be nice. when you flash what does it say/do
It says in the OP
jcracken said:
once I select reboot into recovery, it reboots, gets to the HTC logo screen, something appears on the top edge of the screen, it reboots and boots normally
Click to expand...
Click to collapse
tehh4ck3r said:
It says in the OP
Click to expand...
Click to collapse
reason I asked was maybe there is a bug when selecting reboot into recovery thought it was worth a try to enter it a different way
Fixed it by selecting "Factory Reset" in the bootloader menu--went straight to recovery.
I had the same problem and was able to resolve it by turning off fast boot in the power settings screen.
Im having the same issue with every recovery I flash. Obviously im not a noob and can flash stuff. Im just boggled because everybody is reporting flashing internation stuff just fine. The recoveries don't work for me. Can someone direct link me to the recovery they flashed on their att version?
jmztaylor said:
Im having the same issue with every recovery I flash. Obviously im not a noob and can flash stuff. Im just boggled because everybody is reporting flashing internation stuff just fine. The recoveries don't work for me. Can someone direct link me to the recovery they flashed on their att version?
Click to expand...
Click to collapse
After I selected "Factory Reset" in the Bootloader all the recoveries I tried from the International forum worked.
jcracken said:
After I selected "Factory Reset" in the Bootloader all the recoveries I tried from the International forum worked.
Click to expand...
Click to collapse
I fixed it by flashing recovery and rebooting bootloader till it showed tampered
Sent from my HTC One using xda premium
i had this trouble and just adb pushed them and it worked glad you got it working
my nephew was having the same issue as well and never got it boot to recovery. while i was troubleshooting, i discovered he was using the recovery for the Sprint version. ugh!!! i got the international version and manually flashed it (fastboot flash recovery recovery.img, fastboot reboot-bootloader) and then tried to enter recovery with no success. I rebooted to bootloader again, selected factory reset, and the phone rebooted normally. tried the adb reboot recovery command, phone reboots, i see a window flash in the background with red writing at the bottom, and then it boots normally. i've done this 5 times with no luck. any suggestions?
---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------
CheesyNutz said:
i had this trouble and just adb pushed them and it worked glad you got it working
Click to expand...
Click to collapse
can you share the command for your adb push method?
cortez.i said:
my nephew was having the same issue as well and never got it boot to recovery. while i was troubleshooting, i discovered he was using the recovery for the Sprint version. ugh!!! i got the international version and manually flashed it (fastboot flash recovery recovery.img, fastboot reboot-bootloader) and then tried to enter recovery with no success. I rebooted to bootloader again, selected factory reset, and the phone rebooted normally. tried the adb reboot recovery command, phone reboots, i see a window flash in the background with red writing at the bottom, and then it boots normally. i've done this 5 times with no luck. any suggestions?
---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------
can you share the command for your adb push method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2182792
CheesyNutz said:
http://forum.xda-developers.com/showthread.php?t=2182792
Click to expand...
Click to collapse
Cheesy (lol) thanks for the tip! while i didn't follow all the steps in that post, i did perform one task that got me to recovery: use the POWER+VOLUME DOWN method to reboot to bootloader. once in bootloader mode, i saw *TAMPERED* at the top of the screen and knew i was good to go, e.g., get into recovery mode. thanks again bro!
Help
cortez.i said:
Cheesy (lol) thanks for the tip! while i didn't follow all the steps in that post, i did perform one task that got me to recovery: use the POWER+VOLUME DOWN method to reboot to bootloader. once in bootloader mode, i saw *TAMPERED* at the top of the screen and knew i was good to go, e.g., get into recovery mode. thanks again bro!
Click to expand...
Click to collapse
I have tried all of these methods. I have flashed the recovery, all of them, repeatedly and my phone will only show unlocked. I have used the All in One as well as manually flashing the recovery as well. but my phone never switches to *TAMPERED*. Any advice?
I had this happen on my other One tonight. I had flashed the recovery via fastboot about 15 times and it wasn't working until I let it reboot to OS and then I adb reboot bootloader and magically it showed TAMPERED. Just keep doing the steps over and over again and eventually it'll work. After it finally took TWRP I was able to change it for CWM Touch with no issues.
Disabling HTC Fast boot did it for me!
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
Hi everyone.
I have this device, LENOVO TAB2 A7-20F and i want to install custom recovery on it. The problem is, my volume down button is broken. I successfully flashed the custom recovery to my device (TWRP, via fastboot, and flash_tool), but after flashing i cannot boot straightaway into recovery mode because of the broken volume down button.
So, is there any ways i can boot into recovery mode (from turned off device or fastboot mode) without need of volume down button.
Thanks in advance.
Here is my current attempts:
USING ADB REBOOT
I can use ADB to reboot to recovery using:
Code:
adb reboot recovery
But using ADB means I had to boot to android system. And I read somewhere that i need to boot to recovery straightaway after flashing TWRP. This method return a black screen, with opened-chest-android-robot and red triangle with exclamation mark on it.
Edit:
@wittier suggesting using POWER + VOL UP combo when dead android screen shows up. It successfully bring me to stock recovery. I think it because I'm rebooting to system after flasing TWRP, and the recovery was flashed back to stock.
USING FASTBOOT BOOT
In the past I'm using fastboot boot command to boot using custom recovery image, so i give it a try.
Code:
fastboot boot recovery.img
It returns
Code:
downloading 'boot.img'...
OKAY [ 0.396s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.398s
NRT
Nexus Root Toolkit will boot my phone into Recovery.
Advanced Utilities > Launch
On the left side, under Quick Tools > Reboot Recovery
Just tested this and it worked.
---------- Post added at 02:13 AM ---------- Previous post was at 02:09 AM ----------
You were almost there already, though:
when you see the dead android on its back, hold the power button and tap Volume Up, then release. The key combo takes a little practice. So keep trying that a few times until you get to Recovery.
wittier said:
Nexus Root Toolkit will boot my phone into Recovery.
Advanced Utilities > Launch
On the left side, under Quick Tools > Reboot Recovery
Just tested this and it worked.
---------- Post added at 02:13 AM ---------- Previous post was at 02:09 AM ----------
You were almost there already, though:
when you see the dead android on its back, hold the power button and tap Volume Up, then release. The key combo takes a little practice. So keep trying that a few times until you get to Recovery.
Click to expand...
Click to collapse
Just trying POWER + VOL UP combo, it works! But it load stock recovery (which I cannot use because of my broken button). I guess its because I have to boot to system after flashing recovery using fastboot (to use adb reboot recovery)
Is it true that one must not reboot to system after flashing TWRP because it will wiped and flashed back into stock recovery?
Is NRT can be used in fastboot mode or turned off device? I'm using linux and NRT need Windows.
Thanks for the reply. Very appreciate it.
nickabbooo said:
Just trying POWER + VOL UP combo, it works! But it load stock recovery (which I cannot use because of my broken button). I guess its because I have to boot to system after flashing recovery using fastboot (to use adb reboot recovery)
Is it true that one must not reboot to system after flashing TWRP because it will wiped and flashed back into stock recovery?
Is NRT can be used in fastboot mode or turned off device? I'm using linux and NRT need Windows.
Thanks for the reply. Very appreciate it.
Click to expand...
Click to collapse
NRT can be used to flash / install TWRP as your recovery. I believe NRT can also be used to just Temporarily use TWRP as your recovery.
NRT can be used in fastboot mode or in power on mode on the phone. I don't know if the phone can be powered off when you want to use NRT. Doubt it.
Can't help you with Linux.
Once you are in recovery, can you flash a custom recovery, TWRP? (or in fastboot mode?)
I am no expert. So others will know more.
Have you tried reboot recovery app? It works for me
---------- Post added at 04:40 AM ---------- Previous post was at 04:38 AM ----------
Also, you generally flash a custom recovery image from an application on PC with your device in download mode. Then you boot into it to flash a ROM. You should only have one recovery, stock or custom.
The phone has unlockable bootloader and I only have low mobile data and was wondering if there's a way to rip the stock recovery to port twrp over.
When I get wifi tomorrow, I'll try using PC king root while the phone is in fastboot mode.
Kingoroot will get to 100 but fail, kingroot pc version would just give me Chinese letters and do nothing.
Can anyone list anyother root exploits I might I can try on this phone? I tried the Android version of kingroot , but that just gives me the request device and I can't bypass it.
Root u673c
... has anyone been able to root the U673C version 6.0.1, if so, guide me through it, thanks!
we need to somehow extract the stock recovery.img to port twrp over.
Rooted boot image for u673c
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
tdawgg777 said:
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
Click to expand...
Click to collapse
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
DB225 said:
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
Click to expand...
Click to collapse
Some instructions would be nice, Does not work I can get boot.img to install but it will only boot into stock recovery
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Thank you !
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
does anyone have twrp backup or copy firmware.I wipe internel by accident cant flash u673c no os,thanks sean
---------- Post added at 04:40 AM ---------- Previous post was at 04:32 AM ----------
does anyone have backup or copy firmware u673c cause screwed up wiped internel memory,sean
derwoodbones said:
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
Click to expand...
Click to collapse
I would just disable the app... just in case there is an update for the phone in future... if you remove the app the update will fail but if its disabled you can just enable it take update and then disable it again... also disable the stock gallery and install a third party one from the playstore... the stock gallery app will through all sorts of ads at you full screen ads as well.
I used titainium backup to disable all apps I didn't want... bit you can use what ever app you want. You can disable most apps in the apps info but not all apps.
I just use the phone as a backup and don't know where it is right now but when I come accross it I'll post all the apps I disabled here.
I healthfully thank you
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
I fully thank you
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
tdawgg777 said:
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Click to expand...
Click to collapse
smuskat said:
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
Click to expand...
Click to collapse
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
I appreciate your reply.
But I need some more assistance, please:
I've rooted many devices, flashed custom ROM's, Custom recoveries, etc, but I'm completely stuck now with this phone.
I tried "Power and Vol Down"....nothing.
I tried "Power and Vol Up"...and for a split second I see the Android robot on its back...but after that split second, I'm in the stock recovery menu.
One of the stock recovery menu choices is to reboot into Bootloader. When I try that, the phone reboots; but to the best of my knowledge, does not get into Bootloader mode.
I have installed ADB on my PC. When I type "ADB devices", I see my phone listed. But when I type "adb reboot bootloader", it reboots, but not into Bootloader.
I have USB debugging enabled, I have authorized my PC, and in Developer options, I have enabled the "Unlock Bootloader" option.
My Googling results have not yielded useful info.
I'm stuck.....
I hope that someone with experience with this particular device can please tell me what I'm doing wrong.
Thank you!
tdawgg777 said:
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
Click to expand...
Click to collapse
hope it helps
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Liberator Elite said:
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Click to expand...
Click to collapse
More Info
smuskat said:
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Click to expand...
Click to collapse
Sent ya PM
Smuskat
Hope That Helps.
I Got Magisk, Xposed & Even A Custom Bootscreen With Sound on Mine.
Okay. Got it all done, mostly thanks to Liberator Elite. And just so that no one else should ever be as stuck as I was, please allow me to clarify what actually worked:
I kept on attempting to put the phone into Fastboot mode or Bootloader mode. I could enter the stock recovery, choose to boot into Bootloader, but it wasn't working--or so I thought. All I would see upon reboot was a screen that was black, with the words "UMX" (Ultimate Mobile Xperience??? or whatever...)
However, Liberator Elite called to my attention that that screen WAS THE BOOTLOADER screen. I typed "Fastboot Devices" from the command prompt, and there was my phone! I then was able to flash over the boot.img file, and the TWRP posted here, and from TWRP, I was able to install Magisk.
For some of you, this is all simple--thanks for not laughing.
And to the entire community, thanks for being such a great resource! All done--thanks to you guys. Much appreciated!!!