I have a Verizon Samsung Galaxy S4 update VRUAME7
I successfully rooted it this morning after following instructions on another XDA thread
Then I installed GooManager from the market and installed 'OpenRecoveryScript' from there, which, if I understand correctly, flashed openrecovery-twrp-2.6.3.0-jfltevzw.img on my phone
Now, whenever I try to boot into recovery my phone goes into the download mode:
* in the top left portion of the screen it says:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
Click to expand...
Click to collapse
* in the center it says:
Downloading...
Do not turn off target!
Click to expand...
Click to collapse
I can get out of this by rebooting:
1. holding the power button until the screen goes dark
2. when it starts booting again, hold down Volume Down and Home
3. this brings me to a warning screen where i press Volume Down to restart the phone normally
After digging around a bit more I figured out that I forgot about the bootloader, which is still locked... So, my guess is something went wrong when open recovery got flashed on my phone. I tried going though the steps for using Loki, which are very poorly documented, but i ended up doing the following:
1. Download cwm image
2. Download Loki zip
3. Unzip loki-jfattvzw.zip, then copy recovery-clockwork-6.0.3.8-jfltevzw.img into the same dir and rename it to recovery.img
4. from command line (Windows), run install-cwm.cmd:
adb push loki.sh /data/local/tmp/
190 KB/s (973 bytes in 0.005s)
adb push loki_patch /data/local/tmp/
3306 KB/s (64327 bytes in 0.019s)
adb push recovery.img /data/local/tmp/
4509 KB/s (7657472 bytes in 1.658s)
adb shell chmod 777 /data/local/tmp/lok*
adb shell su -c '/data/local/tmp/loki.sh'
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.686 secs (15285364 bytes/sec)
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.356 secs (5890876 bytes/sec)
[+] loki_patch v1.2
[-] Failed to find function to patch.
0+0 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
Click to expand...
Click to collapse
I have no idea what "Failed to find function to patch." means
Is there a way to un-flash openrecovery-twrp-2.6.3.0-jfltevzw.img so I can at least boot into the default android recovery?
Has anyone been able to do any of this successfully?
steamydump said:
I have a Verizon Samsung Galaxy S4 update VRUAME7
I successfully rooted it this morning after following instructions on another XDA thread
Then I installed GooManager from the market and installed 'OpenRecoveryScript' from there, which, if I understand correctly, flashed openrecovery-twrp-2.6.3.0-jfltevzw.img on my phone
Now, whenever I try to boot into recovery my phone goes into the download mode:
* in the top left portion of the screen it says:
* in the center it says:
I can get out of this by rebooting:
1. holding the power button until the screen goes dark
2. when it starts booting again, hold down Volume Down and Home
3. this brings me to a warning screen where i press Volume Down to restart the phone normally
After digging around a bit more I figured out that I forgot about the bootloader, which is still locked... So, my guess is something went wrong when open recovery got flashed on my phone. I tried going though the steps for using Loki, which are very poorly documented, but i ended up doing the following:
1. Download cwm image
2. Download Loki zip
3. Unzip loki-jfattvzw.zip, then copy recovery-clockwork-6.0.3.8-jfltevzw.img into the same dir and rename it to recovery.img
4. from command line (Windows), run install-cwm.cmd:
I have no idea what "Failed to find function to patch." means
Is there a way to un-flash openrecovery-twrp-2.6.3.0-jfltevzw.img so I can at least boot into the default android recovery?
Has anyone been able to do any of this successfully?
Click to expand...
Click to collapse
IIRC you cannot install a custom recovery if you took the ME7 update. Your mistake was in trying to do so. I would try battery pull then boot into recovery by holding down Volume + and power buttons. (holding down Volume - and power takes you to download, or Odin mode instead.) After that educate yourself concerning Safestrap by devoper Hashcode. (Help me Obi-Hashcode, you're our only hope!)
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
and yet the question still stands
wtherrell said:
boot into recovery by holding down Volume + and power buttons. (holding down Volume - and power takes you to download, or Odin mode instead.)
Click to expand...
Click to collapse
As I said, whenever I try to boot into recovery my phone goes into the download mode
I'm guessing this is a result of flashing openrecovery-twrp-2.6.3.0-jfltevzw.img through GooManager
My main question was and still is:
Is there a way to un-flash openrecovery-twrp-2.6.3.0-jfltevzw.img so I can at least boot into the default android recovery?
steamydump said:
As I said, whenever I try to boot into recovery my phone goes into the download mode
I'm guessing this is a result of flashing openrecovery-twrp-2.6.3.0-jfltevzw.img through GooManager
My main question was and still is:
Is there a way to un-flash openrecovery-twrp-2.6.3.0-jfltevzw.img so I can at least boot into the default android recovery?
Click to expand...
Click to collapse
Set if you can Odin the me7 firmware.
steamydump said:
As I said, whenever I try to boot into recovery my phone goes into the download mode
I'm guessing this is a result of flashing openrecovery-twrp-2.6.3.0-jfltevzw.img through GooManager
My main question was and still is:
Is there a way to un-flash openrecovery-twrp-2.6.3.0-jfltevzw.img so I can at least boot into the default android recovery?
Click to expand...
Click to collapse
Well, if you can't get to stock recovery with volume up and power buttons it seems that the attempt at flashing the custom recovery may have corrupted the stock recovery. In which case you will need to Odin back to stock. I think I remember seeing some discussion of this in the GS4 Q&A or development threads.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
---------- Post added at 12:59 PM ---------- Previous post was at 12:52 PM ----------
Maybe this method would get you going again.
http://forum.xda-developers.com/showthread.php?t=2301259
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
In which case you will need to Odin back to stock.
Click to expand...
Click to collapse
So couldn't I just flash VRUAMDK and unlock that, then install the custom ROM - CM10.1.3? If so, has anyone done that successfully?
steamydump said:
So couldn't I just flash VRUAMDK and unlock that, then install the custom ROM - CM10.1.3? If so, has anyone done that successfully?
Click to expand...
Click to collapse
It's not possible to go backwards. Once you're on ME7 or MI1, there's only going forward. Your only hope is to Odin back to ME7 (or the newer MI1).
Same thing happened to me this evening; my phone is sitting at the same screen. I'm not quite sure where to go from here.
Luckily, I think my phone is within the RMA timeframe.
incade said:
Same thing happened to me this evening; my phone is sitting at the same screen. I'm not quite sure where to go from here.
Luckily, I think my phone is within the RMA timeframe.
Click to expand...
Click to collapse
Turn your phone off and then use vol down and power to boot into download mode, deny it and it should boot normally. Youll have to reflash the stock me7 image to get back stock recovery.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I read quite a bit - but I stopped at the point in which I was worried about bricking the phone (and which Amazon wouldn't accept it back). I think one of my issues, is that unlike previous phone's I've modded through XDA, I can't seem to find the stock ME7 ROM to flash; instead, I've found several that are "bonestock" or rooted/deodexed, etc. Anyone have a link for this? I'm sorry if I've completely missed it, but I must be searching for the wrong thing.
Also, what do you mean by "deny it" after I boot into download mode? At this point, I don't have to hold any buttons, my phone boots straight into download mode.
Thanks a bunch for the help!
hexitnow said:
Turn your phone off and then use vol down and power to boot into download mode, deny it and it should boot normally. Youll have to reflash the stock me7 image to get back stock recovery.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
incade said:
I read quite a bit - but I stopped at the point in which I was worried about bricking the phone (and which Amazon wouldn't accept it back). I think one of my issues, is that unlike previous phone's I've modded through XDA, I can't seem to find the stock ME7 ROM to flash; instead, I've found several that are "bonestock" or rooted/deodexed, etc. Anyone have a link for this? I'm sorry if I've completely missed it, but I must be searching for the wrong thing.
Also, what do you mean by "deny it" after I boot into download mode? At this point, I don't have to hold any buttons, my phone boots straight into download mode.
Thanks a bunch for the help!
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?p=43420604
steamydump said:
I have a Verizon Samsung Galaxy S4 update VRUAME7
I successfully rooted it this morning after following instructions on another XDA thread
Then I installed GooManager from the market and installed 'OpenRecoveryScript' from there, which, if I understand correctly, flashed openrecovery-twrp-2.6.3.0-jfltevzw.img on my phone
Now, whenever I try to boot into recovery my phone goes into the download mode:
* in the top left portion of the screen it says:
* in the center it says:
I can get out of this by rebooting:
1. holding the power button until the screen goes dark
2. when it starts booting again, hold down Volume Down and Home
3. this brings me to a warning screen where i press Volume Down to restart the phone normally
After digging around a bit more I figured out that I forgot about the bootloader, which is still locked... So, my guess is something went wrong when open recovery got flashed on my phone. I tried going though the steps for using Loki, which are very poorly documented, but i ended up doing the following:
1. Download cwm image
2. Download Loki zip
3. Unzip loki-jfattvzw.zip, then copy recovery-clockwork-6.0.3.8-jfltevzw.img into the same dir and rename it to recovery.img
4. from command line (Windows), run install-cwm.cmd:
I have no idea what "Failed to find function to patch." means
Is there a way to un-flash openrecovery-twrp-2.6.3.0-jfltevzw.img so I can at least boot into the default android recovery?
Has anyone been able to do any of this successfully?
Click to expand...
Click to collapse
hi guys..
can u pls refresh the link..
loki-jfattvzw.zip
i need it..
I need I545 openrecovery img for goomanager
Related
Hi everyone, I have fixed the latest CM Recovery, files are attached below,
Thanks to defer from #teamdesire @freenode.
Download and flash with fastboot,
Code:
fastboot flash recovery recovery.img
There is also an alternative version which may work for people who get the black screen, please try the alternative version if the first one doesnt work
Worked great for me!
I wanted to test but after the upgrade to 2.1 is not an android I run mode fastboot...........
I tried to install this. All looked to be written OK.
I hold down vol up\down and power on.
The basic recovery menu appears. I select option 2. The screen now just goes black and I have to remove battery to get back into android. Do I actually need a file on the SD card for the CM menu to be displayed?
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Thanks
be_vigilant said:
I tried to install this. All looked to be written OK.
I hold down vol up\down and power on.
The basic recovery menu appears. I select option 2. The screen now just goes black and I have to remove battery to get back into android. Do I actually need a file on the SD card for the CM menu to be displayed?
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Thanks
Click to expand...
Click to collapse
No but you may need the alternative recovery I made, try that one instead.
Thanks for the quick response.
However I still get a black screen using the alt too.
When I flash 1.8.1.7 that loads up OK and I get the CM menu
I just get a black screen with both your fixed and alt versions.
I guess it works for some though. Thanks again mate.
first one works for me with the 2.1 rom
I did get black screen then I pressed volume key and power button..
if I pressed the power button while in the menu I got the black screen again, so repeated the volume then power to get the menu back
so if you get black screen try volume up or down and then power button,
of course the clockwork recovery is a great way of clearing the cache
pressing all the button (no camera button) you get blank screen
re-pressing all the button the screen reappears
but, me too, with a sim free 00 Streak, I can't do anythings, no menu, no update, nothings
be_vigilant said:
I tried .....
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Click to expand...
Click to collapse
the same here
The 2 kernels I have available for recovery are for baseband 21, I would need a dump of stock recovery or boot image from 00 devices to get it working on other devices.
... Obviously its cosmetic, and I dont get my streak till monday, but can that be flipped to be right side up?
AdamG said:
Hi everyone, I have fixed the latest CM Recovery, files are attached below,
Thanks to defer from #teamdesire @freenode.
Download and flash with fastboot,
Code:
fastboot flash recovery recovery.img
There is also an alternative version which may work for people who get the black screen, please try the alternative version if the first one doesnt work
Click to expand...
Click to collapse
I dont understand what do it?When i must use it.
Hmm...
Been working with a trashed recovery partition for a few days.. No biggy, tried pulling off what was on recovery_1 and placing it on etc.. No luck..
But yeah, the first image did work for me (though nandroid failed, my filesystem is pretty trashed.) Do a bit of screwing around replacing files in the system directory and kill my system. I'd already 'fixed' the failed nandroid backup, so I go to restore it, only to see the standard recovery has somehow resurrected itself and clockwork was no longer on.
Magic I tell you.
kwaaq said:
Hmm...
Been working with a trashed recovery partition for a few days.. No biggy, tried pulling off what was on recovery_1 and placing it on etc.. No luck..
But yeah, the first image did work for me (though nandroid failed, my filesystem is pretty trashed.) Do a bit of screwing around replacing files in the system directory and kill my system. I'd already 'fixed' the failed nandroid backup, so I go to restore it, only to see the standard recovery has somehow resurrected itself and clockwork was no longer on.
Magic I tell you.
Click to expand...
Click to collapse
Nandroid only fails because of the path to /data, I should be able to fix this.
how to make a stock recovery image?
Hi I was just wondering how do we go about making a dump of our stock recovery images? Would be nice to be able to backup and restore back to stock if something goes wrong. I have a US streak with BB=31 and Build 6601
AdamG said:
The 2 kernels I have available for recovery are for baseband 21, I would need a dump of stock recovery or boot image from 00 devices to get it working on other devices.
Click to expand...
Click to collapse
help please?
the cmd prompt and device hangs at <waiting for device>
Funk2641 said:
help please?
the cmd prompt and device hangs at <waiting for device>
Click to expand...
Click to collapse
Have you installed the Dell PC suite to get the fastboot driver?
be_vigilant said:
Have you installed the Dell PC suite to get the fastboot driver?
Click to expand...
Click to collapse
Yeah, it's all good. Works great. Only downside is the 30fps limit, but ah well
cemian said:
Hi I was just wondering how do we go about making a dump of our stock recovery images? Would be nice to be able to backup and restore back to stock if something goes wrong. I have a US streak with BB=31 and Build 6601
Click to expand...
Click to collapse
Enable development, so you can run adb, then in adb shell type the following
cat /dev/mtd/mtd1 > /sdcard/recovery.dump
zip the file and upload it here so I can repack it
No mtd1 folder
The command failed saying no such directory...I looked myself and confirmed there is a mtd folder but nothing inside... No mtd1 Folder exists...hmmm
AdamG said:
Enable development, so you can run adb, then in adb shell type the following
cat /dev/mtd/mtd1 > /sdcard/recovery.dump
zip the file and upload it here so I can repack it
Click to expand...
Click to collapse
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
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
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Does anyone have a suggestion how I can get Fastboot fixed and the Nabi back to "normal" / upgradeable.
Thanks for your help
kaijan said:
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
Click to expand...
Click to collapse
What software rev did you get to when doing the OTA's?
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
Click to expand...
Click to collapse
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Click to expand...
Click to collapse
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
aicjofs said:
What software rev did you get to when doing the OTA's?
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Verifying current system...
assert failed: apply_patch_check("/system/app/Gallery2.apk", "4cadedee1defcdc28afc99ea968ebb1e631e7b9", "ee310bfc0d0ad2fe11356b97f8cb6e754aa43f2b")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
kaijan said:
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Click to expand...
Click to collapse
Hmm that is it weird. It does look like gapps is still installed .As gapps removes gallery2.apk and why it's failing, I don't understand if it's stock how that is happening. Use these updates yet? http://forum.xda-developers.com/wiki/Fuhu_nabi_2
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
hotspace said:
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
Click to expand...
Click to collapse
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
I did try ADB REBOOT-BOOTLOADER all that happens is the NABI2 restarts and sits at the logo screen.
I'm able to push via ADB, so I will download the suggested files and take your advice. I'll report back. And, thanks for the reply.
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
hotspace said:
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
Click to expand...
Click to collapse
Nah Nabi2 is practically impossible to brick.
So do you get the command list in the top left when you press the vol and power buttons? i.e the selection continue, fastboot, recovery kernel, forced recovery? or when you select recovery kernel it just doesn't boot TWRP?
I wont type a lot of stuff until I get you answer but if we need to go the nvflash route this is some good reading. You will need to get in to APX mode, install the driver and issue some commands.
Read this post and next few pages after it
http://forum.xda-developers.com/showpost.php?p=46579190&postcount=1687
General idea of commands
http://forum.xda-developers.com/showpost.php?p=48683262&postcount=124
Might be some work, but we should be able to get the device back, I'll let you know which is the best way after I see your reply.
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
aicjofs said:
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
Click to expand...
Click to collapse
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Get the nvflash package from the Nabi General Info thread I linked above
Unzip in to a directory of your choosing and open a command prompt in that folder
The Nabi will be broken open and connected by USB to computer
So once you get those pins shorted and press the power button the screen should come on and be completely black(you can tell the backlight is on though)
Check in device manager for a new device(it will be auto detected or you will have to manually install APX driver)
Once the driver is installed you can issue nvflash commands
nvflash --bl bootloader.bin --download 4 bootloader.bin
Before pressing enter for the below command get ready to press and hold the vol+ key.
nvflash --resume --go
Right on. I'll dig into this in the morning
Sent from my SM-N920P using Tapatalk
@aicjofs, I still haven't begun breaking the Nabi down. I'm working from home today and should be able to squeeze the disassemble in sometime today.
I scanned through the comments you've left since finding out I wasn't able to get to the boot menu...I'll post back once I get it torn apart.
What hope for an XT1505?
I have an XT1505 that I bought direct from Motorola as a GSM-only phone in April, I just got my bootloader unlock code but I'm a little confused about what next. I want it rooted, but mostly so I can put Debian Linux on it.
I have UPDATE-SuperSU-v2.46.zip but I'm not sure which branch of it, IE what CPU type to use. Spec Device says: Processor: 4 cores; Qualcomm MSM8212 msm8610; Max: 1190.4 MHz; Min: 300.0 MHz. OK, I guess the update-binary script is supposed to handle that. Do I need to install a recovery image? Which one?
I've been following threads about it here for a few months, glad to see the camera bug has been fixed. I'm not a huge Linux fan, started playing with it 20 years or so ago, I've used mostly OpenBSD for 15 years, it's much more stable and reliable. I've built kernels under Linux, OpenBSD, FreeBSD by configuring and compiling. Mostly I write C these days, know several other languages that I can write with reference book in hand. I'm a retired network administrator from chasing viruses on Windows machines. I view Android phones as just the neatest little pocket computers, don't care much about talking on them. I tether from my phone as my main internet connection, there isn't much else available where I live.
What is wrong with this web site? I've had to close Firefox and reopen it 3 times because it was using 400+ megs of RAM and 70% CPU just on this site alone.
I would flash the recovery first. XT1505 is a global model, which doesn't have LTE, so you need to download the recovery for "otus". I'd recommend TWRP recovery. Flash it via fastboot using "fastboot flash recovery name_of_the_file.img" command and once it's done, boot the phone into recovery and flash the zip with SuperSU.
Sent from my XT1524 using Tapatalk
OK, thanks, I also wasn't sure what the scope of the otus name was, whether it included all the Moto E2 models or not. I see it in "about phone" but here on XDA I only see it applied to other models. I guess nobody in their right mind would own one of these, but I bought it to ship to Africa then ended up keeping it. I've got the LTE version ordered.
jamaniek said:
I would flash the recovery first. XT1505 is a global model, which doesn't have LTE, so you need to download the recovery for "otus". I'd recommend TWRP recovery. Flash it via fastboot using "fastboot flash recovery name_of_the_file.img" command and once it's done, boot the phone into recovery and flash the zip with SuperSU.
Sent from my XT1524 using Tapatalk
Click to expand...
Click to collapse
Getting to the recovery menu?
I flashed the recovery with TWRP, did it twice and it looked successful each time, at least it says OKAY twice. I think next I'm supposed to go into recovery mode and load the supersu zip. I can get to where the android is laying on his back and there's a triangle with an exclamation mark, but I can't make a menu come up. The only thing that seems to happen is that if I hold down the power switch long enough it turns off, then it boots normally. I've done that 3 times, it seems reproducible, but I haven't found a menu. I've got copies of my supersu zip on both the external and internal SD but no way to use one.
When you get to the Android laying on his back, hold down the power button for about 3-5 seconds. Then while still holding the power button, press and release the up volume button.
The menu should pop up then.
Sent from my KFFOWI using Tapatalk
I don't think TWRP installed despite the messages that said it was OK. I'm trying to flash UPDATE-SuperSU-v2.46.zip and it goes through the motions but always says the full-file signature verification failed. Looking on here I find that TWRP has an option to disable the verification, but I don't see it, that's why I think it's the stock recovery. It looks like this:
Android system recovery <3e>
LXC22.99-13.3
Volume up/down to move highlight;
Press and release power button to select.
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------------------
I'd never seen it before so I don't know if it changed. I did some looking at an FAQ but I don't see anything that helps. I've tried fastboot reboot after flashing TWRP and somewhere else somebody wrote that you have to "press power + vol down immediatly after you 'fastboot reboot'" so I tried that, also wiped the cache.
Got it
I followed a slightly different set of instructions for flashing the recovery. I don't think I can post links yet but it was at androidmtk.com. I had originally renamed my twrp file to twrp.img in case I had to type it, this time I renamed it to recovery.img and it went right in. Same cable, Linux adb and fastboot.
This site has a screenshot of TWRP and it's GUI, not text. What I posted above is stock. You should see 8 buttons if it's working.
Trying a link: http://androidmtk.com/root-motorola-moto-e-3g-2015
OK, rooted, installing Debian Kit. Just wondering, if I relock the bootloader will I need the unlock code forever to unlock it or was that a one-time thing?
Sent from my MotoE2 using Tapatalk
Just looked up these instructions in 2018 and used them again on my XT1527, thanks again.
jamaniek said:
I would flash the recovery first. XT1505 is a global model, which doesn't have LTE, so you need to download the recovery for "otus". I'd recommend TWRP recovery. Flash it via fastboot using "fastboot flash recovery name_of_the_file.img" command and once it's done, boot the phone into recovery and flash the zip with SuperSU.
Sent from my XT1524 using Tapatalk
Click to expand...
Click to collapse