One of my brother's friend made "something" to my brother's phone trying to update it.
In short, he bricked the phone (p700), which is looping on boot animation.
What I tried so far:
-I used KDZ and pushed the V20A_00.kdz that has CWM 6.0.2.8, still no boot
-I tried to install a Custom Firmware got error "Status 7" telling me that the CF I wanted to install was for the p700 and my device is a "u0"
Now I'm stuck at this point, what am I doing wrong?
-I thought of pushing a valid p700 build.prop through ADB, but "su" command doesn't work.
-I thought of editing the "scriptupdater" file of the CF, first I tried with this method this time it doesn't give me "Status 7" but it aborts the installation without furher explanation
At this point I'm starting to lose hope, I really want to fix this, please, could you help me?
skychronicles said:
One of my brother's friend made "something" to my brother's phone trying to update it.
In short, he bricked the phone (p700), which is looping on boot animation.
What I tried so far:
-I used KDZ and pushed the V20A_00.kdz that has CWM 6.0.2.8, still no boot
-I tried to install a Custom Firmware got error "Status 7" telling me that the CF I wanted to install was for the p700 and my device is a "u0"
Now I'm stuck at this point, what am I doing wrong?
-I thought of pushing a valid p700 build.prop through ADB, but "su" command doesn't work.
-I thought of editing the "scriptupdater" file of the CF, first I tried with this method this time it doesn't give me "Status 7" but it aborts the installation without furher explanation
At this point I'm starting to lose hope, I really want to fix this, please, could you help me?
Click to expand...
Click to collapse
Can u go into CWM Recovery?
froydenzi said:
Can u go into CWM Recovery?
Click to expand...
Click to collapse
Yes, but every ROM gives an error when I try to flash it.
What error say?
Sent from my LG-P700 using Tapatalk
froydenzi said:
What error say?
Sent from my LG-P700 using Tapatalk
Click to expand...
Click to collapse
When I don't edit the "getprop" part of the updaterscript I get "status 7" error as expected. "This is for p700 devices. Your device is u0"
When I do edit it: "installation aborted"
I will search for it tomorrow,for now i must sleep,its 00:00 in my town,am sleepy.
Sent from my LG-P700 using Tapatalk
You have to update your recovery with Rom Manager or flash the latest TWRP with CWM ( TWRP is an other recovery ) ! No need to edit anything !
Sent from my Nexus 7
azvlean said:
You have to update your recovery with Rom Manager or flash the latest TWRP with CWM ( TWRP is an other recovery ) ! No need to edit anything !
Sent from my Nexus 7
Click to expand...
Click to collapse
Sorry, never heard of this, care to explain?
Sky,what recovery u use?
Sent from my LG-P700 using Tapatalk
skychronicles said:
Sorry, never heard of this, care to explain?
Click to expand...
Click to collapse
Sometimes, the problem happens when your recovery is outdated. So, download ROM Manager and in the app you'll be able to update CWM. If it's already update, download TWRP by @tudorsbird and flash it with CWM. Your recovery will be TWRP but you won't be able to restore backups performed with CWM. If you can't boot but have a SD card, you can put TWRP on the card and flash it.
Or, you can try this ( with Fastboot ) to flash a new recovery :
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Sent from my Nexus 7
On th
Sent from my HUAWEI U9508 using xda app-developers app
I use cwm v6.0.2.8
Sent from my HUAWEI U9508 using xda app-developers app
Here is the link for TWRP : http://sourceforge.net/projects/lgl...TWRP Recovery/twrp.v2.6.3.0_p700.zip/download
Sent from my Nexus 7
azvlean said:
Here is the link for TWRP : http://sourceforge.net/projects/lgl...TWRP Recovery/twrp.v2.6.3.0_p700.zip/download
Sent from my Nexus 7
Click to expand...
Click to collapse
WORKED, thank you so much.
skychronicles said:
WORKED, thank you so much.
Click to expand...
Click to collapse
Your welcome, glad I helped you !
Sent from my Nexus 7
Related
Someone Please Help
I was Rooting my Nexus S using the step by step guide to ROOT Nexus S using clockwork Mod posted by AllGamer and am stuck in the 2nd Part now.
I have unlocked the phone now but the next step is not working. Everytime I hit the command fastboot flash recovery recovery.img I get an error saying unable to load recovery.img
I have checked everything, its all fine. i tried downloading the recovery image from other sources and tried it as well, still no luck.
Someone please help me with this!
Thanks in advance!
Cheers.
PS. Im using a Nexus S running on Gingerbread 2.3.3
You may try this > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
If your PC already has the phone driver and fastboot, you can skip several steps including downloading the sdk.
I used this yesterday to root my ns and to install a custom rom.
Cheers!
rajeevkr said:
Someone Please Help
I was Rooting my Nexus S using the step by step guide to ROOT Nexus S using clockwork Mod posted by AllGamer and am stuck in the 2nd Part now.
I have unlocked the phone now but the next step is not working. Everytime I hit the command fastboot flash recovery recovery.img I get an error saying unable to load recovery.img
I have checked everything, its all fine. i tried downloading the recovery image from other sources and tried it as well, still no luck.
Someone please help me with this!
Thanks in advance!
Cheers.
PS. Im using a Nexus S running on Gingerbread 2.3.3
Click to expand...
Click to collapse
Is cwm downloaded to the directory you are ruining the command from and also named recovery.img?
Sent from my Nexus S using XDA Premium App
.cruiser said:
You may try this > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
If your PC already has the phone driver and fastboot, you can skip several steps including downloading the sdk.
I used this yesterday to root my ns and to install a custom rom.
Cheers!
Click to expand...
Click to collapse
Thanks a ton bro!
Worked like a charm, my phone is rooted now Finally!
krohnjw said:
Is cwm downloaded to the directory you are ruining the command from and also named recovery.img?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks for the help mate.
Had made a silly mistake, i didnt navigate to the directory first, had some issues there thats all.
all sorted now! Cheers!!
I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob
Describe steps you have taken to root in detail.
i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob
any one can help me?
Vbob
Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...
vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot
[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?
Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse
has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app
It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app
New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable
CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440
6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7
Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD
No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?
Hi all,
I'm freaking out here. I was trying to install a kernel on my N4 using the Toolkit and somehow it said it was done successfully but then my phone got stuck on the Google screen and was never able to start up again.
I do have a Nandroid back up but unfortunately it's on my computer and not on my phone.
I tried using the toolkit AND adb to push the files to my phone but I get the same message: "failed to copy to sdcard: No such file or directory".
I'm completely stuck now and am panicking. Somebody please help!
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Might also be helpful if you specified which kernel you flashed. As long as you didn't flash a kernel for a different device (e.g. nexus 7) you can definitely recover. To reiterate what others have mentioned, fastboot is your friend. There are numerous tutorials on his to install and use it. Check the stickies.
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My main problem is I need to get my Nandroid backup onto my phone. For some reason, because it's stuck on the Google screen, it's not able to write to the sdcard. Can someone please help me get my files from my computer to my phone?
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Unjustable said:
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your help. I've successfully follows the instructions and got back to Android 4.2.2.
I still want to restore my previous Nandroid though. Although I have placed it in the Clockworkmod backup folder, it's not being seen by CWM recovery. I tried backing up a new nandroid just to test and CWM sees the one it backs up.
Anyone know how I can get CWM to recognize the Nandroid which was done through the toolkit?
Thanks!
darkwolf1789 said:
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Click to expand...
Click to collapse
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Crisisx1 said:
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I realize that now. But any idea how to get CWM to recognize my Nandroid that I did with the toolkit? Anyone?
joshnichols189 said:
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
skezza said:
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
Click to expand...
Click to collapse
Ok well to solve the problem I did download the stock images and flash them according to Effrants guide:
http://forum.xda-developers.com/show...php?p=34552123
Then the reason that CWM wasn't recognizing my Nandroids was because I had them in /sdcard/clockworkmod/backups, but they should be in /data/media/clockworkmod/backup.
I recovered everything and I'm back! Thanks for your help everyone.
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
wrong advice, my mistake... thanks for the reminding simms22.
But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app
You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken
Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks
darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.
Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app
will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.
simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk