Related
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,
another leaked ICS rom from Huawei (leaked here, thx @ th.f from AndroidHilfe.de). Download mirror: http://84.23.79.243/downloads/
There is a .rar file which contains the dload folder and a fastboot flashable boot.img that allows to adb remount and push a su binary.
Have fun!
mblaster
Could you please provide instruction for the boot.img?
lilaliend said:
Could you please provide instruction for the boot.img?
Click to expand...
Click to collapse
You need a working fastboot and adb to fully root the tablet with this. If you don't have it configured yet please search how to do it, there are lots of tutorials for that. Make sure you read them carfully, it's possible to totally screw your tablet if something goes wrong.
1) Boot into fastboot mode (hold vol- while booting the tablet) -> Screen says Fastboot bla bla...
2) fastboot flash boot B010SP03-rootboot.img
3) fastboot reboot
4) adb remount
5) adb push su /system/xbin/su
6) adb shell chmod 6755 /system/xbin/su
7) Install Superuser from Play Store
8) ???
9) Profit!
You will find the su binary in the download folder from my first link in a few minutes.
mblaster
Thanks for the files and instructions.
Hey.. so still a newb Droid tablet owner.. I did the 06 and then 08 build update, simply by throwing the dLOAD file in a SD card and rebooting. I assume the same with this build and is it worth it to migrate from 08?
Thanks!
Confirmed by me, working root (Did this tonight and works!):
http://forums.hardwarezone.com.sg/t...pad-3g-7-tablet-now-singapore-3384632-63.html
can anybody please upload a dload folder with root image complete i cant adb because I have no contact with the mediapad in fastboot
Just use the solution above from me. You don't need adb or fastboot!
I couldn't connect with adb either. So i went looking for another solution.
Good luck!
Eek
eekbb said:
Just use the solution above from me. You don't need adb or fastboot!
I couldn't connect with adb either. So i went looking for another solution.
Good luck!
Eek
Click to expand...
Click to collapse
I cant make that work either, if I exchange the boot.img I get FAIL on the mediapad when flashing so If any1 have a working dload with the rooted img without the games I would be happy.
stinger32 said:
I cant make that work either, if I exchange the boot.img I get FAIL on the mediapad when flashing so If any1 have a working dload with the rooted img without the games I would be happy.
Click to expand...
Click to collapse
Do you still need it? If so I will put it online for you.
Recently I rooted and changed my vold.fstab in a hope of bigger phone storage and then all I got after reboot is a logo.
I using Philips w6610.
I have original vold.fstab file
My phone rooted, and have recovery
My phone don't have usb debug
I tried to make an update.zip but maybe I did not know how to do it right
Now I can't not do anything and through the search on google nothing can help too.
Thank in advance
Update, The update.zip always endup with installation aborted . adb shell commend end up with closed line
Pls helppppppppp ( I just used my phone for 2 weeks
OMG nobody care!
The only two things that pop to mind, are an update.zip (like you already tried) or trying to access 'adb shell' in recovery. Though in the last case you probably need to mount stuff manually, or via the UI of the recovery to get to the vold.fstab file and revert it back.
Can you flash your firmware
The only two things that pop to mind, are an update.zip (like you already tried) or trying to access 'adb shell' in recovery. Though in the last case you probably need to mount stuff manually, or via the UI of the recovery to get to the vold.fstab file and revert it back.
Click to expand...
Click to collapse
Update.zip will be aborted in the first step. I got an installation aborted everytime I update via sdcard.
I also tried adb shell and get command: closed . adb sideload update.zip return same thing with update via sdcard
Can you flash your firmware
Click to expand...
Click to collapse
I really don't know how to flash it right way.
I got and cook ROM from a russian forum for my phone. Only tried to update through sdcard and adb sideload
I am able to get into fastboot but I can not do anything with it!
Is there any methods I can do ?
I have Huawei P6,
It stop booting at logo MIUI (so not possible to use IHM root file manager).
I would like to push a file from my PC to the device (Huawei P6 U06) using ADB Shell in recovery mode.
Push file to device mains push file to /system of device.
Does someone has steps guide or tools to do this?
LikeM8 said:
I have Huawei P6,
It stop booting at logo MIUI (so not possible to use IHM root file manager).
I would like to push a file from my PC to the device (Huawei P6 U06) using ADB Shell in recovery mode.
Does someone has steps guide or tools to do this?
Click to expand...
Click to collapse
Which custom recovery and version do you have installed? I would recommend taking a look at this guide here and following it up through step 10. Let me know if you still have questions.
shimp208 said:
Which custom recovery and version do you have installed? I would recommend taking a look at this guide here and following it up through step 10. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks Shimp for your time.
custom recovery is TWRP v2.6.3.3
The goal is to remove TWRP recovery by a stock one to perform an update with dload/UPDATE.APP from SDCARD.
To do this I would like to copy the file recovery-from-boot.p file in /system device to remove TWRP when boot to recovery mode.
As I said, the phone stope to boot at MIUI logo (error from TWRP E: unable to mount '/cache').
Sideload failed!
LikeM8 said:
Thanks Shimp for your time.
custom recovery is TWRP v2.6.3.3
The goal is to remove TWRP recovery by a stock one to perform an update with dload/UPDATE.APP from SDCARD.
To do this I would like to copy the file recovery-from-boot.p file in /system device to remove TWRP when boot to recovery mode.
As I said, the phone stope to boot at MIUI logo (error from TWRP E: unable to mount '/cache').
Sideload failed!
Click to expand...
Click to collapse
I apologize @LikeM8 for the delay in getting back to you somehow this thread got lost in the shuffle. In the guide I linked I would recommend using that to get ADB access in recovery going that way you can copy the file recovery-from-boot.p to your device, don't worry about the sideload part only use it to get ADB access in recovery mode :good:.
shimp208 said:
I apologize @LikeM8 for the delay in getting back to you somehow this thread got lost in the shuffle. In the guide I linked I would recommend using that to get ADB access in recovery going that way you can copy the file recovery-from-boot.p to your device, don't worry about the sideload part only use it to get ADB access in recovery mode :good:.
Click to expand...
Click to collapse
No problem @shimp208 thanks for your reply. Where I have to copy recovery-from-boot.p ? Where I could be find the stock file for my Huawei P6 U06? Regards!
LikeM8 said:
No problem @shimp208 thanks for your reply. Where I have to copy recovery-from-boot.p ? Where I could be find the stock file for my Huawei P6 U06? Regards!
Click to expand...
Click to collapse
You can get the stock recovery for your device from this thread here, also you won't even need to use recovery-from-boot.p as you can boot your device into fastboot mode to flash the stock recovery.
shimp208 said:
You can get the stock recovery for your device from this thread here, also you won't even need to use recovery-from-boot.p as you can boot your device into fastboot mode to flash the stock recovery.
Click to expand...
Click to collapse
Thanks for the link @shimp208, but when I flash these stock recovery from fastboot, I still again TWRP 2.6.3.3!!! Help please!!!
I thought I broke my maghine and order new one. Recovery SDcsrd works
LikeM8 said:
Thanks for the link @shimp208, but when I flash these stock recovery from fastboot, I still again TWRP 2.6.3.3!!! Help please!!!
Click to expand...
Click to collapse
Hello again @LikeM8 sorry again for the delay caused by my final exams (still in progress for the next two weeks), you can get the stock ROM for your device here in the index thread from the stock rom you can pull recovery-from-boot.p and attempt to install the stock recovery.
shimp208 said:
Hello again @LikeM8 sorry again for the delay caused by my final exams (still in progress for the next two weeks), you can get the stock ROM for your device here in the index thread from the stock rom you can pull recovery-from-boot.p and attempt to install the stock recovery.
Click to expand...
Click to collapse
Thanks @shimp208...pull recovery-from-boot.p from stock ROM??? Did you mean, I have to pull recovery-from-boot.p fill using adb (recovery mode)?
LikeM8 said:
Thanks @shimp208...pull recovery-from-boot.p from stock ROM??? Did you mean, I have to pull recovery-from-boot.p fill using adb (recovery mode)?
Click to expand...
Click to collapse
What I meant was put the stock ROM on your computer unpack and it and extract the from it then push recovery-from-boot.p from your computer to your phone, then re-flash stock recovery.
shimp208 said:
What I meant was put the stock ROM on your computer unpack and it and extract the from it then push recovery-from-boot.p from your computer to your phone, then re-flash stock recovery.
Click to expand...
Click to collapse
Ok @Shimp2008, I try and lets you know. Thanks for your time!
shimp208 said:
What I meant was put the stock ROM on your computer unpack and it and extract the from it then push recovery-from-boot.p from your computer to your phone, then re-flash stock recovery.
Click to expand...
Click to collapse
hello @shimp208, stock ROM I find in the page are dload/UPDATE.APP form, not zip file to unpack.
I have yet recovery-from-boot.p file. When from recovery and adb shell I put it on /system, after reboot, the recovery-from-boot.p file was been delete by the device???
What I did wrong or I have to perform to keep recovery-from-boot.p file in /system directory after reboot?
PS: Before operation, I perform "mount -o remount,rw /system"
LikeM8 said:
hello @shimp208, stock ROM I find in the page are dload/UPDATE.APP form, not zip file to unpack.
I have yet recovery-from-boot.p file. When from recovery and adb shell I put it on /system, after reboot, the recovery-from-boot.p file was been delete by the device???
What I did wrong or I have to perform to keep recovery-from-boot.p file in /system directory after reboot?
PS: Before operation, I perform "mount -o remount,rw /system"
Click to expand...
Click to collapse
TWRP may be overwriting the file on it's own, another possibility would be to follow the directions for the stock recovery flashing i linked to earlier and seeing if only fastboot booting the stock recovery image will let you re-flash the stock ROM.
Hi,
this is a small tutorial to show you how to flash the recovery, also eRecovery, via command line / adb shell within Android.
Flashify and other apps never worked for me, so I used commands to flash it without the need of fastboot.
It's a small tutorial for those who never worked with commands like this.
Please notify me if something went wrong or if you found any other issues.
I wanted to make a small script but I stopped it because of the lack of available commands in Android.
DISCLAIMER:
Read this tutorial first.
Never flash custom recovery to eRecovery.
Never flash recoveries from different devices.
Don't try to flash other partitions with this commands if you don't want to risk a brick.
Requirements:
- Oreo / EMUI 8 installed, Nougat hast other partition names. Pie isn't supported by me until final release.
- working root access
- terminal emulator app (I recommend Termius, it's easy to use and has nice features, it's free to use)
> or a PC, and USB cable and working ADB, also USB Debugging enabled in developer settings
- recovery img files on your phone, I recommend it to put them into your user root /data/media/0/ (internal memory)
NOTE: All commands are case sensitive!
Now open your terminal app or open the adb shell.
Type following command to enable root access:
Code:
su
SuperSU will ask you for root access, grant it.
Following command is needed to figure out, which type of memory your phone has:
Code:
ls /dev/block/platform
There are two possible outputs:
If you've a device with the faster UFS memory, it's ff3b0000.ufs, if eMMC it's hi_mci.0.
From now I'll write MEMORY instead of ff3b0000.ufs or hi_mci.0.
For flashing the recovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/RECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/recovery_ramdisk_a
Example: dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
The output should look like this:
Code:
65536+0 records in
65536+0 records out
33554432 bytes transferred in 0.247 secs (135847902 bytes/sec)
If not, check your command and file paths.
For flashin the eRecovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/ERECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/erecovery_ramdisk_a
Example: dd if=/data/media/0/ERECOVERY_RAMDI.IMG of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
IMPORTANT NOTE: DO NOT INSTALL TWRP IN THIS! Flash only stock eRecovery!
The dd command won't give you any progress output, so be a bit patient. It should be done in a few second, but don't close the terminal app or connection before you got any output.
Unix systems like Android will give an output if something went wrong, always.
I use this to flash new TWRP versions or to flash stock recovery before I update.
If you recently updated your phone, you still need to flash via fastboot, because you lost root during the update.
The dd commands also work with fastboot. Mostly you'll use "fastboot flash recovery_ramdisk", but if you need to flash eRecovery, you can use the dd command.
23. February 2019:
Pie should also work, but you have to remove the "_a" after the partition name.
Example:
dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk
Please report if it's working or not.
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
fr3ker said:
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Jannomag said:
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Click to expand...
Click to collapse
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
M1chiel said:
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
Click to expand...
Click to collapse
Also my thought, I wanted to add this to the requirements when I created this post but apparently I forgot this. Now it's added as first point.
Hi.
I have a hard bricked p10. When I connect to laptop it's says USB SER. It doesn't not turn on I can't access recovery with power + vol. I can't get into fastboot. Anyway I can access fastboot to flash kernel and erecovery?
Jannomag said:
I use this to flash new TWRP versions or to flash stock recovery before I update.
Click to expand...
Click to collapse
Is it mandatory to flash stock recovery before update? Is it applies only to ota update or ff method?
Yes, FF or OTA are using stock recovery to flash the update. With TWRP it won't work.
Updated?
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Blümchen Blau said:
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Click to expand...
Click to collapse
WTF....Why didn't I notice this terrible mistake! Thank you for reading my post completely, you're 100% correct, I'll correct this directly after I submit this post.
Huawei did also a small change at naming the recovery partition, which I'll update, too.
I had also the problem that I wasn't able to boot into fastboot by command before I fried my phone - I couldn't figure out the reason for this.
Again, thank you!
Jannomag said:
Again, thank you!
Click to expand...
Click to collapse
Your'e welcome! I did update now, but didn't need your (correct ) way to fastboot, because the method described by borgerapper did the trick for me to get into fastboot and flash the needed original recovery.
Thanks anyway!