Related
Hi all,
Anyone having the same issues?
As far as I know, the last 4 digits (707.9 or 405.5) represent the region or mobile network and have nothing to do with the update version or build number. So this rom is still the same as 2.73.405.5. Moreover, the flashrec is using an exploit in the android kernel and should theoretically work as far as the kernel stays the same... and it IS still the same!
Now coming to your problem... let me tell you what I experienced:
I had the old stock ROM >> I upgraded it to 2.76.405.5 with the RUU >> wanted to try MoDaCo 2.2, hence installed Flashrec, backed up recovery (worked!), then flashed Cyanogens modified recovery >> turned off the phone and turned it back on with Home and Power buttons, it took me to the recovery screen (all fine!!) >> I installed MCR 2.2 and still everything was fine. The I read about Amon_RA's recovery image and wanted to flash it on top of Cyanogen's recovery using flashrec... and flashrec gave me an error on the backing up step (DIDN'T WORK!) >> I reinstalled the official ROM via RUU >> it removed the original cyanogen's recovery image >> this made flashrec work again!!
So I think, if you already have a recovery image, flashrec does not work to put another on top of it. The way to go then is via ADB SHELL command prompt. This is whay I think... you can try it.
I'm also having the trouble with the same built (2.73.707.9), when i put the cm-hero-recovery.img on the sdcard, then run flash recovery (sdcard/cm-hero-recovery.img) i cant click on backup to flash custom image button, fastboot boot isnt working for me!. Please if someone can help that would be greatly appreciated.
salmanbodla said:
As far as I know, the last 4 digits (707.9 or 405.5) represent the region or mobile network and have nothing to do with the update version or build number. So this rom is still the same as 2.73.405.5. Moreover, the flashrec is using an exploit in the android kernel and should theoretically work as far as the kernel stays the same... and it IS still the same!
Now coming to your problem... let me tell you what I experienced:
I had the old stock ROM >> I upgraded it to 2.76.405.5 with the RUU >> wanted to try MoDaCo 2.2, hence installed Flashrec, backed up recovery (worked!), then flashed Cyanogens modified recovery >> turned off the phone and turned it back on with Home and Power buttons, it took me to the recovery screen (all fine!!) >> I installed MCR 2.2 and still everything was fine. The I read about Amon_RA's recovery image and wanted to flash it on top of Cyanogen's recovery using flashrec... and flashrec gave me an error on the backing up step (DIDN'T WORK!) >> I reinstalled the official ROM via RUU >> it removed the original cyanogen's recovery image >> this made flashrec work again!!
So I think, if you already have a recovery image, flashrec does not work to put another on top of it. The way to go then is via ADB SHELL command prompt. This is whay I think... you can try it.
Click to expand...
Click to collapse
I only have cm-hero-recovery.img in my sdcard. ADB method will return a "not allowed" error..
I am also having the same problem. Flashrec says backup failed but more importantly it says flash failed.
My 2.73.707.9 ROM is straight out of the box so I do not have any recovery image installed. Much appreciated if some clever person can help out. Thanks!
Leechoonhwee said:
I only have cm-hero-recovery.img in my sdcard. ADB method will return a "not allowed" error..
Click to expand...
Click to collapse
I'm Having the exact same problem with the adb commant prompt.
I tried to close all apps with taskiller and tried to use flashrec again and again without any luck, I can't even click on the flash custom image button, I can only click on backup, and it gives me an error.
Leechoonhwee said:
Hi all,
Anyone having the same issues?
Click to expand...
Click to collapse
I have ticked usb debugging and C:\Hero>fastboot boot cm-hero-recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
C:\androidsdk\tools>fastboot devices
HT991L900567 fastboot
C:\Hero>fastboot boot cm-hero-recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
C:\androidsdk\tools>fastboot devices
HT991L900567 fastboot
I have tried flashrec and followed the instructions and it says fail.
It cannot start with back up.
Thanks
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
salmanbodla said:
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
Click to expand...
Click to collapse
Hi, Kernel Version is 2.6.27-44690c1a [email protected] )
Build number : 2.73.707.9 146733 CL#62020 release-keys
This version is for Singapore, malaysia and thailand regions. It's unlocked
awsy44 said:
Hi, Kernel Version is 2.6.27-44690c1a [email protected] )
Build number : 2.73.707.9 146733 CL#62020 release-keys
This version is for Singapore, malaysia and thailand regions. It's unlocked
Click to expand...
Click to collapse
I have the exactly same Kernel version. Some new discovery
1. Use the drivers from SDK 1.6. Phone in normal mode. Adb devices and fastboot devices can recognise the phone.
2. Fastboot USB mode. Fastboot devices recognise devices while adb returns nothing.
OK, I am running the official new European ROM 2.76.405.5 with the following kernel:
2.6.27-8dd6deee [email protected] )
I don't know how different it is from yours, but some numbers are certainly different. May be that is the reason, but I am afraid I am not sure. So keep trying - you may be lucky!
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
salmanbodla said:
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
Click to expand...
Click to collapse
I am getting an error when trying to update the official hero rom
ERROR [131] : CUSTOMER ID ERROR and on the phone it says update failed,
I tried 2.73.405.5 and 2.73.728.5 as well, they both gave me the same error.
I Don't why any sort of upgrade or image recovery isn't working on this phone!.
salmanbodla said:
Can you guys who are having trouble with flashrec, please give following info:
1) Detailed version of your kernel... if the kernel has changes, flashrec is no longer supposed to work as it was an exploit in the old/current kernel.
2) Where is this ROM 2.76.707.9 from? Which region? Which carrier?
Click to expand...
Click to collapse
1. Linux version 2.6.27-44690c1a ([email protected]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #739 PREEMPT Thu Aug 27 19:50:51 CST 2009
2. the ROM on my unbranded HK retail version (htc_asia_hk_wwe) is 2.73.721.9 146733 CL#62020 release-keys
Hey roger,
same here, look like the kernel expliot is fixed:
#adb push /tmp/flashrec-1.1.2-20090909/assets/raw/asroot /sqlite_stmt_journals
932 KB/s (81188 bytes in 0.085s)
#adb shell /sqlite_stmt_journals/asroot /sqlite_stmt_journals/abc /system/bin/sh
FAILURE: Didn't get root.
awsy44 said:
I am getting an error when trying to update the official hero rom
ERROR [131] : CUSTOMER ID ERROR and on the phone it says update failed,
I tried 2.73.405.5 and 2.73.728.5 as well, they both gave me the same error.
I Don't why any sort of upgrade or image recovery isn't working on this phone!.
Click to expand...
Click to collapse
You have CIDlock on youre phone, so it won't work without some tricks.
http://forum.xda-developers.com/showthread.php?t=559806
Heppieboeddah said:
You have CIDlock on youre phone, so it won't work without some tricks.
http://forum.xda-developers.com/showthread.php?t=559806
Click to expand...
Click to collapse
Do you think thats the problem , because I checked the link , my phone is already unlocked, Do you think HTC made the phone un update-able?.
awsy44 said:
Do you think thats the problem , because I checked the link , my phone is already unlocked, Do you think HTC made the phone un update-able?.
Click to expand...
Click to collapse
Your phone is unlocked in a sense that you can insert any sim card and it works. CID lock means that you cannot flash ROMs other than your region.
salmanbodla said:
Or else, you can always TRY toinstall a European Hero ROM. The new official relase is really good and stable. If it installs on your device, you are all sorted You can find the links on XDA to download it as an RUU.
Click to expand...
Click to collapse
Yeah... thought of that but Europe ver does not comes with Chinese IME...
Leechoonhwee said:
Yeah... thought of that but Europe ver does not comes with Chinese IME...
Click to expand...
Click to collapse
Then I think the best way to go is to install Modaco rom version 2.2 enhanced - that has Chinese IME in it. About MCR 2.3, people have several complaints, but there is no harm in trying. Oh but the main question is how will you install the recovery image to do all this rooting/flashing since flashrec is the only option available after the upgarde (I suppose!). The new hboot file won't even allow you to "fastboot boot recovery.img". That's a bit of a shame but I am sure cleverer people out there will soon find a hack
UPDATE: My Experience Getting The Phone Flashed to the 2.73.405.5-rooted-signed.zip
Phone CAN be flashed!
Old Version:
Build: 2.73.728.5 146733 CL#61267 release-keys
Kernal: 2.6.27-8dd6deee [email protected] )
Baseband: 63.18.55.06EU_6.35.06.18
New Version (pre-rooted):
Build: 2.73.405.5 146733 CL#61267 release-keys
Kernal: 2.6.27-8dd6deee [email protected] )
Baseband: 63.18.55.06EU_6.35.06.18
The phone did not have android market on it initially as it was the Malaysian (SEA) version. This is how I flashed it to the WWE version with market and most locales etc.
1. Choose a ROM (Link to Generic ROM's inc. pre-rooted
They will be in the update.zip format, as this is the format we need. The link I have given is for the generic versions with nothing added to them.
2. Download the appropriate files
- Flashrec Download the latest version from here (fastboot will not work for this phone kernal)
- Amon RA Recovery Image
Either: (For Installing .apk's)
- HTC Sync
or
- OI File Manager
3. Install Flashrec
Either using HTC Sync or OI File Manager install the flashrec apk onto your phone.
To install with OI File Manager, just copy to your SD Card, and browse to the SD card and select the file.
4. Run Flashrec
Select backup recovery image (the last option), and let that finish
Then type into the box up the top the following
/sdcard/Recovery-RA-HERO-v1.2.2.img
And select the button below the textbox (flash recovery image)
Once this is done, your recovery image will be flashed, and you can now boot into recovery mode!
5. Backing Up
Rename the ROM file you downloaded to update.zip
Save it to the root directory on your SD card
Turn the phone off, hold down the home and power buttons until a green menu comes up.
*** Select nandroid backup first ***
Let it run its course and then reboot you phone (first option in the menu) and copy the folder 'nandroid' from your SD card to your computer and store it somewhere safe
6. Flashing new ROM
Reboot your phone again into the recovery image (home + power buttons)
And select Wipe/Factory Reset
Then select Apply:update.zip
Let this run, and when it is finished, you will have the 'good' software, and android market!
With this method you can apply any other ROM you want (MoDaCo for instance)...
Hope my learning experience will help some other people!
I have the exact ROM (bought my Hero in Malaysia)
It can be flashed. I use flashrec, Amon Ra's and official pre-rooted 2.73.450.5 update image.
Yes there is no Market, and that's why I flashed it with another ROM.
Micksta said:
I've been looking around for a while and found one thread that's related to my phone. And only found 1 with people talking about this release.
But I am unsure if this phone can be rooted/flashed.
Build: 2.73.728.5 146733 CL#61267 release-keys
Kernal: 2.6.27-8dd6deee [email protected] )
Baseband: 63.18.55.06EU_6.35.06.18
It came like this, I have not flashed the updated Hero rom on it, from what I know its the SEA version of the Hero with no market on it. And I really would like to have the market on it
Has anyone else had experience in trying to root/flash this version of the Hero?
Thanks
Click to expand...
Click to collapse
You're damn lucky dude that you've got THAT kernel version. Check out the thread which says that flashrec doesn't work and those guys have a slightly different kernel and are having hell of a trouble trying to flash a recovery image and a new ROM.
Yep, your best bet is to use FLASHREC AND AMON_RA'S recovery image, then go for any ROM you like (as long as you do not get and Customer ID error). Good luck
Geochelone said:
I have the exact ROM (bought my Hero in Malaysia)
It can be flashed. I use flashrec, Amon Ra's and official pre-rooted 2.73.450.5 update image.
Yes there is no Market, and that's why I flashed it with another ROM.
Click to expand...
Click to collapse
How did you bypass the customer ID error? Did you use RUU or update.zip??
salmanbodla said:
How did you bypass the customer ID error? Did you use RUU or update.zip??
Click to expand...
Click to collapse
I am assuming he used update.zip, I have updated my first post to reflect on my experiences flashing my Hero.
hey guys I'm totally new to this and I think I messed this up already... I'm pretty confused by all this - I am not a computer/technical person in the least I just want market place... anyways I messed up in flashrec and now I don't have the right options - I reset the phone and reinstalled flashrec and I get "phone is ebi1/32a" at the top, the type box, and 'download recovery image' and 'restore backup image buttons'... how do I fix this or atleast get it back to original..? sorry I'm so ignorant, I've not done anything like this before.
Micksta said:
/sdcard/Recovery-RA-HERO-v1.2.2.img
Click to expand...
Click to collapse
I know this is going to be a dumb question but where does this go... after /flashrec or after .org or in place of the whole thing... ?
NM I got it
Thanks for this post. I just succesfully flashed my htc hero.
No i can look for some nice custom roms.
Awesome
The unlockr instructions were way too involved and require hacking an sdcard.
Thanks for sharing.
for some reason i did all kinds of editing to the phone supposed by the website the unlocker to unlock my htc hero.. now after doing all that they said it was as easy as 1...2...3... so after i did the cmd editing and phone cmd editing im still not being able to backup the original img that i have now.. so i understand that once you select backup that there is a load bar that starts working but when using fleshrec (or watever) i select backup and nothing happens... i might have done it already just not too sure is there anyway to check on the HTC Hero by Sprint???
-Thanks in advance
also holding down menu and power button on my phone (htc hero) it just puts me in safe mode ?????
I had to follow unlockr instructions for hackign an sd card as i had perfect spl. It was the only way
hi guys,
been doing a lot of reading & kind of exhausted and the head is hurting
hope someone can help me...
i had a HTC hero on orange UK brought down to India.
Trying to unlock & load a random ROM but having the bizzarest of issues.
the hero is running on stock 1.5 build 2.73.61.66
i downgraded to 2.73.61.5 assuming that would be a better way to go...
anyways the process went well... BUT..
it starts up and goes into the "first setup" page where it asks for language & then asks me to insert the sim card to make calls...
I have NO ORANGE SIM Card.
There is no way i can enter into the phone now. i could do it earlier, the phone would boot without the sim & i used it to play music & stuff.
Now decided to use the phone for wat it is meant for, but stuck in that stage.
Can anyone help me out please.
or direct me in the right direction....
is there a way to get past this and actually come to the home screen so i can continue with everything such as unlocking the phone & loading a different rom?
Await & appreciate any response
If you just want "your phone" back I think you should be able to find the official way of restoring it to default (even upgrade to HTC's android 2.1) here:
http://www.htc.com/europe/supportdownloadlist.aspx?p_id=283&act=sd&cat=all
if you get the green android robot and starts to ask you for google login etc you can click the four screen corners to go directly to Home. Like this:
23
14
afaik Android wasn't built for use without a sim - I've wondered why too. It's complicated using it with no sim. Here's what I found on google:
http://e.ntangled.net/content/howto-set-android-dev-phone-without-sim-card
Perhaps it's because it isn't activated (with your google login) and it was earlier with a sim card but now you can't because you have no working sim card
MP3 files
If you've installed a boot loader like Amon's RA Tool v1.7 (that starts instead of Android when you hold Home and Power/hang up-button 10 seconds at boot) it might give you access to the SD-memory card and your MP3s.
I think The official HTC ROMs can only be installed (the official way) using USB and a flash-programming tool from HTC on your PC.
The Android SDK software - if I remember correctly - allows you to program the phone's recovering boot ROM (a small boot ROM - not the big phone/android OS) and once you've installed a new recovery boot ROM like Amon RA tool you can install any Android ROM directly from the SD card (ROMs in a zip file) without ever needing the PC again. You can even backup the entire phone ROM to the SD card using Amon RA tool's Nandroid backup feature and restore the ROM again if a new custom ROM is bad.
> So you are telling me that I can install Amon Ra directly
> from the PC, without having any interaction with the Phone?
Yes, I think that's probably the ONLY way actually (for the recovery boot tool).
> do you think i would be able to install a new rom and
> probably get past this screen (and probably jailbreak the phone as well)??
Hmm I'm pretty sure that most custom ROMs (I can recommend a few for htc Hero GMS) let's you go directly past the startup procedure.
> btw Thanks so much for your patience dvfk
No problem.
Here's a test how to install the Amon tool using the USB command line/shell to the phone:
http://forum.xda-developers.com/showthread.php?t=561124
If you have htc Hero GSM the newest Amon RA tool is available there. Do you know about the ADB shell that comes with the SDK to control the phone over USB?
btdag:
You can't install AmonRA without root permissions, you can't get root unless you get into android. My advise - downgrade to a different rom: ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe
If that boots then you should be able to gain root using my guide:
http://forum.xda-developers.com/showthread.php?t=645253
If not why not install an orange rru exe from HTC support? That might work.
Click to expand...
Click to collapse
Currently one of the most popular ROMs is CyanogenMOD and the newest version (with android 2.2) is here - they're not 100% stable though (and camera can only shoot video in build 08312010 - I now see build 09012010 is just out but I haven't tried it):
http://mirror.kanged.net/cm/nightly/hero
When it's stable it will be moved to .../cm/stable and /hero I guess.
It lacks Gmail and other closed source google apps. They can be found here and should also be installed using Amon RA recovery boot tool after the full CM6 ROM is installed:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps_for_HDPI_devices_2
(Hero works nicely with the HDPI version of Google apps for high-res displays)
I've found another ROM, though, called FroydVillain v1.4.4 to be more stable and cam working. It's a modified copy of the CM6 and includes the google apps from the start. However to get the newest version you currently need five zip files and install them all in the number order (FroydVillain 1.4.0 - 1.4.1 and 1.4.1 - 1.4.2 etc on to 1.4.4).
Links can be found here:
http://forum.xda-developers.com/showthread.php?t=762206
letmedanz said:
well, not so good
1) trying btdags advise -
> "You can't install AmonRA without root permissions, you
> can't get root unless you get into android. My advise -
> downgrade to a different rom:
> ftp://xda:[email protected]_NoDriver.exe"
i end up with error 131. i guess this means i need a gold card. just started reading about it
Click to expand...
Click to collapse
I think this is the newest guide to root/hack your Hero:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click
...but the link to Amon RA boot tool is outdated - there's a version 1.7 afaik (see in my earlier post).
If I remember correctly I used this old/obsolete version:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero/
letmedanz said:
2) your suggestion:
> "I've found another ROM, though, called FroydVillain
> v1.4.4 to be more stable and cam working"
> as you should know by now, am completely new to
> this, so i tried the guide:
> http://www.villainrom.co.uk/forum/showthread.php?2054
i've just reached this step:
reboot into recovery (press Home and then power on the Hero, keep Home pressed) after copying 1.4.0 & 1.4.1, But when i hold home & power, it reboots & shows an exclamation mark within a triangle, next to a phone. supposing this is not right.
Click to expand...
Click to collapse
That's because as I said first VERY first think you need to do is install the Amon RA recovery tool - and make sure home + power boots into the RA tool.
letmedanz said:
i have no ideas on adb, trying to see if thats the way and i need to learn to use it..
Click to expand...
Click to collapse
When you install the Android SDK you get the ADB command line/shell and drivers for the phone. When the phone is plugged in (and usb phone drivers intalled) you can access the phone using ADB and do anything with it.
The old/obsolete verison of unlocking/rooting your Hero describes how you use ADB:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero
...but it seems the new version of unlocking (one-click rooting) doesn't even need it.
dvfk said:
I think this is the newest guide to root/hack your Hero:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click
Click to expand...
Click to collapse
well, that is where the problem started
Orange UK Users - Please downgrade your ROM version to 2.73.61.5 using this HTC Program. Then you can follow the rest of this procedure as it is written. Good luck!
i had the .66 version, after reading the above, i downgraded to the .5 version.
After the install, it boots, reaches the initial setup page.
First asks for language, next screen is "Insert sim to make calls"
so unable to proceed....
...and in this guide you get stock too?
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero
It mentions USB debugging must be on (so you need to access Settings I guess) but it's worth a try.
At work now.. so will need to try after heading home
Any progress?
well... just tried the obsolete htc hero root method
**How To: Gain Root Access on Your HTC Hero (OBSOLETE)**
Steps 1 to 10 are smooth, no issues
Step 11 . If the serial number and the word fastboot next to it popped up, then go back to the command prompt on the computer and type
fastboot boot cm-hero-recovery.img
here i get an error-
downloading 'boot.img'... FAILED <remote: not allow>
so stumped there..
checked in unlockr.com & they says to get past this stage i need to create a gold card...
which obviously is not possible i cant get into android...
Any suggetions/comments/help ???
Why not to flash a custom ROM?
Sent from my GT-S5660 using xda premium
Here are instructions on how to unlock and root your htc desire 610. These work for both models, but the files are for the AT&T version.
BEFORE WE BEGIN, SOME TERMINOLOGY:
Unlocked Bootloader: HTCDev website will help us do this. It's free. It allows you to flash a recovery and signed boot image, which we have. It does not allow you to flash unsigned images.
S-On: Security on. This is how our phones come stock. Htc will not allow us to flash unsigned images because of this.
S-off: once someone achieves this for us, it will allow us to modify anything and everything, signed or not. We can flash new boot image and radios without worry of version number or signature.
Root: Allows you "administrative access" to your device, to move files and do certain things. However, our phone also has...
System Write Protection: HTC included this in the kernel, and it basically means that unless you have a kernel or boot image that gets around it, any changes you make to the system partition (aside from flashing in recovery) won't stick through a reboot. Essentially they will be temporary in an effort to preserve the phone. We don't like this.
Now then, with that out of the way...
1) HTCDev Bootloader Unlock: Under "Select Your Device", scroll ALL THE WAY TO THE BOTTOM, and choose "All Other Supported Models". I know it works, because I just did it. IT WILL WIPE YOUR DEVICE DATA. If you want the data backed up beforehand, turn on USB Debugging and use this command through adb to make a backup:
Code:
adb backup -apk -shared -all -f C:\desirebackup.ab
2)Download ClearD's Root Tool V3(USE VERSION 2.1 BELOW, VERSION 3 DOESN'T WORK FOR MOST PEOPLE): After you have drivers installed for your desire (install htc sync, plug in your phone, then let them load, then uninstall htc sync), fastboot turned off in the battery options in settings, and USB debugging turned on through the hidden developers menu, read the disclaimer in red below, and download and run this exe on your Windows machine with your phone plugged in. It'll install twrp recovery 2.8.0.1, install the engineering boot image, install SuperSU and root, and then install jmz's system-unlocked kernel to make root work like it should. I'm still working out kinks, so if it doesn't work right the first time, run it a second time! Thanks go to jmz, deez_troy, AdriVelazquez, and chainfire for the pieces to make this work.
DISCLAIMER: ONCE YOU USE THIS TOOL, YOUR DEVICE WILL HAVE THE ROOTED ENGINEERING BOOT IMAGE, WHICH CANNOT BE REVERSED. THERE ARE NO SIDE EFFECTS TO THIS IMAGE EXCEPT THAT IT SHOWS A DISCLAIMER ON YOUR SPLASH SCREEN WHEN YOU BOOT THE PHONE. THIS CANNOT BE CHANGED UNTIL WE GAIN S-OFF, WHICH HAS BEEN ACCOMPLISHED, BUT IS NOT YET PUBLICLY AVAILABLE. IF YOU ARE OK WITH THIS, PROCEED.
IF V3 DOESN'T WORK, HERE IS VERSION 2.1: Download ClearD's Root Tool V2.1. THIS VERSION INSTALLS ENGINEERING BOOT IMAGE AND JMZ KERNEL.
Return to Stock (AT&T ONLY) :http://dl3.htc.com/application/RUU_...16_10.20.4187.00L_release_392486_signed_2.exe
This ruu will bring you back to complete stock, version 1.50.502.7. It has to be run through Windows, and you have to have a locked bootloader to run it. If you're unlocked, you can relock it in fastboot with the command:
Code:
fastboot oem lock
. Feel free to unlock it again after updating through the RUU. You can use your original unlock token or get it again through htcdev.
Older root tool version 1:
Download ClearD's Desire 610 Root Tool V1. This version does not contain the engineering boot image, and needs it to work fully, thus is buggy and probably won't root you with one click. It will fail to adb remount, which will fail to auto install the zip files in recovery. If you've already flashed the engineering boot image, then it will work properly without issue. Otherwise, it'll place the root zip files on your phone, but you'll have to flash them manually in recovery.
Click to expand...
Click to collapse
Old manual method:
2) Recovery: After you're unlocked, download TWRP recovery from this thread, rename the image file to "recovery.img", and flash through fastboot with the command:
Code:
fastboot flash recovery recovery.img
This will give you the official Team Win Recovery Project recovery for our device, which will allow you to root.
3) Insecure Boot Image and Root: Once you have recovery installed, the rest is easy. In recovery, if you try to reboot back into the rom, it will ask you if you wish to root. Select yes. It will do the rest I believe, and install SuperSU when you boot back into the rom. You'll also want to download and flash JMZ's insecure kernel, which unlocks the system file lock that htc places on their newer devices. Once flashed, you can then change system files and the changes will stick through reboots.
Click to expand...
Click to collapse
HTC Engineering Boot Image:
Once unlocked, download the root zip provided in this thread, then open it. We can't just flash the zip file because most of us have an updated rom version than the one it was intended for, and I'm not sure how to fix that. But no bother. Pull out the boot image file, and place it somewhere you can find it. I put it right in my MiniADB/Fastboot folder for easy access. Then, you need to flash it. Here's how:
Code:
fastboot flash boot boot_root.img
You'll then have an insecure boot image, and it will say so on your splash screen. Trust me, the words are pretty ominous.
To restore your backup you made before unlocking, use this in adb:
Code:
adb restore C:\desirebackup.ab
Click to expand...
Click to collapse
A few superstars are currently working on s-off, and this will be updated once that occurs.
Special thanks to:
-JMZ (Recovery and Kernel)
-Deez_Troy (officiating recovery)
-AdriVelazquez (Insecure boot image)
-Chainfire (SuperSu)
Also, to save this spot and before I forget it going to sleep tonight, I'm actually not sure if firewater or sunshine will work or not yet because I haven't gotten app root yet for them to function. I'll have to get that, then we'll try one or the other of those. /end thought
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
ClearD said:
Edit: I do believe we will need the wp_mod to disable system write protection and allow su to stick before we continue. That'll allow us full root. Or, we could continue with a twrp build or a Clockworkmod build if someone can assist.
Click to expand...
Click to collapse
I could help with that, but you will have to build, I currently don't have a cyanogenmod source around. I need outputs of:
cat /proc/emmc
mount
cat /system/build.prop #<-- root maybe required
and I need your stock recovery.img, try getting it from an ota, or using dd.
The kernel source for this phone is released, you don't need to use the wp_mod.
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
ClearD said:
It is? Where did you find it released? And how would we go about getting system writable without wp_mod? I'm still trying to work out all the kinks and have never built from source.
The outputs you need should be in my dev info thread except for the build prop, but I can remount and pull that.
Click to expand...
Click to collapse
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
dummie999 said:
? never built from source? You are RD!
http://www.htcdev.com/devcenter/downloads Filter device desire 610.
About the system write protection: https://github.com/dummie999/android_kernel_htc_z4u/commit/19626f6c38b56b715dcc0b005ec8b82ce8ca264a
Should work
Well, build.prop then,
Edit: I need your stock recovery. You can get this with:
Code:
dd if=/dev/block/mmcblk0p41 of=/path/to/file/recovery.img
But you'll need busybox installed.
Edit2: You play subwaysurf! :highfive:
Click to expand...
Click to collapse
I'll add this hear also since I was adding it to the rooted forum. But dummie999 is right.
AdriVelazquez said:
That logic is sound; however slight differences in the model maybe.
Currently in the M8 this file is located in block/blk-core.c, which has the following.
Code:
#ifdef CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
sprintf(wp_ptn, "mmcblk0p%d", get_partition_num_by_name("system"));
if (!strcmp(bdevname(bio->bi_bdev, b), wp_ptn) && !board_mfg_mode() &&
(get_tamper_sf() == 1) && (bio->bi_rw & WRITE)) {
pr_info("blk-core: Attempt to write protected partition %s block %Lu \n",
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = 0;
goto wp_end_io;
} else if (atomic_read(&emmc_reboot) && (bio->bi_rw & WRITE)) {
pr_info("%s: Attempt to write eMMC, %s block %Lu \n", current->comm,
bdevname(bio->bi_bdev, b), (unsigned long long)bio->bi_sector);
err = -EROFS;
goto wp_end_io;
}
#endif
That line of code will need to be intercepted at boot to allow permanent root.
I haven't checked recently, but is the source for desire 610 posted?
Click to expand...
Click to collapse
Also, you'll need to build from source for this.
Also, you can just create modules to intercept the data on boot, which would be easier.
AdriVelazquez said:
Also, you can just create modules to intercept the data on boot, which would be easier.
Click to expand...
Click to collapse
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
My company has actually done a lot of work with the desire 610 and HTC, unfortunately some proprietary. But other's aren't.
Click to expand...
Click to collapse
Just curious, where do you work?
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Also, those outputs were not from my device, but from an unlocked and s-off device of a friend lol. I noticed that also, but was too lazy to remove it.
ClearD said:
I usually build from pre built stock, then change what I want through decompiling and recompiling, also do gui things and script things and theme things. This is new territory, but nothing I'm not uncomfortable doing by any means. I'll work on it tonight.
Click to expand...
Click to collapse
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
dummie999 said:
Well, then I hope you have a linux pc/laptop somewhere around
Good luck!
Click to expand...
Click to collapse
One of each. we'll see what happens lol.
dummie999 said:
Lol, no I couldn't get that working , compiling from source was a lot easier, at least for my d500
Edit:
Just curious, where do you work?
Click to expand...
Click to collapse
Yonder Music. It's a new music streaming app.
ClearD said:
One of each. we'll see what happens lol.
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
AdriVelazquez said:
Yonder Music. It's a new music streaming app.
Click to expand...
Click to collapse
Why do you make your devices S-off? (the thread in general)
dummie999 said:
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source before I forget. There is also a readme included with your download.
Why do you make your devices S-off? (the thread in general)
Click to expand...
Click to collapse
Instead of you paying a subscription fee every month, Yonder Music sells the app bundled with the phone which you have free streaming music for the lifetime of the device.
S-off let's us do all of that.
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
ClearD said:
The only source code currently offered by HTC is:
Device Carrier Region Type Kernel Android Size Description
Desire 610
Vodafone
UK
CRC
3.4.0
v4.4.2 152 MB
1.29.161.2
Desire 610
Vodafone
CH GER
CRC
3.4.0
v4.4.2 155 MB
1.29.166.2
Any idea if either of those would work? :/
Click to expand...
Click to collapse
They usually work, you just have to be sure that your software version (1.29.sth) matches. For example, if you are on 1.29.401.3, it should work. I'm not sure, but I think this usually is only a problem on high end smartphones (one m7&m8), because the carriers there modify the kernels of those devices.
Mine (and I assume others) are on 1.30.x.x
ClearD said:
Mine (and I assume others) are on 1.30.x.x
Click to expand...
Click to collapse
Try it anyway, it might work. For example:
On my phone, the kernel for 1.20 runs fine on 1.13 1.10 1.16, but it doesn't run on 1.26 1.32 1.34. You can't know if it works before you try it.
Root achieved thanks to jmz (confirmed on my unit after his) , s-off is being worked on (by pros, not by me). Jmz built us a twrp recovery that allows for an easy root. Hopefully it'll be released to the masses soon!
first post
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Shattariff said:
Does this image works with At&t devices because I am running firmware 1.19.502.4 not sure if it would stop me from booting...I have attained root by using TWRP however nothing sticks whenever i restart my phone so I was hoping this would be a solution
Click to expand...
Click to collapse
Nope that wont fix it. I am working on a kernel that will solve that problem
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Ophidian_DarkCore said:
if your savvy with the shell, aroma fm has a built in terminal.
flash this in recovery http://forum.xda-developers.com/showthread.php?t=1646108
then cd to the directory.
rm settings.db
mv settings_old.db settings.db
Click to expand...
Click to collapse
Thanks you for you reply. I have one question though, I have no idea if my bootloader or my kernal or any of that is 'unlocked' I only rooted my phone. If I try to flash aroma fm and they are locked or something would that actually really brick my phone?
ALSO: I don't have an SDCARD... I don't think it's possible to flash anything then? Because flashing from the Internal Storage might brick the device. right?
ALSO: I don't think the LG Optimus F60 has ARM Neon support... & the "Recovery mode" doesn't have any flashing support. It's all STOCK.
LG Optimus F60 Specifications
Any Ideas?
Ophidian_DarkCore said:
well damn, if you have a custom recovery usb-otg you can make a flashable zip that runs some shell commands.
flashing wont brick a device. putting unsigned boot/recovery imgs usually bricks locked devices.
as with all lg devices, there is download mode to load stock firmware/updates. [LOL apparently I can't post outside links yet even, if their a quote...]
Click to expand...
Click to collapse
That's RIGHT! But, sorry for the noob question: What is a custom recovery usb-otg and how do I make a flashable zip that runs some commands? (For example: maybe one that just runs the commands but doesn't actually change the recovery software or the boot just one that can rename the files?)
Also, I don't think it would work but, would flashing the recovery to stock not delete any data, and have the phone be able to boot?
If it's too much to explain that's okay just show me some related posts that can show me how.
Thanks again for your time.
Ophidian_DarkCore said:
maybe try this http://forum.xda-developers.com/showpost.php?p=59637778&postcount=62
EDIT: Disregard below
you need a custom recovery before anything. and apparently your device supports fastboot.... so give this a go http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
and later you might get android L
Click to expand...
Click to collapse
I'm not sure, because the phone already has the factory boot and I haven't flashed anything into the Boot Partition. It's probably an error that happens when it tries to validate the settings.db or the permissions it has [chmod or that its mounted read write]. [To my understanding] what TWRP boot loop fix does is install fastboot then the custom recovery and the stock boot again. Which should do about the same thing because the phone is already stock. Right?
Would installing a custom recovery then allow me to access adb or the filesystem? (If so any recommendations?) Or how would I run a script from download mode?
Thanks for your time.
Ophidian_DarkCore said:
you only need to flash the recovery. not the boot img.
installing a custom recovery will either give you adb, or an on device shell.
Click to expand...
Click to collapse
That's right, Thank you. I'm going to try flashing one right now. Do you know of any that give you access to adb? (and maybe have low risk of bricking LG phones?)
Ophidian_DarkCore said:
the one in that thread should work.
fyi, recoveries, roms, and kernels are specialised software usually only compatible with one model. so no mixxy matchy
i guess using those instructions you could try the img from here http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
Click to expand...
Click to collapse
How would I install the img? I would need to install fastboot, right? Then run fastboot ****.img?
Is fatboot run from adb or from SendCommand.exe?
Thanks again for all your help.
Ophidian_DarkCore said:
yea, just grab a fastboot binary, the lg driver, go into whatever mode in that thread and
Code:
fastboot flash *.img
edit: fastboot is it's own binary. so it's run in a command shell on your pc like adb is.
Click to expand...
Click to collapse
One last question (Need to make sure...): I have fastboot.exe from the SDK tools, so all I need to do is:
1. Connect the USB
2. Boot into Download Mode
3. Run fastboot flash *.img
4. When finished unplug the USB and take the battery out.
5. Then boot back into Download mode or Recovery Mode to get TWRP?
6. Then try to see if I can get ADB to work?
Also, sorry for all the questions: But If I ever needed to, will a factory reset delete TWRP or will I need to flash it again with the Stock recovery?
Thanks for your time. You are awesome.
Hi, thank you for using XDA Assist. Unfortunately there is no device specific forum for your device. I'm going to ask a moderator to move your thread here, http://forum.xda-developers.com/android/help
Solved it.
I used an exploit to access the filesystem and fix the corrupt db.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
I did the same thing, you installed the wrong model FW. just install the base rom and start over.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it.
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen seems also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
how do i restore my us metropcs lg f60 phone back to stock?
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
Help Help
Help anyone, i have LG f60 (390n) running with 5.0.1 lollipop. I wanted to instal custom recovery and install custom rom CM. But i have two problems:
1. If i want to boot to download mode - i have error "SECURE BOOT ERROR" (but it boots up normally, and work normally)
2.If i want to boot to recovery mode - i have error "LOADING KETSTORE FAILED STATUS 5"
Please help.
I am not able to flash it trough LG Flash tool, and i am not able to boot into custom recovery.