attached is a semi-working recovery, you can flash it with "fastboot flash recovery recovery.img".
update: the recovery can flash boot.img's too, if the custom rom uses "dd" instead of "write_raw_image" to flash the boot.img. i hope mike updates his rom
don't use anything except for "install from sdcard"
i take no responibility for any harm to your device or data
it's basicaly a repacked cwm recovery combined with the stock 1.26 recovery kernel/ramdisk with modifications to init.rc
it is intented for developers wanting to toy around with custom roms, until someone makes a real recovery
no support nor updates will be made for this
is it tested or not yet.
I've tested it
ok thanks, since currently there is no other option to unlock bootloader other than htcdev & lack of RUU sources is too risky to flash custom recovery at this point. so technically it will skip zip package signature check? so we can start working on working custom rom.
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
looks nice!
could you maybe share your knowledge about creating this recovery? i'm trying the same for the one s but can't get it packed together correctly...
blubbers said:
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
Click to expand...
Click to collapse
Understand. My concern is no RUU for my device available yet & im afraid to use from other region stock rom Thanks for ur effort.
Do I have to unlock my phone to install this recovery?
moom999 said:
Do I have to unlock my phone to install this recovery?
Click to expand...
Click to collapse
yes, there are only 2 ways of installing a recovery.
fastboot and adb
fastboot requires you to unlock in order to "fastboot flash recovery"
and in order to possibly do it through adb you need root and in order to get root at the minute you need to be able to flash an insecure boot image through fastboot, which again, you need to unlock in order to "fastboot flash boot"
Hi blubbers,
There is a guy on general thread who wants to dump a developer phone. It's s4 not tegra but might help.
http://forum.xda-developers.com/showthread.php?p=24496390
sent from my HTC one X using tapatalk
Related
Hi, here is the situation. I got one half-broken Desire.
Fully formatted, s-off,cwm 5.0.2.0 with broken volume up and down keys.
So, when I get into the bootloader I can't get into the recovery to flash zip.
Anyone has some rooted image with boot.img, system.img data.img so I can flash it via fastboot?
Thanks.
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
byglet said:
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
Click to expand...
Click to collapse
Thanks didn't know that... But pretty much useless since community roms don't contain android-info.txt file and some other related stuff.
However, I've figured out that after flashing boot.img via fastboot, it shows itself up in adb devices command so I managed to get into recovery by adb reboot recovery and flashed.
Hi, tried to install a 4.4 ROM but it failed and then went downhill. Does anyone have the latest image file for the bootloader? Now I am soft bricked trying to go back to stock but all I can find are the old bootloaders and they do not work with the kitkat image file from google. Thanks for the help!
http://forum.xda-developers.com/showthread.php?t=2383146
See post#2
I flashed it from recovery.
hyperxguy said:
http://forum.xda-developers.com/showthread.php?t=2383146
See post#2
I flashed it from recovery.
Click to expand...
Click to collapse
Hi, thanks for that but I already have it. The thing is it's a .zip i need the .img and inside that zip there are multiple files i don't exactly know which one is the bootloader.
Thanks!
th3xeroeagle said:
Hi, tried to install a 4.4 ROM but it failed and then went downhill. Does anyone have the latest image file for the bootloader? Now I am soft bricked trying to go back to stock but all I can find are the old bootloaders and they do not work with the kitkat image file from google. Thanks for the help!
Click to expand...
Click to collapse
You can find many of the kernels/recoveries/bootloaders in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2534698
The problem is it might not get you to where you want to be.
What exactly are you calling a "brick"?
If you have a bootloader issue, you won't even see the Google during boot. It is rare to be bricked in that way.
You are probably stuck on the X or bouncing balls animation.
You can get out of that by going to recovery and performing wipe data factory reset.
If you are stuck at "Google", then you need to reflash the factory image (you can choose the nowipe option and possibly keep your user data)
sfhub said:
You can find many of the kernels/recoveries/bootloaders in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2534698
The problem is it might not get you to where you want to be.
What exactly are you calling a "brick"?
If you have a bootloader issue, you won't even see the Google during boot. It is rare to be bricked in that way.
You are probably stuck on the X or bouncing balls animation.
You can get out of that by going to recovery and performing wipe data factory reset.
If you are stuck at "Google", then you need to reflash the factory image (you can choose the nowipe option and possibly keep your user data)
Click to expand...
Click to collapse
hey, thanks for the reply. I'm trying to get my tablet to kitkat with the stock image from google. but I hear that with kitkat there is a new bootloader so I want to update that through fastboot (my device is recognized so I call it a soft boot) but the problem is when I erase the boot and reflash the boot.img and try to flash the new .img it doesn't load up. im using these commands
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash boot
fastboot flash recovery
fastboot flash system
fastboot reboot-bootloader
my current bootloader version says FLO 4.01 not sure how to update it.
th3xeroeagle said:
hey, thanks for the reply. I'm trying to get my tablet to kitkat with the stock image from google. but I hear that with kitkat there is a new bootloader so I want to update that through fastboot (my device is recognized so I call it a soft boot) but the problem is when I erase the boot and reflash the boot.img and try to flash the new .img it doesn't load up. im using these commands
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash boot
fastboot flash recovery
fastboot flash system
fastboot reboot-bootloader
my current bootloader version says FLO 4.01 not sure how to update it.
Click to expand...
Click to collapse
4.01 is the bootloader that came with kitkat.
you can't just say
fastboot flash boot
you need to say
fastboot flash boot boot.img
and have the boot.img in place.
I suggest you just follow the instructions in this post:
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
Use the nowipe option and you should be able to keep your user data unless you erased or messed it up earlier.
sfhub said:
4.01 is the bootloader that came with kitkat.
you can't just say
fastboot flash boot
you need to say
fastboot flash boot boot.img
and have the boot.img in place.
I suggest you just follow the instructions in this post:
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
Use the nowipe option and you should be able to keep your user data unless you erased or messed it up earlier.
Click to expand...
Click to collapse
AH! It was in the general section, I looked everywhere in the development sections. Thank you very much!
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
**edit: what....? never had to use that command before, but thanks a lot Entropy512 **
So this means, every time you update ota from baidu now, you have to unlock bootloader, first, then fastboot twrp, then install gapps + super su, phyy :silly:
spoonymoon said:
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-1.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
Click to expand...
Click to collapse
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Entropy512 said:
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Click to expand...
Click to collapse
Oem unlock don't make any difference, still locked, wont flash twrp, even it claims both oem unlock and flashing twrp.img went ok....but still stock recovery!?
They must have made some partition changes in 35, because when flashing through twrp, it gives two errors can't wipe data , but it don't give any flashing fail error, then when booting up it fc setup and won't continue , then booting into recovery again it's stock! ! Then flashing 35 through stock recovery, there's no errors and system boots up!
As said don't flash 35 you'll regret it
Think 34 is also similar in what you described.
To Entropy512......
What do you think will happen if we delete the new ´recovery dir (just including install_recovery.sh file) completly and replaced boot image from older ota version´s ? eks. from 33 which is not locked, i know because i flashed it and all ok and then put in 35 ota??
would it work you think? i dont have the guts to try...hehe
thx in advance
Try this. Download tantrums recovery flasher, unpack the zip on your computer, then in the "rec" folder go to "oppo" and extract the one other than "stock"
Now copy the modded recovery into the folder which contains fastboot.exe
And then "fastboot boot recovery.img"
the modded recovery will boot and then via that recovery, flash the tantrums recovery flasher. Aroma installer will start, then select twrp and flash what ever you like!
Basically I'm stuck. Phone won't boot.....I can get to the white screen/bootloader.
It had a custom recovery on it (TWRP) so wonuldn't update....I followed a video to put the stock recovery on it.
I've downloaded a few files, stock recovery, stock boot etc.....put on sd card but no joy. It says reading sd card.....then "no image or wrong image"
In all honesty i'm so lost...Has anyone ever over come this???
vtec3483 said:
Basically I'm stuck. Phone won't boot.....I can get to the white screen/bootloader.
It had a custom recovery on it (TWRP) so wonuldn't update....I followed a video to put the stock recovery on it.
I've downloaded a few files, stock recovery, stock boot etc.....put on sd card but no joy. It says reading sd card.....then "no image or wrong image"
In all honesty i'm so lost...Has anyone ever over come this???
Click to expand...
Click to collapse
What are you trying to do in the first place?
If you're going to flash a custom rom, place the rom in your SD card or internal storage, do a full wipe and install the rom.
If you're returning to stock for OTA, restore your nandroid backup (system, kernel etc) after which flash your stock recovery and do a reset from settings than search for OTA.
If you can't boot into recovery, flash the latest TWRP on your phone through fastboot. Use the commands: fastboot flash boot boot.img
Bobbi lim said:
What are you trying to do in the first place?
If you're going to flash a custom rom, place the rom in your SD card or internal storage, do a full wipe and install the rom.
If you're returning to stock for OTA, restore your nandroid backup (system, kernel etc) after which flash your stock recovery and do a reset from settings than search for OTA.
If you can't boot into recovery, flash the latest TWRP on your phone through fastboot. Use the commands: fastboot flash boot boot.img
Click to expand...
Click to collapse
dude i know you are trying to help but please get your facts right and complete !
flashing a recovery image to the boot partition is not helping !!!
it's : fastboot flash recovery recovery.img
Mr Hofs said:
dude i know you are trying to help but please get your facts right and complete !
flashing a recovery image to the boot partition is not helping !!!
it's : fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Bobbi lim said:
What are you trying to do in the first place?
If you're going to flash a custom rom, place the rom in your SD card or internal storage, do a full wipe and install the rom.
If you're returning to stock for OTA, restore your nandroid backup (system, kernel etc) after which flash your stock recovery and do a reset from settings than search for OTA.
If you can't boot into recovery, flash the latest TWRP on your phone through fastboot. Use the commands: fastboot flash boot boot.img
Click to expand...
Click to collapse
It had a custom recovery on it Team win recovery project......which was stopping the software from updating.
So tried to put the stock recovery back on it.
At the moment I don't think its corresponding properly with my laptop......in the fastboot menu it does come up "fastboot usb" Drivers are installed too
But when trying to send it commands via command prompt it keeps saying device not found.
I'm wondering if it has deleted to operating system , as on the fastboot menu next to " OS - it says nothing "
Sorry for being brief....this is the first time i've ever come across all this stuff
[Please help]Bootloop, adb "unauthorized, fastboot flash not working, CWN not working
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
i have the same problem
jules.renz said:
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
Click to expand...
Click to collapse
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
majeida said:
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
Click to expand...
Click to collapse
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
sorry for the misunderstanding
jules.renz said:
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
Click to expand...
Click to collapse
sorry i have the same problem .
I'm using FML-AOSP-5.0-20141207-maguro and CWM V6.0.5.1 on a rooted Maguro.
Your personal data includes what?? Apps or photos and videos?
varadparulekarofficial said:
Your personal data includes what?? Apps or photos and videos?
Click to expand...
Click to collapse
yes
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
ashclepdia said:
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
Click to expand...
Click to collapse
I used this method
*I boot into costum temporary recovery "TWRP 2.8.3.0" Then I tried erasing and reflashing "bootloader", "radio", "boot" and new "system" through recovery All finished successfully according to TWRP but a reboot showed the system in the same state as before