My goal is to determine if it is possible to flash Rom's, as well as Kernels and Modems without incrementing the flash counter. I've already gathered some basic information about Kernels, mostly from Entropy512. What I've done so far, without seeing the exclamation at boot, and without incrementing the flash counter, is flash Entropy512's stock root package with odin and then flash one of Entropy512's Kernel zImage with adb. So I'm as far as rooted with CWM without incrementing the flash counter.
Next step is to understand the flash counter better.
I read in the I9100 forums that to see your flash count, you need to boot into download mode with the three button method. Since we don't have the third button on our phone, the only method I'm aware of for reachinig download mode is holding volume down plus volume up, then pluging in the usb cable. Then at the warning screen with the yellow triangle, press Volume up to enter download mode. When done gathering information, don't flash anything, just pull the battery and then reboot the phone. Entering download mode by itself does nothing to the the flash counter. Flashing a stock kernel and system image in odin also does not increment the counter.
At the top of the screen you will see something like:
Odin Mode (in red letters)
Product Name: SGH-I777
Custom Binary Download: No
Current Binary: Samsung Official
That's what my phone shows right now. I'm going to keep my flash counter at 0 if at all possible, so I'm not doing any random testing right now. I'm assuming that if you flash a non-stock image with odin that the above information will be different. I'd also be interested to know if flashing with Heimdall increments the flash counter. Does the Custom Binary Download field reflect the number of times you've flashed, or just say Yes?
What does your phone show in these fields, compared to what you've flashed.
BTW, does anyone know any other methods for getting into download mode? And if so, does that method show the same info on the screen?
If you have root, you can use terminal emulator.
Code:
su
reboot download
This will put you into download mode, but it bypasses the flash warning you get when entering download mode via volume and USB insert, and you will not get the info you are talking about
Sent from my SAMSUNG-SGH-I777 using XDA App
dayv said:
If you have root, you can use terminal emulator.
Code:
su
reboot download
This will put you into download mode, but it bypasses the flash warning you get when entering download mode via volume and USB insert, and you will not get the info you are talking about
Click to expand...
Click to collapse
And the same with adb no doubt. Actually I was wondering if there is any other way to enter download mode with just the phone, maybe a button combo that does not require plugging in the usb cable like the I9100 does? Guess I wasn't real clear with the initial question. Finished that up just as I was running out the door. And it's good to know that using terminal emulator, and presumably adb, will not display the flash warning.
Related
Hi there,
Currently my phone has no ROM and a disfunctioning ClockworkMod Recovery. (It cannot install zips or take updates).
Therefore I'm using ADB to flash a new recovery and ROM into the phone.
Code:
mount data
Results in:
Code:
mount: can't find /etc/fstab: No such file or directory
So I copied my file into the /data/ folder with
Code:
adb push c:\rom.zip /data/
This was done successful.
After that I tried to install the rom.zip using
Code:
adb shell
recovery --update_package=DATA:rom.zip
Unfortunately this results in:
Code:
sh: /sbin/postrecoveryboot.sh: not found
Also tried to replace the recovery.img but this also resulted in:
Code:
sh: /sbin/postrecoveryboot.sh: not found
In short:
Can't mount USB in ClockWorkMod
Can't access phone files with Windows Explorer
Can't use Kies to recover phone.
Can't use ClockWorkMod to install a zip or update.
Can't do normal boot.
Can't mount data using ADB.
Can't install recovery ROM using ADB.
I can't think of any way to fix this, hope someone else can help me with this.
Simple Use Odin
Sent from my GT-I9100 using XDA
Can you get in to Download mode?
As the 2 people stated above:
If you are able to get into the download mode, then you should be able to install a stock rom via Odin.
Have a good day and good luck with your phone.
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Magiciano said:
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Click to expand...
Click to collapse
what happens when you try and get into download mode? is it just blank? when you plug it in to charge do you get the battery charging animation?
nutmegy said:
what happens when you try and get into download mode? is it just blank? when you plug it in to charge do you get the battery charging animation?
Click to expand...
Click to collapse
The download mode button combination has no effect, it won't even try to load.
I get a frozen image of a empty battery with the spinning wheel inside, the battery is more than half full tho.
Magiciano said:
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Click to expand...
Click to collapse
USB recovery jig would be the next step before it all becomes expensive .
jje
I would say try using a USB jig to get into download mode. If that doesn't work, I think the only thing left to do would be to take it to Samsung.
Edit: Damn, I never saw JJE's post above. Sorry.
Jtag might be cheaper than taking it to samsung
Sent from my sgs2 running cm9 using xda app
Sounds annoying..
Tryed this?
http://forum.xda-developers.com/showthread.php?t=1449771
fastboot erase cache ( if failed ignore it)
fastboot oem rebootRUU ( not shure if RUU is htc dependent or not )
fastboot flash zip your_recover.zip
fastboot reboot-bootloader
it's worked for me, its basically change your recovery, so you can install a properly working clockwork
I've found my friend's sgs2 last few days ago as yours..
Couldn't go 2 download mode w/ buttons combination
..
Randomly as a noob (sorry4that.. ) I tried adb shell :
adb reboot download
N it worked ready2 next step flashing progress via Odin 1.85 (just try this ver!)
If yours don't: try USB Jig neither to JTaG or SSC @ last opt
Hope this may help & sorry about 'tittles'
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 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
Hello,
I have a crappy Samsung S4 copy (MT6575 GT-I9500, see info.jpg) that I would like to hack.
After reading a few posts if I understand correctly, the first step is to set a correct recovery image to be able to flash a custom ROM.
I have already done it on an HTC using fastboot (I use Linux), so the step was to go to the bootloader and use
Code:
fastboot flash recovery recovery.img
However, the bootloader I get does not seems to accept this command (get "< waiting for device >", see bootloader.jpg).
Using adb, I was able to access the recovery mode (abd reboot recovery) but I get "e3" recovery (see recoevery1.jpg) but I get the same empty screen whatever option I use (see recoevery2.jpg.
Any idea how I can flash a custom recoevery and/or ROM ?
Thanks
Hello together,
I currently want to install a custom recovery twrp for lineage os.
I come to Download mode. But I can't reboot to recovery because the volume up button is not Working any more.
When I reboot in normak mode and from there to recovery mode using adb reboot recovery then the custom recovery is overwritten.
As I read this is a "feature" in the Samsung Software that recovery id overwritten with stock recovery during normal boot.
So the question is: can i boot from download mode to recovery with software. In odin mode i can't connect using adb. As there is no fastboot for Samsung devices I can't connect using a command line adb. So any chance to do it with defect volume up button?
Thanks for any ideas in advance.
Have you root access? I don't think, but if you have you can use "flashify" to flash twrp.img in recovery partition and then use "Reboot to recovery" to boot twrp. You find both in play store.
Edit: you can flash a old 4.1 firmware and use this https://forum.xda-developers.com/showthread.php?t=1695238 to have SuperSU and cwm, then in cwm you can flash twrp in zip file
Tapastalking
Thanks
Hi thanks for the idea. This was the other option but needs root. I thought there is an easy solution with something like adb in odin mode. In fastboot I could do that.... so I thoguht there might be a pendant with Samsung smartphones.
You need root to change the recovery.
Beamed in by telepathy.
It worked but Encryption failed and after the password lineageos hangs.
Is there any possibility to boot into Recovery from odin / download mode using adb or anything other.
With a jig i will come to download mode.