Related
Hello,
Here i will give you a quick guide for HTC Hero to flash recovery image, root and flash custom rom and radio update.
1st download this package:
http://www.mediafire.com/?znq5hwjmldk
Or here
http://www.2shared.com/file/9305692/347b5ebf/sdk.html
Unzip it on c:\ so you have c:\sdk
In there you have 2 folders tools and usb driver for x86.
Connect your hero switch on to a usb and point to /sdk/usb drivers/x86 to install drivers
Download this rom:
http://content.modaco.net/hero/2.9-update-hero-modacocustomrom-core-signed.zip
And this Radio:
ftp://xda:[email protected]_6.35.08.22-signed.zip
copy them to sd card and rename rom image update.zip and radio to radio.zip
Now turn off hero and then press back+power to enter bootloader.
connect hero to usb port and let it install drivers or point to usb drivers/x86 folder again.
After done installing follow this commands to have root and recovery image to phone.
click start->run in open: write cmd
then cd\
cd sdk
cd tools
Copy paste this:
1. fastboot boot recovery.img
2. adb shell mount /sdcard
3. adb shell push recovery.img /sdcard/recovery.img
4. adb shell flash_image recovery /sdcard/recovery.img
5. adb shell mount /system
6. adb push su /system/bin/
7. adb shell chmod 4755 /system/bin/su
8. adb push Superuser.apk /system/app/
9. adb shell reboot
Let it reboot, then power off and press home+power and keep pressing home button until you see recovery image.
then you pick radio image radio.zip to flash, let it flash and will return to recovery then you can flash update.zip but before flash update.zip is recommended to wipe.
This is a collection of other tutorials so give credit to others not me.
thanks
The problem is that this works only on older versions of the Hero firmware. Newer versions are patched to not allow unsigned images to be fastbooted.
Soaa- you can use the GoldCard method to install an older ROM.
I know that. I did that.
But my point is this guide is outdated.
I think this guide is same as one Rooting HTC Hero ....success
Sorry to ask on many topics but I don't understand why we should "flash" the RADIO and SPL...What is "RADIO" and "SPL" ? What is the risk of flashing RADIO and SPL ?
Also why some ROMs need to flash RADIO and SPL ?
Thanks,
omokas
You need to worry about those things once decided to root or unroot.
HTC or your middle supplier will never ask you to do that. Because official Rom update will update everything.
I did updated with the latest European WWE update that updated my Build Number to 2.73.405.5.
Does this means that I can install MoDaCo 2.9 ROM (For Hero) without any risk of need to update Radio and SPL ?
I don't have warranty if I brick it Also yes I am rooted
i have had problems with Rom manager not flashing recovery correct leaving me with no recovery. so i had to manually flash recovery following these steps exact. I have personally bricked 2 ERIS phones lucky me.The first i thoought it was just something i did, lucky i had another to replace it...(the second BRICK eris).
So here is a solution to keep from having a BRICK
USE Amon RA's Recovery PERIOD.
credit to northmendo @droidforums
1. download flash_image Here Updated Link 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_RA'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.
ROM Manager and Clockwork recovery does not work for the Eris.
ROM Manager and Clockwork recovery does not work for the Eris (as far as I know).
Edit: Oops, sorry for the double post.
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
trishuhh said:
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
Click to expand...
Click to collapse
try to flash it from rom manager,(under other recoveries) if Rom manager has worked for you with no problems. if it doesnt work follow instructions as listed in 1st post
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Yeah, use Amon's. It does every job you need, and is 100% stable and reliable.
t2noob said:
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Click to expand...
Click to collapse
yea you beat me too it, , i only used it because i had it for my DROID and thought maybe devs would try to add it to the list on rom manager.
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
jrhoades858 said:
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
Click to expand...
Click to collapse
reboot into recovery and read the bottom
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
I flashed amons ras recovery from my phone it was easier for me I didn't use rom manger or terminal emulater
Sent from my FroyoEris using XDA App
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
tkryan said:
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
Click to expand...
Click to collapse
You do exactly what the first post says
Sent from my Eris
ufccowboyfan said:
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
Click to expand...
Click to collapse
When you are doing this, are you in the correct directory? For example, my SDK is installed in /android , so first I would:
cd /android/tools
then
./adb shell
could someone help me with this. i really need to get the stock recovery image on my eris and im alittle noobie at this stuff. if any one could help id be sooooo happy
I'm not sure how to flash amons on a mac. I know for windows you put the recovery.img in the sdk tools folder, boot into fastboot and type
Fastboot flash recovery recovery.img
To get stock recovery (I assume you want your phone back to stock) then flash the official ruu. Will return your phone to 100% stock. You can find it on a sticky in the Eris general forums I believe.
Sent from my Eris using XDA App
I'm not sure on a mac, but on Windows you put the img in the tools folder of your sdk, boot into fastboot and type in adb:
Fastboot flash recovery recovery.img
To get stock recovery back, simply flash the official ruu found on a sticky in the Eris general forums I believe. Flashing the ruu will unroot your phone.
Sent from my Eris using XDA App
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Slugdoc said:
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Click to expand...
Click to collapse
There is no new version out; the first version (v1.6.2) is the only one that Amon_RA published.
IF there was a new version, you could flash it by using adb with the existing Amon_RA. You don't even need to push a version of "flash_image" to the phone, because it is already in /sbin in Amon_RA recovery. Just get the recovery image to your SD card, start an interactive shell (adb shell), and then
flash_image recovery /sdcard/<wherever-you-put-it>/recovery-RA-eris-v1.6.2.img
Yes, you can "flash a recovery partition by using the recovery" - because when you are interacting with it (the recovery boot), it lives entirely in a ramdisk.
The second easiest way is to have the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash it with fastboot from the PC, as in
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Note that neither of these two methods perform any integrity checks on the recovery image file that the normal "Flash .zip from sdcard" ROM installation method does. Therefore, it is imperative that someone using these methods is extremely diligent in cross-checking image MD5 signatures after it has been transferred to the SD card. Amon_RA also has the "md5sum" utility built into it's shell, BTW.
I mention this last point as a warning to newbs - they seem to routinely corrupt files when they transfer them to the SD card. (I suppose they are not using the "safely remove hardware" controls correctly, or they are getting truncated downloads).
bftb0
hi,my htc got stuck logo.i format my desire z with no backups.i unlocked bootloader with htcdev.com........temp root.....S-on..........nothing flashing any Rom...neither custom roms..Nor default roms.....plzzzz help....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
klassikkamii said:
hi,my htc got stuck logo... ....only fastboot is working....no adb.....plzzzzzzzzzz heellppppppp
Click to expand...
Click to collapse
Hello,
I am not sure If someone can help in this case.
Please provide more information.
* Do you confirm, that you cannot boot in recovery from HBOOT?
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
When only fastboot is working then I only see a little chance for your phone when you have an engineering HBOOT.
Best regards,
Catherall
P.S: Seems like you really tortured you helpless Desire Z
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
More Detail are,
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
emmc-boot
Dec 20,2011,16:21:13
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.i flashed Villision1.0 ,Android_Revolution_HD-4G_7.0.3,C7 succesfully but never start normally just stuck in logo.i use also fastboot flash boot boot.img as well but nothing happened.same stucking.when i use adb commands or adb shell ,getting error device not found.plzz give me back earlier position as company setting it was gingerbread 2.3.3.
i am sorry abount my low english language capabality.
Get your phone back on track with proper unlocking (S-OFF)
klassikkamii said:
thxx for reply......i try to provide in detail.
* Do you confirm, that you cannot boot in recovery from HBOOT?
yes , i can boot in recovery-clockwork-3.0.2.4-vision.
* What is your exact HBOOT version? Do you have an "Engineering HBOOT"?
No i think i am on stock hboot but i dont know indeed.
My Hboot Screen shoes it.
****Unlocked****
Vision pvt ship S-on
HBoot-0.85.0015
Microp-0425
Radio-26.10.04.03_M
Also,should know.i installed Clockwork Recovery.which is working perfectly.when i flash rom it all goes success.but when i reboot with hope ,stuck in logo.
Click to expand...
Click to collapse
Two things are not clear to me:
1) How did you "unlock" you phone, did you use http://htcdev.com/bootloader/ method to get "****Unlocked****" in HBOOT? This is important to know for me.
When you indeed unlocked using http://htcdev.com/bootloader/ method, then you have to install an suitable "boot.img" every time you flash a new ROM.
Otherwise the old boot.img tries to boot the old ROM that was overwritten with the new one you flashed.
2) When you can boot ClockworkMod Recovery then you can connect using adb. Just use adb while booted into your custom recovery.
I really recommend to proper unlock your HTC Desire Z as described in
http://goo.gl/aXNr
The advantage of this method is, that you can flash any custom ROM without the need to flash the kernel of the ROM (boot.img) separately!
ATTENTION: Before doing anything like "fastboot oem lock"
you have to use "misc_version 0.1" and "flashgc". Do not continue without that!
When you do not know how to use that then ask (here or in freenode IRC channel #G2ROOT)!
Then you can go on to downgrade your phone:
[GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
http://forum.xda-developers.com/showthread.php?t=1178912
Please make sure that you follow the steps described under the topic ***If you have used the "official" htcdev.com unlock option***
Then you can gain S-OFF (real unlock) using gfree
If you have questions then come to the awesome freenode IRC channel #G2ROOT.
Best regards,
Catherall
yes i unlocked with htcdev.com,so i will lock it again with "fastboot oem bootlock" command and will try to unlock as your advice.
i am so happy after seeing your advices.and i didn't know that i can use adb shell in recovery.you mean boot in recovery than use adb terminal from pc.ok i check it and try to apply it.and thankyou very much again for your help.
I will tell you results.
Attention
Before using fastboot oem lock make sure that downgrade would work.
Run the commands "misc_version 0.1" and "flashgc" successfully before doing anything like
fastboot oem lock!
Visit freenode IRC channel #G2ROOT
I am not 100% sure what happens on your semi-bricked phone with fastboot oem lock!
Best regards,
Catherall
one more plzz
ok i will make sure but plzzz tell me can i restore officialy stock rom with adb support ( may be with golcard support ) sothat i dont wanna take any risk.no downgrade,no s-off just my previous position.
I went to #G2Root but i didnt understand how talk anybody.i am not familiar on that.again thxx for your attention for me.
P.E : ok i tried adb commands while booted in recovery. adb devices command works and show serial number, but when i command ' adb shell ' got " # " instead " $ " so stuck again need more advice plzzzzzzzzzzzz.how can get " $ "
PLssss Help
i am getting " ~ # " Error in adb shell please helppp....
Options for S-OFF/root or reverting to Stock
Hello klassikkamii,
most custom Recoveries provide root access when you use "adb shell" to connect to them.
So adb shell returns "#" to indicate root access. When you get the prompt "$" then you have access as a user.
I would do the following steps. They allow you to get full S-OFF, Engineering HBOOT and a ROOTed ROM, or if you prefer return to stock ROM.
Returning the latest stock is much easier and safer when you do the following steps to change the internal software version number of the phone an make your SD card a goldcard.
Download misc_version 0.1:
http://forum.xda-developers.com/attachment.php?attachmentid=661216&d=1311237785
Download flashgc:
http://forum.xda-developers.com/attachment.php?attachmentid=819704&d=1324116910
And then use the following procedure to change version number and make a goldcard (as provided by Setherio in his guide [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo:
1) Unzip misc_version_01.zip and flashgc.zip in the platform-tools directory.
2) Run the following commands from you platform-tools directory:
Code:
adb shell mount /data
adb push misc_version /data/local/tmp/misc_version
adb push flashgc /data/local/tmp/flashgc
adb shell chmod 777 /data/local/tmp/*
adb shell
Now you are in the phone shell with root access (indicated by the prompt "#").
Continue with the commands:
Code:
cd /data/local/tmp
./misc_version -s 1.00.000.0
This should return:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Continue to make you SD card a goldcard:
Code:
./flashgc
Note: If you get the following error, please make sure your sdcard is inserted in your phone: Error opening backup file.
Continue with the command
Code:
sync
Double check that you phone's software version number is set to 1.00.000.0 with the command:
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
The first line of the command output must be:
1.00.000.010+0 records in
Exit the phone's shell with
Code:
exit
From here you can get an Engineering HBOOT and a custom, rooted ROM, or revert to a stock ROM. Both ways are about the same effort.
Please post how this worked out for you.
Best regards,
Catherall
still stuck
adb push misc_version /data/local/tmp/misc_version
Getting Error
failed to copy 'misc_version' to /data/loca/tmp/misc_version :Not a directory
As i am already with "~ #" i try direct command :cd /data/local/tmp
Got Error This :/sbin/sh: cd:can't cd to /data/local/tmp
if i use command for sd card,
adb push misc_version /Sdcard/misc_version
it show size of file or push succed but not in local/tmp.
i think if i would get "$" instead " ~#" May be i can do all u advice me.
Better do it interactive
Hello,
there might be several reasons why the command did not work.
Not having "$" is none of them.
Please come to freenode IRC and login to channel #G2ROOT. Ask for Catherall, I should be there for the next hours. When I am not there then check back later.
Best regards,
Catherall
ok i solved all Puzzle.solution was only use " GoldCard Method".i use command mmc2 instead mmc1 and voilaaaaaa i got my CID then everything was eassy.....in the End i really thanks to Catherall,You help me well...your information was helpfulln from your instructions i got my way thanksssss...
Just like title says. I cant access the bootloader or anything else besides fastboot. I just s-offed with the wire trick and it says "locked" at the top. Please help thanks
gearlo said:
Just like title says. I cant access the bootloader or anything else besides fastboot. I just s-offed with the wire trick and it says "locked" at the top. Please help thanks
Click to expand...
Click to collapse
You're at the bootloader right now. Use fastboot to flash the recovery and boot.img you were using before the s-off (controlbear makes a backup of it automatically so look in the folder it's in)
gearlo said:
Just like title says. I cant access the bootloader or anything else besides fastboot. I just s-offed with the wire trick and it says "locked" at the top. Please help thanks
Click to expand...
Click to collapse
I had the same issue. Fixed it using the steps from this page. Step 1 is all I had to do...
http://unlimited.io/juopunutbear-public-beta-0-1/troubleshooting/
ROM/Data Recovery
There are three ways to recover your ROM. Try each until one succeeds.
1. ControlBear -r (This is run with the phone at the JuopunutBear/Arrow screen). If this succeeds recovery is complete otherwise continue to step 2.
2. ControlBear -f (This is run with the phone at the fastboot screen). If this succeeds skip to step 4 otherwise continue to step 3.
3. fastboot flash boot boot_backup.img
4. fastboot flash recovery recovery_backup.img
This is done with the phone in fastboot mode, continue to step 4.
5. Boot the phone to android and install busybox from the market if not already installed.
6. adb push sdcard.img /data/local/tmp/
7. adb shell
8. $ su
9. # busybox dd if=/data/local/tmp/sdcard.img of=/dev/block/mmcblk1 conv=notrunc
10. Reboot the phone.
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
steelforce said:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
Click to expand...
Click to collapse
Id wait until a dev chimes in, but my understanding is that as you can still get into DL mode, ODIN would be your best bet. Id flash one of the all in one ODIN ICS packages that also contain boot loaders (LL6 would be most recent). As a last resort you can also flash the stock .pit file and repartition the whole phone, BUT BE SURE TO BACKUP YOUR EFS FOLDER if possible. I say this as I did not do this and now have a generic IMEI on my phone, hindering some aps from working.
ADB is able to reformat and flash ROM packages as far as i know, though it should be unnecessary as long as you can still use ODIN. The only reason i used ADB was to resurrect a S2 i bought of someone that flashed a ROM from a i9100.
steelforce said:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
Click to expand...
Click to collapse
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
creepyncrawly said:
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
Click to expand...
Click to collapse
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
steelforce said:
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
Click to expand...
Click to collapse
So, home with my phone. When I get into the shell, format isn't a valid command:
Code:
[email protected]:/ $ format
format
/system/bin/sh: format: not found
Trying to su ends up segfaulting, so I don't think it's a permissions issue. Other sources suggest using fastboot, but as I understand it, the i777 doesn't support it.
I'm looking at the mounts - is there documentation on which of the /dev/block/mmcblk0pX partitions map to the mount points? I'm familiar with Linux (at least enough to get me in trouble), but I'm lost on where to go next.
You have to have root access to do the format command. Requires the # prompt, like this:
Code:
adb shell
$ su
# format data
# exit
$ exit
Probably, cache is mounted but system and data are not mounted. It shouldn't make any difference though, if I remember right.
If you can't get the su command to give you the # prompt, then maybe adb is not connected to the daemon correctly?
Edit:
I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try
Code:
adb root
followed by
Code:
adb shell
From reading, it seems some people say both wipe and format commands should work in shell in recovery, but I couldn't get them to work. I would get "/sbin/sh: format: not found" error. So the work around is this:
Code:
adb shell
~ # mount /data
~ # rm -rf /data/*
~ # reboot
This will recursively force the removal of the contents of the data directory. I did not test this, but I did test "rm -rf /cache/*" and successfully removed the contents of the cache directory, so I know it should work.
If your system still doesn't boot, you could wipe cache and system as well as data and then reboot into download mode and flash the full stock tar
Code:
adb shell
~ # mount /data
~ # mount /system
~ # rm -rf /cache/*
~ # rm -rf /data/*
~ # rm -rf /system/*
~ # reboot download
creepyncrawly said:
Edit:
I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try
Code:
adb root
followed by
Code:
adb shell
Click to expand...
Click to collapse
Ugh - adb root fails with the following error:
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds
Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
steelforce said:
Ugh - adb root fails with the following error:
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds
Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
Click to expand...
Click to collapse
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
creepyncrawly said:
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
Click to expand...
Click to collapse
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
steelforce said:
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
Click to expand...
Click to collapse
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
creepyncrawly said:
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
Click to expand...
Click to collapse
I tried both of Entropy512's packages from here. Flashed them and tried to boot, both hung at the Rethink Possible screen. Rebooted into recovery, was able to connect to it via adb - but adb root failed on both.
I'm getting closer and closer to punting and picking up a Nexus 4 after this....
With lineage recovery I do a full wipe like:
Code:
mkfs.ext4 -qFF /dev/block/by-name/userdata
mkfs.ext4 -qFF /dev/block/by-name/cache
mkfs.ext4 -qFF /dev/block/by-name/system