Okay, so I have everything flashed and Cyanogen's mod is working. However I decided to flash the radio as well. On entering recovery, it is now stuck at the loading screen (with the 4 color X's). Is this normal after flashing radio? I read that you are supposed to be patient and not remove the battery after flashing radio. How long does it usually take? It has been on this screen for about 20 minutes now.
How did u flash the radio? Did u do it from recovery? Normally after initiating flashing radio through recovery, it will extract the package, then reboot and install the new radio, THEN reboot again.
It's hard to say where u might have gone wrong without more info.
I flashed from fastboot using "fastboot flash radio radio.img". It said done on the two lines (Flashing and writing?). Anywho, I decided to go ahead and boot to the recovery to install my gapps. This is when it got stuck on the 4 color logo X. It is still there.
Can you go into the bootloader, or the recovery console? I just want to know if you have bricked your phone or not, if you haven't - then I recommend you just try wiping everything (as usual) and reflashing the ROM. If that doesn't work, at least I tried to be helpful.
Well I haven't removed the battery and tried rebooting yet. Should I?
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
cicrockets said:
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
Click to expand...
Click to collapse
I would recommend downloading the radio in a .zip format made to flash through recovery... that's the most reliable in my experience...
Thanks, I might try that next time. Too much suspense in one day pour moi.
Related
Ok, let me start off by saying my phone is currently not bricked. I can get into recovery(H+P) or fastboot(C+P) just fine. My problem lies with the last step of rooting when I flash the new ROM. I am currently trying to flash v4.2.15.1 which is apparently the latest Cyanogen Mod.
Now I've tried two different methods and both won't boot after the ROM is flashed.
The first method is "method B" seen over at the AndroidAndMe website. This method works fine and I can get back into the phone all the way to the point of flashing the SPL and then the ROM. It installs fine, but after reboot it gets stuck on the G1 startup screen.
The second method is the wiki guide for updating from original OS to Cyanogen. This one is a bit different using the Android 1.6 base image. The installation on this method goes smooth up untill the last reboot after flashing the ROM just as the other method. The difference here is instead of it hanging at the G1 startup screen, it get's just past that to a blank backlit screen. No images, no android logo, no sound, no nothing.
Like I said before, I can still access recovery and fastboot which seams to be my only way out. I have repeated this process multiple times on both methods with the exact same results. Fastboot keeps bringing me back to the Android 1.0 firmware(RC29) which is atleast giving me access to a phone while I try to figure this out.
Suggestions? Ideas? I really need to get this phone working again.
I am always on AIM "DeathstarsOG" if that is more convienient for those offering up some help.
What steps did you take to flash the rom?
Did you read the steps outlined in his wiki? The most important step is to flash DRC83_base_defanged.zip first, then his rom over the top.
dbl post sorry.
evilkorn said:
What steps did you take to flash the rom?
Did you read the steps outlined in his wiki? The most important step is to flash DRC83_base_defanged.zip first, then his rom over the top.
Click to expand...
Click to collapse
I followed the steps on both writeups exactly how they were written. As far as the wiki one, I already had a few of the files needed from trying the Androidandme method. Also, my phone is basically already downgraded to the RC29 so thats another step i can skip. All needed files are already on my SD card and were installed in the following fashion:
DREAIMG.nbh
cm-recover-1.4.img
DRC83_base_defanged.zip
update-cm-4.2.15.1-signed.zip
ota-radio-2_22_19_26I.zip
My SD card is already formatted to FAT32
I set up the telnet to get access to recovery mode, wipe phone, then install DRC83, then the cm-4.2.15.1 and lastly the radio. I do a Home+Back reset after installing the radio and it goes past the G1 Startup screen, to a black lit screen of nothingness.
If you're looking at the wiki guide named: "Full Update Guide - G1/Dream Firmware to CyanogenMod" you'll see I basically am supposed to be seeing a update screen that loos like a open box with an arrow pointed down toward a phone after I do this reboot. Well, that doesn't happen. It just goes to that black screen.
Now I'm not a whiz when it comes to stuff like this however I can figure things out fairly sufficiently for the most part. But this has got me stumped. It sounds like I may have a corrupted version of Cyanogen as everything else I have been able to install and actually run on the phone(besides the DRC83). Or maybe I need to flash the radio before the DRC83? I haven't even gotten to the SPL, and after all this I may not want to.
I've done this process over and over atleast 8 times and I feel like I basically know every step by heart, but I still don't want to just guess at what it could be and risk a brick. So that's why I'm here. What do you guys think could be the issue?
Do not wipe the phone after istalling RC29. nbh file rewrites everything, and I mean it... everything.
Here's your order:
DREAIMG.nbh
Boot, sign-in, obtain root (telnet, connect to local host, you know the shpill).
Flash recovery (use ra 1.6.2, it's more updated then cm 1.4)
Wipe
Flash DRC83 defanged.zip
Flash ota radio, follow directions on the screen, you will need to reboot at least once
Flash 1.6 rom (cyan's is a good one to start at least)
Fix permissions.
Wipe
Reboot
Do not set-up linux swap or apps2sd at this time, it will complicate the process more then needs to at this point, you can do it all later.
Good luck.
borodin1 said:
Do not wipe the phone after istalling RC29. nbh file rewrites everything, and I mean it... everything.
Here's your order:
DREAIMG.nbh
Boot, sign-in, obtain root (telnet, connect to local host, you know the shpill).
Flash recovery (use ra 1.6.2, it's more updated then cm 1.4)
Wipe
Flash DRC83 defanged.zip
Flash ota radio, follow directions on the screen, you will need to reboot at least once
Flash 1.6 rom (cyan's is a good one to start at least)
Fix permissions.
Wipe
Reboot
Do not set-up linux swap or apps2sd at this time, it will complicate the process more then needs to at this point, you can do it all later.
Good luck.
Click to expand...
Click to collapse
You my friend are a genius!
Maybe the write-ups for rooting should be re-written to follow this as it worked flawlessly.
I started all the way back from step one at the default G1 1.6 Firmware.
Downgraded to the RC29.
DL'd telnet from the market.
Installed the new RA-recovery
Wiped.
Flashed DRC83.
Flashed Radio.(promted me to reboot)
Flashed the ROM.
Fixed Permissions.
Wiped again.
Then reboot.
Process went flawless, no hicups or anything. Thank you very much sir!
I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.
Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App
fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU
I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos
Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.
I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?
bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.
Hey Guys,
Before i start let me explain that i use to cook roms for my magic, so i know what im doing with this stuff.
Anywho i have been having a weird issue where whenever i flash a rom, it will not boot to either the rom or back into the recovery. my only option is to relock the bootloader and flash back to the stock ruu, and reinstall recovery.. right now im stuck on the stock rom and i hate it!
btw the device is s-off and unlocked bootloader, so wth, if anyone has any advice please let me know!
Did you try reflashing the recovery? Or a different recovery ? had a problem once with my pc antivirus blocking certain files and was causing the zip to be corrupted , just some thoughts
shael said:
Hey Guys,
whenever i flash a rom, it will not boot to either the rom or back into the recovery.
Click to expand...
Click to collapse
All you get is the white HTC screen when you reboot?
What about when you boot into HBOOT, then choose recovery manually?
As you mentioned, you're used to this stuff, so this part probably isnt helpful - do you do the 4 wipes when flashing? (data/cache/dalvik/system?)
I wonder if (even though you are S-OFF), the kernel portion of the rom isnt flashing? This can cause your phone not to boot and just sit there... i.e. your phone hasn't experienced a stockish/insecure kernel flash first, so recovery is having trouble flashing the custom recovery that comes with the rom.
See this thread for more info (it helped another user):
http://forum.xda-developers.com/showthread.php?p=30658376#post30658376
Also - to what Bigtjmc is saying - in the link above, I mention the recovery I use (which has not let me down at all!) Maybe you want to try it (if you're not using it already?)
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
Try Wildchild's Recovery (by far MY most favorite)
And if it's not passing verificiation, like the other user said check your anti-virus and check the MD5 Checksum to make sure you have a complete good download, wipe all data cache and blah blah blah then with fastboot "fastboot flash boot <Insert kernel file name here>.img
hmm, well in the past ive always flashed kernel with fastboot... its almost like my chip timed out and wont let me flash the kernel anymore :s
If recovery is crashing you might need to relock the bl and run the stock ics ruu to get you back up and running then try n start over , I used the tool kit just this morning for the same troubles and got back where I wanted to be in just a few minutes .
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
This happened to me as well... can't remember what script it was that was running but there is a script that is associated with a rom (vague I know) that is messing up the cache partition. If I remember correctly I also might be associated to the recovery you are using... but I can't remember. Anyway, If you do a fastboot erase cache command from the bootloader and re-flash the recovery of your choice you should be back to normal.
Awesome, thanks for you help guys, unfortunatley i dont have easy access to a pc, so i gotta wait a bit before i can try this... thanks again though
OMG!!!!! you guys are simply amazing, thank you everyone for your help! wiping the cache from fastboot, then flashing stockish kernel, then flashing cwm recovery, then wiping cache, and factory reset, then flashing my rom worked!!! <3
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.
Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?
Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.
bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.