Related
I'm stuck at a nearly 99% brick I think...
I've got an AMOLED Desire from T-Mobile Germany (still branded), with HBOOT 0.80.0000, rooted via Unrevoked and still S-ON.
The phone gets stuck during the boot process when the provider-splashscreen (or HTC-Logo) is shown at the beginning. Only pulling out the battery will shut the phone down.
The same happens when I try to get into Recovery via HBOOT. The only option is to pull the battery.
If I connect the phone via USB and enter Fastboot it is recognized by the computer with the command "fastboot devices".
I can't use ADB, because I can't access the recovery.
I downloaded the right RUU for my provider/amoled/hboot 0.80.0000 Desire (RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed) and extracted the ROM.zip from the installer. I renamed the file to PB99IMG.zip and manually moved it to the SDcard using my computer.
But, when I enter HBOOT the file is recognized and extracted, but then it fails ...due to an "incorrect CID".
The same happens if I manually execute the RUU....exe under Windows with my phone plugged in via USB. (It's error code 131 in the flash program of the RUU....exe).
A very helpful user (cargo) of a german Android forum (www.android-hilfe.de - link to his posting) assumed that my HBOOT is not correctly displayed and I might have a "newer" one than 0.80.0000
This leaves me quite without any option than to flash HTC RUU 2.29.405.5, which brings HBOOT 0.93.0001...(but I may be able to downgrade again.)
But this flash process is only possible if I have a Goldcard, which I actually don't have at the moment
Is there any way to create a Goldcard for my device in my actual position (only fastboot working, no boot to run the system, no adb working, no recovery access)?
Every howto explaining the goldcard crating process requires either working adb or even a running system for apps like "goldcard helper" or being able to use "terminal emulator"
I would be very very thankful for every bit of help
Maybe there is some way
Thanks in advance guys!
I believe that goldcards are specific to the card and not the phone(read it somewere on here) so it should be possible to make one without using your phone.
Sent from my HTC Desire using XDA App
TheGhost1233 said:
I believe that goldcards are specific to the card and not the phone(read it somewere on here) so it should be possible to make one without using your phone.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
As far as I know you need the phone for your goldcard. At least it was said in the tutorial I was following a few months back. You need to connect the phone to get the serial number (through ADB shell) which you will need to hex-reverse and put it on your SD card image.
To be honest, they are more sophisticated methods now (as I read) creating a goldcard, but since unrEVOked, i do not follow that part.
And by the way, why don't you flash the HTC RUU 2.29.405.5? 0.93 HBOOT can be downgraded. But with the latest tools you can S-Off, root & whatever with that HBOOT, too.
I just tried flashing the HTC RUU 2.29.405.5 with the PB99IMG-method.
But I get an error "CID incorrect"
I treid to execute the HTC RUU.exe and I get again error code 131...which means something like "user-ID error"
But I could grab a screenshot of the actual "version" of the RUU...or what is this?
Thanks guys
CID incorrect? Your phone is unbranded or branded? Because I found this:
ERROR [294] : INVALID VENDOR ID
Every device contains a short string that identifies the operator who sold it. Because the same device is sold by different operators, this prevents users from flashing a T-Mobile ROM to a device that was sold by Orange, for example. You probably need to Install a HardSPL or CID Unlock your device.
Click to expand...
Click to collapse
I recommend to find a RUU for your device (e.g Vodafone, T-mobile etc.)
Also:
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
Click to expand...
Click to collapse
If it's saying wrong CID then it's branded, simple as that
1. Boot your phone in fastboot
2. Run the ruu that matches your phone.
You need a T-mobile branded ruu.
You can look here for one that matches. http://shipped-roms.com/index.php?category=android&model=Bravo
I think you can try an UK one, because it is multilingual.
If it is giving you the same errors, then you picked a wrong version.
EddyOS said:
If it's saying wrong CID then it's branded, simple as that
Click to expand...
Click to collapse
well it said "incorrect cid" even with a t-mobile branded ruu :/
If you are rooted, then boot into the bootloader and flash a custom rom. Then create a gold card.
Lennyz1988 said:
If you are rooted, then boot into the bootloader and flash a custom rom. Then create a gold card.
Click to expand...
Click to collapse
Yes, try that too, if you can.
Also use a NOA2SD Rom if you dont have ext partition. Or create one on your PC (if you want to use an A2SD ROM).
How can I flash a Rom using the bootloader?
Simply rename the zipped Image of a custom Rom into "PB99IMG.zip", put in on the SDcard and boot into HBOOT?
Thank you
spaboleo said:
How can I flash a Rom using the bootloader?
Simply rename the zipped Image of a custom Rom into "PB99IMG.zip", put in on the SDcard and boot into HBOOT?
Thank you
Click to expand...
Click to collapse
Yes, if you rooted with unrEVOked. Boot in to recovery (clockworkMOD/AmonRa) wipe all data and flash a CUSTOM rom.
You don't have to rename it, it can be anything as soon as it is .zip
nagypapi said:
Yes, if you rooted with unrEVOked. Boot in to recovery (clockworkMOD/AmonRa) wipe all data and flash a CUSTOM rom.
You don't have to rename it, it can be anything as soon as it is .zip
Click to expand...
Click to collapse
Uhm...flashing a custom rom in general is no problem...but i can't access Recvoery
as described in the initial post of the thread only the bootloader (HBOOT) and fastboot are working.
spaboleo said:
Uhm...flashing a custom rom in general is no problem...but i can't access Recvoery
as described in the initial post of the thread only the bootloader (HBOOT) and fastboot are working.
Click to expand...
Click to collapse
Yeah, sorry, my bad.
Well you can try to falsh it via PB99IMG.zip, but i won't think it work.
your only hope is finding a working RUU. (at least seems to me, if you can access only fastboot).
Hi all, have same trouble with flashing via PB99IMG, but in my case, the device normally loads the firmware and returned to fastbut. When you try to go to recovery device hangs on the logo. Фfter removing the battery and re-attempt to restart the device, it begins to vibrate 7 times and then freezes on the logo. What do these vibration?
PB99IMG.zip will work as you don't need recovery. Just put it on the root of your SD card and boot into HBOOT. It'll find the file and flash it
did renaming rom to pb99img nd flash via hboot work for you?
i have a similar problem, rather same prob, only fastboot available
To let this thread maintain usefullness for future readers:
The solution was to take a goldcard from a friend and flash the right (matching hboot, provider and version) RUU, by using the PB99IMG method.
By this the phone will be set back to it's delivery state! This will include the Rom, all data in the NAND storage the recovery and everything else, which got modified like getting root access or S-OFF etc.
Troubles were caused by USB-Brick or an error on my old ext3 partition or maybe even corrupt data in my Titanium file-backup I restored a few days before the crash :/
I can't clearly say what is the main cause...maybe it was a combination of all.
If you don't have got any chance of getting another goldcard (yes the goldcard creation does NOT depend on the devices! It can be created with ANY android phone ) you are really screwed.
My advice: Always keep a spare microSD card, equipped with it's goldcard image around!
Because I was not able to find any method to echo the CID (Id of the SDcard) in fastboot.
Greetings
And good luck to all of you having comparable issues
Rooted (via Revolutionary) Incredible 2. Was running stock Rom.. Decided to try CM7. downloaded and installed via ROM Manager. MMS didn't work so i tried to restore to my backup via Rom Manager. Now phone sticks at white HTC Screen.
Can get into recovery.
But receive the following error messages:
E: Can't Mount/cache/Recovery/command
E: Can't Mount/cache/Recovery/log
E: Can't Open/cache/Recovery/log
E: Can't Mount/cache/Recovery/last-log
E: Can't Open/cache/Recovery/last-log
INFO:
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO 1.09.01.0622
EMMC-BOOT
When I attempt to restore a backup I get:
Checking MD5 sums...
Erasing boot before restore...
Restoring Boot Image...
Restoring System Image...
Error while Formatting/System!
TRIED FLASHING A COUPLE DIFFERENT ROMS:
FINDING UPDATE PACKAGE
OPENING UPDATE PACKAGE
INSTALLING UPDATE
E: ERROR IN /SDCARD/CCM7_INC2_V1.4ZIP
(STATUS 1)
INSTALLATION ABORTED
Tried Flashing the return to stock PG32img.zip
get these messages:
Loading [PG32DIAG.ZIP]
NO IMAGE!
Loading [PG32DIAG.NBH]
NO IMAGE OR WRONG IMAGE
IT LOADS THE FILE AND I START THE UPDATE.
IT BYPASSES (1) BOOTLOADER
AND THEN STICKS AT (2) BOOT----UDATING
MESSAGES AT BOTTOM OF SCREEN SAY:
DO NOT POWER OFF DEVICE!
CAN NOT ROLL BACK HBOOT VERSION
WILL JUST SAY STAY LIKE THIS FOR HOURS.
Any help to get a working phone would be greatly appreciated. THANKS!!!
Any chance the SD card is corrupted?
card
Not sure, the card seems to work ok in my computer, and I used a different card to try and flash the roms and the return to stock PM32IMG.ZIP. I will try another card when i get one.
Install another recovery... I personally like 4ext. Its in the dev section... also did u nandroid your stock rom before flashing? Try restoring it an verifying it is a correct md5 for the rom and that your recovery is up to date
Sent from my Incredible 2 using Tapatalk 2
I tried 2 different sd cards with no luck. i have 5 or 6 backups but none of them will load. how would I go about install the 4ext recovery?
http://forum.xda-developers.com/showthread.php?p=20013819
Read down where it says if you lost your recovery img... that's how u install it via fast boot
Sent from my Incredible 2 using Tapatalk 2
Hey, this is DroidDev from AndroidCentral. Just incase you didnt see it there:
Seems like corrupted HBOOT or Bootloader to me? Will do some more digging/thinking but it doesnt look good.
When you install the pg32img.zip, which is the stock RUU, you roll everything back to stock. HBOOT, OS, everything, even loosing root. First thing it tried to do is roll back the HBOOT, it if cant do that then you probably have corrupted HBOOT.
In the mean time I would grab the Froyo RUU here and try that:
http://forum.xda-developers.com/show....php?t=1466295
If you were trying with the Froyo RUU, then try the Gingerbread one. The Guide in this thread, if you read it, has instructions on pushing hboot starting at step 11. But I would just do the guide from beginning to end. It will return your phone to complete stock froyo. If successful you can upgrade back to GB.
Click to expand...
Click to collapse
If you cant get the Froyo RUU to install then I would not continue with the guide, could make it worse.
Here is a link to the GB RUU for you.
Turn on your phone and enter the bootloader, select fastboot and plug into your computer. Leave the phone here, then just run the .exe file on your computer. This'll wipe everything including bootloaders, radio, recovery etc. back to stock GB, without relying on your SD card to do the work.
It's worth a shot, while I don't think the SD card is the issue I haven't been able to not recover with an RUU before, from anything
Good luck!
Sounds like flash memory is messed up, I bet all partition sizes read zero, same thing happened to me. I tried to reformat with parted but no luck.I never could find exact sizes for the various mtblk's but my final judgment was that the physical flash memory was fried. dunno maybe if you knew the exact format sizes for everything you could try to push the needed Linux file through adb and try to reformat them one at a time, but I never could get it to work.
On a side note someone on XDA who said they work @ Verizon said they've had a rash of inc2's being turned in with similar problems, maybe a manufacturing glitch
Sent from my 2nd Incredible 2
Ok, so i tried flashing the 4EXT recovery by loading on an sd car and flashing with fastoot. Appeared to install, but still getting same problems. Tried to flash the recovery with abd fastboot from computer...just sticks a writing... never completes. Also tried flashing different backups and ROMS from flashboot with computer, with ROMS I get a message saying their is an error in zip file and can't be read. Tried to install Froyo ROM again via fastboot from SDcard. Just hangs at 2nd 1 saying updating for hrs, never completes. Not sure how to run GB RUU by the exe file? Do i extract the RUU file first? Whenever I have tried to extract those update files in the past i got an error. I'll try and figure it out this afternoon. An interesting side note, CM9 rom appears to install via flashboot from card but never loads upon reboot. Thanks to All for their continuing help!!!
PS...surfing at work and found this post - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ - sounds similar to my problem...basically says partitions on internal storage are messed up and how to use parted to fix. May also try that.
well, tried to install the gb rom exe file. Hung almost from the start, trying to reboot phone into bootloader. I'm at loss. Guess I have a new red paperweight. Not sure how to do parted, so holding off on that for now. Open to any other suggestions.
your using the wrong ruu i think you have to get the latest update, god and i forget the link, go to rootzwiki, jelly belly has what you need or condemned soul on here
My DINC2 is FIXED!
Turn on your phone and enter the bootloader, select fastboot and plug into your computer. Leave the phone here, then just run the .exe file on your computer. This'll wipe everything including bootloaders, radio, recovery etc. back to stock GB, without relying on your SD card to do the work.
It's worth a shot, while I don't think the SD card is the issue I haven't been able to not recover with an RUU before, from anything
Good luck![/QUOTE]
Hey man thank you, I had the same issue as the thread starter and tried all the same methods as he did before searching the forums. Your solution worked for me after getting the latest RUU from jellybelly. This event happened to me randomly, i think the wrong buttons were pushed while my phone was in my pocket. I have a commuter otterbox case and it makes the buttons easier to press. But some tips:
1. verify md5sum
2. i had s-off so I used the latest 2.3.3 ruu file from jellybelly
3. rename downloaded zip file "PG32IMG" only exclude the .zip part like what most folks tell you.. i explain below
i initially renamed the zip "PG32IMG.zip" and stored on the root location of the sdcard, well fastboot/hboot could not find the file, after loading the sdcard back on my computer and clicking the files properties i noticed the the file name was "PG32IMG.zip.zip", after renaming the file to "PG32IMG" the bootloader was able to find the zip file and the process was completed.
4. I do not know about an .exe file, If you can get into fastboot/hboot by holding the "volume down button" + power , that is the method i did
I hope I helped somebody and thanks everybody for yours!
I had similar problems sticking on white with green HTC on it. Mine had to do with the boot.img. I had to extract a boot.img out of a rom put it in folder on C Drive installed rom with 4extrecovery let it load but did not reboot I connect to computer pulled up bootloader with adb and flashed the boot.img and flash reboot and it past that screen and loaded. Had to be unlocked to do it.
daddythree said:
Rooted (via Revolutionary) Incredible 2. Was running stock Rom.. Decided to try CM7. downloaded and installed via ROM Manager. MMS didn't work so i tried to restore to my backup via Rom Manager. Now phone sticks at white HTC Screen.
Can get into recovery.
But receive the following error messages:
E: Can't Mount/cache/Recovery/command
E: Can't Mount/cache/Recovery/log
E: Can't Open/cache/Recovery/log
E: Can't Mount/cache/Recovery/last-log
E: Can't Open/cache/Recovery/last-log
INFO:
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO 1.09.01.0622
EMMC-BOOT
When I attempt to restore a backup I get:
Checking MD5 sums...
Erasing boot before restore...
Restoring Boot Image...
Restoring System Image...
Error while Formatting/System!
TRIED FLASHING A COUPLE DIFFERENT ROMS:
FINDING UPDATE PACKAGE
OPENING UPDATE PACKAGE
INSTALLING UPDATE
E: ERROR IN /SDCARD/CCM7_INC2_V1.4ZIP
(STATUS 1)
INSTALLATION ABORTED
Tried Flashing the return to stock PG32img.zip
get these messages:
Loading [PG32DIAG.ZIP]
NO IMAGE!
Loading [PG32DIAG.NBH]
NO IMAGE OR WRONG IMAGE
IT LOADS THE FILE AND I START THE UPDATE.
IT BYPASSES (1) BOOTLOADER
AND THEN STICKS AT (2) BOOT----UDATING
MESSAGES AT BOTTOM OF SCREEN SAY:
DO NOT POWER OFF DEVICE!
CAN NOT ROLL BACK HBOOT VERSION
WILL JUST SAY STAY LIKE THIS FOR HOURS.
Any help to get a working phone would be greatly appreciated. THANKS!!!
Click to expand...
Click to collapse
I'm having this exact same problem. Did you ever get your fixed? Any new suggestions ??
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
If you have CWM did you made a nondroid backup?
Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.
Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)
Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why
Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA
Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done
@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.
Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse
master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse
master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse
master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse
master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!
Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.
I messed my mobile while trying to flash it using fastboot. Earlier SIM was unable to register on network, and now SIM and WiFi won't show at all.
I have access to TWRP/ADB/FastBoot.
I have tried various solution, but they have failed in one way or another
A) I tried restoring TWRP backup from a file I found on internet, but it didn't fix it.
B) I tried flashall.bat in stock ROM, it fails on modem partition
C) I tried renaming modem partition (NON-HLOS.bin to NON-HLOS.img) and flash it using TWRP but it fails because it's larger than partition size.
D) I tried qboot blank-all, but it is stuck on "Waiting" because Lenovo P2 doesn't show up in serial mode in device manager (I tried EDB cable and also installing all .drivers).
E) I tried QFIL but it complains about missing files.
I'm not sure what to do anymore. Everything has failed me.
VarunAgw said:
I messed my mobile while trying to flash it using fastboot. Earlier SIM was unable to register on network, and now SIM and WiFi won't show at all.
I have access to TWRP/ADB/FastBoot.
I have tried various solution, but they have failed in one way or another
A) I tried restoring TWRP backup from a file I found on internet, but it didn't fix it.
B) I tried flashall.bat in stock ROM, it fails on modem partition
C) I tried renaming modem partition (NON-HLOS.bin to NON-HLOS.img) and flash it using TWRP but it fails because it's larger than partition size.
D) I tried qboot blank-all, but it is stuck on "Waiting" because Lenovo P2 doesn't show up in serial mode in device manager (I tried EDB cable and also installing all .drivers).
E) I tried QFIL but it complains about missing files.
I'm not sure what to do anymore. Everything has failed me.
Click to expand...
Click to collapse
Only solution here I think so is to re flash back the stock rom .
this is the video tutorial from TechXplicit do as he did
https://www.youtube.com/watch?v=-b7bx7Dl17w
VarunAgw said:
B) I tried flashall.bat in stock ROM, it fails on modem partition
Click to expand...
Click to collapse
You need to re-lock your bootloader before using flashall.bat