I've been at this for like 8 hours going in circles. I have about 12 hours to figure this out. I am scheduled to go back to TMO to return this phone. Please help me.
While trying to revert back to stock, upon boot, at first there is a green icon, then it turns red w/ an exclamation point and just hangs there. It seems to have booted into the recovery because where it hangs, if i touch the "home" button, it disappears and shows me the cwm recovery main menu with a few errors relating to unable to mount SD. Its a very gimpy CWM with more than half of the commands/functions missing. (see pics below)
This is what I am currently getting in order....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Boots to image 01
- Then to 02, here its trying to load/mount stuff, notice the SD icon and load bar near the bottom
- In 03 it looks like it ran into an error and hangs there
- Not sure why but I realized it boots straight into recovery. From 03, if i touch the home button I get 04. Notice all the stuff missing from cwm options
- 05 is what my HBoot / Bootloader looks like
-------------------------------
I am able to get back into HBoot / bootloader screen and can confirm that while in that mode the PC does recognize the device. But everything I flash does not work. When I run RUUs they seem to begin a process, but once that is done ( which isnt long), I would reboot but see nothing has changed. I tried to undo that stock recovery to access to NAND backups and start the process again but that Recovery doesn't have options for backups (strange?). Anyways, but can not flash another CWM successfully.
This is what I currently see when flashing a CWM now
c:\android-sdk\tools>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-vi
lle.img
sending 'recovery' (6616 KB)...
OKAY [ 0.969s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.210s
c:\android-sdk\tools>fastboot reboot
rebooting...
I am completely out of options now. I looked at all the stickies around here and other places but can not find anything that will work. I did my best to be as thorough as I can. Please let me know if there are more info that would help. Thanks ahead of time.
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Chris Boyer said:
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
enzyme said:
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
Click to expand...
Click to collapse
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
These are the steps I took that led me here.....
1. flashed ville_recovery_signed.img via Fastboot from here
2. re-locked the bootloader with in fastboot
3. ran RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed from here that was from this thread.
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Moved To Q&A
Do not open question threads in the development section, thats what Q&A is for.
Chris Boyer said:
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Yeah i have full control of Fastboot, just not always getting the desired final results. Yes I have the AIO pack and have tried to flash those recoveries w/o results. I mean from the log it looks like that did the trick but nothing changes after reboot, I can't get rid of the current Recovery.
stealthnoodle said:
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Click to expand...
Click to collapse
Steath! Now we are getting somewhere!
As I was going through the steps, I got the CWM from the AIO. That was before I had a chance to flash the 2nd time (step3), before I could get to the rest of the steps I allowed the phone to boot normal instead of HBoot, then it reverted back to the other recovery. But as of right now I did flash via AIO, cleared storage, factory defaulted, flashed via AIO again and now I am on step 5.
I am still sitting in the AIO CWM right now. The guide says to flash the UTB rom, which I am unfamiliar with and it appears like a custom rom. So what should I flash and what method should I use? Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty. Should I .....
- flash one of the RUUs via fastboot?
-rename the RUU and push it to the SD via ADB and flash via CWM (like in the guide)?
(not sure if that method works with customRom only or RUUs as well.
enzyme said:
Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty.
Click to expand...
Click to collapse
If you can mount your sdcard partition in recovery, you can then adb push a rom to it and flash it.
On your PC:
adb push yournewrom.zip /sdcard/
Then on your phone, in recovery:
Format system, data, cache
Flash zip from sdcard -> choose zip -> /sdcard/yournewrom.zip
Before you boot into the new rom, flash the boot.img (extract it from the zip) in fastboot.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Steath's advice led me to the guide and got me on the right track. Even with detailed instructions, I went in circles for awhile, but in the end I got it. I'm so relieved, its been a stressful 12hrs.
So now I just have one last question. Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice who knows, I'm still very new to much of it.
enzyme said:
Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice...
Click to expand...
Click to collapse
It is safe and common practice (and in many cases required to prevent bootloops) to extract the boot image from the rom you flash, and flash this boot image through fastboot.
Custom roms do not come with their own recovery (only their own boot.img). The only reason to extract a recovery from a RUU or OTA and flash it, is when you need to go back complete stock.
Edit: But if you want to switch to a different custom recovery, then yes, flashing it through recovery is safe and the proper way. (You just don't 'extract' it from anything.)
Related
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Wrong section.
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.
polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I have the android sdk but after "adb devices" its saying command not found
ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.
i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No boot or recovery img
This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.
Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium
Hi... i tried to flash CWM and enter recovery mode a couple of times and not once am i successful. I keep getting a white HTC screen with red text "This build is for development purposes only, not to be distributed.. etc etc"
No matter which CWM i tried it just would not work... i noticed some people have this problem but no solution? Does the latest One S have some kind of block or something that does not let us run these images?
Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?
First person I have heard of not being able to flash recovery. Unlock bootloader. Then go to appstore and download goomanager. Download and flash TWRP thru goomanager.....done
Sent from my HTC VLE_U using XDA Premium HD app
Moved To Q&A
Please post questions in the Q&A section
azzledazzle said:
Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?
Click to expand...
Click to collapse
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right
onlinechi said:
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right
Click to expand...
Click to collapse
Yes, If it says unlocked then it is unlocked did YOU unlock it ?
Are the recovery images flashing successfully ? without any errors ? you could try and use adb to reboot in to recovery.
If that fails, You could try and fastboot boot recovery, You can flash almost anything this way
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get.... yes I did unlock it. Yes I did successfully flash. Its just when I reboot and enter bootloader and choose recovery... I keep getting that despite trying multiple images ... what is the meaning of that screen anyway... if we know what it does perhaps we can know what is wrong
--duplicate post--
That writing you see is normal, It happens as soon as you put non official software on the device. I cant figure out why it wont boot into recovery.
You could try to flash stock recovery,
Then fastboot erase cache.
Then reflash CWM and hope for the best.
Dont give up, Ill have a look around for some kinda fix for you !
EDIT: Also try Hasoons All In One Tool until i figure this out
when I click recovery in the bootloader... it shows that and just stays there.... may I know where the link is to a stock recovery as I did not back up mine...
https://dl.dropbox.com/u/69014495/stock recovery.zip
Does the phone boot ?
Did you try fastboot erase cache ?
Hi.. i tried flashing the stock recovery with Hasoons tool... I still get to the screen which shows... "this build is for development purposes only. Do not distribute.. etc etc..." Thats so strange. Logically it should should just show that for awhile then go on to the recovery isnt it? Why does it just stay there?
By the way.. how do i erase cache? Is it possible to be done without entering recovery?
I tried flashing the stock recovery. Locking the bootloader... then unlocking it all over again. Then flashing the CWM recovery... then boot to recovery.. still.... the same. :-(
so the phone does never boot ??
If i was you i'd run an RUU and start all over again
Oh no... the phone is perfectly fine.. its just the Recovery in to which its stuck. The normal operation of the phone is totally OK. I read something.. if i had flashed a recovery image... it should show my phone as "tampered" in the bootloader. Mine does not show that.. it just shows "Unlocked".. Is there something i missed?
Btw... i do not know if it matters.. but my phone is from Singapore.
it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.
I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.
jayelbird said:
I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.
Click to expand...
Click to collapse
How did you use Rom Manager when you dont have root?
azzledazzle said:
it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.
Click to expand...
Click to collapse
MMM.... Does not work.. I tried this
Boot into boot loader.. did the erase cache. Was ok. Did a reboot.
Reboot in to bootloader.. install recovery.. reboot
Reboot then attempted enter recovery.. still the same... Stuck at the red text
I then tried this
Boot into boot loader... did the erase cache.. was ok.. no reboot
Flash the recovery.. no reboot
Enter recovery.. still the same.. stuck at red text
Reboot.. enter recovery.. also the same.. stuck at red text...
:-( I have had HTCs.. Samsungs... and rooted all of em.. this is the first time i have been unsucessful.. heck i even rooted a China Device before....
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Simple mate...
Download cm rom zip
Reboot into recovery
Mount ur storage
Put cm rom zip somewhere
Install that rom zip via recovery(twrp is recovery not the boot loader )
Flash gapps (optional if u want google services n apps) (u can do this later also)
Reboot
forstyy said:
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Click to expand...
Click to collapse
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
doctor_droid said:
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
Click to expand...
Click to collapse
What do you mean lol?
Lethargy said:
What do you mean lol?
Click to expand...
Click to collapse
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
As in browse files on a PC or what?
Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
forstyy said:
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
Click to expand...
Click to collapse
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lethargy said:
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
Click to expand...
Click to collapse
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
Click to expand...
Click to collapse
forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
Just push a cm rom made for ur hammerhead...
forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Lethargy said:
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Click to expand...
Click to collapse
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Its the bootloader fastboot is what's used in the bootloader. And yeah, flash a custom recovery then you're good to go!
forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Welcome to flashing world...now since u know how to revive ur phone... U will definately mess up it again...
doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
Mount storage only works on a non-fuse /sdcard. Meaning either:
- device has removable sdcard
- device is not using fuse for internal storage.
Nexus 5 meets neither.
Sent from my Nexus 5 using Tapatalk
Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
My thoughts exactly
sent from my thumbs
Same here I've messed my n5 up about 5 times these Google images come In handy
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
forstyy said:
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
Click to expand...
Click to collapse
The N5 is basically the best contemporary phone to soft brick or break. The support and tools available are great.
Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch - don't get the 'amber LED' which various guides tell me to press Vol Down at.
I'm using
Code:
fastboot boot recovery.img
to boot the phone into recovery and
Code:
fastboot flash recovery recovery.img
to flash it, which hasn't worked at all. All of theTWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
[snip]
TimTams said:
Hi all,
I've followed various sets of instructions for installing a recovery onto my E6653. I was able to get recovery to boot successfully using the sony-recovery-z5.img found HERE, but it can't see, mount, format or wipe my ext SD card at all in this recovery so I can't initiate the install of a ROM from it.
I've tried stacks of other recoveries and boot images (kernels?), including:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , all ROMs
[TWRP][E6653/E6603] 2.8.7.0 and Stock Rootable Kernel [2015-11-15]
[KERNEL][E6653/E6633/E6683] Zach's Kernel Playground for Z5, WIP (work in progress)
https://www.gizdev.com/sony-xperia-z5-e6653e6603-unlock-bootloader-install-twrp-recovery-root/
but none of these work - the phone will no longer boot after flashing boot.img (stuck at sony logo) and the recoveries will not launch. I'm using
Code:
fastboot flash boot boot.img
to write the boot images and
Code:
fastboot boot recovery.img
to boot the phone into recovery. All of the other TWRP versions I have found around the place do not work at all - it stays at the SONY white boot up screen. I have seen other kernels in .zip files and was extracting them to flash the boot.img file but looking now that seems incorrect - how do I flash the .zip file? Maybe that's unrelated but I seem to be missing something there
At the moment, the only way I can use my phone is if I flash the firmware in flashmode, using Flashtool.
My steps, from stock, were:
get unlock code from sony
enable USB debugging
turn on "Enable OEM Unlock"
issue "adb reboot bootloader"
issue oem unlock command
reboot phone and confirmed "Bootloader Unlocked: YES"
issue "adb reboot bootloader"
Then what should I do? What other steps do I need to take to get from stock onto a custom ROM such as this one? Please tell me step-by-step (like i'm 5) and assume you're talking me through it and I know nothing... because I am clearly missing some obvious step that nobody else here has struggled with.
Thanks heaps in advance for your help guys
Click to expand...
Click to collapse
I don't think your bootloader is unlocked because:
1: your device won't boot after flashing an image.
2: your rooting status says: bootloader unlock allowed.
(if unlocked, it says rooting status: bootloader unlocked)
Yes means it can be unlocked.
Unless you unlocked already and use drm fix because then it still shows yes but Im pretty sure your bootloader isn't unlocked.
BTW this thread belongs in Q&A section.
You can request a movement by hitting the small "!" triangle button underneath your post when viewing this page in a browser.
Sent from my E6653 using XDA-Developers mobile app
Thanks heaps - that sounds like it might be the issue, I'll have a play and post back here. It would explain why I've had so much trouble with what seems like a simple task
langeveld024 said:
I don't think your bootloader is unlocked
...
Click to expand...
Click to collapse
EDIT:
It looks like this was done correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure I want to go and have another crack at flashing a recovery... I couldn't seem to get any of them to work.
I've just followed this guide to installing recovery and it hasn't worked... I still just get stuck at the sony logo. Any ideas why? How do I know the recovery image linked is correct for my phone?
http://www.digitbin.com/unlock-bootloader-flash-twrp-root-sony-xperia-z5/
OK, I got recovery installed! Thanks to this guy: http://forum.xda-developers.com/xperia-z5/help/boot-flashmode-fastboot-t3457818
mentions what no other guide mentions...
I need to have a custom kernel before I can flash recovery (first mention of this I've seen)
The kernel I flash needs to match the firmware I have installed
With that, I had instant success.
EDIT:
And now I have managed to get a custom ROM installed at last My procedure was, for anyone that be stuck in a similar way:
If your phone already won't boot:
Download Flashtool and install it. I have mirrored it here as all the sources I found were very slow: http://noobs.wtf/uploads/flashtool-0.9.22.3-windows.exe
Go to the 'drivers' folder inside your Flashtool install directory (default C:\Flashtool\drivers) and follow the instructions to install the "flashmode" driver
Select XperiFirm within Flashtool and download the correct firmware for your phone - mine was "Xperia Z5 > Sumire > E6653 > Australia > Telstra AU > 32.2.A.0.253 / R5C"
Turn off your phone and boot it in flashmode - Insert USB while holding vol down until the LED is green
Once Flashtool has finished downloading your firmware, go back to the main screen and click the 'lightning' button to flash your phone with the new firmware that should show up in the list - leave all the options unticked. Wait for it to say 'complete - un plug your phone'
Your phone should now boot successfully
To install a custom ROM:
I was not able to access my SD card in any version of TWRP - so copy your ROM to the internal storage of your phone. I used v1.5.0 of THIS ROM successfully.
Copy v36 (or newer) of THIS KERNEL .zip file to your internal storage as well. (v32 and higher are in the google docs link) NOTE this must match the firmware version - v36 was the one I used because, as above, I re-flashed my phone with 32.2.A.0.253 from Flashtool. The appropriate versions are listed on that link
[*]Also download TWP-3.0.2-2-E6653.img (or newer equivalent) from that same link.
[*]Follow the instructions HERE to unlock your bootloader (and make sure your fastboot drivers are installed correctly)
[*]Reboot your phone and re-enter fastboot mode (vol-up while plugging in USB) you can issue the command 'fastboot oem unlock' and it will return 'already rooted' if it has been done correctly
[*]Now with your phone in fastboot mode, issue the commands "fastboot flash recovery TWP-3.0.2-2-E6653.img" then "fastboot boot TWP-3.0.2-2-E6653.img" to install and then boot into TWRP recovery
[*]Once in TWRP, go to "Install" and install first the Kernel, then install the ROM, making sure to do the wipes
For me, this completed the process of installing a custom ROM I was stuck on the lack of info around installing the kernal and whatnot.
TimTams said:
I was stuck on the lack of info around installing the kernal and whatnot.
Click to expand...
Click to collapse
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
langeveld024 said:
But the info was right here on the forum's, wasn't it?
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
TimTams said:
not in any of the guides that outline how to go from "stock" to one of the custom ROMs, no.
Click to expand...
Click to collapse
Hmm maybe u should suggest the OP of those threads to add this information then.
I personally never read those guides lol[emoji14](not anymore at least, at some point I was learning about this like you as well, we all had to learn)
Sent from my E6653 using XDA-Developers mobile app
DO NOT FORMAT YOUR MICRO SDCARD INSIDE TWRP RECOWERY
WARNING: If you want tho use /data and internal sdcard first have to format data in stock recovery This will wipe your internal storage, and factory reset your phone!
encryption is not supported yet
To flash this img to your phone use fastboot
Code:
fastboot flash recovery twrp-x.x.x-x-h840.img
+new test build with encryption support
source code https://github.com/synescu/twrp_lg_h840
1.Unlocking the bootloader.
1.1Get the latest drivers: ( http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 )
1.2Get ADB fastboot. If you hate installing huge files for just a few commands, you have 3 options:
-MINIMAL ADB and fastboot: (https://forum.xda-developers.com/showthread.php?t=2317790 )
-15 seconds ADB Installer v1.4.3: (https://forum.xda-developers.com/showthread.php?t=2588979 )
-SDK Platform-Tools coming directly from google: (https://developer.android.com/studio/releases/platform-tools.html )
I personally went with the “15 seconds ADB Installer v1.4.3”, because it installs also a Google driver, which might, or might have not helped out in the process to follow.
1.3Follow the instructions at the official LG unlocking page ( https://developer.lge.com/resource/mobile/RetrieveBootloader.dev ), just keep in mind that after step 1.2 you have adb ready to go @ your main drive C:\adb. You go to that folder shift + right click and open a command prompt at that location, the rest is trivial.
2.Updating to the latest official stock android.
2.1Get the latest kdz from: (https://lg-firmwares.com/lg-h840-firmwares/ ). As far as I know you can go for any of those firmwares, but it is advisable to use one from your region (Europe, South America, Middle East). As mentioned above my LG G5 H840 is the newest European model, totally unbranded. So I took the 20c for Spain. This is as high as you can get at present moment.
2.2 Flash with LGUP 1.14 and UPPERCUT 1.0.0, both available at: (http://downloads.codefi.re/autoprime/LG/LG_G5 )
2.3 Reboot and do a quick setup. I recommend to have your sim card, SD card out at this moment, do not connect to wireless networks, all of this you will have plenty of time to do later, besides whatever you set at this point will be lost in the next step.
3.Get TWRP and root
3.1TWRP. As a courtesy of synescu, we have 2 versions: a regular one and such with encryption support. It took me long to realize that only the one with encryption would work on a latest H840 installed with v20c. So I guess if you have an old phone and possibly firmware 10a/b/c/d, than you can try “twrp3.1.1-0-h840.img”, otherwise go straight to “twrp_encryption-h840.img”. If you use the one without encryption support you will find no way to root the phone, because it can not see the SD card, or any USB flash attached and also if you connect the phone to a PC with MTP mode, or any other mode you won’t be able to browse both (internal and external) memories on that phone.
3.1.1Put on a SD card following files: 1) latest stable SuperSU 2.79 2) no-verity-opt-encrypt.zip from here (https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip ) and just in case although not mandatory “twrp_encryption-h840.img”.
3.1.2Put in the C:\adb folder the “twrp_encryption-h840.img” and the stock recovery from here (https://forum.xda-developers.com/attachment.php?attachmentid=4149809&d=1494791791 ). The stock recovery is necessary in case you make a mistake and have to do a factory reset.
3.1.3Turn off the phone.
3.1.4Boot into stock recovery (holding volume down + power, at LG logo releasing power shortly and than pushing power again).
As a side note here, after I unlocked the bootloader I’ve got that annoying message on start-up that the phone is untrusted. With G4 H815 it was a small message in the upper corner, this time around it is a huge message in the middle of the screen. LG, for the love of god! After all the playing, I have now also a message screen, which I call “Options Menu”, it shows right after the nagging untrusted message. Although esthetically ugly, I have an easy way to go to recovery and fastboot in each and every regular power on, or restart. As said the Options Menu is showing up for 5 sec after the untrusted nagger. If you click the volume up, or down you get to the options (Power off, Restart, Recovery, Fastboot ), otherwise after 5 sec the phone would boot normally. I don’t know if this is the expected behavior of the phone, or did I trigger it somehow, but now I don’t have to use the combo buttons for anything.
Back from the side note. The new stock recovery is a white screen with 2 options for No and Yes. Go for YES and than YES again, after both YES the phone will be factory reset and will reboot. Do not allow it to boot though, because the userdata will be encrypted at this point and you will have to repeat the reset again. Use the combo buttons for recovery, which will bring you to the “Options Menu”, or Volume up and plug in the phone into the PC. Yet again there is hardly any time so maybe plugin in won’t be fast enough, so just keep pressed the combo buttons, also change with volume up and power, or remove the battery and start again. In any event do not let it boot until it brings you to the “Options Menu”
3.1.5In the Options Menu pick fastboot and plug the phone to the PC
3.1.6Open command prompt in adb and flash TWRP ( fastboot flash recovery twrp_encryption-h840.img ) you might be ok also to do factory reset from adb with this command (fastboot –w ), but unfortunately I forgot already if I did it, when it finally worked for me
3.1.7Disconnect from the PC and pull the battery out, or just keep the buttons combo pressed. It is possible that you see the old stock recovery (white screen YES/NO), which might have stayed somehow in memory. Do not perform further resets, just keep pressing the button combo and it will reboot eventually to the Options Menu.
3.1.8There you go 3 times volume down and power to pick recovery. Follows a reboot of the bootloader, nagging screens, but eventually it loads TWRP.
3.2Root.
3.2.1For some reason even after the factory reset, the data partition keeps an encrypted flag. So you can not write to it. Stock recovery should have reset it to non-encrypted, but it does not do it correctly, I guess. Therefore you go to Wipe, pick only the Data check box and go to change format in the bottom. Change the format to FAT and than back to EXT4
3.2.2Go to the SD card and flash no-verity-opt-encrypt.zip and SuperSu. Yes I know, that SuperSu is supposed to install also no-verity, but I like to flash both just in case.
3.2.3Do NOT wipe anything in TWRP at this point. Reboot only!!!!! Once the phone has booted in v20c you can go back to TWRP, Wipe and make all the backups you like
Thanks to @svetloslav for this complex post
Thanks a lot.
Can't wait to flash!!
YESS finally we have root on the SE thank you very much man
Hi all. When I try to flash recovery, fastboot give me that message:
target reported max download size of 536870912 bytes
sending 'recovery' (15089 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
Any suggestion? Thanks
Solved: I had not extracted the .img from the .tar archive
synescu said:
For now external sd card is mounted as internal. De only way you can flash something for now When I would have more time I will try to fix this and upload the source to github. I rooted the phone and installed the supersu and no verity zip
source code https://github.com/synescu/twrp_lg_h840
Click to expand...
Click to collapse
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
bob8x said:
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
Click to expand...
Click to collapse
I'm booting this vith android 7.0
6.0 must boot just fine. didn't tried encryption but I'm pretty sure that doesn't work
Build compiled from Omni 6.0 sources
Sent from my LG-H840 using Tapatalk
Thank you very much for your precious time my friend. Good work
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Wire1122 said:
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Click to expand...
Click to collapse
Yes internal storage it's properly mounted now
Sent from my LG-H840 using Tapatalk
Anyone can confirm if encryption works?
Sent from my LG-H840 using Tapatalk
synescu said:
Anyone can confirm if encryption works?
Click to expand...
Click to collapse
I have flash it succesffully. But how can I yest if it works?
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Wire1122 said:
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H840 using Tapatalk
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Wire1122 said:
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
In Order to use data first you have to factory reset your phone using the stock recovery
Sent from my LG-H840 using Tapatalk
How? Stock recovery? Where is it? I'm noob and rooted with supersu
My log
Wire1122 said:
My log
Click to expand...
Click to collapse
stock h840-recovery.img
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Wire1122 said:
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
Why would you think that you would keep TWRP after flashing stock recovery? Also, why would you flash stock recovery after flashing TWRP and SuperSU? You either have TWRP or stock recovery, not both. Also, don't ever recommend flashing stock recovery after modifying system in any way unless you reflash whole stock system as stock. Anyways, all you need to do to get TWRP back is use the :
fastboot flash recovery TWRP.img