Database Users

Flash recovery image Droid Eris How To

First of all thanks to Amon_RA for this. I had no part in creating this. I am just providing a how to flash it. There may be an eaiser way but this is what worked for me.
First let me say I am on a Mac. If you are on windows the adb commands should work fine but I can't say how to get adb working for you.
1. download flash_image Here Link updated 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download Amon_AR's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
I made an automator script the help all of you having problems getting adb working. Make sure you have the android sdk downloaded and named android-sdk Put it in your home folder and then run this script. Let me know how it works for you.
Disclaimer: I am not responsible for any damage you may do to your phone. I am only providing instructions on what worked for me. This is very beta. Good luck. Enjoy the nandroid goodness.

First link is Dead...........
ooopps Srry my bad, Its up.

You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
adb push flash_image to /system/bin
Click to expand...
Click to collapse
I don't think there's a "to" in that command either. lol

testing567 said:
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
I don't think there's a "to" in that command either. lol
Click to expand...
Click to collapse
Thanks. I don't think the "to" is going to work either. I made the corrections.

Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.

Will this put the regular android on it or keep it the same, sorry just kinda getting started with android

coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
For testing567:
Do all the adb shell commands run as root against the 2.1_root install ... or maybe the above could be simplified even more by just running "adb root" first?
For Austinjs0102 (not a question)
This process only applies (at the moment) to phones with "2.1_root" - there isn't a path at present to go from "2.1_leak" to a rooted phone. Assuming that a way to roll back (or get root) for "2.1_leak" eventually is found, then the answer to your question is this: it is a process to apply a custom recovery partition to the phone that include tools that will allow you to perform complete phone backups and restore operations. This can be critical for devs who are experimenting with writing boot or system partitions to their phones - if something goes wrong with their experiments, they can "boot" their phone into recovery mode and restore back to a working configuration. To reiterate, though: this only applies to phones that are already rooted.
bftb0

Thanks a bunch that helps clear up info.
hopefully the hard working dev's here find a 2.1 leaked fix for us early people, if not then i may need to lose the phone lol.

Austinjs0102 said:
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Click to expand...
Click to collapse
I am in same boat as you...

Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc

DocTauri said:
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
Click to expand...
Click to collapse
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Doc,
I understand exactly what you are getting at... and also think I can explain why it's not easy.
First - what has been discovered so far was not a "root break-in", but rather an engineering ROM with root "built in". It is cryptographically signed so that a production phone will recognize the .zip file as a valid ROM. That first validation step has nothing to do with version numbers.
If the "SPL" on an unrooted phone was doing something as simple as looking at a couple of bytes in the initial file downloaded to the phone, then yes - doing what you suggest would work... just patch a few bytes using a hex editor. Unfortunately, the phone SPL is quite sophisiticated: it verifies the crypto signature on the entire zip file first, unpacks that zip, and then examines the contents of an individual file within the zip archive (and possibly even unpacks one of the YAFFS image files and then looks in a file within the YAFFS image) to read version numbers.
That means that the fundamental issue is the cryptographic signature on the .zip file. If you do anything which breaks step #1, step #2 (version # checks) are never reached. Certainly an individual file could be byte-patched, and then images and zip files could be re-assembled... but you would have no way to sign the zip with HTC's private key. Or you could even attempt to byte-patch the zip file - but then that would break the crypto signature. Either way, the crypto signature on the zip file is no longer valid.
If you have HTC's private RSA key, let us know!
bftb0

bftb0 said:
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
Click to expand...
Click to collapse
I added the reboot because. All I would get is out of memory errors. The reboot fixed that.
e.g.
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)

northmendo -
That first link (that you corrected) now points to the recovery image, not "flash_image".
Note that the "flash_image" executable which Amon_RA originally included with his first recovery (.zip) is identical to the /system/bin/flash_image binary which ships on the Eris with 1.5 (1.17.605.1); the md5sum signature (of both of those files) is:
16559f2c27d08ff1ddfcaca05fbf10fb flash_image
That's also the same md5 signature as the "flash_image" file which was posted to dl.dropbox.
I don't have 2.1_root installed on my phone, but if the same binary is already on the phone after installing the 2.1_root ROM, there's no need to include those steps in your instructions. It is also possible that even if the "2.1_root" version of /system/bin/flash_image is different, it would also work.
Note that the only reason I bring it up is that your instructions might be (a) unnecessary, and (b) are encouraging folks to overwrite a binary that is already on the phone. No harm (but unneeded) if it is the same, and unknown harm if it is different.
Also (while I'm at it)
901167f6b5541b488c8e0404bceb0631 recovery-RA-eris-v1.6.2.img ***
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
[Edit]***Wow, my post was obsolete the moment I posted it - don't know how I missed Amon_RA's announcement post. Note that there appears to be several versions of "v1.6.2" floating around now - make sure to check his post if you want the most recent.

bftb0 said:
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
Click to expand...
Click to collapse
I will keep the link updated to the newest version here. Also I tried the quicker method without success. I will try it again when I get home from work.
Thanks

bftb0 said:
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Click to expand...
Click to collapse
Sorry, didn't mean to. Understood on the explaination. I didn't realize it was a different rom image, I thought the key had been broken, allowing someone to resign a modified image.
Thanks!
Doc

I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?

sdk issues for flashing recovery...
Hey guys,
Im a noob but here's whats going on, Ive downloaded sdk extracted it to my c drive, ive downloaded all the required packages reccomended in the forum, Ive up dated my driver and still my machine doesnt recognize my phone...
Ive also extracted the recovery image to my tools directory and added the the path in enviromentals...
So at this point Im stuck as to how to get my pc (xp) phone and sdk in sync in order to get this recovery image working...So any advice would be highly appreciated. Thanks in advance.
Chris

Spencer_Moore said:
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
Click to expand...
Click to collapse
You could try this.
If you have your phone pluged in and type in to the terminal
adb reboot recovery [hit enter]
After you phone reboots it should come up with text options to do back-ups and restores. Do you get any of that?

Anyone know the key combo to get into recovery without adb?

having issues getting adb
got the command prompts working in xp, however while trying the methods here in the forum i am getting adb not foud errors. Any suggestions?

Problem with recovery.img on nandoid backup.

If I am posting in the wrong place, please advise me on where to post to get help.
I have followed the directions on this forum to root my Sprint Hero Phones with the stock 2.1 using this topic //forum.xda-developers.com/showthread.php?t=694572 (sorry it isn't a link, i do not have permission to post links). I have rooted three Hero's thus far. The first two gave me zero problem. The third one will not do a Nandroid backup. When ran connected USB i can view the log which I will post below. Yes the SD card is empty 2GB free, I tried to reformat the card. It is a problem while backing up the recovery. IF i run it with switches nandroid-mobile.sh -b --recovery then it runs without error but there is no recovery.img file. Therefore, it is obvious it cannot created a recovery.img and that is the part that fails. Can anyone help me with this issue. I am new to root so I don't even know what recovery.img is for? Is that the recovery menu I am in when trying to make this backup?
LOG:
Create Nandroid backup?
Press HOME to confirm,
any other key to abort.
Performing backup : .
nandroid-mobile v2.2.1
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default: Accepting default.
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
..Dumping boot to /sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/boot.img.....done
.mtd: ECC errors (0 soft, 1 hard) at 0x00380000
error reading recovery: No such file or directory
.Dumping recovery to /sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/recovery.img....mtd: ECC errors (0 soft, 1 hard) at 0x00380000
.error reading recovery: No space left on device
md5sum: can't open '/sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/recovery.img': No such file or directory
mtd: ECC errors (0 soft, 1 hard) at 0x00380000
.error reading recovery: No space left on device
md5sum: can't open '/sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/recovery.img': No such file or directory
.mtd: ECC errors (0 soft, 1 hard) at 0x00380000
error reading recovery: No space left on device
md5sum: can't open '/sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/recovery.img': No such file or directory
.mtd: ECC errors (0 soft, 1 hard) at 0x00380000
.error reading recovery: No space left on device
md5sum: can't open '/sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/recovery.img': No such file or directory
.mtd: ECC errors (0 soft, 1 hard) at 0x00380000
error reading recovery: No space left on device
md5sum: can't open '/sdcard/nandroid/HT01NHF07567/BCDMRS-20100701-0617/recovery.img': No such file or directory
Fatal error while trying to dump recovery, aborting.
Error : Run 'nandroid-mobile.sh' via adb!

Nandroid is corrupted. Try a different one. There is a thread for that error. Just search for it

Per the instruction, i have tried to copy unrevoked to to the sd card again and then run it by "sh /sdcard/unrevoked" shouldn't that copy nandroid to my phone again? If not, does anyone have instructions on how to get a new copy of non corrupted nandroid to my phone?

in the previous post i actually ment to say i ran "flash_image recovery /sdcard/recovery.img"
Shouldn't that recopy nandroid to my phone?

gupter said:
in the previous post i actually ment to say i ran "flash_image recovery /sdcard/recovery.img"
Shouldn't that recopy nandroid to my phone?
Click to expand...
Click to collapse
Yes it will. But you may need to re-download recovery though. Either re-download the same one from the server/website and push it to your sd card again, or download an entirely new/different recovery image. There are several recovery versions floating around this forum.

I'm starting to think there is something wrong with this particular phone. Here is what I got when i tried RA-heroc-1.6.2
/ # flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-pink.img
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-pink.img
flashing recovery from /sdcard/recovery-RA-heroc-v1.6.2-pink.img
mtd: erase failure at 0x00380000 (Input/output error)
mtd: erase failure at 0x00380000 (Input/output error)
mtd: skipping write block at 0x00380000
and now it will not boot into recovery.
So, I flashed back to 1.5.2 and it worked...
tried 1.6.2 again and got the same error.
is there a problem with 0x00380000? that is what is wrong with the nandoid backup and now i can't reflash a recovery. Is this fixable?
Any suggestions?

Nope, sorry, that is a little over my head.
The only other suggestion I would have is completely start over. Try to run the RUU again and restore your phone to regular stock 2.1. Then re-download all the root tools all over again....Android SDK, HTC Sync, and the .zip that contains the rest of the files....and start the whole root process over from square one. Maybe you've already tried that with no success, but that's about the only other thing I can think to suggest.

Thanks for all your help so far. Now I hope some else on here might have an idea. My phone works great and this is my wife's phone....she is none too happy at the moment!

The recovery partition isn't writable. Either you are not properly rooted, or you need to mount it as writable. If you adb shell, then su, do you get the # prompt? If not, then you are not rooted. If so, exit the shell, type adb remount, and then try flashing
Sent from my Hero CDMA using XDA App

I have a # sign at the prompt.
I can mount as writable and successfully flash 1.5.2.
But nandroid reports an error at 0x00380000
Therefore, I decided to flash 1.6.2 to see if this fixes my problem. Instead i get an error about 0x00380000 when trying to reflash. When I try to boot recovery afterwards, it just hangs on the "HTC" screen
So, I boot back into regular OS and use adb to mount writable and then reflash the recovery back to 1.5.2. That happens with success. But of course if I try to run nandroid it reports an error again at 0x00380000.
So i think I am rooted and I think I am mounting it correctly. But evidently i can't read or write into memory 0x00380000. But I don't know what that means or how to fix.
Any additional suggestions would be much appreciated. Thanks in advance.

Full root for A50x ICS 4.0.3[LEAK]. Simple method.

Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
For A500 and A501 ICS[LEAK] firmware.
How to:
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/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
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).
PS: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
PS2: Sorry for the Russian language in the old executable file, the archive has been confused

ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
For firmware:
Acer_AV041_A500_0.019.00_WW_GEN1
Acer_AV041_A500_0.014.00_WW_GEN1
Acer_AV041_A500_0.009.00_WW_GEN1
How to:
1. The tablet should be already upgraded to ICS 4.0.3[LEAK] for A500.
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: Command "mount -o remount,rw /system" for directory /system (partition) - works perfectly!
Click to expand...
Click to collapse
I wrapped something like this up into a GUI ages ago Perhaps I'll make a linux & mac one at some point too. My GUI installs Superuser and allows the user to install Trebuchet, FaceLock (currently buggy) and other tweaks: http://forum.xda-developers.com/showthread.php?t=1520469

blackthund3r said:
I wrapped something like this up into a GUI ages ago Perhaps I'll make a linux & mac one at some point too. My GUI installs Superuser and allows the user to install Trebuchet, FaceLock (currently buggy) and other tweaks: http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
Ok. Read:
blackthund3r said:
exodusevil said:
You are wellcome! And if possible help me grow here in XDA using "Thanks button" (it's free lol).
Well, about the root is the same here, I can see superuser and su, and can go to shell and call #
But, when I try (for example) create a directory inside system the message "ready only" appear.
But it's my firts time trying to use root. Any help will be very glad!
Regards,
Click to expand...
Click to collapse
Simply fire up ICS Root and click "Remount /system rw" In the "Remount Tools" menu
Once you get the success message, feel free to unplug your tablet and play around with the system folder as you see fit
Click to expand...
Click to collapse
My method work "as it should".

ZeroNull said:
Ok. Read:
My method work "as it should".
Click to expand...
Click to collapse
How exactly?! Surely you'd need a patched kernel for that. The bash scripts in the zip file are incredibly complicated

Aw com'on. One of you guys install the full 500 ICS, and see if this works!
Then see if you can push a recovery image.

blackthund3r said:
How exactly?! Surely you'd need a patched kernel for that. The bash scripts in the zip file are incredibly complicated
Click to expand...
Click to collapse
Are you absolutely sure?

I just flash my Acer A500 with Acer_AV041_A500_0.019.00_WW_GEN1
This method works with my. I can use titanium backup and superuser. Thank you!
But I don't know how to test push a recovery image.
below is my way to root.
I use windows Vista.
1. On a tablet: "Settings" -> "Development" -> "USB debugging" switch on.
2. Сonnect the tablet to the computer.
3. Unpack the files. then put ICS_rooting folder in c:\ (I try unpack in other place not work)
4. then run runit-win.bat by run as adminstrator.
Done

This seemed to work for me on Acer_AV041_A500_0.009.00_WW_GEN1
Thanks a lot.

I have installed Acer_AV041_A500_0.019.00_WW_GEN1 and aquired root using this method.
I will try to push CWM or RA recovery.
The root access works perfectly. I just deinstalled all acer bloatware and other stuff.
Edit:
The strange part was, I could not get the ADB interface working on my laptop. When I switched my Acer from MTP (Media Device) to PTP (Camera device), found in storage settings, the ADB interface showed up in my device list under Windows 7. Then after a driver install, it worked perfectly.
When I switch back to MTP, the ADB interface disappears again.

Ping192 said:
I have installed Acer_AV041_A500_0.019.00_WW_GEN1 and aquired root using this method.
I will try to push CWM or RA recovery.
The root access works perfectly. I just deinstalled all acer bloatware and other stuff.
Edit:
The strange part was, I could not get the ADB interface working on my laptop. When I switched my Acer from MTP (Media Device) to PTP (Camera device), found in storage settings, the ADB interface showed up in my device list under Windows 7. Then after a driver install, it worked perfectly.
When I switch back to MTP, the ADB interface disappears again.
Click to expand...
Click to collapse
Maybe a reboot on the win system?

Moscow Desire said:
Maybe a reboot on the win system?
Click to expand...
Click to collapse
Hehe. I tried several windows installations. I think something is wrong with my acer. Like this, I have several strange things, like never get a fast fix on GPS. Whatever fix or GPS.conf I use... But it makes it challenging to het it working again

Pushing a custom recovery fails atm. I even get an error flashing the unlocked bootloader.bin
Code:
Loading bootloader...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0xxxxxxxxxxxxxxxxxxxx
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 1192188/1192188 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader status: success (code: 0) message: flags: 1073840124
[COLOR="Red"]bootloader failed NvError 0x0
command failure: bootloader download failed[/COLOR]
All other nvflash commands fail afterwards.
After this command, the tablet enters "Entering OS download mode" with the acer logo in the middle.

Just update to Acer_AV041_A500_0.022.00_WW_GEN1.
After update Lost root. But use this method then got root again.
Thank you.

It didnt work for my acer, I meant it wasnt fully rooted. I saw superuser but when in Acer Receovery Installer, it says that Bootloader version 0.03.11-ISC is locked or something. Now I cant install any other rom as it got stucked at boot screen (receovery mode) with a message "Recovery verified failed". Anyone, please help me.
I need to use USB 3G on this tablet with this ISC or please help me downgrade to 3.2.1.
Many thanks

Jamesbond007vn said:
It didnt work for my acer, I meant it wasnt fully rooted. I saw superuser but when in Acer Receovery Installer, it says that Bootloader version 0.03.11-ISC is locked or something. Now I cant install any other rom as it got stucked at boot screen (receovery mode) with a message "Recovery verified failed". Anyone, please help me.
I need to use USB 3G on this tablet with this ISC or please help me downgrade to 3.2.1.
Many thanks
Click to expand...
Click to collapse
Take a look at my A500 APX Flash Tool with the patched bootloader, recovery and kernel package. That will get you ClockworkMod. To downgrade take a look at Timmydean's 3.2.1 downgrade package

Hi, will it work on ACER_AV041_A500_1.031.00_WW_GEN1 ?

CaH9 said:
Hi, will it work on ACER_AV041_A500_1.031.00_WW_GEN1 ?
Click to expand...
Click to collapse
+1 to this anyone try it yet and is their a simple way to unroot ics I need to send unit to Acer but its damaged so till its fixed I want root back!
Sent from my A500 using Tapatalk 2

I can confirm, that it works with ACER_AV041_A500_1.031.00_WW_GEN1 too

+1

How about the unroot part of things anyway to do that? For peeps that need warranty related things to be done?
Thanks
Sent from my A500 using Tapatalk 2

[Q] How to root official ICS ?

I know that someone probably asked this but can someone tell me how to root official ICS ?
and i prefer if u have tried it already.
Or at least tell me if it can be rooted at all
Thank you.

Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469

japinder said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
That one worked for me.

yes
Yes I tried it the tab just froze and i restarted it but nothing happened

I used Civato's guide in his flexreaper rom thread, and it worked just fine. Follow all instructions to the letter.

japinder said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
Worked for me with official update.

worked
At the first time i have done something wrong so it didn't work but now that i have done it right it worked thanks alot.

Can you unroot it the same way?

speeddaddy said:
Can you unroot it the same way?
Click to expand...
Click to collapse
2nd.... this would be good to know...

If you got stok ICS running and you got the unlocked booltoader and custom recovery running you can flash the patched boot.img (kernels from Flexreaper thread) for ICS bootloader users , they give you full root without any other proces except installing superuser app. No need to use the easy root tool then.
If you want to go back flash the stock boot.img back or restore it from a nandroid backup , remove the super user app and you are root less.

japinder said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=1520469
Click to expand...
Click to collapse
everything works... but in the end I get:
./root.sh: line 282: syntax error: unexpected end of file
when I try again I get:
Is your device listed? (y/n) y
[: 144: y: unexpected operator
[+] Uploading exploit
1020 KB/s (37273 bytes in 0.035s)
[+] Uploading busybox
1296 KB/s (821340 bytes in 0.618s)
[+] Setting permissions
[+] Creating directories
[+] Uploading files...
[: 164: ==: unexpected operator
[: 173: 0: unexpected operator
[: 178: 0: unexpected operator
[: 183: 0: unexpected operator
[: 188: 0: unexpected operator
[: 193: 0: unexpected operator
./root.sh: 281: Syntax error: end of file unexpected (expecting "fi")

Android root fail - LG H440n Spirit 4G

Hi,
rooting my LG H440n Spirit 4G phone (Lolipop 5.0.1) has failed at the moment when "Firmware Update" notification showed up on the mobile phone screen (after rooting had started and rebooted once). It says on the phone screen that I should not unplug USB connection to my phone. But since rooting failed what should I do now?
Closing down command line with LG Root Script running did not stop Firmware Update and it is still displayed on my phone.
Is it safe to disconnect usb right now from my phone and try rooting my phone again?
Thank you very much for any advise and support.

cbx44 said:
Hi,
rooting my LG H440n Spirit 4G phone (Lolipop 5.0.1) has failed at the moment when "Firmware Update" notification showed up on the mobile phone screen (after rooting had started and rebooted once). It says on the phone screen that I should not unplug USB connection to my phone. But since rooting failed what should I do now?
Closing down command line with LG Root Script running did not stop Firmware Update and it is still displayed on my phone.
Is it safe to disconnect usb right now from my phone and try rooting my phone again?
Thank you very much for any advise and support.
Click to expand...
Click to collapse
I have the same problem I tried one click root 1.3 and the old script 1.2 android 5.0.1 v10f-EUR-XX. HELP US!

Updated to V10j-214-03 and cannot root
Hello.
Last Friday 23/10/2015 I updated my phone to V10j-214-03 and cannot root it again.
Anyone has updated and rooted this version?
Thank you very much!

Hello. I tried to see if we could use the Low Effort Root on our device. I made some progress, but I am unable to finish what I started because I am stuck[ somewhere.
What I did:
1. Extract the v10h kdz.
2. Get the v10h system.img and the file "PrimaryGPT_0.bin" from the extracted files.
3. Inject root into the v10h system.img: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
3. Rename the "PrimaryGPT_0.bin" into "gpt.img". Then go to ubuntu, open a terminal and run: "# sudo gdisk /path/of/gpt.img"
This gives us the partition info for our device: http://pastebin.com/u9maAAdm
This will help us determine the bs, seek and count when we will use the "Send_Command.exe" to push the v10h system to our device.
4. Based on @autoprime 's help, we have to do some calculations. http://pastebin.com/brcXBpja
[I think that he made a mistake though (missed to multiply by 512 on count). This seems more correct to me: http://pastebin.com/tHUbicR8 )
5. After calculating bs, seek and count, we are supposed to run the Low Effort Root procedure for our device.
But, after running the dd command, a "#" comes immediately, which means that something is going wrong. The "#" should take some time to appear, meaning that the copy is in progress. I couldn't identify what I am doing wrong, so I publish my effort, because maybe someone has more knowledge and may be able to make it work! @midzan21 maybe?
Autoprime, thanks for your help and guidance through irc.
Original Low Effort Root thread: http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765

polfrank said:
Hello. I tried to see if we could use the Low Effort Root on our device. I made some progress, but I am unable to finish what I started because I am stuck[ somewhere.
What I did:
1. Extract the v10h kdz.
2. Get the v10h system.img and the file "PrimaryGPT_0.bin" from the extracted files.
3. Inject root into the v10h system.img: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
3. Rename the "PrimaryGPT_0.bin" into "gpt.img". Then go to ubuntu, open a terminal and run: "# sudo gdisk /path/of/gpt.img"
This gives us the partition info for our device: http://pastebin.com/u9maAAdm
This will help us determine the bs, seek and count when we will use the "Send_Command.exe" to push the v10h system to our device.
4. Based on @autoprime 's help, we have to do some calculations. http://pastebin.com/brcXBpja
[I think that he made a mistake though (missed to multiply by 512 on count). This seems more correct to me: http://pastebin.com/tHUbicR8 )
5. After calculating bs, seek and count, we are supposed to run the Low Effort Root procedure for our device.
But, after running the dd command, a "#" comes immediately, which means that something is going wrong. The "#" should take some time to appear, meaning that the copy is in progress. I couldn't identify what I am doing wrong, so I publish my effort, because maybe someone has more knowledge and may be able to make it work! @midzan21 maybe?
Autoprime, thanks for your help and guidance through irc.
Click to expand...
Click to collapse
Well that what you try to did we got for v10a ROM via Universal LG Root for Lollipop. There is something that you can look about commands. Unfortienatly I can't try anything for now, because I need fully working phone and fully working Arch Linux VM for some networking testings.

midzan21 said:
Well that what you try to did we got for v10a ROM via Universal LG Root for Lollipop. There is something that you can look about commands. Unfortienatly I can't try anything for now, because I need fully working phone and fully working Arch Linux VM for some networking testings.
Click to expand...
Click to collapse
I think it's not the same. With Universal tool we ran a script that was stored on internal SD and this script pushed SuperSU.apk su.bin etc to the system. Now, we replace the whole System.img with a rooted one, and I think this is the point of Low Effort Root.

polfrank said:
I think it's not the same. With Universal tool we ran a script that was stored on internal SD and this script pushed SuperSU.apk su.bin etc to the system. Now, we replace the whole System.img with a rooted one, and I think this is the point of Low Effort Root.
Click to expand...
Click to collapse
so here are some of calculations which I did on my Windows ... I think that somewhere calculation for count is weird because it get into floating data point (decimal numbers)
skip/seek = 51008
count = 314530.125
bs = 8192 (used that as default)
edit: calculated using this calculations for count
[(end sector - start sector +1)*Logical sector size] / bs
Logical sector size iz 512 b

midzan21 said:
so here are some of calculations which I did on my Windows ... I think that somewhere calculation for count is weird because it get into floating data point (decimal numbers)
skip/seek = 51008
count = 314530.125
bs = 8192 (used that as default)
Click to expand...
Click to collapse
Aha, I noticed this and I set the bs to 1024. Then, I made the calculations and they seemed normal. But I 'm not sure if changing the bs would mess up things. The thing is that, whatever I used as numbers, the command wouldn't run.

I mean like how will ur calculations help us to root our phones? Is there a way to root my LG spirit?

JJolii said:
I mean like how will ur calculations help us to root our phones? Is there a way to root my LG spirit?
Click to expand...
Click to collapse
They can help us write a dd command correctly, so that we can send a rooted system.img in the correct partition of our device. So basically, if it worked, we would have had root on v10h now. But as I said, I am missing something.

polfrank said:
They can help us write a dd command correctly, so that we can send a rooted system.img in the correct partition of our device. So basically, if it worked, we would have had root on v10h now. But as I said, I am missing something.
Click to expand...
Click to collapse
Ive got v10f-eur-xx
I've tried SRSroot v5.1.
20:02:34 [+] Testing exploit: root8 (please wait..)
20:02:35 [+] Remounting /system Filesystem as R/W..
20:02:35 [+] Installing SU Binary...
20:02:35 [+] Installing SuperUser APK...
20:02:35 [+] Remounting /system Filesystem as R/O..
20:02:42 [+] Rooting Complete !
After restart theres not SU apk and I checked if my phone is rooted by Root checker basic and it says its not rooted. Im so frustrated in rooting my phone.. Im out of solutions how to root that piece of ****.

JJolii said:
Ive got v10f-eur-xx
I've tried SRSroot v5.1.
20:02:34 [+] Testing exploit: root8 (please wait..)
20:02:35 [+] Remounting /system Filesystem as R/W..
20:02:35 [+] Installing SU Binary...
20:02:35 [+] Installing SuperUser APK...
20:02:35 [+] Remounting /system Filesystem as R/O..
20:02:42 [+] Rooting Complete !
After restart theres not SU apk and I checked if my phone is rooted by Root checker basic and it says its not rooted. Im so frustrated in rooting my phone.. Im out of solutions how to root that piece of ****.
Click to expand...
Click to collapse
Have you tried kingroot?

polfrank said:
Have you tried kingroot?
Click to expand...
Click to collapse
Yes I did, Pc version and android app version, none of them worked.

Well, just go back to v10e-EUR-xx with the LG Flash Tool and root it with Kingroot. Worked for me.
Not mentioning the amount of hair I pulled out trying to root v10f...

Tomo123 said:
Well, just go back to v10e-EUR-xx with the LG Flash Tool and root it with Kingroot. Worked for me.
Not mentioning the amount of hair I pulled out trying to root v10f...
Click to expand...
Click to collapse
Just CSE flashed v10c and rooted with kingroot

Tomo123 said:
Well, just go back to v10e-EUR-xx with the LG Flash Tool and root it with Kingroot. Worked for me.
Not mentioning the amount of hair I pulled out trying to root v10f...
Click to expand...
Click to collapse
can u help me/guide me through Skype or Teamviewer? Please.

k got v10e-eur-xx rom and tried to root with kingoroot and oneclickroot 1.3 still doesn't root. What could be the problem?

JJolii said:
k got v10e-eur-xx rom and tried to root with kingoroot and oneclickroot 1.3 still doesn't root. What could be the problem?
Click to expand...
Click to collapse
Which version of kingroot are you using?

polfrank said:
Which version of kingroot are you using?
Click to expand...
Click to collapse
BETA : 2.5 android app

JJolii said:
BETA : 2.5 android app
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/devdb/project/dl/?id=14576
Click Direct Download.