Greetings to all I'am somewhat new to the android rooting,
I'm more used to to the sprint touch pro roms.But non the less I have successfully
lost track of how I cannot get pass the splash screen.I began using cmw-4.0.1.4
after researching it was ok but found out it was more hassle then nessecary I
finally have what works per the post in the forums.I was able to root it when I
was able to get pass the splash screen .titainium backup, root folder superuser ect...
all worked fine then tried to install the SOS_M_1.4 rom and thats all she
wrote.I was able to install to the very end including MeanROM-ICS-v091-E3D to
the end but couldnt get pass the splash screen after that. I do apologize for
the lengthy request for help I'm lost in the sauce right now
hboot 1.5 S-on
Unlocked
TWRP1.1
su-2.3.6.3zip
blackbolo said:
Greetings to all I'am somewhat new to the android rooting,
I'm more used to to the sprint touch pro roms.But non the less I have successfully
lost track of how I cannot get pass the splash screen.I began using cmw-4.0.1.4
after researching it was ok but found out it was more hassle then nessecary I
finally have what works per the post in the forums.I was able to root it when I
was able to get pass the splash screen .titainium backup, root folder superuser ect...
all worked fine then tried to install the SOS_M_1.4 rom and thats all she
wrote.I was able to install to the very end including MeanROM-ICS-v091-E3D to
the end but couldnt get pass the splash screen after that. I do apologize for
the lengthy request for help I'm lost in the sauce right now
hboot 1.5 S-on
Unlocked
TWRP1.1
su-2.3.6.3zip
Click to expand...
Click to collapse
Ooh HBOOT. In 1.5 S-On , users have difficulty flashing ics ROMs . My only recommendation is , DOWNGRADE !
http://forum.xda-developers.com/showthread.php?t=1563342
Sent from my PG86100 using Tapatalk 2
Comments Withdrawn
I see that was info I wish I knew before I've been at this all day literally small breaks in between I'm currently stuck in a loop I can get into the recovery no problem but having I've tried has lead me here asking for help
Comments Withdrawn
zcink said:
So, not sure what you're saying you can get into recovery? What recovery are you using?
Latest 4EXT?
Can you flash a rom?
Try a 401 rom and if you are using 4ext recovery, you should be all set.
Click to expand...
Click to collapse
twrp1.1 actually
blackbolo said:
twrp1.1 actually
Click to expand...
Click to collapse
Im on the cdma network aswell I think in honesty Ive mixed up the files that are used for the command prompt :crying: so Im really going off of the threads
Comments Withdrawn
zcink said:
Ok well the advise I gave you was sound. From experience.
But you do what you want. Seems you will anyway.
Good luck to ya.
Click to expand...
Click to collapse
okay so you say you had this problem before ? its just im not getting enough detail to go about it I should say Im still new to this
Comments Withdrawn
blackbolo said:
okay so you say you had this problem before ? its just im not getting enough detail to go about it I should say Im still new to this
Click to expand...
Click to collapse
I appreciate the help
blackbolo said:
I appreciate the help
Click to expand...
Click to collapse
ok thanks bro ( when I said I was going off the threads) I didn't mean I was not taking head to your advice I was saying that's how I've been learning about my problem so far
zcink said:
You need to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1561999
When you do it will ask if you are S-On -- say yes. Then when you boot into recovery and flash a rom it will boot one extra time and flash the boot.img for you so you don't have to do it manually.
Flash any CDMA rom with the base 401 and it should boot up all the way for you. Give it time on the first boot, could take up 10 mins or so.
Click to expand...
Click to collapse
thank you again.I how do I install it being that its apk file,i cant access home screen to get it my phone so what other was are there?
I'm having the same problem. I figured out by holding down the power button for 20 seconds when its stuck in the splash screen it will bypass the issue. If that doesn't work pull the battery out and put it back in. Hold down the power button down 20 seconds while it attempts to boot.... hopefully that will get it to boot into what ever Rom you previously flashed. I have flashed, several differant roms, done super wipes, modified wipes, flashed differant recoveries, updated the radio, and I'm still having issues where I get stuck in the splash screen or I have issues where I can't boot into recovery (its a hit or miss after a couple of different approaches)
This all happened after I went from ICS back to GB (mean rom)
Sent from my HTC Flyer using Tapatalk 2
Sent from my HTC Flyer using Tapatalk 2
Comments Withdrawn
I was only trying to help blackbolo boot past the splash screen.
I was only sharing my experience and resolution to my problem with the splash screen and recovery.
I'm not new to this...
When I mentioned recoveries:
I am having issues directly rebooting in to any recovery from bootloader or my rom
I have flashed twrp, 4ext and clockworkmod,one recovery at a time through 4EXT/ root toolbox/rom manager/adb and bootloader. After every flash I attempt to boot into recovery. For the most part each attempt failed where I get stuck in a boot loop or it freezes in the splash screen.
The only success I have had is clockworkmod 5.0.2.0 where I can reboot directly into recovery from my Rom or Bootloader... but I am still have issues booting back into my rom from recovery/initial power on/ bootloader. It gets stuck in the splashscreen or boot loops. I have super wiped and reflashed meanrom, then modified wiped reflashed, reflashed radio...
Either way when my phone reboots it stays in the splash screen till I pull and put back the battery. hold down the power button as it boots showing the splash....
Again I was just sharing what works for me for now till I trouble shoot and figure out what it could be... this used to happen to me when I had my G1 and the MyTouch Slide... there was residual files on the sdcard or partitions that prevented the phone to properly boot...
Sent from my HTC Flyer using Tapatalk 2
Comments Withdrawn
h8dannyboy said:
I'm having the same problem. I figured out by holding down the power button for 20 seconds when its stuck in the splash screen it will bypass the issue. If that doesn't work pull the battery out and put it back in. Hold down the power button down 20 seconds while it attempts to boot.... hopefully that will get it to boot into what ever Rom you previously flashed. I have flashed, several differant roms, done super wipes, modified wipes, flashed differant recoveries, updated the radio, and I'm still having issues where I get stuck in the splash screen or I have issues where I can't boot into recovery (its a hit or miss after a couple of different approaches)
This all happened after I went from ICS back to GB (mean rom)
Sent from my HTC Flyer using Tapatalk 2
Sent from my HTC Flyer using Tapatalk 2
Click to expand...
Click to collapse
I definitely appreciate the consideration I wasn't sure if was all alone I'm still going tru the boot loop as Iam typing now its crazy I'm starting over from scratch to see were I went wrong SDK to TWRP has to be something I missed.that 4extrecovery isnt going to work for me as I haven't found a way to get it installed,as Im stuck at the splash screen looping :laugh:
Comments Withdrawn
zcink said:
Just flash an older rom, any rom for your phone. GB for now. By whatever way you flash now. You have to take the extra step of extracting the boot.img and putting in your tools folder.
Then flash the boot.img from the adb with the command fastboot flash boot boot.img
Once you get a rom to boot all the way up then I recommend installing 4ext recovery touch.
Click to expand...
Click to collapse
ok now that is what I needed to hear thank a million bro ? and I haven't been able to locate a rom that doesn't require a kernel to install or flash to the phone.? which tools folder you speak of I think thats the problem Ive had actually
Related
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
When it asks you to install update, what if you say no, then you should be able to boot into recovery from the bootloader.
Sucks you're having issues.
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
Take the PBxxxx.zip file off of your zip card
I was wondering the same thing; thanks for the info.
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
Can't we do this in adb?
"adb reboot recovery"
g00s3y said:
Take the PBxxxx.zip file off of your zip card
Click to expand...
Click to collapse
Like g00s3y said, you must first remove the file you were trying (or successfully) flashed off your sd card. It's always best to remove this file once youre done with it. In your case you will probably need to use a sd card reader unless you can get your phone to mount.
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
I got the exact same problem
I ran into the same problem last night. I hooked my phone up to my laptop which has adb installed. When you're stuck at the start up screen, in a command prompt just type:
adb devices
You should see your phone show up under devices. If it shows up, then just type:
adb reboot recovery
This will get you into your recovery, and I just started the whole process over again. The 2nd time through everything worked great.
Hope this helps. (my phone wouldn't hard boot in to recovery, which I'm assuming is your problems also)
To hard boot into recovery, just hold the volume up key and turn the phone on. (correct me if I'm wrong)
Now I went and did it!
OK, so I was loading a new ROM and something went terribly wrong. I got stuck on the HTC, quietly brilliant screen. I then tried to boot into recovery thinking I would just restore the back up I had made and for some reason it jumped right to the HBoot and ran through some sequence of commands. Next thing I know I don't have root! So I'm screwing around trying to get adb to work on my computer and having problems with that. I try to recover again on the phone (power button and down volume) and notice that I still have s-off. Doesn't that mean I have root? But I also can't find a super user on the phone and none of my 'rooted' only programs work, they all say I don't have root. What do I do now?
Hboot is vol down and power.. not recovery. What that did was look for an update file on your SD card and flashed it. When you rooted your phone did you use the 1 click root? If so you probably just need to do step 3 again.. which gives you root and the super user app.. hopefully that's all it takes. When your done go into your SD card and remove the PG05 (there's more to the name don't have the whole file name memorized) zip file that's on there so it doesn't happen again
Sent from my ADR6400L using XDA App
BobVS said:
OK, so I was loading a new ROM and something went terribly wrong. I got stuck on the HTC, quietly brilliant screen. I then tried to boot into recovery thinking I would just restore the back up I had made and for some reason it jumped right to the HBoot and ran through some sequence of commands. Next thing I know I don't have root! So I'm screwing around trying to get adb to work on my computer and having problems with that. I try to recover again on the phone (power button and down volume) and notice that I still have s-off. Doesn't that mean I have root? But I also can't find a super user on the phone and none of my 'rooted' only programs work, they all say I don't have root. What do I do now?
Click to expand...
Click to collapse
You will have to re-root now. This should teach you to be more careful and not just go randomly flashing and updating things. Read up some more before just trying things.
Yeah probably like he said your best bet is to re do the whole process.. Idk what you flashed on your phone or anything so just be careful and do your research before jumping into things.
Sent from my ADR6400L using XDA App
castxaway said:
Okay so I installed a gingerbread ROM that keeps getting stuck at the boot screen. Yes, I installed the radio first and took all the correct steps.
But now I'm trying to simply boot into recovery to flash my backup of my other gingerbread ROM that actually worked. I boot into bootloader and it automatically tries updating the radio and there is no possible way to boot into recovery.
I don't know what to do.
Click to expand...
Click to collapse
When flashing a new rom make sure you check the md5sum. You can do this in adb or dl a program, just google it. If the md5sum comes back with the correct number then you know the dl isn't corrupted and you have the correct dl.
But as far as your current problem, you need to re-root.
Research your steps before you do them. I'm NOT a fan of 1-click. If you do it manually, and one step seems not to go right, then stop and ask on the forums. Someone should respond.
So I went to flash to my cell using romrepo.info/wiki/index.php?title=Install_from_Stock_Optimus. I got to step 15, and I realized I forgot to place the ROM in my sd card so I restarted the cellphone so I could place the ROM in my sd card, go to reboot to repeat the process and I get a screen that goes:
Fastboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()
--suspend--
--reset--
--portchange--
--reset--
--portchange--
fastboot: processing commands
Its a blue screen. I just want to flash this Any guides to get me out of this?
http://forum.xda-developers.com/showthread.php?t=1088046
Sent from my LG-P500 using Tapatalk
In the above guide replace optimus one recovery with optimus v.
Sent from my LG-P500 using Tapatalk
Can someone post a link to a recovery file for my phone? You guys are the best.
I followed the above guide, and used the ROM here prepaidandroid.org/index.php?title=How_to_restore_your_Optimus_V_to_almost_original_condition
It reboots, and the same blue screen is up
My brother flashed the wrong recovery, I tried using the tutorial to fix it using fastboot.exe from windows, but it won't work as it can't find the device. windows sees an android device and I installed the drivers from lg, but it refuses to enumerate in adb shell, so I can't connect to it, any ideas?
okay after fiddleing with it a bit, I got the origional recovery mode restored on it, and when I boot into recovery and plug in usb adb can see the device, I have a stock froyo rom how do I restore from here, or can I reflash clockwork from here?
MtDewFella said:
okay after fiddleing with it a bit, I got the origional recovery mode restored on it, and when I boot into recovery and plug in usb adb can see the device, I have a stock froyo rom how do I restore from here, or can I reflash clockwork from here?
Click to expand...
Click to collapse
Can you get me to where you are? Step by step would be nice
Not sure what recovery files I need or ROM I need or anything, or how to use adb. I've been looking online for the past 3hrs on this stuff.
kaivorth said:
Can you get me to where you are? Step by step would be nice
Not sure what recovery files I need or ROM I need or anything, or how to use adb. I've been looking online for the past 3hrs on this stuff.
Click to expand...
Click to collapse
go to this page
this only works if you have some sort of custome recovery, My brother had the wrong one for the optimus v (clockworkmod 3.2.0.0) and it wouldn't install any rom.
I just played around with this page until I got the stock bootloader/recovery back, however I'm not sure if this is what we want, you may want to try flashing one of the custom recoveries listed on the site, now that I have the stock I can re-flash anything.
MtDewFella said:
go to this page
this only works if you have some sort of custome recovery, My brother had the wrong one for the optimus v (clockworkmod 3.2.0.0) and it wouldn't install any rom.
I just played around with this page until I got the stock bootloader/recovery back, however I'm not sure if this is what we want, you may want to try flashing one of the custom recoveries listed on the site, now that I have the stock I can re-flash anything.
Click to expand...
Click to collapse
How did you get the stock recovery working though thats what I need. I can't get into any recovery.
kaivorth said:
How did you get the stock recovery working though thats what I need. I can't get into any recovery.
Click to expand...
Click to collapse
you need to get into a custom recovery, optimus v press back, volume up and power at the same time to boot into a recovery, if you don't have a recovery at all there maybe an issue. so try and boot into a recovery and let me know what you have.
MtDewFella said:
you need to get into a custom recovery, optimus v press back, volume up and power at the same time to boot into a recovery, if you don't have a recovery at all there maybe an issue. so try and boot into a recovery and let me know what you have.
Click to expand...
Click to collapse
Nothing happened. Just that blue screen.
Looking in my SD card I noticed I have a backup of the recovery-clockwork-3.2.0.0-vm670 file. This anything helpful?
kaivorth said:
Nothing happened. Just that blue screen.
Click to expand...
Click to collapse
if you can't get into any recovery your device maybe permintally bricked, but don't take what I say as gospel I'm new at this as well, I'm still looking up more info, in the mean time you need to figure out how to get into recovery, google for key combos, also when using a key combo to get into recovery make sure power is the last button you press in the combo, hold down the others then power (while still holding the other buttons) and release as soon as you see the lg logo, it should go away quickly and after a few seconds of black you'll see the recovery, if the lg logo stays up for a while it's trying to normal boot.
kaivorth said:
Looking in my SD card I noticed I have a backup of the recovery-clockwork-3.2.0.0-vm670 file. This anything helpful?
Click to expand...
Click to collapse
you don't want that version of clockwork, that's what my brother flashed and that started this whole mess
MtDewFella said:
if you can't get into any recovery your device maybe permintally bricked, but don't take what I say as gospel I'm new at this as well, I'm still looking up more info, in the mean time you need to figure out how to get into recovery, google for key combos, also when using a key combo to get into recovery make sure power is the last button you press in the combo, hold down the others then power (while still holding the other buttons) and release as soon as you see the lg logo, it should go away quickly and after a few seconds of black you'll see the recovery, if the lg logo stays up for a while it's trying to normal boot.
Click to expand...
Click to collapse
I think if I can get adp to recognize this device I can fix it. Fastboot recognizes this, but adp doesn't. Is there a special adp driver maybe lol?
Got a little bit of progress....did a full system flash using fastbootroot and NVM OMG its fully booted! wow never thought I'd see the homescreen again...now to try to flash it again hahahaha
Now what verison of recovery and rom should I be looking at?
kaivorth said:
Got a little bit of progress....did a full system flash using fastbootroot and NVM OMG its fully booted! wow never thought I'd see the homescreen again...now to try to flash it again hahahaha
Now what verison of recovery and rom should I be looking at?
Click to expand...
Click to collapse
if you want to get aospCMod on your phone, follow this tutorial, this is what I did for my phone works great.
Now my question to you is how did you use fast boot root tool to get back to home screen because I'm still stuck at recovery
okay I finally managed to fix it, I figured out how to use fast boot root and got a custom recovery, from there I could flash other recoveries, which was importaint because even though I could install any rom I wanted it was stuck in a boot loop where it would keep booting into recovery, So i flashed Xionia_CWMA_12518.4_VM_Recovery.zip from here and under advanced it has an option to fix the boot loop, then from there I could flash a rom and it's fixed.
Lot of work fixin' my first bricked phone, but I learned alot.
Maybe somebody can help me with this. I went through all the steps to unlock the bootloader and root the phone using Lokifish Marz guide(very helpful by the way). and now when you boot the phone up in the top left of the screen is the word unlocked.
However, when I go through the process of moto-fastboot. it acts like it's working just fine,erase recovery...OK, Sending Recovery.... OKAY, writing Recovery.... OK. but when I go to boot into recovery (power+volume down, scroll down to Android recovery and hit volume up) I get the Triangle with a !.
To make matters even more confusing, is I have got it to boot up to CWM. I did a full back up on internal, including web top and I thought I was good. I had to run to the grocery store so I booted my phone back up for the time being and went and did my errands, came back and booted into recovery(with the above way.) and bam! triangle, !, android guy.
I've done this a couple times. I'm assuming I'm doing something wrong however I can't seem to find anybody else that has had the same problem. I've held of on trying to flash a different rom, so I'm still running stock rooted.
I'm running Android Ver. 2.3.4 Build 198_6 and I've tried flashing a coule diffent versions of recovery3 including the one that came with Root-Unlock-Recover.
Anybody have any ideas?
I also have the same problem with my motorola photon. i went thru the steps
to unlock the bootloader it said it was unlocked i checked to make sure i was rooted with root check and it said i was. but when i power the phone on and boot i can see android recovery but when i select it the menu is not there just
a triangle and the android symbal, then i have to pull the battery to restart
it does and the phone seems to be working ok.
Well it make me feel better that im not the only one. What tools did you use to unlock your boot loader?
Sent from my MB855 using Tapatalk
What version of stock did you guys start with? I think there was an USCC OTA that IIRC locked up the boot loader on the Electrify.
Sent from my MB855 using xda premium
Started with Android Ver. 2.3.4 Build 198_6 , its the same one that's on there right now. and it's saying my boot loader is unlocked, I actually went through the fastboot unlock process again to check and it said it was already unlocked. Although I just tried flashing twrp recovery and the same thing happened, so it seems to be behaving like it flash's the new recovery but it doesn't.
Strangely though, I've been able to get into Clockwork Mod once or twice, but as soon as I reboot, and to go to recovery it takes me to triangle !, is that just stock recovery/bootloader? So basically CWM is a one time use then back to fast-boot to try again and again.
maybe I should look into re-locking and just going with a boot-strap?
So with some more Tinkering it seems I can get to ClockWorkMod so long as I don't reboot my phone all the way.
if I flash clockwork mod. pull the battery and boot into CWM it works fine, but if I fastboot reboot all the way it goes back to stock recovery. I'm beginning to think the boot loader isn't really unlocked even though it says it is.
Anybody else heard of this?
I have the same problem
please help me what to do
an9093 said:
I have the same problem
please help me what to do
Click to expand...
Click to collapse
READ THIS
and then
READ THIS
an9093 said:
I have the same problem
please help me what to do
Click to expand...
Click to collapse
I end up posting over in the developers form and the problem appears to be the file install-recovery.sh inside system/etc
I posted how I fixed it and somebody else also posted. check down at the bottom.
http://forum.xda-developers.com/showthread.php?t=1468978
Well I've really done it this time. The phone will not power up at all. Ever since the whole Google Maps Rebooting issue the phone has been worthless. It hasn't been able to be turned on in a week. Just black screen. Before it completely failed it would boot, but after about 10 seconds it would restart or power off.
I have a feeling that the battery is not charging. When I plug it in to charge the orange battery led lights up but for only a couple of seconds and then it turns off. Maybe I need to get an external charger or something to charge my battery.
I would love to send the phone back for warranty, but I'm unlocked and rooted, so I am afraid that they won't help me out with warranty. Also, I would love to sell the phone, but obviously I'm not going to sell a phone that doesn't work.
If I could just get the phone to turn on so I can get some of my personal documents off of it that would be great. For some reason the phone stopped syncing contacts a few months ago and I need to get these off of the phone. Anyway. Any help would be appreciated. Thanks for any help/ideas.
Have you tried putting in a new battery? Also what recovery did you have on your device?
HTC Rezound
luis86dr said:
Have you tried putting in a new battery? Also what recovery did you have on your device?
HTC Rezound
Click to expand...
Click to collapse
I haven't tried a new battery. I don't have one. I might have to get one or an external charger.
I am using CWM touch. Yeah, I have read on here that CWM is crap for the rezound.
currentsupply said:
I haven't tried a new battery. I don't have one. I might have to get one or an external charger.
I am using CWM touch. Yeah, I have read on here that CWM is crap for the rezound.
Click to expand...
Click to collapse
there's your problem. the touch recovery will not allow the phone to charge when its 100% dead.
let me find the thread you need to bring it back to life
EDIT: follow this guide and report back please
http://forum.xda-developers.com/showthread.php?t=1711408
edit2: here is a mini ADB and fastboot zip i have. it will give you the tools you need if you dont have them of course. link
synisterwolf said:
there's your problem. the touch recovery will not allow the phone to charge when its 100% dead.
let me find the thread you need to bring it back to life
EDIT: follow this guide and report back please
http://forum.xda-developers.com/showthread.php?t=1711408
edit2: here is a mini ADB and fastboot zip i have. it will give you the tools you need if you dont have them of course. link
Click to expand...
Click to collapse
Thanks for you help. I will try this as soon as I get home this evening. I will report back, thanks again...
currentsupply said:
Thanks for you help. I will try this as soon as I get home this evening. I will report back, thanks again...
Click to expand...
Click to collapse
you're welcome.
on a side note, if you like touch recovery and that's why you chose CMW touch, the TWRP is a good alliterative. LINK
synisterwolf said:
there's your problem. the touch recovery will not allow the phone to charge when its 100% dead.
let me find the thread you need to bring it back to life
EDIT: follow this guide and report back please
http://forum.xda-developers.com/showthread.php?t=1711408
edit2: here is a mini ADB and fastboot zip i have. it will give you the tools you need if you dont have them of course. link
Click to expand...
Click to collapse
Lol just checked thread when I got home. Beat me to it.
HTC Rezound
Ok, I did that trick and I am back in business. Thanks for your help. Now I need to figure out how to go back to stock. I would like to install the RUU file, stock ota file.
I am looking for instructions on how to do this. I know there are many threads covering this, but not very many good answers.
currentsupply said:
Ok, I did that trick and I am back in business. Thanks for your help. Now I need to figure out how to go back to stock. I would like to install the RUU file, stock ota file.
I am looking for instructions on how to do this. I know there are many threads covering this, but not very many good answers.
Click to expand...
Click to collapse
here is the global ruu http://bit.ly/RaKEAr, instructions are on mostly on rom's on how to do this. very simple to do!
i followed nil's 6.1 version to do it.
abrego47 said:
here is the global ruu http://bit.ly/RaKEAr, instructions are on mostly on rom's on how to do this. very simple to do!
i followed nil's 6.1 version to do it.
Click to expand...
Click to collapse
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Rename to PH98IMG.zip, put on the root of the external SD, boot to bootloader and it will do the rest automatically. Make sure you delete the file from the SD after you're done so you won't have trouble in the future.
EDIT: It might reboot two or three times during the installation and look like it's doing some things multiple times. That's normal, so don't panic.
currentsupply said:
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Click to expand...
Click to collapse
Rename to PH98IMG.zip and flash in boot loader.
currentsupply said:
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Click to expand...
Click to collapse
Flashing the RUU will get you phone back to 100% right out of the box stock.
it will update your hboot to 2.27 and lock it.
it will wipe internal storage.
it will give you global firmware and kernel.
all you need to do is relock the device via fastboot command " fastboot oem lock"
then place zip on root of the sd card and rename it to PH98IMG.zip
boot into hboot and it will detect it.
first flash will update hboot, firmware, kernel, splash, radio
it will reboot automatically. (back to fastboot)
then go back to hboot and let it run one more time. (this will take a while as its wiping, formatting, then installing system files)
after its all complete it will boot the phone into the os.
Ok, I'm going to go for this tonight when I get off work.
Hopefully the RUU OS stops the rebooting problem I am having. I am currently running Scott's Clean ROM. I was working great since about May, but now even after a few wipes and re-installs, it still has the reboot bug. Phone won't stay on for longer than 5 minutes and it continually reboots and quickly drains the battery. Basically it is unusable. I was able to flash Amon Recovery and that did fix the charging issue, but it didn't help with the reboots.
Hopefully after the RUU it's back to stable.
currentsupply said:
Ok, I'm going to go for this tonight when I get off work.
Hopefully the RUU OS stops the rebooting problem I am having. I am currently running Scott's Clean ROM. I was working great since about May, but now even after a few wipes and re-installs, it still has the reboot bug. Phone won't stay on for longer than 5 minutes and it continually reboots and quickly drains the battery. Basically it is unusable. I was able to flash Amon Recovery and that did fix the charging issue, but it didn't help with the reboots.
Hopefully after the RUU it's back to stable.
Click to expand...
Click to collapse
It should, Scotts Rom is to old. Once you do the ruu, do a clean install of a newer Rom
Sent from my iPhone...
So far so good. Thanks for your help guys. Right now it is loading the ph98img.zip in the hboot,
checking..[ph98img.zip]
Androids on Skateboards on bottom of screen ****RELOCKED**** in purple on top
Do I want to start update it asks.. Vol Up for yes
it's going through the list. screen goes black.... waiting..... back on
HBOOT IS UP AGAIN LOOKS LIKE IT'S STARTING OVER.... AGAIN LOADING....[PH98IMG.zip]
Vertical status bar on right upper again going through loading....
again Checking..[PH98IMG.zip]
..... Waiting ......
Update is in progress.....
Do not power off the device!
stayed at system for a while... now Update Complete, press power to reboot.. ok
htc on white
beats logo
4G LTE logo
and.......
WAITING..... AND I'M IN.. HELL YEAH.. CROSSES FINGERS FOR NO REBOOTS!
currentsupply said:
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Click to expand...
Click to collapse
it depends if you are s-on or s-off?
currentsupply said:
WAITING..... AND I'M IN.. HELL YEAH.. CROSSES FINGERS FOR NO REBOOTS!
Click to expand...
Click to collapse
giggidy.
Let us know if you need anymore help.
I've been going from AOKP to CM 10.1.3 stable a few days ago.
After about two days of no problems at all, my phone all of a sudden went really hot (like 58°C), battery drained from almost full to complete empty within less than two hours. I didn't install any new apps or flashed any updates.
I switched it off, turned it on again, but the battery drain continued. After being drained, it wouldn't boot to system and wouldn't charge for a whole while, saying "2%+" in TWRP for ages.
The problem now is, when I push the power button to turn it on, it doesn't react for about 2 to 5 minutes, then all of a sudden shows the HTC logo for another five minutes, then shows the CM bootanimation for another 5 to 10 minutes. If it finally finishes booting, I can use the system with almost no problems.
Flashing another version of CM (latest snapshot) and the matching kernel didn't help.
Can it be, that my bootloader is somehow corrupt?
Could it be a hardware issue like faulty memory?
Any ideas would be very welcome.
Thanks
19Uhr30 said:
I've been going from AOKP to CM 10.1.3 stable a few days ago.
After about two days of no problems at all, my phone all of a sudden went really hot (like 58°C), battery drained from almost full to complete empty within less than two hours. I didn't install any new apps or flashed any updates.
I switched it off, turned it on again, but the battery drain continued. After being drained, it wouldn't boot to system and wouldn't charge for a whole while, saying "2%+" in TWRP for ages.
The problem now is, when I push the power button to turn it on, it doesn't react for about 2 to 5 minutes, then all of a sudden shows the HTC logo for another five minutes, then shows the CM bootanimation for another 5 to 10 minutes. If it finally finishes booting, I can use the system with almost no problems.
Flashing another version of CM (latest snapshot) and the matching kernel didn't help.
Can it be, that my bootloader is somehow corrupt?
Could it be a hardware issue like faulty memory?
Any ideas would be very welcome.
Thanks
Click to expand...
Click to collapse
yes CM 10.2 (M1 Snapshot) has a LONG boot as does the nightlies due to a change i made for it to run smoother. but supply me with a log anyway of boot.
Lloir said:
yes CM 10.2 (M1 Snapshot) has a LONG boot as does the nightlies due to a change i made for it to run smoother. but supply me with a log anyway of boot.
Click to expand...
Click to collapse
Thanks for the quick reply, Lloir.
Is the time it takes my phone from pushing the power button to showing the HTC logo in any way related to the ROM it's running?
I've attached a log. There are many different (driver-) problems of which I'm not sure they are related to my initial problem.
Thanks for your help.
19Uhr30 said:
Thanks for the quick reply, Lloir.
Is the time it takes my phone from pushing the power button to showing the HTC logo in any way related to the ROM it's running?
I've attached a log. There are many different (driver-) problems of which I'm not sure they are related to my initial problem.
Thanks for your help.
Click to expand...
Click to collapse
power button > logo nope, but that can take a little bit anyway. my device takes SOMETIMES around 5-10seconds to display anything
Lloir said:
power button > logo nope, but that can take a little bit anyway. my device takes SOMETIMES around 5-10seconds to display anything
Click to expand...
Click to collapse
5-10 seconds is what I was used to before yesterday. Now it's more like several minutes.
Any ideas? Could reflashing the bootloader help? Erasing boot partition and reflashing?
19Uhr30 said:
5-10 seconds is what I was used to before yesterday. Now it's more like several minutes.
Any ideas? Could reflashing the bootloader help? Erasing boot partition and reflashing?
Click to expand...
Click to collapse
Bootloader and boot partition are 2 diffrent things. Boot partition stores the kernel. I doubt your bootloader is corrupt as your phone wouldnt even switch on if it was.
The only way to reflash bootloader with S-On devices is finding a compatible RUU.
Sent from my HTC One X+ using Tapatalk
AndroHero said:
I doubt your bootloader is corrupt as your phone wouldnt even switch on if it was.
Click to expand...
Click to collapse
Makes sense. I'm S-OFF btw.
When I flash a boot.img, does it overwrite the boot partition? Would it make sense to fastboot erase boot first?
19Uhr30 said:
Makes sense. I'm S-OFF btw.
When I flash a boot.img, does it overwrite the boot partition? Would it make sense to fastboot erase boot first?
Click to expand...
Click to collapse
Yeah when you flash a boot.img it overwrites boot partition. there is no real need to wipe boot before flashing a new kernel, but if you want to try it, it will cause no harm.
Sent from my HTC One X+ using Tapatalk
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
AndroHero said:
Yeah when you flash a boot.img it overwrites boot partition. there is no real need to wipe boot before flashing a new kernel, but if you want to try it, it will cause no harm.
In theory if you have S-Off, you could try reflashing bootloader. But be warned this is a last resort method. AFAIK Jtag is disabled with Tegra 3 so if something did go wrong, you would have a permanent brick.....
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC One X+ using Tapatalk
AndroHero said:
In theory if you have S-Off, you could try reflashing bootloader. But be warned this is a last resort method. AFAIK Jtag is disabled with Tegra 3 so if something did go wrong, you would have a permanent brick.....
Click to expand...
Click to collapse
Thanks for the warning and your help. Will try a few last things first. Flashing a RUU will change the bootloader without the risk of bricking my phone?
Have you any other thoughts or opinions on this issue?
Alright, so I ended up wanting to run the RUU to return to stock.
Now the damn problem is, as I start running it, it reboots the bootloader first and waits for the phone. But as it takes my phone ages to reboot, the software stops with a connection error after one minute or so.
What can I do?
After relocking the bootloader, my fastboot is showing me a security warning and won't boot to system or recovery any more.
Is it finally dead?
Sent from my Nexus 7 using xda app-developers app
19Uhr30 said:
Alright, so I ended up wanting to run the RUU to return to stock.
Now the damn problem is, as I start running it, it reboots the bootloader first and waits for the phone. But as it takes my phone ages to reboot, the software stops with a connection error after one minute or so.
What can I do?
After relocking the bootloader, my fastboot is showing me a security warning and won't boot to system or recovery any more.
Is it finally dead?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If u have a custom ROM installed and locked bootloader u will get the security warning
[email protected] said:
If u have a custom ROM installed and locked bootloader u will get the security warning
Click to expand...
Click to collapse
Thanks, that's what I noticed. Do you know how to remove or reset it?
19Uhr30 said:
Thanks, that's what I noticed. Do you know how to remove or reset it?
Click to expand...
Click to collapse
U can unlock it again and flash custom recovery to install any custom ROM .....or if ur hboot is 1.35 u can run RUU and return to stock
if ur hboot is not 1.35 u got no other choice than unlocking ur bootloader
[email protected] said:
U can unlock it again and flash custom recovery to install any custom ROM .....or if ur hboot is 1.35 u can run RUU and return to stock
if ur hboot is not 1.35 u got no other choice than unlocking ur bootloader
Click to expand...
Click to collapse
Thanks for the summary. But sadly the first solution doesn't solve my problem and the second solution doesn't work because of my problem.
Okay, I found something interesting here:
http://forum.xda-developers.com/showpost.php?p=32574569&postcount=2
It says, I can fetch the ROM, the RUU wants to flash and flash it manually in HBOOT. I found the ROM and I think it would go round my problem with the 5 minutes of boot time.
Does anybody know, if this would work with my enrc2b?
Any dangers with using this method?
And most importantly, how will I have to name the file?
Alright, so I managed to return to stock now with the appropriate RUU, sensor problems and camera crash persist. But at least, I can return it to HTC for service now.
Here's how I got the RUU to run:
First, after running the .exe, I accepted the warning screen. Then I went to C:\Users\_user_\AppData\Local\Temp\ where I found a temporary folder, created by the RUU. It looked like this on my computer {C528E446-42D4-4210-B236-35BE15A71702} and it contains a dotnetinstaller.exe.
There is also a subfolder, where I found a ARUWizard.ini. Checking this out, I could change the values for "UpdateTimeout" and "VerifyTimeout" to way more than the default 90 seconds. This indeed helped. After saving the .ini, I went through the rest of the RUU.
The software was now waiting long enough for my phone to boot. But obviously there was another problem, since the update wouldn't run.
I remembered that after a reboot, I sometimes had to unplug the USB cable once and plug it back in for the connection to work and to see my device under fastboot devices.
I did this, while the black HTC screen was showing up and finally, the RUU went through the whole update process.
Thanks for all the support!