HTC Dumlock
HTC Dumlock is a workaround for devices with HTC's unlock that cannot flash boot from recovery. Put simply, we make backups of recovery and boot, then we flash the backup of recovery to boot. When you reboot normally, you'll be in your recovery, but since your recovery is flashed to boot, you can make changes to boot. Head on over to our website for download links and instructions.
NOTE: The Rezound does not have TWRP, so you will be using the universal version!
New v2 version scans / compares the backups of boot and recovery to help ensure that you don't run it twice and wipe out your backup of boot.
I believe I can unify all of the zips into a single one that is touchscreen based It would make it extremely easy and useful.
con247 said:
I believe I can unify all of the zips into a single one that is touchscreen based It would make it extremely easy and useful.
Click to expand...
Click to collapse
Con,
I hope your professor's appreciate you ! I was hoping you would simplify it.
Quick question, so reading through the website a few times. It is my understanding once this is properly set up when we make backups it will be backing up the kernel and when we restore backups we wouldn't have to reflash kernel or am I taking it to far ?
Also would our backups from Amon Ra still work or better to just delete them and just make fresh backups of current rom with TWRP recovery.
There's 2 versions, one is the universal version that works with any recovery. The other, the TWRP version, is only available for a handful of devices and that doesn't include the Rezound. I don't have a Rezound, so I can't speak for it myself, but I would imagine that your existing backups would be fine (you could read boot, just not write to it) unless you chose not to back up boot.
I believe once I rebuild it specifically for the Rezound it will clear the confusion surrounding the purpose and use of the tool.
I look forward to seeing where this goes...
This may be huge. Invaluable tool if used properly.
I wonder if this same technique would work using "fastboot boot recovery.img" instead of actually having to save / flash / restore the boot.img?
I've been asking the same question
Sent from my ADR6425LVW using XDA Premium App
RustyNailz said:
I wonder if this same technique would work using "fastboot boot recovery.img" instead of actually having to save / flash / restore the boot.img?
Click to expand...
Click to collapse
nolimit78 said:
I've been asking the same question
Sent from my ADR6425LVW using XDA Premium App
Click to expand...
Click to collapse
Yes, but the point is to avoid fastboot.
con247 said:
Yes, but the point is to avoid fastboot.
Click to expand...
Click to collapse
True. But I would think there would be a way to duplicate the fastboot behavior and boot from an alternate image file without requiring the use of a PC.
You can only issue fastboot commands from an external device via USB while your Rezound is in fastboot mode in the bootloader.
RustyNailz said:
True. But I would think there would be a way to duplicate the fastboot behavior and boot from an alternate image file without requiring the use of a PC.
Click to expand...
Click to collapse
This is that way lol
Sent from my ADR6425LVW using XDA App
Not quite. I don't believe the fastboot method actually flashes anything to the boot image, so this method leaves more room for error due to the process of saving / flashing / restoring the boot image.
Totally awesome gentlemen. I cannot wait to install this on my phone.
RustyNailz said:
Not quite. I don't believe the fastboot method actually flashes anything to the boot image, so this method leaves more room for error due to the process of saving / flashing / restoring the boot image.
Click to expand...
Click to collapse
That is the only way to do it without fastboot.
---------- Post added at 07:18 PM ---------- Previous post was at 07:17 PM ----------
Irieone said:
Totally awesome gentlemen. I cannot wait to install this on my phone.
Click to expand...
Click to collapse
I am building a GUI for this so it will be pretty sick. Should be out tomorrow night.
Sent from my ADR6425LVW using Tapatalkwa
RustyNailz said:
Not quite. I don't believe the fastboot method actually flashes anything to the boot image, so this method leaves more room for error due to the process of saving / flashing / restoring the boot image.
Click to expand...
Click to collapse
Sure, but this method doesn't require a computer (or other external device) for those times when you are away from a computer. You can't do the fastboot method without a second device.
The 3D had a program called Flash Image GUI. It did what we're trying to accomplish here. Interestingly enough the program "worked" but it wasn't nearly as reliable as the fastboot method
Sent from my ADR6425LVW using XDA Premium App
And please don't take any of what I say a hating. I am merely discussing and spitballing. Lord knows that with the drama over at the 3D forums and Chad kernels I am not trying to bring that hate here. Not in the slightest.
I will post this in the other thread too. Thanks for all your hard work sir!
Sent from my ADR6425LVW using XDA Premium App
Related
We've tested and can confirm this bootstrap recovery is working. Thank you to bane449 for testing. The recovery is a straight APK pull from the Droid X2. Worked thanks to the similarities between devices.
Instructions and download:
http://briefmobile.com/motorola-photon-4g-root-custom-recovery-now-available
Looks successful to me: DroidX2 Recovery GFAN.COM V2.5.1.8
And it booted back into Android properly, even
So what will this allow me to do? What are its advantages? What are the risks?
sub2k1 said:
So what will this allow me to do? What are its advantages? What are the risks?
Click to expand...
Click to collapse
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Forgive my ignorance but what is a "pseudo-Rom"?
kennethpenn said:
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
10 chars
I know what ROM's are, never heard anyone say psuedo-ROM.
Lokifish Marz said:
Custom ROMs (if available for the Photon) like MIUI, CM7 etc...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
I know what ROM's are, never heard anyone say psuedo-ROM.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Psuedo meaning "not really" a ROM. A locked bootloader will prevent true custom ROMs, but P-ROMs will be possible.
P-ROMs are based off of stock files and modifications. They don't replace the kernel or modem.
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
b-reezy said:
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
Click to expand...
Click to collapse
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
kennethpenn said:
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
Click to expand...
Click to collapse
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
brianez21 said:
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
Click to expand...
Click to collapse
Caveats:
This is not a *real* recovery. The way this recovery works is by hijacking portions of your boot process during system initialization and starting into recovery instead. So, if you hose your system *COMPLETELY* you will need to SBF. Specifically, if your logwrapper, logwrapper.bin, or hijack binary are missing from /system/bin, you will be screwed.
This is from koush himself concerning droid x/2 bootstrap. I would seriously wait til an sbf surfaces before flashing any of these "psuedo-ROMS" or even just deleting any system apk's. Just my opinion.
sub2k1 said:
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
Does the phone need to be rooted first in order to installl this recovery apk?
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
mediawiz said:
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
Click to expand...
Click to collapse
This is CWM bootstrap. Original one was on the Droid X, created by Koushik Dutta. Then it was ported to the Defy. Then to the Atrix. Next, the Droid X2. Now, the Photon 4G.
V2.5.1.8
Sbf is gonna be your friend when it comes to unrooting and restoring. It will pop up soon.
sub2k1 said:
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
beartrap said:
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
Click to expand...
Click to collapse
You can unplug.
Sent from the best phone yet!
As you guys know, we can't flash boot images directly from Recovery. This makes restoring nandroid backups more difficult.
Well, not anymore. This flashable allows you to restore the boot image from a nandroid backup directly from recovery. For those of you who are experts, this duplicates the functionality of "fastboot boot recovery.img" in a self-contained zip.
To Use:
1) Flash the attached zip file
2) Press Volume UP when prompted at HBOOT
3) Reboot the Device (it will probably ask you to press power to do so)
NOTE: If the device doesn't reboot on its own, reboot "normally" not into recovery. It will take you to recovery automatically. If you go into recovery via the HBOOT menus, you still won't be allowed to restore boot images.
4) Restore your nandroid and with its boot image. It will flash this time
5) Done.
How it works:
1. Dumps your recovery image
2. Zips it into a viable PH98IMG.zip and drops it on your SD card
3. Downgrades your main version
4. Reboots to HBOOT so you can flash it
5. You then boot into unprotected recovery.
Haha I had an issues yesterday that this would have fixed. You do amazing work con, keep it up! We appreciate it!!!!!
Sent from my Ice Cream covered Rezound
Why are there not 1000 thanks for this??? This is awesome!
Great stuff. Thanks
DbZ Gokuu said:
Haha I had an issues yesterday that this would have fixed. You do amazing work con, keep it up! We appreciate it!!!!!
Sent from my Ice Cream covered Rezound
Click to expand...
Click to collapse
WasabiWa83 said:
Why are there not 1000 thanks for this??? This is awesome!
Click to expand...
Click to collapse
NilsP said:
Great stuff. Thanks
Click to expand...
Click to collapse
I am glad you guys like it. Not sure how much use it will get, but atleast it is out there.
con247 said:
I am glad you guys like it. Not sure how much use it will get, but atleast it is out there.
Click to expand...
Click to collapse
Worked perfectly ! wow, nice job just like using my OG droid now with backups I had quit making them since I always had to remember what kernel for the rom etc.. tried the endeavor leak and afterwards flashed my backup without a hitch
mjh68 said:
Worked perfectly ! wow, nice job just like using my OG droid now with backups I had quit making them since I always had to remember what kernel for the rom etc.. tried the endeavor leak and afterwards flashed my backup without a hitch
Click to expand...
Click to collapse
Good to get a confirmation that it works.
So we use this any time we restore a nand correct?
yep. It just allows Recovery to flash the boot image, but it is temporary.
Curious. Could this be used on a fresh install as well?
sent from ics land
pwned3 said:
Curious. Could this be used on a fresh install as well?
sent from ics land
Click to expand...
Click to collapse
Yeah but it offers no benefit or extra ease. The way we install custom roms right now is the ideal way.
con247 thank you so much for this. I fastboot flash everything from the computer. But two guys that I help out on gtalk on a regular basis had a bunch of trouble with the PH98 process, but aren't able to use fastboot on their computers while at work.
Both guys have been using this rom very heavily going back and fourth between ICS and gingerbread, and both have confirmed this is very easy for noobs compared to the fear they have of ADB, fastboot.exe, and the cmd line.
Thanks again. You are an incredible asset to the Rezound and Android community.
Nice work
Sent from my ADR6425LVW using xda premium
con247 said:
I am glad you guys like it. Not sure how much use it will get, but atleast it is out there.
Click to expand...
Click to collapse
No more renamed PH98IMG files on my sd card! Good work, sir
Sent from my Ice Cream covered Rezound
I used this quite a bit the other night , after I ran the RUU before I found out restoring old backups was a bad idea LOL. Still worked flawlessly though , so this tool has been invaluable to me ! I started making backups again
I can't restore any backups. I'm using the latest amonra. It just says oops check recovery log. I tried doing it regular and with this but they both failed and I had to use the ruu to recover each time. I don't understand what the problem is.
Sent from my HTC Vigor
Andro X said:
I can't restore any backups. I'm using the latest amonra. It just says oops check recovery log. I tried doing it regular and with this but they both failed and I had to use the ruu to recover each time. I don't understand what the problem is.
Sent from my HTC Vigor
Click to expand...
Click to collapse
well give me the recovery log please. Do you have an external SD card?
con247 said:
well give me the recovery log please. Do you have an external SD card?
Click to expand...
Click to collapse
It might be related to using the Amon Ra 3.14 and trying to backup android secure. Dres, just released a fix because the Devblock location changed so it borked making or restoring backups that contained android secure. Sorry , if this wasn't helpful , but I realized my backups worked because I never backup android secure. Just figure it might save you a lot of debugging when its probably on the recovery this time not the app.
mjh68 said:
It might be related to using the Amon Ra 3.14 and trying to backup android secure. Dres, just released a fix because the Devblock location changed so it borked making or restoring backups that contained android secure. Sorry , if this wasn't helpful , but I realized my backups worked because I never backup android secure. Just figure it might save you a lot of debugging when its probably on the recovery this time not the app.
Click to expand...
Click to collapse
You could have also gotten a bad download. This script shouldn't be affected by the new firmware.
Thanks guys but I figured it out. I left a space when renaming the folder containing my backup. So once took out the space I was able to restore.
Sent from my HTC Vigor
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
twrp recovery..
kenohki88 said:
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
Click to expand...
Click to collapse
What did you have checked while making the backup? data? recovery? cache? system? and did you rename the back up?
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
---------- Post added at 12:42 PM ---------- Previous post was at 12:34 PM ----------
canemaxx said:
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
Click to expand...
Click to collapse
also some roms are picky about which recovery is used to install/backup. I can say I have had no issues backing up stock or custom roms with twrp on my DNA
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Check out NOS its a great rom
canemaxx said:
Check out NOS its a great rom
Click to expand...
Click to collapse
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no thats how that rom boots....leave it alone for about 5-10 minutes youlll see the notificatiion light come on and your =e good to go
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I may have misread but did you wipe everything before loading nos? I saw what was checked for backup but not about wiping. You should wipe everything-system, then cache, then delvik cache-not exactly in that order (make SURE there IS a backup just in case). Load the rom AND flash the correct image file with adb. Also, many roms when FIRST loading up sit a long time before they start up, not sure if nos does this or not-I have been jumpy about the time sitting with a few roms when waiting was all I needed to do. I have had different Viper versions on a few times and moving to another rom was quirky each time I did so, not sure why.
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
rootntootn said:
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
Click to expand...
Click to collapse
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
Click to expand...
Click to collapse
Oh yeah, and I restored my back up and that works just fine
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
Oh yeah, and I restored my back up and that works just fine
Click to expand...
Click to collapse
Its the kernel in NOS. Flash NOS and then flash cpalmers kernel. Then reboot and do the setup and if you want to change to the zarboz kernel you need to delete system/bin/thermald or rename it to thermald_old.bak
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Hmmm well I did everything via my cell (been the way I've been flashing ROMS unless something goes wrong then I use ADB on computer) and everything when properly done works fine using Flash GUI APP love that app! I've flashed super charged hatka 320 (used that for a couple weeks) then switched over to viper...both using Flash GUI I tried using NOS but yes no dice loaded up but when I pull the unlock ring for whatever reason the splash screen comes up and it won't budge from there....and as for my original question haha TWRP did not work for me when restoring it tripped out like if it was missing the boot image (done that before so I'm familiar with that behavior haha)
Oh and I'm still S-on
Sent from my HTC6435LVW using xda app-developers app
CharliesTheMan said:
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
canemaxx said:
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
Click to expand...
Click to collapse
Really? After it boots up? That's odd but ok I'll give it a shot again but probably tomorrow will post here again if it doesn't work....thanks everyone for responding. I'm out at the moment and need cell to be functioning hahaha just in case
Sent from my HTC6435LVW using xda app-developers app
If you are rooted (assuming you are) with busybox and Android Terminal Emulator installed I was wondering if the flash_image binary could actually flash a recovery image to the device, of course there is no recovery image for our device yet BUT maybe we can start building it if this flasher alternative does work.
yes,i think it is possable
and there is some flash recovery in official roms,it named as hidden.img
and hidden.img have more than one version
hidden.img will be flash to partion 6 (mmcblk0p6 UP)
by now, we can not decrypt it's content
Well, we can't create an standard type of recovery as we wouldn't be able get that to boot. However there are ways to hi-jack the Android boot process and start a recovery that way, look at Safestrap for Motorola RAZR.
This way we can boot another rom from the internal storage (image files) and keep the original safe.
I'm very interested an trying to port it over to the XTS, however when playing with the hi-jack there is a risk of bricking so I need to first find out how to un-brick the tablet when the system partition is broken (boot partition would still be fine).
We can even boot to a custom kernel using kext however that one can be quite difficult to get working properly.
But just the ability to boot an Paranormal Android rom would be fantastic (I don't know if that rom requires changes in the kernel. But CM and AOKP doesn't).
If anyone could assist in Safestarp work it would be great. At this stage it's mostly to find out how to un-brick.
I haven't even been able to boot the tablet into recovery or bootloader mode. I have tried both ADB (reboot recovery, reboot bootloader, reboot-bootloader) and holding volume up on boot but whatever I do it still boots into Android.
With this technique I would also expect to be able too boot into the backup system partition or whatever mmcblk0p3 is (contains the system of the firmware the device where preloaded with, mmcblk0p4 is the current system that gets updated) I would hope Sony have built a whay to boot to this partition using the standard bootloader but I can't seem to find any.
EDIT: I were able to reach the recovery by mashing the volume up button on boot so now I feel much better. However I'm still interested in any information that might be interesting.
pajn said:
Well, we can't create an standard type of recovery as we wouldn't be able get that to boot. However there are ways to hi-jack the Android boot process and start a recovery that way, look at Safestrap for Motorola RAZR.
This way we can boot another rom from the internal storage (image files) and keep the original safe.
I'm very interested an trying to port it over to the XTS, however when playing with the hi-jack there is a risk of bricking so I need to first find out how to un-brick the tablet when the system partition is broken (boot partition would still be fine).
We can even boot to a custom kernel using kext however that one can be quite difficult to get working properly.
But just the ability to boot an Paranormal Android rom would be fantastic (I don't know if that rom requires changes in the kernel. But CM and AOKP doesn't).
If anyone could assist in Safestarp work it would be great. At this stage it's mostly to find out how to un-brick.
I haven't even been able to boot the tablet into recovery or bootloader mode. I have tried both ADB (reboot recovery, reboot bootloader, reboot-bootloader) and holding volume up on boot but whatever I do it still boots into Android.
With this technique I would also expect to be able too boot into the backup system partition or whatever mmcblk0p3 is (contains the system of the firmware the device where preloaded with, mmcblk0p4 is the current system that gets updated) I would hope Sony have built a whay to boot to this partition using the standard bootloader but I can't seem to find any.
EDIT: I were able to reach the recovery by mashing the volume up button on boot so now I feel much better. However I'm still interested in any information that might be interesting.
Click to expand...
Click to collapse
Well there is two system partitions and you can use the backdoor thingy from Condi's tools to avoid a soft brick BUT if it writes to the bootloader then we have ourselves a brick.
Sent from my Nexus 4 using xda app-developers app
;42754576 said:
yes,i think it is possable
and there is some flash recovery in official roms,it named as hidden.img
and hidden.img have more than one version
hidden.img will be flash to partion 6 (mmcblk0p6 UP)
by now, we can not decrypt it's content
Click to expand...
Click to collapse
I have the hidden.img BUT the MD5Sum is badf0628deff7f47b1148e5ae662aa26
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Well there is two system partitions and you can use the backdoor thingy from Condi's tools to avoid a soft brick BUT if it writes to the bootloader then we have ourselves a brick.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Of course as the boot partition requires a signature. Safestarp only writes to the system partition and it only does that once under install, after that in only touches the storage. You can have four ROM slots in the storage where you can installed custom ROMs, the system partition shall always contain the stock system. If I can get kexec to work there aren't any noticeable problems with having a locked boot loader.
Sent from my XT910 using Tapatalk 4 Beta
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
pajn said:
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
Click to expand...
Click to collapse
Holly crap, you got the recovery installed, will this work with the original Sony Tablet S and how did you manage to do such thing?
EDIT: I see you used Safestrap but from where?
Sent from my Nexus 4 using xda app-developers app
pajn said:
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
Click to expand...
Click to collapse
What device are you using? STS or XTS?
Sent from my GT-S5830 using xda app-developers app
jumper62 said:
What device are you using? STS or XTS?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
That is the Sony Xperia Tablet S, I can tell by the branding near the screen and the IR Blaster plastic cover is smaller.
Sent from my Nexus 4 using xda app-developers app
jumper62 said:
What device are you using? STS or XTS?
Click to expand...
Click to collapse
Definitely an XTS. Notice the Multi Port connection at the bottom center of the tablet.
WOW! coooool. btw, how did you manage to boot safestrap in XTS? probably same method could be done on STS
As some saw it's a XTS. The recovery is safestrap and it works using 2nd-init. I found a good text describing it using normal language here http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
It should be portable to STS aswell. Every rooted Android should be able to run it. I can't promise anything as I'm working but when I'm done I can take a look at the STS aswell but I would need help from someone with at least basic adb and linux knowledge as I don't have a STS.
It wore actually easier to get this far than I expected so that's good but there are more work needed so I can't relax yet.
Sent from my XT910 using Tapatalk 4 Beta
Just contacted Chainfire on Google+ for any ideas how this is going to work.
UPDATE: Nothing yet...
Sent from my Nexus 4 using xda app-developers app
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i think you need to contact Hashcode, original developer of Safestrap for that
andyabc said:
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I do have recovery working on XTS, should be quite simple to port to STS. Things left is hijack (simple but scary) and manager app (simple but can ne time consuming)
Sent from my XT910 using Tapatalk 4 Beta
pajn said:
I do have recovery working on XTS, should be quite simple to port to STS. Things left is hijack (simple but scary) and manager app (simple but can ne time consuming)
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
How did you do it though?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
How did you do it though?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Studied safestrap to see how it worked and applied the same
techniques to the XTS. Where things don't work I work around them
by googling, studying others work or just testing. A pretty good
knowledge of Linux, it's boot process and programming does
help quite a bit
pajn said:
Studied safestrap to see how it worked and applied the same
techniques to the XTS. Where things don't work I work around them
by googling, studying others work or just testing. A pretty good
knowledge of Linux, it's boot process and programming does
help quite a bit
Click to expand...
Click to collapse
Can't wait for recovery on sts good job on the xts dude!
Sent from my LT28i using xda app-developers app