[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help - HTC One X

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.

Related

[Q] Stuck on S-Off Screen

Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated
can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed
What would i need for that? That's going into new territory
j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot
to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense
Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse
Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App
Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084
It is still the same.
If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...

Rom Advice / Steps please

Good Afternoon everyone,
Here once again. I have been having lots of problems recently with my phone memory getting low, crashes freezing, un-expected reboots etc. I have been using the same rom for a few months and was fine at first but just broke down. So I went into recovery and did a wipe now when powered on for the first time it doesnt get past boot animation just stay on the screen no matter how many reboots or further wipes. I also got a brand new 32GB Micro SD card for xmas that I haven't used yet so my idea was to get a new cool rom and use the SD card
First of all which rom. Now I know people say try different roms and see which you like but so many roms I dont know what to go for and was wondering for some advice. My requirements are that it is not ICS version as I get a phone upgrade on contract in July and want to leave ICS for a new phone so Gingerbread it is.
Now the rom requirements are:
> HTC Sense, prefferably a latest 3D version but if it doesn't work or very laggy then no.
> Camera needs to be fully working
> USB Tethering
> As much as possible on the SD card to save phone space
> Dont need super battery life but at least something that lasts a day and doesnt drain it
> Music Working nicely
> Not too buggy and fairly stable
Now secondly I still have not got myself familiar with Android flashing etc. If I want to start again from scratch new memory card does anyone know the steps. Is there any plain step by step instructions out there that tells me completly what I need to do as I can get confused quite easily.
Thanks in advance for any responses,
Regards,
Max
For this moment(in my opinion) this is the one from the best ROM for HTC Desire...including everything what you questing...
http://forum.xda-developers.com/showthread.php?t=1315961
Thanks. I was already interested in this rom and you saying that has swayed by boat. The next problem is how to go about it. the first steps appears to be installing EXT4 Recovery but its an APK and they are installed with the phone botted up normally correct? My phone isnt booting only in Recovery Mode which is the clockwork mod (from about 8 months ago)
4ext has an app to download its recovery. If you are s-off, the app will flash the recovery img.
Sent from my HTC Desire using Tapatalk
Ok I beleive I do have S-OFF from previous flashing however I can no longer boot the rom up so what do I do?
I can boot into recovery mode but as soon as I boot normally it just sits on the boot animation completly animated but never going further (left it for 3 hours until battery died) also tried wiping about 5 times after a wipe and I just cannot get it on. So what do I do?
I'll upload it for you (from my sd card).
If you are s-off, you can fastboot flash it (see link to my guides for info on fastboot flash - Forget adb, not relevant...)
Thanks but I am a little confused as to what I am doing.
Is there any step by step?
i have the 4EXT now not installed yet. What about HBOOT, radio rom I have no idea what I am doing in what order now due to my phone not botting :-(
If you don't have 4EXT recovery-reboot phone normally, install this app and update you're recovery from the list...
But if you read above I cannot boot my phone normally!
1.update the recovery(like i say)
2.change the hboot:downolad file PB99IMG.zip, put it on your sdcard, then start the phone in HBOOT mode (VolDown+POWER) to flash(update) the HBOOT.
3.Restart phone in recovery,perform full wipe(format all partition without FAT32)
4.Download file with ROM, put into your SDCARD and reflash...
I am sorry not having much luck. I have put both the EXT4 recoevry zip and the pb99img zip on my memory card rebooted into the boot loader with vol down went into the fastboot option and the only options there are bootloader (takes me back to main screen) reboot, reboot bootloader and power down.
I am so lsot and need my phone working again :-(
max_carpenter said:
But if you read above I cannot boot my phone normally!
Click to expand...
Click to collapse
If you'd bothered to read the fastboot faq I told you to read, you'd know that you fastboot flash from the fastboot screen NOT in Android!
max_carpenter said:
Irebooted into the boot loader with vol down went into the fastboot option and the only options there are bootloader (takes me back to main screen) reboot, reboot bootloader and power down.
Click to expand...
Click to collapse
Again, all in the FAQ you were supposed to read!!!
Sorry missed the link couldnt see one very tired. I appreciate your help. I am looking over it now trying to figure it out.
max_carpenter said:
Sorry missed the link couldnt see one very tired. I appreciate your help. I am looking over it now trying to figure it out.
Click to expand...
Click to collapse
OK good luck, although if you're tired, it may be better to wait until tomorrow. Its not broken so its just a case of remaining calm and doing the required.
Ok I think I got it phone is plugged in with the HBOOT drivers I h ave extracted that EXT4 zip you sent me to the C Drive and I run the following command:
fastboot flash recovery c:\recovery.img
Just wanted to check before I did it.
Hmm ok I have done something wrong :-(
sending 'recovery' (3730 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.004s
Ok I went into FASTBOOT on the phone screen then tried running the command again and I get this:
sending 'recovery' (3730 KB)... OKAY [ 0.676s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.197s
Are you sure you're s-off? Should say on the hboot screen
Sent from my HTC Desire using Tapatalk
Ahh its on damn I am sure it was off. Dont you have to be booted into a rom to get it off though?
Ok so who is clever enough to figure out the mess I am in now then..
1: Custom rom Won't boot even after wipe/several reboots
2: HBOOT Version = PVT1 0.93.0001
3: Radio Version = 5.09.05.30_2
4: Recovery Image is ClockworkMod v2.5.0.7
5: S-ON is set
6: Running the HTC Official RUU returns this error after a little while:
ERROR[140]: Bootloader version error
7: I have been asked to run the following commands with the following files and results are on each line after the = sign:
fastboot erase cache = OK
fastboot oem rebootruu = ... INFO[ERR] Command error !!!
fastboot flash zip C:\rom.zip = INFOsignature checking...
FAILED (remote: not allowed)
fastboot flash zip C:\PB99img.zip = FAILED (remote: signature verify fail)
rom.zip was extracted from the official HTC RUU utility.
Any ideas? At the moment i will be pleased jsut to get back to stock.

Some assistance is requested

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.

Nexus 7 completely bricked?

So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.
Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.
someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.
I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.

[Q] Huawei Ascend Y300: Back to Stock ROM Problems.

Hello,
I need some help, because I can't find any solution on my own.
Short story: I need to go back to stock rom and it doesn't work. I can't flash it via fastboot, and recovery mode doesn't work, because I can't use touch and CWM doesn't work either.
Long story:
This morning I wanted to install a Custom ROM, because I've got problems with RAM and touch lately. I heard that touch might be a software problem, so I thought this could solve it.
After several problems with installing Cyanogenmod, I finally made it, just to find out it doesn't find my sd card, which meant I couldn't load my backuped files onto my phone, which meant it was useless.
When I finally gave up on the sd card problem, I just wanted to go back to stock ROM. I also found out that touch doesn't seem to be a problem caused by software, because it doesn't even work in recovery mode.
So now I can't go back to stock ROM. I downloaded the original version from the Huawei Website.
FIRST WAY: Recovery mode.
I can't make a factory reset, because my touchscreen doesn't allow me to swipe, which is needed in TWRP. CWM doesn't work for me, I've tried it several times, but when I go to recovery mode, I only stay at the "huawei ascend" logo. So TWRP; but this doesn't work because of touch problems.
SECOND WAY: Fastboot.
This should work better. BUT:
for fastboot -w I get this error:
Code:
erasing 'cache'...
FAILED (remote: Command not allowed)
for fastboot erasing cache it's the same.
When I just ignore that and go by fastboot update [file], I get the following:
Code:
sudo fastboot update '/home/laura/Schreibtisch/root/HUAWEI_Y300_firmware%28Y300-0100%2CAndroid%204.1%2CEmotion_UI%2CV100R001C00B189%2CGeneral%20version%29.zip'
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
At the moment I have TWRP installed and no OS, because I can't flash any.
Please help me out! I'm sitting here for eight hours, it's in the evening in Germany and I need my phone.
Thanks!!!
Laura

Categories

Resources