Database Users

Can Not Flash Big Recovery Images (Cm-Amon Ra) Only Jfv1.42

Following the CyanogenMod Full Update Guide, to flash a T-Mobile G1 with the latest CyanogenMod, 4.2.15.1 at the time of this writing, I run into a problem while trying to flash the cm-recovery-1.4.mg.
Basically, when I tried to do: flash_image recovery /sdcard/cm-recovery-1.4.img (or recovery-RA-dream-v1.5.2.img or recovery-RA-dream-v1.6.2.img), I got this error:
mtd: erase failure at 0x003e0000 (Input/output error)
mtd: erase failure at 0x003e0000 (Input/output error)
mtd: skipping write block at 0x003e0000
I even tried (without any luck either):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
If I then turned off the phone, and tried to get into recovery mode, by pressing the Home and Power/End buttons, I got into the rainbow screen, and can not do anything.
By trial and error, I was able to flash a recovery image called recovery_RC30_xda-dev_v1.2.img, with an MD5 of 8d055734022496906244b71f849a6b6d, without errors, so that, when I boot in recovery mode, I get:
Android system recovery utility Build: JFv1.42
ALT+S Apply update.zip
ALT+W Wipe/factory reset.
ALT+B Backup.
ALT+X Console mode.
I was then able to flash the HardSPL, by copying a "Hard SPL zip" file into the SD Card as "update.zip", turning off the phone, starting recovery mode, ALT+S to apply, and then rebooting.
After that, I flashed an Android ROM called JFv1.42_RC33, by copying a "JFv1.42_RC33 zip" file into the SD Card, again as "update.zip", turning off the phone, starting recovery mode, ALT+S to apply, and then rebooting.
While all was functioning fine, I still wanted to install CyanogenMod 4.2.15.1.
The problem is that the Full Update Guide states, after downgrading, rooting, and wiping, there are 3 more steps:
1) flash DRC83_base_defanged.zip
2) flash update-cm-4.2.x-signed.zip
3) flash ota-radio-2_22_19_26I.zip
and between 1, 2, 3, it says "STOP - DO NOT REBOOT YOUR PHONE".
So I took the chance, and did 1, 2, and 3. And after each flash, the recovery tool (JFv1.42) would tell me to reboot, which I did.
Basically, I had to mount the phone, copy the corresponding zip file to SD Card, rename to update.zip, turn off phone, turn on phone in recovery mode, ALT+S to flash the update.zip, reboot, and repeat, with each 3 of the zip files.
At the end, I also did the same with the the SPL_Hard_Update_Signed.zip, as it is a G1.
(Basically i did the wiki article, but substituting the recovery.img with the small one, and by having to copy one "update.zip" at a time, and rebooting)
So, while I now have a fully flashed CyanogenMod 4.2.15.1, there are still a couple of doubts:
1) Why can't i flash bigger Recovery Images? Could it be a bad memory?
2) Is there any other "small" Recovery Image i should try that allows me to select the zip and not reboot?
3) Is there a way to do the flashes using the terminal in recovery mode (ALT+X)?
4) If i want to try again to flash CM or RA, and it fails, can i just go ahead and re-flash the recovery image that i have working, or should i need to re-do all again?
5) If, lets say i want to flash SuperD, and i boot in recovery, and flash it, would it be ok, or i would need to do anything else?
Any other ideas/comments?

yaffs2 needs to be -yaffs2
yes, you just replace it, or rename recovery-RA-dream-v1.5.2.img to recovery.img. Also, v1.6.2 is out.
I've never seen the cat recovery.img > /system/recovery.img
I've never had to do it, but if it says do it - do it.
Are you sure you are holding home power? Seems like you're holding back and power or camera and power. Home and power shouldn't do that. By any means. The most it should do is refuse to boot into recovery and just hang on the G1 screen because you either soft-bricked or flashed the wrong recovery.

I have been doing some tests, so i rewrote the first post.

re-wrote it once more.

Anybody has an idea?

have you tried fastboot ?
fastboot erase recovery
fastboot flash recovery recovery-RA-dream-v1.6.2.img
?

kwanbis said:
1) Why can't i flash bigger Recovery Images? Could it be a bad memory?
2) Is there any other "small" Recovery Image i should try that allows me to select the zip and not reboot?
3) Is there a way to do the flashes using the terminal in recovery mode (ALT+X)?
4) If i want to try again to flash CM or RA, and it fails, can i just go ahead and re-flash the recovery image that i have working, or should i need to re-do all again?
5) If, lets say i want to flash SuperD, and i boot in recovery, and flash it, would it be ok, or i would need to do anything else?
Any other ideas/comments?
Click to expand...
Click to collapse
1/
Dunno, it seems weird, but I would try and erase it in fastboot and then go from their.
2/
I dont know of any, they all float around the same size
3/
If you build a system.img and what not, you could do.
flash_image system system.img | flash_image boot boot.img etc etc from the console.
4/
Its a risk, but flashing the recovery wont effect the install of cyanogen (or whatever custom build of android you have installed), worse case though is losing recovery if you cant put one back on.
5/
It should be ok.
Dont know how good you are with coding etc... but most recovery images have the source code avalable.
You could rip out all the crap you didnt want and shrink its size like that.

vixsandlee said:
1/ Dunno, it seems weird, but I would try and erase it in fastboot and then go from their.
Click to expand...
Click to collapse
You mean to flash a recovery image with fastboot?
vixsandlee said:
2/ I dont know of any, they all float around the same size.
Click to expand...
Click to collapse
The one i have flashed, is about 2M, the ones from CM/AR are about 4MB.
vixsandlee said:
3/ If you build a system.img and what not, you could do.
flash_image system system.img | flash_image boot boot.img etc etc from the console.
Click to expand...
Click to collapse
I have no idea of what you are talking about. (I just got this G1 a week ago.)
vixsandlee said:
4/ Its a risk, but flashing the recovery wont effect the install of cyanogen (or whatever custom build of android you have installed), worse case though is losing recovery if you cant put one back on.
Click to expand...
Click to collapse
So, if i can not flash CM/AR, i can re-flash the one that worked you mean?
vixsandlee said:
Dont know how good you are with coding etc... but most recovery images have the source code available.
Click to expand...
Click to collapse
While I have been programing for more than 20 years, I do not code much in C/C++ which i assume is what this is done in.

kwanbis said:
You mean to flash a recovery image with fastboot?
Click to expand...
Click to collapse
Yes, you can
Code:
fastboot erase recovery
fastboot flash recovery recovery-RA-dream-v1.6.2.img
A few guides saw to follow this step if you have problems flashing a recovery image, but it can be risky of course because it will wipe your now working recovery, so if it then wont let you flash the recovery image you now have you wont have one.
The one i have flashed, is about 2M, the ones from CM/AR are about 4MB.
Click to expand...
Click to collapse
yes I should have said most newer ones
I have no idea of what you are talking about. (I just got this G1 a week ago.)
Click to expand...
Click to collapse
I know that when you compile from source you get boot.img (the boot image) and system.img (the system.img)
you can flash them from the recovery console using the commands
flash_image boot boot.img
flash_image system system.img
etc... if you can find a build that has those images in the update.zip you could flash them manually.
So, if i can not flash CM/AR, i can re-flash the one that worked you mean?
Click to expand...
Click to collapse
I cant see why you wouldnt be able too, if it has flashed once it should flash again, but given that it may be a hardware fault (I am not saying that it is, but IF it is) then it could be risky.
While I have been programing for more than 20 years, I do not code much in C/C++ which i assume is what this is done in.
Click to expand...
Click to collapse
I have never looked, but yes I agree. If i knew more about it I would attempt it for you, but I am inexperienced at that kind of programming.

[Q] bricked g2 upon custom rec overy

ok so i wanted to flash clockwork 3.0 but i was still running cm 6.1.1 and now i am stuck at the htc boot screen. i also cant get into recovery please i am begging for help.

please someone i really need help i obviously cant use my warranty obviously so please help me restore this or just get it back to working without a root anything

Dont worry pal.
OK,... AFAIK...... If you have flashed ClockworkRecovery 3, the only ROMs that will work are the 2.3 ROMs,... If you are trying to boot up a 2.2 ROM, it is likely to bootloop.
So boot back into recovery, full wipes, then flash a 2.3 ROM,... If that is what you were planning to do.
If you want to keep your 2.2 ROM on,... flash back to an older Clockwork Recovery,... then try to boot? If you get boot loops, try wiping cache and try again. If it still fails I would just do a fresh flash of your ROM again,... Remember full wipes 1st.

wileykat said:
Dont worry pal.
OK,... AFAIK...... If you have flashed ClockworkRecovery 3, the only ROMs that will work are the 2.3 ROMs,... If you are trying to boot up a 2.2 ROM, it is likely to bootloop.
So boot back into recovery, full wipes, then flash a 2.3 ROM,... If that is what you were planning to do.
If you want to keep your 2.2 ROM on,... flash back to an older Clockwork Recovery,... then try to boot? If you get boot loops, try wiping cache and try again. If it still fails I would just do a fresh flash of your ROM again,... Remember full wipes 1st.
Click to expand...
Click to collapse
the thing was i couldnt even get into recovery because i was running 6.1.1 while on cw3 but i hit simlock from fastboot and that worked but thanks

rajbaba2 said:
please someone i really need help i obviously cant use my warranty obviously so please help me restore this or just get it back to working without a root anything
Click to expand...
Click to collapse
Can you boot into Hboot screen (phone off then volume-down + power)? If yes try to select recovery from the Hboot screen, it should reboot into recovery, if it doesn't and something is wrong with your recovery, Do you have an Eng. Hboot? , if yes do you have Andriod SDK set up and fastboot? If yes, boot into Hboot, select fastboot from the options, then plug in your usb. Once your device is recognized by fastboot:
Code:
fastboot devices
should return a serial number + "fastboot"
then reflash ClockWorkMod Recovery 2.5.1.3( you can download it from here:http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html then place the ClockWorkMod Recovery 2.5.1.3( make sure its named recovery.img) into the tools folder in AndriodSDk where Fastboot is located, then run the command :
Code:
fastboot flash recovery recovery.img
fastboot reboot
once rebooted your probably gonna be stuck at the HTC screen again, pull the battery, then Volume-down+ power back into Hboot, then select recovery from Hboot screen and it sholud reboot into ClockworkMod recovery, then reflash the rom of your choice.

thanks but i already fixed it by pressing sim lock and i have no idea why that worked and i should probably set up adb now right?

rajbaba2 said:
thanks but i already fixed it by pressing sim lock and i have no idea why that worked and i should probably set up adb now right?
Click to expand...
Click to collapse
I would if you haven't.
Sent from my HTC Vision using XDA App

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .

jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!

i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?

jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.

you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot

Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium

Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?

jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.

So I can literally flash a different recovery from within another?

jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium

Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks

Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk

I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.

Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.

firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.

My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.

Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.

Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

" x " appears on the screen

Malfunction " x " appears on the screen !! help me what is going on

Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.

Did you flash any ROM if so, did you clean your Dalvic+REgular Cache

If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM

you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is

Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?

study it ,thank you
study it ,thank you

Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i

not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems

rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!

Glad that you got it

Stock recovery flashable .zip?

How can i flash the stock recovery?
Or what can i do to have it? I want to download the new firmware...but im using the TWRP Recovery... (Bootloader unlock)
Any suggestions?

andrexp31 said:
How can i flash the stock recovery?
Or what can i do to have it? I want to download the new firmware...but im using the TWRP Recovery... (Bootloader unlock)
Any suggestions?
Click to expand...
Click to collapse
k1ll3r8e's toolkit should be able to do it for you, give it a try.

Thanks for the answer. But the stock recovery didnt work for the thing that i want to do... I want a fresh installation of the last compilation of the firmware. I want to wipe it all...and install the the stock firmware,to start from 0. (Cause i have to much garbage in the system. The Ram memory is down of 1,60 gb with 3 user apps installed) You know how can i do that?
I had it the stock recovery this morning but didnt download me the last firmware...(cause i have the bootloader unlocked) So i return to twrp...
I just want a fresh installation of the stock rom to start from there.

andrexp31 said:
How can i flash the stock recovery?
Or what can i do to have it? I want to download the new firmware...but im using the TWRP Recovery... (Bootloader unlock)
Any suggestions?
Click to expand...
Click to collapse
You can get stock recovery here http://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Download the zip extract it and I believe it's called stock.img
I'm going to assume bootloader is unlocked and USB debugging is enabled
Enter fastboot mode and connect to PC
Load up adb terminal on your PC type fastboot flash recovery PATH/stock.img (PATH= file path to the recover img)
After that is done download the latest firmware for your phone version and extract it, extract update.zip and put its contents on the root of your sd card in a file called dload (make if it doesn't exist)
With the SD card inserted and phone turned off power up by holding volume up, volume down and power at the same time for about 8 seconds, this will start the update, once that has done you will want to power the device holding volume up and power for a while, select factory/data reset, then wipe cache, reboot into clean stock rom.
This will also remove root and relock bootloader