Develop Bugs

Sprint is rolling out the first over-the-air HTC Hero update

The rumors are true, Sprint is indeed rolling out an OTA update for the HTC Hero, which I can say because my HTC Hero is being updated as I type up this post. I am not sure of the roll out process or how long this will take for everyone to get notified. Instead I choose to take the shortcut route and went into settings to do a manual check. (Settings -> About Phone -> System Updates -> Firmware Update)
That said the update was ready and waiting.
“A firmware update for your HERO200 is available. Would you like to download?”
In total, the update came in at “3748377 byte” and was a relatively quick download even with my poor Sprint data speeds. After the download is complete, you then see the following message;
“The firmware update for your HERO200 is now ready to be installed. Your device will be updated to version 1.56.651.2. You cannot make or receive calls during the installation, even for emergencies. Do you want to install?”
Click OK, and it goes into the reboot and update process. Of course, this part takes a bit longer than the initial download. And thankfully I can live without making or receiving calls during the process — its a perk of working at 5am.
As to what this OTA update corrects, well unfortunately there is no change log. However according to the details coming from others;
It corrects issues with DST
It corrects the battery drain/SMS issue
Fixes some lag that was experience when moving from a home screen to an app
As to what I have seen, honestly nothing yet. But then again I have just updated. That means I will have to keep these items in mind and offer an update later on today. But on a positive note, the RTM app icon that I was complaining about yesterday was still correct, even after the reboot to complete the update process. So maybe it did do something — time will tell.

jasonkwh said:
The rumors are true, Sprint is indeed rolling out an OTA update for the HTC Hero, which I can say because my HTC Hero is being updated as I type up this post. I am not sure of the roll out process or how long this will take for everyone to get notified. Instead I choose to take the shortcut route and went into settings to do a manual check. (Settings -> About Phone -> System Updates -> Firmware Update)
That said the update was ready and waiting.
“A firmware update for your HERO200 is available. Would you like to download?”
In total, the update came in at “3748377 byte” and was a relatively quick download even with my poor Sprint data speeds. After the download is complete, you then see the following message;
“The firmware update for your HERO200 is now ready to be installed. Your device will be updated to version 1.56.651.2. You cannot make or receive calls during the installation, even for emergencies. Do you want to install?”
Click OK, and it goes into the reboot and update process. Of course, this part takes a bit longer than the initial download. And thankfully I can live without making or receiving calls during the process — its a perk of working at 5am.
As to what this OTA update corrects, well unfortunately there is no change log. However according to the details coming from others;
It corrects issues with DST
It corrects the battery drain/SMS issue
Fixes some lag that was experience when moving from a home screen to an app
As to what I have seen, honestly nothing yet. But then again I have just updated. That means I will have to keep these items in mind and offer an update later on today. But on a positive note, the RTM app icon that I was complaining about yesterday was still correct, even after the reboot to complete the update process. So maybe it did do something — time will tell.
Click to expand...
Click to collapse
Do you still have root access? and are you still able to get into Amon-Ra's recovery?

On my Hero, Amon's Recovery is PREVENTING the update. Everytime the phone goes to install the update I get the following:
Welcome
Build : RA-heroc-v1.2.3
Finding update package...
Opening update package...
Verifiying update package...
E:No signature (265 files)
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
I can't seem to find any way to flash back to the standard rom without wiping the entire phone, so I am at a loss here.

zefie said:
On my Hero, Amon's Recovery is PREVENTING the update. Everytime the phone goes to install the update I get the following:
I can't seem to find any way to flash back to the standard rom without wiping the entire phone, so I am at a loss here.
Click to expand...
Click to collapse
Stoopid question, but you're not "trying" to boot into recovery right? It's my understanding that the OTA should just reboot and apply by itself. Does IT boot you into recovery?
If the update is done through the recovery boot, then you should be able to use flashrec to put the backup recovery image on your phone.
Can somebody confirm that the OTA requires the HTC recovery image?

Yeah, it boots you into recovery. Here is the recovery.img from the Sprint RUU. I flashed that and am trying to update now.
EDIT: If you have removed stock apps the update will fail.
Here are the steps to upgrade from a modified STOCK rom
1) Make a nandroid backup
2) RUU (or otherwise flash) the original Sprint ROM
3) Install OTA Update
4) Reboot and wait
5) Re-root and flash amon's recovery (http://forum.xda-developers.com/showthread.php?t=581577)
6) Make another nandroid backup
7) Back up both nandroid backups externally
8) Take the data.img and cache.img from your first nandroid backup, and place them in the latest one, overwriting existing files
9) Edit nandroid.md5 in the latest backup with the hashes for data.img and cache.img from your first
10) Restore your modified nandroid backup
DO NOT REBOOT YET
Note: This segment will differ from specific updates.
In the script file for the update, we notice 3 commands being run on the DATA partition, we must manually execute them.
The commands are:
delete_recursive DATA:dalvik-cache/
delete_recursive DATA:boot-cache/
delete DATA:data/com.smithmicro.DM/libomc.so
So we must execute these manually.
While still in Amon's recovery, connect an adb shell
in the adb shell run the following:
mount /data
rm -r /data/dalvik-cache
rm -r /data/boot-cache
rm /data/data/com.smithmicro.DM/libomc.so
reboot
Wait for the Hero to reboot and rebuild its caches.
With any luck, you will be on the latest update, with all your settings in tact.
Now you are welcome to re-remove the apps you did before, however remember you will need to do this again next time there is an update.
For those like me, who cant get the RUU to work, or you semi-bricked your hero, here is another way:
Run RUU installer
When installer window appears asking you to upgrade your phone, move it out of the way
Open windows Explorer
navigate to "%TEMP%" (without quotes)
Search for "rom.zip"
copy "rom.zip" to your SD Card as "HERCIMG.zip"
restart phone in fastboot mode (power + Volup)
press VolDown to load HBOOT
Wait for it to prompt you to flash.
For the record: "action" = press in trackball
More info here:
Manual RUU Flashing Guide: http://midnightchannel.net/blog/248-htc-hero-semi-bricked-recovery-method.html
Upgrading Modified Stock ROM Guide: http://midnightchannel.net/blog/249...e-to-your-modified-stock-rom-1-56-651-2.html/

A couple of notes & observations that may help others. I rooted my phone and installed the Amon-RA recovery image, so when I tried the OTA update it failed, as zefie has noted.
I rebooted, re-flashed with the RUU recovery image and tried the OTA update again, but this time when I went to upgrade the firmware it said there was no update available for me (although my firmware version still said 1.29.whatever).
So, I went in as root and removed the /cache/fumo/update.pkg file, then rebooted the phone and tried the OTA update again. This time it worked. So if others get stuck in the same situation, removing that file is a way to force the OTA update to download again. It seems the phone will not check the current firmware version ... it just sees the update package was downloaded and assumes the OTA update was successfully applied, even if it failed. It's also interesting to note that *after* the OTA completes, it still leaves the 3.7MB file sitting there wasting space on your internal NAND storage. It also "phones home" with some data about the upgrade ... not sure what it's reporting to the mothership, but that was interesting to see. Caveat utilitor.
One other important observation: keeping root access after this update will require you to re-root your phone and reset the setuid bit on /system/bin/su, even if you apply it on top of an already-rooted device (like I did). When it installs, it resets the suid permissions on all files (& presumably all directories) under /system, at least, so typing "su" after you reboot does nothing special (you still have the '$', not '#', prompt). I had no problem re-running the "asroot2" exploit to get my root shell back.

the_deacon said:
A couple of notes & observations that may help others. I rooted my phone and installed the Amon-RA recovery image, so when I tried the OTA update it failed, as zefie has noted.
I rebooted, re-flashed with the RUU recovery image and tried the OTA update again, but this time when I went to upgrade the firmware it said there was no update available for me (although my firmware version still said 1.29.whatever).
So, I went in as root and removed the /cache/fumo/update.pkg file, then rebooted the phone and tried the OTA update again. This time it worked. So if others get stuck in the same situation, removing that file is a way to force the OTA update to download again. It seems the phone will not check the current firmware version ... it just sees the update package was downloaded and assumes the OTA update was successfully applied, even if it failed. It's also interesting to note that *after* the OTA completes, it still leaves the 3.7MB file sitting there wasting space on your internal NAND storage. It also "phones home" with some data about the upgrade ... not sure what it's reporting to the mothership, but that was interesting to see. Caveat utilitor.
One other important observation: keeping root access after this update will require you to re-root your phone and reset the setuid bit on /system/bin/su, even if you apply it on top of an already-rooted device (like I did). When it installs, it resets the suid permissions on all files (& presumably all directories) under /system, at least, so typing "su" after you reboot does nothing special (you still have the '$', not '#', prompt). I had no problem re-running the "asroot2" exploit to get my root shell back.
Click to expand...
Click to collapse
Wow. Lots of great information. Thanks for the hard work... One other thing that you can do to keep root after updates is to copy su to some other directory and name it something else. Place that file in a directory that should never be touched by an update.

the_deacon said:
A couple of notes & observations that may help others. I rooted my phone and installed the Amon-RA recovery image, so when I tried the OTA update it failed, as zefie has noted.
I rebooted, re-flashed with the RUU recovery image and tried the OTA update again, but this time when I went to upgrade the firmware it said there was no update available for me (although my firmware version still said 1.29.whatever).
So, I went in as root and removed the /cache/fumo/update.pkg file, then rebooted the phone and tried the OTA update again. This time it worked. So if others get stuck in the same situation, removing that file is a way to force the OTA update to download again. It seems the phone will not check the current firmware version ... it just sees the update package was downloaded and assumes the OTA update was successfully applied, even if it failed. It's also interesting to note that *after* the OTA completes, it still leaves the 3.7MB file sitting there wasting space on your internal NAND storage. It also "phones home" with some data about the upgrade ... not sure what it's reporting to the mothership, but that was interesting to see. Caveat utilitor.
One other important observation: keeping root access after this update will require you to re-root your phone and reset the setuid bit on /system/bin/su, even if you apply it on top of an already-rooted device (like I did). When it installs, it resets the suid permissions on all files (& presumably all directories) under /system, at least, so typing "su" after you reboot does nothing special (you still have the '$', not '#', prompt). I had no problem re-running the "asroot2" exploit to get my root shell back.
Click to expand...
Click to collapse
Sorry, I did forget to mention that you need to check for firmware update twice after reflashing to RUU. Don't need to hack in though.
I updated the blog post to reflect this.

Are you using Windows Vista? I am using XP so when I enter %temp% do I click "Run" under the start bar?
zefie said:
Yeah, it boots you into recovery. Here is the recovery.img from the Sprint RUU. I flashed that and am trying to update now.
EDIT: If you have removed stock apps the update will fail.
Here are the steps to upgrade from a modified STOCK rom
1) Make a nandroid backup
2) RUU (or otherwise flash) the original Sprint ROM
3) Install OTA Update
4) Reboot and wait
5) Re-root and flash amon's recovery (http://forum.xda-developers.com/showthread.php?t=581577)
6) Make another nandroid backup
7) Back up both nandroid backups externally
8) Take the data.img and cache.img from your first nandroid backup, and place them in the latest one, overwriting existing files
9) Edit nandroid.md5 in the latest backup with the hashes for data.img and cache.img from your first
10) Restore your modified nandroid backup
DO NOT REBOOT YET
Note: This segment will differ from specific updates.
In the script file for the update, we notice 3 commands being run on the DATA partition, we must manually execute them.
The commands are:
delete_recursive DATA:dalvik-cache/
delete_recursive DATA:boot-cache/
delete DATA:data/com.smithmicro.DM/libomc.so
So we must execute these manually.
While still in Amon's recovery, connect an adb shell
in the adb shell run the following:
mount /data
rm -r /data/dalvik-cache
rm -r /data/boot-cache
rm /data/data/com.smithmicro.DM/libomc.so
reboot
Wait for the Hero to reboot and rebuild its caches.
With any luck, you will be on the latest update, with all your settings in tact.
Now you are welcome to re-remove the apps you did before, however remember you will need to do this again next time there is an update.
For those like me, who cant get the RUU to work, or you semi-bricked your hero, here is another way:
Run RUU installer
When installer window appears asking you to upgrade your phone, move it out of the way
Open windows Explorer
navigate to "%TEMP%" (without quotes)
Search for "rom.zip"
copy "rom.zip" to your SD Card as "HERCIMG.zip"
restart phone in fastboot mode (power + Volup)
press VolDown to load HBOOT
Wait for it to prompt you to flash.
For the record: "action" = press in trackball
More info here:
Manual RUU Flashing Guide: http://midnightchannel.net/blog/248-htc-hero-semi-bricked-recovery-method.html
Upgrading Modified Stock ROM Guide: http://midnightchannel.net/blog/249...e-to-your-modified-stock-rom-1-56-651-2.html/
Click to expand...
Click to collapse

jmanley69 said:
Wow. Lots of great information. Thanks for the hard work... One other thing that you can do to keep root after updates is to copy su to some other directory and name it something else. Place that file in a directory that should never be touched by an update.
Click to expand...
Click to collapse
No problem, I'm just hopeful my experiences will help someone down the road doing a Google search or browsing the forums, who is experiencing similar symptoms.
I like your idea, and I had actually tried it (sorta). I copied the 'su' binary to 'xx.bak' with the same permissions (in the same directory). It still got reset to non-suid permissions by the upgrade. I'm guessing they wrote a script to recursively search all directories under /system/ and remove suid from all files it finds, then put it back on just the ones they want to keep. That's how I would do it. Since /system/ is the only filesystem that is allowed to have suid binaries, the 'su' (regardless of name), has to be somewhere under that directory structure, so hiding it from a recursive search would be difficult. (And you can't put it somewhere else, say /sdcard/, then copy it back under /system/ after rebooting, since you won't be root after the update - doh!)

the_deacon said:
No problem, I'm just hopeful my experiences will help someone down the road doing a Google search or browsing the forums, who is experiencing similar symptoms.
I like your idea, and I had actually tried it (sorta). I copied the 'su' binary to 'xx.bak' with the same permissions (in the same directory). It still got reset to non-suid permissions by the upgrade. I'm guessing they wrote a script to recursively search all directories under /system/ and remove suid from all files it finds, then put it back on just the ones they want to keep. That's how I would do it. Since /system/ is the only filesystem that is allowed to have suid binaries, the 'su' (regardless of name), has to be somewhere under that directory structure, so hiding it from a recursive search would be difficult. (And you can't put it somewhere else, say /sdcard/, then copy it back under /system/ after rebooting, since you won't be root after the update - doh!)
Click to expand...
Click to collapse
From the script:
set_perm_recursive 0 0 0755 0644 SYSTEM:
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
set_perm 0 3003 06755 SYSTEM:bin/ip
set_perm 0 3003 02755 SYSTEM:bin/netcfg
set_perm 0 3004 02755 SYSTEM:bin/ping
set_perm 0 2000 06755 SYSTEM:bin/reboot
set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluez
set_perm 0 0 0755 SYSTEM:etc/bluez
set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf
set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks
set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh
set_perm_recursive 0 0 0755 0644 SYSTEM:
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
set_perm 0 3003 06755 SYSTEM:bin/ip
set_perm 0 3003 02755 SYSTEM:bin/netcfg
set_perm 0 3004 02755 SYSTEM:bin/ping
set_perm 0 2000 06755 SYSTEM:bin/reboot
set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluez
set_perm 0 0 0755 SYSTEM:etc/bluez
set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf
set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks
set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh
So yeah, basically you need to move your su off of the /system/ partition. You could back it up on /data.

justin24 said:
Are you using Windows Vista? I am using XP so when I enter %temp% do I click "Run" under the start bar?
Click to expand...
Click to collapse
I'm on 7, but %TEMP% should work in Start > Run, or any open Explorer window

Full root for A10x and A5xx ICS. Simple method.

Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
How to:
1. The tablet should be already upgraded to stock ICS for A100/A101 (or stock ICS A500/A501/A510 for other tablets).
2. Download this archive on the computer. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programs:
SuperUser APK
Titanium Backup
At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
Change:
The error of final check of receiving root is corrected (The messaging that "root" isn't received, though it was not so)
Support of A510 of tablets is improved
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
List of rooting versions:
New - ICS_rooting_A10x_A5xx.zip
Old - ICS_rooting.zip
PS: I understand English rather badly, but I'll try to help, if it is necessary.
PS2: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
PS3: This method does not work on the A511 tablets

Just tried this and it works perfectly as described; tested on Linux Mint 12, the su binary is even the latest, superuser is required from the market to grant permissions of course.
Thanks for this post ZeroNull.
I couldn't try Crossix's great .bat as we're a Windows free household, and the Missus keeps forgetting her laptop! This filled the gap nicely, will try to see what I can do with memory management now.
Thanks!

Always please!
Not at all
I was afraid that something was translated incorrectly. But now everything is all right!

Thank you very much worked perfect could not be easier I now have rw permission

Thank you, thank you, thank you, thank you. I can now load Siraxis on here and start gaming via PS3 wireless controller.
Not only is this the best 7incher on the market, you can get it for under $300

ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
How to:
1. The tablet should be already upgraded to ICS for A100.
2. Download this archive. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer.
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programms:
SuperUser APK
Titanium Backup
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
PS: I understand English rather badly, but I'll try to help, if it is necessary.
PS2: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
Click to expand...
Click to collapse
is this a permanent root? or temporary? it give r/w permission on system folder?

spino1970 said:
is this a permanent root? or temporary? it give r/w permission on system folder?
Click to expand...
Click to collapse
Permanent

spino1970 said:
is this a permanent root? or temporary? it give r/w permission on system folder?
Click to expand...
Click to collapse
Definitely allows r/w access, done so myself with root explorer, and root has stuck after a reboot.
Sent from my A100 using xda premium

ZeroNull said:
Permanent
Click to expand...
Click to collapse
thanx! what will happen if i'll try this over the crossix one? is it better to wipe the device and start from a clean installation?
And, it already mount r/w or i need to do it manually?
thanx again!

This should be moved in the development section. Thanks gonna try it now.
---------- Post added at 11:09 AM ---------- Previous post was at 10:55 AM ----------
spino1970 said:
thanx! what will happen if i'll try this over the crossix one? is it better to wipe the device and start from a clean installation?
And, it already mount r/w or i need to do it manually?
thanx again!
Click to expand...
Click to collapse
Did this over crossix and worked fine. I can now R/O system folder. Didn't have to wipe.

FINALLY!! A system r/w root that sticks! Outstanding work!

Zeronull, EXCELLENT post! It worked for me.
Your instructions were very understandable.
Thanks again!

I get this error - I had had the partial root before I tried this method.
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
1299 KB/s (839527 bytes in 0.631s)
Unable to chmod /data/local/tools/loop: Operation not permitted
2274 KB/s (37273 bytes in 0.016s)
-
Preparation is finished.
-
Executing of the main script.
/system/bin/sh: /data/local/tools/runit.sh: cannot execute - Permission denied
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.

myprecious27 said:
I get this error - I had had the partial root before I tried this method.
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
1299 KB/s (839527 bytes in 0.631s)
Unable to chmod /data/local/tools/loop: Operation not permitted
2274 KB/s (37273 bytes in 0.016s)
-
Preparation is finished.
-
Executing of the main script.
/system/bin/sh: /data/local/tools/runit.sh: cannot execute - Permission denied
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
Click to expand...
Click to collapse
Can you access /data/local without root on your tab? If so, try deleting this folder and then running the process again, that's all I can think of.

I deleted the folder, but still it didn't work - so I created the folder /data/local/tools in root explorer then it went without a hitch.

myprecious27 said:
I deleted the folder, but still it didn't work - so I created the folder /data/local/tools in root explorer then it went without a hitch.
Click to expand...
Click to collapse
If you have used some other rooting methods, wipe your tablet (for example - flash through recovery) and try my method again.

ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
How to:
1. The tablet should be already upgraded to ICS for A100.
2. Download this archive. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer.
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programms:
SuperUser APK
Titanium Backup
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
PS: I understand English rather badly, but I'll try to help, if it is necessary.
PS2: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
Click to expand...
Click to collapse
Awesome! It all worked! Thanks a bunch!
I did the other root from before, this time I just deleted the folder /data/local/tools and then ran your script. Maybe you should add that to the begining of your script as it will clean everything up from before? Or you could just use a new folder
Either way, THANKS!

OH man thanks, it worked great. I did it right over crossix "double click" root and can now mount system r/w and back to r/o without doing anything else.
Would it be safe now to delete the data/local/rootme folder now that it's not being used as a loop?
Edit: I guess what I'm asking is, what would the clean up process be to clean up other rooting methods?

get root!! thanks a lot.

myprecious27 said:
I get this error - I had had the partial root before I tried this method.
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
1299 KB/s (839527 bytes in 0.631s)
Unable to chmod /data/local/tools/loop: Operation not permitted
2274 KB/s (37273 bytes in 0.016s)
-
Preparation is finished.
-
Executing of the main script.
/system/bin/sh: /data/local/tools/runit.sh: cannot execute - Permission denied
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
Click to expand...
Click to collapse
I got this error too, but when I open superuser it works, mine got rooted..
P.S. I didnt remove superuser before Ive flashed ICS...

[ROOT] Root Archos Stock Firmware 4.1.0 JB !

Hi !
Here you can find the latest updates Archos Gen10 101XS - root version - Archos Firmware 4.1.0 - Jelly Bean !
Install this version only if you have previously installed SDE interface !
Root version is one and the same with official version Archos Firmware 4.1.0 but with root access !
As SDI interface can not install in this latest version of the Archos JB 4.1.0 , you need first to downgrade your device to Officialy Archos Firmware 4.0.26 - Android ICS !
After you install android ICS on your device, only now you can install SDE interface !!!
For install SDE recovery ( for now you can do this only if your device run on android ICS ! ) - please, follow this THREAD !
Downgrade your device to Android ICS - Archos Firmware 4.0.26 :
Download : Officialy Archos Firmware 4.0.26 :
firmware_archos_it4x.aos !
Installation :
connect USB cable ;
go to recovery -> Format System -> Reformat Device... -> I Understand !
copy here ( in the new driver ) firmware_archos_it4x.aos -> ok -> wait to install !
Root version : Android JB -> Archos Firmware 4.1.0 !
Downloads :
please download from here :
archos.ext4
zImage
initramfs.cpio.lzo
Gen10_JB_Root.zip
Installation :
first you need to run on your device Archos Firmware 4.0.26 - root version !
put archos.ext4 in your device in root directory or by adb command : > adb push archos.ext4 /mnt/storage
reboot your device in recovery SDE , navigate to Developer edition Menu -> ( Remove Android Kernel if exist ! ) -> go to Flash Kernel & Initramfs ; now copy here ( in the new driver ) zImage & initramfs.cpio.lzo -> OK !
do not disconnect USB cable - wait to install ( device will reboot after all is done ! )
Now you have the latest version of the ARCHOS device Gen10 -> Android JB ( Firmware 4.1.0 with root access ! ) :good:
To recap :
install ( downgrade ) your device to android ICS - Archos Firmware 4.0.26 ;
install SDE recovery ;
install Archos Firmware 4.1.0 - Android JB - Root version !
regards,
Surdu Petru !

hello
I have a 80 xs, I try to reach the recovery menu, but I don't arrive. I try power + volume - with USB or WITHout. There is nothing to do about it.
Have you got an idea?
I have the form 4.1.0

nico21311 said:
hello
I have a 80 xs, I try to reach the recovery menu, but I don't arrive. I try power + volume - with USB or WITHout. There is nothing to do about it.
Have you got an idea?
I have the form 4.1.0
Click to expand...
Click to collapse
Hi!
First you need to install firmware 4.0.26 ! ( android ICS )
- now , you can enable SDE !!! :good:
To boot in SDE :
1° - connect USB cable , enable USB debugging on Settings, and > adb shell reboot_into recovery
( your device will reboot in SDE menu ! )
2° - power off your device ! ; press & keep volume down and power button , after 2 sec. you can release power button but not volume down -> you will see soon SDE menu ( or Archos Recovery ! )
( ...does not matter if USB cable is connected or not for step 2° ! )

I understood, but I don't have the menu recovery.
I try to launch firmware_archos_it4x.aos but no think. the file is on SDcard ?

nico21311 said:
I understood, but I don't have the menu recovery.
I try to launch firmware_archos_it4x.aos but no think. the file is on SDcard ?
Click to expand...
Click to collapse
Hi !
Just read well my first post ! you have all instructions there !
- also is very easy
If you have not yet instaled SDE menu, you can follow my step 2° to boot in Archos recovery !

where is recovery ?
---------- Post added at 01:05 AM ---------- Previous post was at 12:59 AM ----------
i don't arrive with the hardware. and when I use ADB and the command recovery the device boot and I have the men of android with a computer open in stade of recovery menu

nico21311 said:
where is recovery ?
---------- Post added at 01:05 AM ---------- Previous post was at 12:59 AM ----------
i don't arrive with the hardware. and when I use ADB and the command recovery the device boot and I have the men of android with a computer open in stade of recovery menu
Click to expand...
Click to collapse
You need to use step 2° to boot in Archos recovery - because you have not yet installed SDE recovery !
step 1° is just for SDE enabled !
Can you come in Archos A80XS Recovery ? - following what I told you to do in step 2° above ....

Petru, he is a starter ), he does not understand all the terms
Istalling root by Paul O Brian
adb push 1 /data/local/
adb push 2 /data/local/
adb shell chmod 0755 /data/local/1
adb shell chmod 0755 /data/local/2
adb shell /data/local/1
adb reboot
Wait untill the tablet starts again
adb shell /data/local/2
adb reboot
Wait untill the tablet starts again
Installing SDE
adb push zImage /data/local/tmp
adb push initramfs.cpio.lzo /data/local/tmp
adb push abcbox /data/local/tmp
adb shell chmod 755 /data/local/tmp/abcbox
adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zImage -i /data/local/tmp/initramfs.cpio.lzo
adb reboot
Wait untill the tablet starts again
Copying the Rooted Firmware to Internal Sd Card and aplying it via Recovery Mode. DO NOT DISCONNECT THE TABLET !!!
push archos.ext4 /mnt/storage
adb shell reboot_into recovery
The tablet will reboot in Recovery Mode
Select RECOVERY SYSTEM by using the volume buttons to navigate and the power button to select
Navigate to: Developer Edition Menu/Flash Kernel and Initramfs
Copy from your computer the ZIMAGE and INITRAMFS.CPIO.LZA to the new removable disk.
Wait untill the tablet reboots.
The tablet will enter now in the old ICS firmware, reseting the tablet.
adb shell reboot_into recovery
Select Developer Edition and enjoy your rooted Jelly Bean
This is the detailed way .
Ps: Have you changed something in the last firmware?
Also, encourage the people to use my batch file, it is much easy: D
Did you received back the g9, or a g10 ?

globula_neagra said:
Petru, he is a starter ), he does not understand all the terms
Istalling root by Paul O Brian
adb push 1 /data/local/
adb push 2 /data/local/
adb shell chmod 0755 /data/local/1
adb shell chmod 0755 /data/local/2
adb shell /data/local/1
adb reboot
Wait untill the tablet starts again
adb shell /data/local/2
adb reboot
Wait untill the tablet starts again
Installing SDE
adb push zImage /data/local/tmp
adb push initramfs.cpio.lzo /data/local/tmp
adb push abcbox /data/local/tmp
adb shell chmod 755 /data/local/tmp/abcbox
adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zImage -i /data/local/tmp/initramfs.cpio.lzo
adb reboot
Wait untill the tablet starts again
Copying the Rooted Firmware to Internal Sd Card and aplying it via Recovery Mode. DO NOT DISCONNECT THE TABLET !!!
push archos.ext4 /mnt/storage
adb shell reboot_into recovery
The tablet will reboot in Recovery Mode
Select RECOVERY SYSTEM by using the volume buttons to navigate and the power button to select
Navigate to: Developer Edition Menu/Flash Kernel and Initramfs
Copy from your computer the ZIMAGE and INITRAMFS.CPIO.LZA to the new removable disk.
Wait untill the tablet reboots.
The tablet will enter now in the old ICS firmware, reseting the tablet.
adb shell reboot_into recovery
Select Developer Edition and enjoy your rooted Jelly Bean
This is the detailed way .
Click to expand...
Click to collapse
Hi!
Yes you are right....but all this will not work if you are not in android ICS!
because he is already in Android JB - first, he must downgrade to Android ICS -> Archos Firmware 4.0.26 !

Well that is the first step in the end )
I still not found a solution to root in another way this tablet and i am busy testing some stuff with some other 2 tablets
read my ps
edit: i see your signature, seems that you got the g10 )

I think i don't have the menu recovery on my device, is it possible ?
the version of android is 4.1.1 ? and not 4.1.0
version 3.0.8+ ?
Is it normal ?

From jelly bean you cannot reboot using adb shell reboot_into recovery, it is not working
Shut down your tablet, then press the volume key - and the power button in the same time, when you see the first flash of image on your tablet, release the keys, if you get`it right (if you do not get it right, try again), you will see a white menu, with some options, format the tablet, and install the ICS firmware, and then you can use the stuff that is written above by Petru, and me.

globula_neagra said:
Well that is the first step in the end )
I still not found a solution to root in another way this tablet and i am busy testing some stuff with some other 2 tablets
read my ps
edit: i see your signature, seems that you got the g10 )
Click to expand...
Click to collapse
Yes, take a look here !

Nice ), good for you that you got this one, i really like the tablet, but for the future i don`t think they will choose anymore tiomap SOC`s, i have an impression that it will be rockchip new SOC`s 3166, based on a 28 nm global foundries tech, possibly a quad core and maybe with 8 video mali cores
On the g9, it was possible to boot in normal mode (android, not developer) a rooted firmware?

Correct is in the following way : ( otherwise you risk to re-boot the device ! )
Shut down your device !
Press and keep "Volume Down" buttun - ( do not release "Volume Down" ) now just press the "Power" button for a few seconds and release it ! - continue to hold down "Volume Down" button until Archos recovery interface appears :good:

I have a G9 and I made lot of time this process all is ok
But with My 80XS no result the device continus the process and boot normaly
---------- Post added at 01:59 AM ---------- Previous post was at 01:58 AM ----------
Please give what do you think on my version of rom ?

globula_neagra said:
Nice ), good for you that you got this one, i really like the tablet, but for the future i don`t think they will choose anymore tiomap SOC`s, i have an impression that it will be rockchip new SOC`s 3166, based on a 28 nm global foundries tech, possibly a quad core and maybe with 8 video mali cores
On the g9, it was possible to boot in normal mode (android, not developer) a rooted firmware?
Click to expand...
Click to collapse
Also G9 has the same structure as g10 ! - sure , if you not remove "Android Kernel" !

nico21311 said:
I have a G9 and I made lot of time this process all is ok
But with My 80XS no result the device continus the process and boot normaly
---------- Post added at 01:59 AM ---------- Previous post was at 01:58 AM ----------
Please give what do you think on my version of rom ?
Click to expand...
Click to collapse
Ok! so, can you enter in Archos recovery or not ?
Follow this : Shut down your tablet than press and keep "Volume Down" buttun - ( do not release "Volume Down" ) now just press the "Power" button for a few seconds and release it ! - continue to hold down "Volume Down" button until Archos recovery interface appears !
( no matter the version installed in your device ! - your device has recovery interface 100% )
If you fail by pressing "Volume Down" - , please try again with "Volume Up" !!!
if you fail anything , please RESET your device ( press and keep 10 sec. "Power" button ! ) - now just please try again , once with "volume down" and once with "volume up" !
...also you can try :
- open your device -> go to power off menu and check reboot -> after only a few seconds, please hold down and keep "Volume Down ( - ) " button -> your device will boot in Archos recovery !

When i follow tout requirement please find the result
Sent from my HTC HD2 using xda app-developers app

to arrive this result, I hold the volume +. with the volume - the device continue normaly the boot.

[Q] need help rooting telus GS3

Trying to root it to get the hidden basebands so i can use it on wind mobile. I just switched to lnux and I found this video and instruction set on androidrootz "how to root galaxy s3 on max osx/linux/ubuntu [Jelly Bean] US/Canadian" (can't actually post the link because i'm apparently still new)
having some problems, the root isn't taking properly. I keep getting this readout from the console when I try to root the phone.
[email protected] ~ $ cd Desktop
[email protected] ~/Desktop $ cd motochopper
[email protected] ~/Desktop/motochopper $ chmod 755 *
[email protected] ~/Desktop/motochopper $ sudo sh run.sh
[sudo] password for apollo:
[*]
[*] Motochopper: Android root exploit (Linux/OS X version)
[*] v1.1
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well.
[*]
[*] Before continuing, ensure that USB debugging is enabled and that
[*] your phone is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
run.sh: 39: read: Illegal option -n
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
5985 KB/s (1283460 bytes in 0.209s)
[*] Pushing root tools...
6124 KB/s (366952 bytes in 0.058s)
5589 KB/s (1867568 bytes in 0.326s)
5915 KB/s (1578585 bytes in 0.260s)
pkg: /data/local/tmp/Superuser.apk
- waiting for device -
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
run.sh: 83: read: Illegal option -n
everything is fine until that part that I have highlighted in red. suddenly stops and just says failure for no apparent reason. When the phone reboots, I have the superuser app installed but because the phone isnt actually rooted, i can't do anything with the app, just keeps trying to get me to update the su binary (again can't actually do it because the phone is not actually rooted). Anybody know what i can do to make it work properly?
Running telus GS3 32gb with android 4.3
Baseband version
I747MVLUEMK5
Kernel version
3.0.31-2140838
[email protected] #1
Tue Nov 19 19:35:04 KST 2013

This might help: http://autoroot.chainfire.eu/

audit13 said:
This might help: LINK BLOCKED
Click to expand...
Click to collapse
I just read through that page you posted, I do have KNOX on my GS3, and it says that using the CF autoroot on a KNOX device will trip the KNOX void warranty.... is that going to cause a problem with actually rooting the phone or is it just going to void the warranty and they wont cover it if it goes sideways?

Loading any non-Samsung software is going trip the Knox counter so, if you have a warranty on your phone, it may be best that you not flash it.

audit13 said:
Loading any non-Samsung software is going trip the Knox counter so, if you have a warranty on your phone, it may be best that you not flash it.
Click to expand...
Click to collapse
what does that actually do then, tripping the knox counter? does it just disable knox completely? also i've had this phone for over a year now so the warranty is completely gone

capp apollo said:
what does that actually do then, tripping the knox counter? does it just disable knox completely? also i've had this phone for over a year now so the warranty is completely gone
Click to expand...
Click to collapse
Knox is security software that Samsung included with the 4.3 update. It's a method of separating work files from personal files on the phone.
Here's a link to pre-rooted stock ROMs: http://forum.xda-developers.com/showthread.php?t=1739426

audit13 said:
Knox is security software that Samsung included with the 4.3 update. It's a method of separating work files from personal files on the phone.
Here's a link to pre-rooted stock ROMs: http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
if i'm not worried about knox though.... will rooting the phone disable knox somehow (also could disabling knox affect the phone in some way)

capp apollo said:
if i'm not worried about knox though.... will rooting the phone disable knox somehow (also could disabling knox affect the phone in some way)
Click to expand...
Click to collapse
I assume you have no warranty because rooting will void it.
Routing will not disable Knox.
If you have access to a PC, you could load a custom recovery, root from recovery, disable Knox from recovery, and you're good.

just tried the same method from a different source with slightly different method of inputting the commands into the console, here's what it looks like this time
Prometheus apollo # cd Desktop
Prometheus Desktop # cd motochopper
Prometheus motochopper # ./run.sh
[*]
[*] Motochopper: Android root exploit (Linux/OS X version)
[*] v1.1
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well.
[*]
[*] Before continuing, ensure that USB debugging is enabled and that
[*] your phone is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
error: protocol fault (no status)
[*] Device found.
[*] Pushing exploit...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
error: device offline
[*] Pushing root tools...
error: device offline
error: device offline
error: device offline
- waiting for device -
rm failed for /data/local/tmp/Superuser.apk, No such file or directory
[*] Rooting phone...
/system/bin/sh: /data/local/tmp/pwn: not found
[*] Cleaning up...
rm failed for /data/local/tmp/pwn, No such file or directory
rm failed for /data/local/tmp/su, No such file or directory
rm failed for /data/local/tmp/busybox, No such file or directory
[*] Exploit complete. Press enter to reboot and exit.
as you can see, it didn't hang on anything, it actually went through what I'm assuming is the entire process, and it even rebooted my phone for me but when i went in to check titanium backup, it told me that I don't have the root privelages enabled.....

Fire TV 2 - stuck at b/w boot logo after flashing prerooted 5.2.1.0

Hi folks,
I having some problems here while I try to flash the latest prerooted rom from rbox. So here is the situation
FireTV was on Stock Rom 5.0.5.1
- I followed the Guide on aftvnews to install TWRP Recovery link
- everythink looked good, prerooted rom was installed without any errors
- reboot system -> stuck at black&white "amazon" logo
- I noticed that the LED completly turned off after 30 seconds (i guess) so might be looping
- back to twrp I did wipe /cache, then reboot -> same behavior
- tried over adb shell : mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
-> same result
- tried factory reset -> guess what, same as before of course
so what the hell can I do to reset it in some way?
One thing I also noticed is that when I open a local terminal or an adb shell I'm already root. Is this normal for prerooted rom?
And another thing is the supersu binary. I could remember that the bin was installed to /sbin/su ,but this is not the case here.
'which su' gives no result back
'find / -name su' give me /system/xbin/su
Is that the way it should be? I ask because adblink gives me an error when I try to run FS R/W
"root requiered"
Thats explainable cause adblink will run 'su' first.
I would be really happy if someone could give me some advice. I dont know what else I could try

!! Problem solved
It was the god damn HDMI cable -.-
Behind the boot logo it was waiting for paiing the remote
Maybe it could help some of you guys too
Kind regards

Thank you, had the same issue, never would have tried a new cable, as i was getting video from it.