Develop Bugs

[Q]phone bricked

my phone died.....
When I see a new recovery,i flashed it in my one x.But failed.
I use fastboot flash recovery recovery123.img (i changed the name to recovery123.img)But the screen show,
sending 'recovery' (5452 MB) ... OKAY (6.973s)
writing 'recovery' ... INFOFormat SOS done
OKAY
I tried it many many times already but still fail

Flash your RUU via fastboot to get back to stock (relock the bootloader first)

EddyOS said:
Flash your RUU via fastboot to get back to stock (relock the bootloader first)
Click to expand...
Click to collapse
The RUU can't verify my phone already on fastboot usb mode

1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Courtesy of DaDoctor
Mod or Die
Mod or Die

snowwhite007 said:
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Courtesy of DaDoctor
Mod or Die
Mod or Die
Click to expand...
Click to collapse
My phone can't flash anything via fastboot

sending 'recovery' (5452 MB) ... OKAY (6.973s)
writing 'recovery' ... INFOFormat SOS done
OKAY = DONE AND WORKING
and you can allways flash from fastboot..
have you got all files ?
fastboot.exe
adb.exe
AdbWinApi.dll

[Q] TWRP recovery Stuck at Booting recov image

Hi, it's the second time i try to install TWRP recovery v2.2.0+ and each time it keeps getting stuck at the boot with the message
Bootloader version 0.03.06-ics unlock mode
Booting recovery kernel image.
Waited for more than 10 minutes and nothing happened.
i can reboot and and log into ics normally i just don't have access to a recovery.
---I want to know how to properly install twrp , what went wrong and how to fix it.:
the script:
@echo off
cls
echo reboot to bootloader
adb wait-for-device
adb shell su -c "mount -o remount, rw /system/ && mv /etc/install-recovery.sh /etc/install-recovery.offsh;"
adb reboot-bootloader
echo flashing recovery
fastboot flash recovery recovery-A100ICS-TWRP-2.2.0.img
echo -
echo -
fastboot reboot
adb wait-for-device
echo check the recovery XXXXXXXXXXXXXXXX--This is where i'm stuck at.
adb reboot recovery
MY SETUP:
ROM FLEX-A100-REAPER-RELIX_Rev2 , OC A 1500, CWM was working ok.
WIN64

I would suggest downloading the image again, then trying the install script after you delete the current image with the newly downloaded image.
If you feel OK using a terminal its pretty straight forward
Open a terminal and CD to the folder with adb fast boot and recovery image
Example
cd c:\recovery
If powered on type
adb reboot bootloader
After it boots into download protocol type
fastboot erase recovery
fastboot flash recovery twrp.img
Twrp.IMG being whatever the file name is.
fastboot reboot
Let it boot into android then
adb reboot recovery
See what it does.
Tapatalked from my Galaxy S II.

a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?

IamModeste said:
a100/openrecovery-twrp-2.2.2.1-a100.img
renamed to recovery.img and flashed properly.
Same problem. Can it be related to the bootloader number ?
Click to expand...
Click to collapse
That's the only boot loader we can flash on so that's fine. Did you download the image again?
Tapatalked from my Galaxy S II.

pio_masaki said:
Did you download the image again?
Click to expand...
Click to collapse
yes i did , donloaded openrecovery-twrp-2.2.2.1-a100.img,
renamed to recovery.img and flashed without any problem.

I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.

IamModeste said:
I redownloaded and flashed it again,
To no avail...
Nothing else to suggest ? I'd like to use a touch enabled recovery.
Sent from the usual suspects.
Click to expand...
Click to collapse
Did you erase recovery before flashing?

Theonew said:
Did you erase recovery before flashing?
Click to expand...
Click to collapse
Agreed.
I would try again make sure to: 'fastboot erase recovery', then 'fastboot flash recovery recoveryname.img' (make sure it's recovery [space] then the img name).
You can also try Zeronull's 2.1.1/2.2.0 and Linuxsociety's 2.2.2.0. It could be a bad upload of the 2.2.2.1 img

Answer
There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it.
sounds like you may need to start fresh.
Use fastboot to erase the system, boot, recovery and cache, perform a fastboot -w and then install the new recovery and ROM. Erasing the system will kill that recovery file from above.
Let me know. There are a couple of other options that I can think of.
---------- Post added at 06:48 AM ---------- Previous post was at 06:32 AM ----------
Here is what it should look like in fastboot on the command prompt yours will be different of course because mine is setup differently. But basically load up fastboot on windows or whatever you use and first erase the recovery then run fastboot -w and then flash the twrp recovery image and finally fastboot reboot. After reboot hold down volume button and enter recovery as usual. Should work then. My explanation is above. It's the install_recovery.sh file fastboot -w takes care of it! Sorry for bumping and old thread. But it doesn't look like it ever got solved.
Code:
C:\>C:/android/fastboot.exe erase recovery
erasing 'recovery'... OKAY [ 0.733s]
finished. total time: 0.734s
C:\>C:/android/fastboot.exe -w
erasing 'userdata'... OKAY [ 5.480s]
erasing 'cache'... OKAY [ 2.052s]
finished. total time: 7.533s
C:\>C:/android/fastboot.exe flash recovery C:/recoverytwrp.img
sending 'recovery' (4410 KB)... OKAY [ 0.491s]
writing 'recovery'... OKAY [ 0.255s]
finished. total time: 0.746s
C:\>C:/android/fastboot.exe reboot
rebooting...
finished. total time: 0.001s

help with my htc one x

hi guys sorry if i put this in the wrong place but i tried to put the jelly bean on my htc one x on o2 and ive completely messed it up and now it wont boot up its stuck on the o2 screen i don't know what ive done but is there anyway i can get it back to its original state i feel like a complete retard i would be very happy if some one could help me :crying:

What hboot do you have ? And did you flash the boot.img with fastboot commands ?
Can you do fastboot commands
Put the phone in fastboot usb mode and do these commands
Fastboot getvar version-main
Fastboot oem readcid
Post the outcome here please

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Laptop>fastboot getver version-main
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Laptop>
i take it i cant do commands lol
my hboot-1.12.0000
Mr Hofs said:
What hboot do you have ? And did you flash the boot.img with fastboot commands ?
Can you do fastboot commands
Put the phone in fastboot usb mode and do these commands
Fastboot getvar version-main
Fastboot oem readcid
Post the outcome here please
Click to expand...
Click to collapse

Oke 2 mistakes on your side, you dont have the updated hboot to run JB roms and since fastboot commands do not work you didn't flash the boot.img with the commands
Do you have a folder on the pc with adb and fastboot files ? If no
Download this
http://db.tt/ldx3qOOU
And place it like this
C:\fastboot\the files i gave you
And then open a cmd prompt in the folder and do those commands again

sorry for the long wait
it still say waiting for device + i dont think my usb debugging is enabled

Do you have java sdk and the hyc drivers installed ?

Mr Hofs said:
Do you have java sdk and the hyc drivers installed ?
Click to expand...
Click to collapse
(bootloader) DEBUG: cid: O2___001
OKAY [ 0.110s]
finished. total time: 0.110s
C:\Users\Laptop>C:\fastboot\Fastboot getvar version-main
version-main: 2.17.206.2
finished. total time: 0.063s
C:\Users\Laptop>
there we go sorted it

I don't see your ruu on htcruu.com ! You didn't do a nandroid backup before flashing the JB rom ?
Maybe its on file factory but i don't have an account there
I know somebody that has the nandroid backup that you need, he stated the 28th that he was uploading it.
Its in the nandroid backup thread by Matt95 in the general section ! Gonna PM the guy for the nandroid !!! :thumbup:

Mr Hofs said:
I don't see your ruu on htcruu.com ! You didn't do a nandroid backup before flashing the JB rom ?
Maybe its on file factory but i don't have an account there
Click to expand...
Click to collapse
lol so what do i do now lol i aint bothered about jb i just ics back so i can use my hox again
and as for this (You didn't do a nandroid backup before flashing the JB rom) i dont know what you mean so i guess i didnt do it lol

Now lets get a working phone back for you
Do he next please
Download any ICS rom (i can recommend the viper x) and put it on the sdcard of the phone (do that by mounting the sdcard as a usb disk within the recovery) copy the boot.img file from within the rom.zip file and copy it to the fastboot folder
Put the phone in fastboot usb mode and flash the boot.img with this command
Fastboot flash boot boot.img
Fastboot erase cache
Enter the recovery and do a full wipe (do not wipe the sdcard)
Then choose install zip from sdcard and choose the rom.zip and install it ! Reboot and you have a working phone until I have news about the nandroid backup you need, i already sent him a message

Mr Hofs said:
Now lets get a working phone back for you
Do he next please
Download any ICS rom (i can recommend the viper x) and put it on the sdcard of the phone (do that by mounting the sdcard as a usb disk within the recovery) copy the boot.img file from within the rom.zip file and copy it to the fastboot folder
Put the phone in fastboot usb mode and flash the boot.img with this command
Fastboot flash boot boot.img
Fastboot erase cache
Enter the recovery and do a full wipe (do not wipe the sdcard)
Then choose install zip from sdcard and choose the rom.zip and install it ! Reboot and you have a working phone until I have news about the nandroid backup you need, i already sent him a message
Click to expand...
Click to collapse
i do not how to do this you say put it on my sd card how do i that is there any chance you could show me on skype or something matey ?

Sorry mate no Skype here, and I have only my phone now.....but
Can you get into fastboot mode ?
Unplug the cable to the pc
And choose with the volume rocker the HBOOT press 1 time the power button, it loads a second screen and you see the text RECOVERY and navigate to that again and press power button 1 more time , it will start the recovery .....check which version you have (5.4.8.0)
Then select mounts & storage and check the last option .... Mount as usb disk and plug in the cable
Don't worry mate we will get there .... Just stay with me

tommydee90 said:
i do not how to do this you say put it on my sd card how do i that is there any chance you could show me on skype or something matey ?
Click to expand...
Click to collapse
i did what you said and it puts me right where i started again recovery dont work for me

Reflash the recovery , download this one
http://db.tt/Krlm4dPs
Rename it to recovery.img and put it in the fastboot folder on the pc, put the phone back into fastboot usb mode
Do
Fastboot erase cache
Fastboot flash recovery recovery.img
Fasrrboot erase cache
And enter the recovery again !

C:\Users\Laptop>c:\fastboot\fastboot erase cache
erasing 'cache'...
OKAY [ 0.111s]
finished. total time: 0.111s
C:\Users\Laptop>c:\fastboot\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\Laptop>c:\fastboot\fastboot erase cache
erasing 'cache'...
OKAY [ 0.093s]
finished. total time: 0.094s
C:\Users\Laptop>c:\fastboot\fastboot flas recovery recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Laptop>c:\fastboot\fastboot erase cache
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.086s
i pressed recovery again and it takes me back to fastboot.. the htc load screen come on with red writing at the bottom end of it also i have in pink ***relocked***security warning ***

Ah its relocked, that explains it. Can you find back the unlock_code.bin file that you received by the hycdev site when you first unlocked the device ?
Put that file also in the fastboot folder on pc and reboot the phone again into fastboot usb mode
Do
Fastboot flash unlocktoken unlock_code.bin
This will unlock the bootloader and you will be able to flash the recovery .... So try again

Tom,
If you want I will walk not run you through everything buddy. PM me and we can chat on FB or whatever so you not only sort yourself out but you understand too!
Sent from my HTC One X using xda premium

leonforthewin said:
Tom,
If you want I will walk not run you through everything buddy. PM me and we can chat on FB or whatever so you not only sort yourself out but you understand too!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This feels like a small kick in the nuts, you think i ain't helping him the right way
But you can take over and i will enjoy the rest of my evening

Mr Hofs said:
This feels like a small kick in the nuts, you think i ain't helping him the right way
But you can take over and i will enjoy the rest of my evening
Click to expand...
Click to collapse
My bad man, I didn't even think about that. I did the exact same thing when I first messed around with my HOX and I completely panicked. I'm sure after the next reply the issue will be resolved.

leonforthewin said:
My bad man, I didn't even think about that. I did the exact same thing when I first messed around with my HOX and I completely panicked. I'm sure after the next reply the issue will be resolved.
Click to expand...
Click to collapse
No mate you didn't mean no harm, and if its easier for him .... He's has the choice always good that people want to help ! Just messing with ya for a bit

one x 3uk back to stock problem

i neded to flash stock 3uk romy (any) and lock bootloader
i have customn rom and custom recovery
INFODEBUG: cid: H3G__001
version-main: 1.28.771.9
i found solution but maybe its wrong
1.fastboot oem lock
then i have message in bootloader:
https://www.dropbox.com/s/oq8e5ko9p3zexbl/20130213_032052.jpg
and then i downloaded:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed
im in fastboot but i have error 170 problem with connection.
can someone please help me...

lukers said:
i neded to flash stock 3uk romy (any) and lock bootloader
i have customn rom and custom recovery
INFODEBUG: cid: H3G__001
version-main: 1.28.771.9
i found solution but maybe its wrong
1.fastboot oem lock
then i have message in bootloader:
https://www.dropbox.com/s/oq8e5ko9p3zexbl/20130213_032052.jpg
and then i downloaded:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed
im in fastboot but i have error 170 problem with connection.
can someone please help me...
Click to expand...
Click to collapse
so you have fastboot up and running, if you give the fastboot command
fastboot devices
it gives a serial back in the command window ? (your bootloader says fastboot usb, so i guess it should be fine)
how did you execute the RUU, did you execute the RUU with admin rights (right click the ruu.exe and select run with admin rights)

Mr Hofs said:
so you have fastboot up and running, if you give the fastboot command
fastboot devices
it gives a serial back in the command window ? (your bootloader says fastboot usb, so i guess it should be fine)
how did you execute the RUU, did you execute the RUU with admin rights (right click the ruu.exe and select run with admin rights)
Click to expand...
Click to collapse
fastboot devices - back
SH24XW111133 fastboot
ruu as amin
after if have this message relocked security warning if i want use phone i have to:
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
and unlock bootloader ant then my old rom is working but because i want unlock my phone i have from network unlock pin but not working i someone said that i have to back to stock with lock bootloader.
and i cant find answer
why i have this error 170 in fastboot?
this ruu is ok: RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.12 04.103.14H_release_256494_signed?
the only thing i noticed that radio its diffident in ruu then in bootloader. and im using Windows 7 and when im in fastboot windows see phone as fastboot.

The main version matches so that should be fine. What you can try is this :
Flash the stock recovery 1.28 and the stock boot.img back first. Then relock the bootloader and run the ruu again.

Mr Hofs said:
The main version matches so that should be fine. What you can try is this :
Flash the stock recovery 1.28 and the stock boot.img back first. Then relock the bootloader and run the ruu again.
Click to expand...
Click to collapse
i reinstalled drivers and connect to diffrent usb and ruu start but now during process error 155??? The flash fails at checking mid/cid and before that there is image version 1.28.771.0 to image version 1.28.771.0
so i will try
Flash the stock recovery 1.28 and the stock boot.img back first???
i did unpack ruu and from rom.zip recovery and boot from (RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.12 04.103.14H_release_256494_signed)
i did:\
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4282 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
C:\fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (5790 KB)... OKAY
writing 'recovery'... INFOFormat partition SOS done
OKAY
then
C:\fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
C:\fastboot>fastboot erase cache
erasing 'cache'... OKAY
this time no security warning
ant then in fastboot ruu again and error 155 again
thanks for your help

Download this one
http://androidfiles.org/ruu/securek...adio_1.1204.105.14H_release_260888_signed.exe
Try again

Mr Hofs said:
Download this one
http://androidfiles.org/ruu/securek...adio_1.1204.105.14H_release_260888_signed.exe
Try again
Click to expand...
Click to collapse
now its look good
i flashed recovery and boot from this fresh downloaded rom
its stock 3 android 4.0.3
wowwwwwwwwww
can now upgrade to jelly bean?
i checked ota update but is not available from phone,

lukers said:
now its look good
i flashed recovery and boot from this fresh downloaded rom
its stock 3 android 4.0.3
wowwwwwwwwww
can now upgrade to jelly bean?
i checked ota update but is not available from phone,
Click to expand...
Click to collapse
Yeah you should be able to update the phone, try to check a couple of times manually for ota's.

[Q] TIFU going from GPE5.1 Back to Sense, Please help :)

So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!

Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.