Database Develop

After booting aospCMod 2.3.2

So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.

Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App

okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.

i tried also and still no luck .. i hate this

to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.

So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.

I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.

i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!

sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass

il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™

Yeah I'm using clockwork 2.5.0.1.

sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.

So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App

sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH

Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).

got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?

sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!

There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.

mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.

touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help

[Q] having trouble installing custom rom

guys i was able to s-off and root my IS last night with help from alpha rev x.
i then attempted to install custom rom using CWM recovery.
inside recovery i can install the rom fine, it says its installed, aswell as no-sense 1.5 - there are no errors.
but when i go to reboot again, it just sits on the htc boot screen and i have to pull battery to get back into recovery.
please help
is it possible ive bricked my phone??

djbenny1 said:
guys i was able to s-off and root my IS last night with help from alpha rev x.
i then attempted to install custom rom using CWM recovery.
inside recovery i can install the rom fine, it says its installed, aswell as no-sense 1.5 - there are no errors.
but when i go to reboot again, it just sits on the htc boot screen and i have to pull battery to get back into recovery.
please help
is it possible ive bricked my phone??
Click to expand...
Click to collapse
I think it's to do with the radio, someone said that in the alpharevx chat.

did they say how to fix?
is it in the alpharev x thread?
can you link?

how long do you wait for the white htc screen?
I took quite a while for it to load, ill say try reboot and wait for 30 mins
and make sure u have ext4 if the rom require ext4
and i dont think that your phone is bricked

same here...
hi, i am in the same boat as you are. I s-offed through alpharevx, great work btw! I also rooted through superoneclick by means of gingerbreak, also great work! thank these guys so much. Here comes the problem. I downloaded rom manager from the market and installed clockworkmod recovery through that. and i attempted to load a custom rom through the recovery tool. it went fine without any error. however, when i try to reboot, i get the htc logo on white background.... I flashed partition using ext4 formatting tool from here, http://forum.xda-developers.com/showthread.php?t=1088498 , i also flashed the radio specified in this post....but same thing, stuck at "htc"... help...

you have to install 4EXTRecovery_v1.0.6_modded_CWMR_v4.0.0 first. you can find the steps here: http://forum.xda-developers.com/showthread.php?t=1104765. when I tried with just Format_data_partition_EXT4 I got the same results as you

Thank you! I tried the other recovery you mentioned. worked like a charm! Thanks.

once you've flashed, let me know if you still have earpiece volume with the custom rom. And if you do, did you flash a new radio?

gmarcoux said:
once you've flashed, let me know if you still have earpiece volume with the custom rom. And if you do, did you flash a new radio?
Click to expand...
Click to collapse
I lost the earpiece volume too, no matter How I change different Radio, still cannot get it back, now I got a phone cannot make a phone call

kakawong said:
I lost the earpiece volume too, no matter How I change different Radio, still cannot get it back, now I got a phone cannot make a phone call
Click to expand...
Click to collapse
Thats not right ... which rom? If its ARHD ... then did you try the AU radio linked in the first post?
That will surely give you sound on ARHD ...
Sent from my Incredible S using XDA App

Unable to get into Recovery after 4.1.2 upgrade...

Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.

*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!

That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium

MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.

Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .

I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium

There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.

spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.

Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.

the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.

smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.

There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..

I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.

smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.

gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!

I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium

I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)

I am so glad to have found this thread. This problem was beginning to drive me nuts.

[Q] Velocity 4G (VODAP120) boot loop / can't RUU

Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings

deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice

rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!

Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk

rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.

deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk

rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:

is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?

deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk

rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...

deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!

The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One

WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?

Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.

well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?

AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk

If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.

Unable to install any custom Roms

ok my problem is ive tried installing a few different roms VIPERONE being the one i want. when i go to recovery and try installing any custom Roms i get the Succesful FAILED instantly. i tried bad boyz rom based on the 1.54.654.9 version but still no luck. i cannot figure out why this is happening. ive tried with TWRP 2.7.0.0 revcovery as well and same thing happens. i really want ViperONE Rom as i have used it on my previous phones and its the best. anyone having this issue or know why its happening please help. thanks
i have the HTC ONE M8 Harman kardon edition with software version 1.54.654.9 i am htc unlocked, Captains Recovery, rooted, s-off', and SuperCID on stock Rom still
i searched for an answer already but did not find anything on it so sorry if i missed something.

Try to update your recovery to 2.7.0.2
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
Original T said:
ok my problem is ive tried installing a few different roms VIPERONE being the one i want. when i go to recovery and try installing any custom Roms i get the Succesful FAILED instantly. i tried bad boyz rom based on the 1.54.654.9 version but still no luck. i cannot figure out why this is happening. ive tried with TWRP 2.7.0.0 revcovery as well and same thing happens. i really want ViperONE Rom as i have used it on my previous phones and its the best. anyone having this issue or know why its happening please help. thanks
i have the HTC ONE M8 Harman kardon edition with software version 1.54.654.9 i am htc unlocked, Captains Recovery, rooted, s-off', and SuperCID on stock Rom still
i searched for an answer already but did not find anything on it so sorry if i missed something.
Click to expand...
Click to collapse
Here install this and you can try multiple recoveries to see which one works for you. I think that is your problem. Just a side note...you have to use the volume and power buttons to navigate through aroma installer. Hope this helped man. Let me know
http://forum.xda-developers.com/showthread.php?t=2743927
[AROMA][SPRINT]Recovery Switcher[2014-05-07]
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2

Just try capt throwbacks version, you'll find it on the mikmik website or in his signature.
Sent from my 831C using XDA Premium 4 mobile app

FYI, I posted in the other thread he made about the issue and it is indeed a problem with twrp recovery, it is not fully compatible with the hk version for some reason, I "solved" my issue by using philz touch recovery

I am currently running capt. Throwbacks recovery but I will give the other recoveries a try as u suggest. I'll let ya know if I get one to work.

stark1159 said:
Try to update your recovery to 2.7.0.2
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
Here install this and you can try multiple recoveries to see which one works for you. I think that is your problem. Just a side note...you have to use the volume and power buttons to navigate through aroma installer. Hope this helped man. Let me know
http://forum.xda-developers.com/showthread.php?t=2743927
[AROMA][SPRINT]Recovery Switcher[2014-05-07]
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
Click to expand...
Click to collapse
Sorry to thread jack if that's what I'm doing but his issue was probably fixed as he has not updated this and it's touching on an issue I have with Aroma installers....I've tried the Bad Boys, NVProject, Bad Seed (i think) and one or two other Sense ROMS and they all use Aroma installers. Even that Recovery Switcher that uses Aroma I can't get working properly. I believe in many cases the touch screen is supposed to be working but mine will not work nor do that arrow keys + power advance me down the list of options. I can SOMETIMES check the agreement boxes if I hold power and press a bunch of times on the screen while hitting the side buttons, lol. This 'technique' has gotten me almost all the way through an Aroma installation but, inevitably, I end up hitting back instead of finish or can't make anyting but the "about' to come up.
I have no problems installing AOSP and AOKP roms via Philz or the Twrp I was using its only the Sense ROMS/Aroma combo that are giving me trouble....
Currently I am S-OFF and have reverted back to the sense stock rom and taken the OTA which has me up to software version 1.54.654.13.
I am having issues with my 3G and getting stuck in 1xRTT or Roaming constantly but I think this may be a network issue as tens of thousands of acres have burnt to the ground as close as 1 mile from my house this week and Sprint said they had dispatched some technicians to examine some of their structures/tower in southern california......
The only other thing I can think of is that I had to fastboot oem writeCID 11111111 to get the RUU to work...was I supposed to change that to something else afterwards?

slimbrady said:
Sorry to thread jack if that's what I'm doing but his issue was probably fixed as he has not updated this and it's touching on an issue I have with Aroma installers....I've tried the Bad Boys, NVProject, Bad Seed (i think) and one or two other Sense ROMS and they all use Aroma installers. Even that Recovery Switcher that uses Aroma I can't get working properly. I believe in many cases the touch screen is supposed to be working but mine will not work nor do that arrow keys + power advance me down the list of options. I can SOMETIMES check the agreement boxes if I hold power and press a bunch of times on the screen while hitting the side buttons, lol. This 'technique' has gotten me almost all the way through an Aroma installation but, inevitably, I end up hitting back instead of finish or can't make anyting but the "about' to come up.
I have no problems installing AOSP and AOKP roms via Philz or the Twrp I was using its only the Sense ROMS/Aroma combo that are giving me trouble....
Currently I am S-OFF and have reverted back to the sense stock rom and taken the OTA which has me up to software version 1.54.654.13.
I am having issues with my 3G and getting stuck in 1xRTT or Roaming constantly but I think this may be a network issue as tens of thousands of acres have burnt to the ground as close as 1 mile from my house this week and Sprint said they had dispatched some technicians to examine some of their structures/tower in southern california......
The only other thing I can think of is that I had to fastboot oem writeCID 11111111 to get the RUU to work...was I supposed to change that to something else afterwards?
Click to expand...
Click to collapse
The problem is the aroma installer hasn't been updated to be compatible with spirit as of yet. Use the volume up/down to highlight things and power to select. I think it's vol down 4 times and then up once to get to next. You will get the hang of it.
Sent from my 831C using Tapatalk

ok sorry havent updated til now but i have tried all the recoveries in the zip to install multiple recoveries easily and not one of them would work to install viperone rom but i tried bady boyz with them all as well and i was able to get that installed using philz recovery but none of the others worked with it. when i try viperone with any recovery it wont even start up aroma intsaller at all just gives me failed right away in the recovery. so as of now im on bad boyz rom but i want viperone rom im not satisfied with any other. bad boyz is a good rom dont get me wrong i have just used viper since i began rooting my phones and i love it. anyways aroma works for the recovery install zip just fine (other then the touch not working) so i dont knopw if its a recovery issue or something with aroma or possibly viperone rom even i have no clue?. thanks for all ur replies and suggestions everyone ur a big help always. id love to get this solved so i can run viperone rom again as i had on my first H/K M8 that i exchanged for the current one i am using. sorry again took so long to update

Konfuzion said:
The problem is the aroma installer hasn't been updated to be compatible with spirit as of yet. Use the volume up/down to highlight things and power to select. I think it's vol down 4 times and then up once to get to next. You will get the hang of it.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
oh as to the volume/power buttons for selecting the options in aroma. i believe that there is no exact combo to get the selection on the next button. ive had 1 or 2 pages that i only hit down once and it selected next right away and then sometimes it didnt. so it varies on the up down number of times. ive had it not work using down so many times then up once a few times so its hard to really be certain . just my finding about that issue.

Original T said:
ok sorry havent updated til now but i have tried all the recoveries in the zip to install multiple recoveries easily and not one of them would work to install viperone rom but i tried bady boyz with them all as well and i was able to get that installed using philz recovery but none of the others worked with it. when i try viperone with any recovery it wont even start up aroma intsaller at all just gives me failed right away in the recovery. so as of now im on bad boyz rom but i want viperone rom im not satisfied with any other. bad boyz is a good rom dont get me wrong i have just used viper since i began rooting my phones and i love it. anyways aroma works for the recovery install zip just fine (other then the touch not working) so i dont knopw if its a recovery issue or something with aroma or possibly viperone rom even i have no clue?. thanks for all ur replies and suggestions everyone ur a big help always. id love to get this solved so i can run viperone rom again as i had on my first H/K M8 that i exchanged for the current one i am using. sorry again took so long to update
Click to expand...
Click to collapse
Did you try formatting data, cache, and system partitions in any of the recoveries that worked? Or have you tried a RUU (if you are s-off)

metalspring said:
Did you try formatting data, cache, and system partitions in any of the recoveries that worked? Or have you tried a RUU (if you are s-off)
Click to expand...
Click to collapse
i have not tried that in all the diff recoveries actually.
i am s-off and not sure about RUUing at all with this phone. i will give them ideas a try now and report back once done. hope that works.
which RUU would u suggest i try? i am on Bad Boyz Sprint ONE M8 Harman v1.1 rom with build 1.54.654.13. if that matters any.
If u know a link to the RUU thatd be great help and save me a lill time. thanks

Original T said:
i have not tried that in all the diff recoveries actually.
i am s-off and not sure about RUUing at all with this phone. i will give them ideas a try now and report back once done. hope that works.
which RUU would u suggest i try? i am on Bad Boyz Sprint ONE M8 Harman v1.1 rom with build 1.54.654.13. if that matters any.
If u know a link to the RUU thatd be great help and save me a lill time. thanks
Click to expand...
Click to collapse
I know my issue was fixed by using philz recovery, wiping data, cache, and system and then installing a new rom. If the issue is what I think it is, then wiping all the partitions I mentioned should fix it. (I think the issue is related to some file system corruption and twrp not being able to properly handle the corruption, when other recoveries work just fine, so formatting the partition will get rid of the corrupted data)
http://forum.xda-developers.com/showthread.php?t=2729173

metalspring said:
I know my issue was fixed by using philz recovery, wiping data, cache, and system and then installing a new rom. If the issue is what I think it is, then wiping all the partitions I mentioned should fix it. (I think the issue is related to some file system corruption and twrp not being able to properly handle the corruption, when other recoveries work just fine, so formatting the partition will get rid of the corrupted data)
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
i noticed u didnt include the boot partition to wipe.. do i only wipe the partitions u suggested or include the boot as well? sorry just dont want to mess anything up if i can avoid it. thanks again tho for quick replies.

Original T said:
i noticed u didnt include the boot partition to wipe.. do i only wipe the partitions u suggested or include the boot as well? sorry just dont want to mess anything up if i can avoid it. thanks again tho for quick replies.
Click to expand...
Click to collapse
You can wipe boot partition as well, just dont wipe anything you dont immediately recognize (I know philz touch has tons of options to wipe different partitions, and a lot of them probably would be bad to wipe lol)

metalspring said:
You can wipe boot partition as well, just dont wipe anything you dont immediately recognize (I know philz touch has tons of options to wipe different partitions, and a lot of them probably would be bad to wipe lol)
Click to expand...
Click to collapse
ok i wiped said partitions and tried installing viper from philz recovery and twrp recovery and no go same thing happening. almost got worried when i tried rebooting and got the "no OS installed, r u sure?" but i just installed bad boyz again to get going again. im gonna try RUUing cause now i get a message after my phone starts saying something bout inconsistent partitions, u must wipe data partition or phone will be unstable. so gonna just RUU and start from there. do u know by chance if it is possible to create a backup with say twrp recovery and able to restore it with any of the recoveries such as philz or does a backup need to restored using the recovery it was created with? thanks again.
Here is a shot of what I received in philz after attempting viper install. http://i1369.photobucket.com/albums...s/2014-05/IMG_20140519_010012_zpsl8wwj5mi.jpg

ok so i RUUed with the RUU u suggested and then tried installing Viperone rom and still getting the same failed status. i tried restoring my backup i made before attempting these suggestions and it seems they do not restore completely either. errrrr so frustrating! my first M8 i had no problems with root soff recovery or installing viperone... this one is just not going so well. im gonna keep at it tho until i get viperone on my phone. lol

Good news.. I was able to install ViperONEm8 rom finally after all the hassle.
i went to TWRP recovery website and downloaded the TWRP recovery 2.7.0.2 and downnloaded ViperONEm8 1.5.0 version and flashed the recovery and installed the 1.5.0 version without a problem i tried 1.6.0 first but got the failed thing again but 1.5.0 installed no problem. YAYYY!!
Thank you all for your help