Ok so a couple days ago in preperation of selling my evo 3d , i flashed a new rom of which i cant remember , i also beleive i flashed silverneedle kernel through the gpl tool app. Ever since no matter what i do , i cant get past the white HTC screen , it just reboots from there . Ive tried the superwipe tool and it seemed like it was going to work , but nothing . Ive also looked over several threads on here and no one seemed to have had an answer, thus im making my own thread. Im currently trying to flash warm 2.3 rom. I even thought maybe it was a bad transfer to the sd card because the sd card was acting funky when the rom was being transfered to it in my galaxy s2 so then i just downloaded it dirtectly from dolphin browers to the root of the sd card right from the galaxy to see if that was the problem. Still nothing , just the htc screen. Anybody have any idea how to fix this? I just want the phone back to stock so i can sell it , ugh. O and im on HBOOT 1.5 with the official HTC unlock and S-on.
I'm in the same boat. Fairly new evo 3d with hboot 1.5 rooted through htc. I've been flashing several roms over the last few days all with success, found I like Xplod XE from team nocturnal the best, nice and fast. What i found was that the kernel never changed, as I had read would happen with s-on. After doing some reseach and trying a few things I ran into your problem. Now no matter what or how i flash i'm stuck in a boot loop at the white HTC screen. The last kernels I've attempted to push were Tiamat_E3D-v1.1.0-Sense and silverneedle-test5. I've tried various combinations of wiping both caches with and without factory reset/system wipe as well as flashing several roms with success, still stuck with the boot loop. Flashed all roms through TeamWin Recovery and pushed kernels through clockwork recovery via fastboot/cmd promt.
Darthdaddy said:
.... and pushed kernels through clockwork recovery via fastboot/cmd promt.
Click to expand...
Click to collapse
Not sure about this.
But when flashing kernels, it happens through fastboot. You shouldnt see clockwork anything.
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
carnivalrejectq said:
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
Click to expand...
Click to collapse
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Followed directions from another site to work through command prompt and get into recovery, pm me for the link. Made sure i had my rom file on my sd card, did a factory reset then manual install of rom via clockwork then rebooted. Went through fine.
tailsthecat3 said:
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Click to expand...
Click to collapse
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
carnivalrejectq said:
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
Click to expand...
Click to collapse
Youll need to have all the necessary files/programs which I imagine are fastboot, adb, device/android drivers...
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
carnivalrejectq said:
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
Click to expand...
Click to collapse
Try this. Watch the vid, download the files.
Frankly, you should be able to run the RUU, so long as youre 'relocked'. Thats how Ive done it, multiple times. Hopefully we can get you back to stock.(Which we can)
Whew , i finally got it! The last part there was my erorr for using an older RUU , i didnt look close enough and i thought i was using 2.08. So i dled the 2.08 one and now its all good to go. Haha literally been doing this since 930 am. Thanks for the help guys , btw.
Related
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
babybear293 said:
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
Click to expand...
Click to collapse
can't do commands via usb, i'm reading this to mean, you don't have adb access.
after wiping the /data partition, where system settings are stored, including the toggle for adb access via, you will probably have to re-enable.
to enable adb access via usb on sense -> settings -> applications -> development -> usb debugging. this should be toggle on.
if that doesn't work, post back and we can start digging deeper but i'm hoping that'll resolve your isse!
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
thos25 said:
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
Click to expand...
Click to collapse
Well there is a lot going on in that post ... Not sure how my application Flash Image GUI failed. I would be more than happy to fix/resolve any bug or issue you've encountered!
Fastboot usb mode should always work. There is no setting in Android which will have any impact on fastboot usb mode (other than not allowing the device to boot into the bootloader). I generally find the best process to be, boot the device into the bootloader, plug in usb and then select fastboot.
Perhaps, once you're in the bootloader, you can also select fastboot and then plug in USB (this works best on my NS4G).
Either way, fastboot usb should always work. If you're using Windows, there could definitely be a drivers issue or Windows being finicky with the drivers and that might result in fastboot USB not working. A simple reboot of the Windows machine should clear any fastboot driver issues.
The best working method to correctly load a ROM is by properly loading the recovery to work with the HTC unlock method. HTC unlock method will only grant the recovery write access to the boot partition when the recovery image is temporarily fastboot boot'd. The command is: fastboot boot c:\android\cwm-recovery.img.
If you boot into the bootloader and select recovery from the menu, it will boot into the recovery, but the HTC unlock method will not grant the recovery write access to the boot partition. You can flash a ROM from here and restore a nand. Both will completely successfully and claim they flashed the kernel w/o any issues but the memory write lock will have prevented the kernel writes from being retained.
Also, regarding my application, Flash Image GUI, it should properly flash any EVO 3D kernel .zip file from normal Android mode as the HTC unlock method allows kernel write access while in normal Android mode.
Why did HTC block kernel write access from recovery mode? They haven't provided an answer .. we can only speculate ...
Hope that helps explain a few more steps to the process and provide greater clarity!
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
thos25 said:
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
Click to expand...
Click to collapse
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
I had a similar issue when i was switching to AOSP kernels/roms. I rebooted my phones once or twice and it connected fine. Maybe it have something to do with AOSP since MIUI is aosp also.
joeykrim said:
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
Click to expand...
Click to collapse
Thanks for the comments and lesson. I apologize for not responding sooner, but a recent death in family prevented me from really being on here too much lately.
1) I pretty much figured that. Yeah. I only try to flash using this method, that is why when my fastboot USB disapeared I thought I was really in a bad spot. Luckily I got it working again, so all was not lost.
2). Yes. I know it should remain on SD card, which was strange why I couldn't find it. However, thinking back on it, I do remember deleting some files off of my SD card on the same night. I probably just mistakenly deleted my CWM Recovery with my NAND backups. Sometimes when I double click a file to look at it, when I leave the file I see that there is a checkmark on that file. I may have just not noticed the checkmark on the CWM, went to delete another file, and mistakenly deleted CWM with it.
3) An RUU will not change a RADIO? I was under the impression that they did. Sort of like applying an OTA, but manually doing it through SYNC.
well, thanks again though. I learned some new things and appreciate it.
Flash image GUI works like a charm
Sent from my PG86100 using XDA App
i m a newbie
plz tell me how to get out of the fastboot usb mode. i m stuck with the G1 screen having fastboot usb title on the top.
PLZ HELP!!!
Ok, this is my first post so be gentle. I tried to root my sons phone and now it's useless. I went thru HTC's website to unlock bootloader due to having HBOOT 1.5. I'm unlocked and thinking life is good but, I loaded several different ROM's and get the same result. It starts to load the ROM and reboots, sometimes it goes into a safemode with the Viper Rom. I've been jacking with this for 2 days and need some help. I can't find a good link for the RUU or PG86...bla bla bla, I would take it back to stock and surrender but, can't even do that. I've installed TWRP and CWM, just to try different stuff, but get all the same reults.
I think you need to flash the boot.img separately. I'm not sure though. There's a thread for flashing with 1.50 somewhere in the development section
We're comin from a pure power source.
I am having the same issue here, I installed several ROMS, it works for a day, but then the reboot attack starts. Constant lockups and random restarts, sometimes 3 reboots in a row.
ROMs I tried to flash:
1. Xperia XE
2. Titan Trinity 3 HD
3. Nocturnal Adrenaline 1.0.2
Maybe it's the kernel, is there a list of kernels that I can flash?
This worked for me
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
armydude13090 said:
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
Click to expand...
Click to collapse
Unroot my phone?
Is it possible to re-root it?
Thanks all for the posts. I will give some of this a shot and see what happens. I can get to fastboot, and have loaded a couple of things thru the cmd prompt to try and help, but nothing so far. I'm not really sure if the kernel thing is what's stopping the roms for loading. I can't get the S-OFF, I'm unlocked. I can send anything I want thru the cmd prompt, and also flash zips thru twrp or cwm. Would like to start over but ca't even find a way to do that. Thanks again for the posts.
Cardmastr, we're on the same boat, pg86 takes forever to download, so as I'm waiting patiently, keep me in on the loop with what you're doing.
RUU didn't cut it, kept failing. have not found an image file to flash thru the cmd prompt. Still no luck. What can I throw into fast boot that might help me?????!!!!!!
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Which recovery did you install? Twrp 1.1.1 is your best bet.
The 2.x version twrp or cwm do not okay nice with some phones.
S3nt from my 3D wond3rland
I used the TWRP 1.1.1. Might of messed up with some of the cmd prompt stuff I'm going back thru.
thefsfempire said:
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Click to expand...
Click to collapse
Everyday is Halloween for u dude!! UR a Monster! This little tidbit hooked me up. Thanks to you we are back in game.
When installing a ROM, doesn't it wipe /data, /system, etc for us?
So I hate to be the frantic guy screaming for help cuz im normally pretty savvy at all this types of stuffs. But........
ZOMG [email protected]#[email protected]@[email protected][email protected]%!!
Im stuck pretty hardcore here. Allow me to give you the run down:
Was on Clean Rom Dev Edition. the newest version. ICS and the lot. But I wanted to try something different. Devil toast. When I tried to install the CM9 rom I got bootloops. I did some reading and found out this could be because I was S-on with hboot 1.50. So I found the JBEAR method for achieving s-off. It said I had to go back to stock so i tried to install a stock rom. didnt work. bootloops non stop. I tried a few different versions. odex, deodex blah blah blah. non of them worked. i only got bootloops. So I decided I would try and reinstall the Clean rom. That worked. I was able to reinstall it. I still wanted to try and get back to stock so I Got the RUU EXE and gave that a try. I only got errors and was unsuccessful at the RUU. So i figured what the heck I will try and do this with the rom i am already on. (since it says that it can work with some custum roms) gave it a try and got the still sober error a few times. I have tried about 5-6 times now with no luck. the phone wont boot into the rom. only the bootloader/fastboot. when i try to load CWM it wont mount my sd card so i can try installing a rom. if i try and power on the phone normally it just goes to a black screen with the word "juopunutbear" hanging above a phone. What should my next step be XDA friends? what can I do to get myself out of this situation. and wind up with soff and some devil toast!?
sorry if im being a noob. but i really need some help. thanks guys
djkozdefantastico said:
So I hate to be the frantic guy screaming for help cuz im normally pretty savvy at all this types of stuffs. But........
ZOMG [email protected]#[email protected]@[email protected][email protected]%!!
Im stuck pretty hardcore here. Allow me to give you the run down:
Was on Clean Rom Dev Edition. the newest version. ICS and the lot. But I wanted to try something different. Devil toast. When I tried to install the CM9 rom I got bootloops. I did some reading and found out this could be because I was S-on with hboot 1.50. So I found the JBEAR method for achieving s-off. It said I had to go back to stock so i tried to install a stock rom. didnt work. bootloops non stop. I tried a few different versions. odex, deodex blah blah blah. non of them worked. i only got bootloops. So I decided I would try and reinstall the Clean rom. That worked. I was able to reinstall it. I still wanted to try and get back to stock so I Got the RUU EXE and gave that a try. I only got errors and was unsuccessful at the RUU. So i figured what the heck I will try and do this with the rom i am already on. (since it says that it can work with some custum roms) gave it a try and got the still sober error a few times. I have tried about 5-6 times now with no luck. the phone wont boot into the rom. only the bootloader/fastboot. when i try to load CWM it wont mount my sd card so i can try installing a rom. if i try and power on the phone normally it just goes to a black screen with the word "juopunutbear" hanging above a phone. What should my next step be XDA friends? what can I do to get myself out of this situation. and wind up with soff and some devil toast!?
sorry if im being a noob. but i really need some help. thanks guys
Click to expand...
Click to collapse
Have you tried running the stock RUU in fastboot? I usually get errors when I try and run the RUU in andriod but no issue when in fastboot.
djkozdefantastico said:
So I hate to be the frantic guy screaming for help cuz im normally pretty savvy at all this types of stuffs. But........
ZOMG [email protected]#[email protected]@[email protected][email protected]%!!
Im stuck pretty hardcore here. Allow me to give you the run down:
Was on Clean Rom Dev Edition. the newest version. ICS and the lot. But I wanted to try something different. Devil toast. When I tried to install the CM9 rom I got bootloops. I did some reading and found out this could be because I was S-on with hboot 1.50. So I found the JBEAR method for achieving s-off. It said I had to go back to stock so i tried to install a stock rom. didnt work. bootloops non stop. I tried a few different versions. odex, deodex blah blah blah. non of them worked. i only got bootloops. So I decided I would try and reinstall the Clean rom. That worked. I was able to reinstall it. I still wanted to try and get back to stock so I Got the RUU EXE and gave that a try. I only got errors and was unsuccessful at the RUU. So i figured what the heck I will try and do this with the rom i am already on. (since it says that it can work with some custum roms) gave it a try and got the still sober error a few times. I have tried about 5-6 times now with no luck. the phone wont boot into the rom. only the bootloader/fastboot. when i try to load CWM it wont mount my sd card so i can try installing a rom. if i try and power on the phone normally it just goes to a black screen with the word "juopunutbear" hanging above a phone. What should my next step be XDA friends? what can I do to get myself out of this situation. and wind up with soff and some devil toast!?
sorry if im being a noob. but i really need some help. thanks guys
Click to expand...
Click to collapse
Boot your phone into fastboot. Plug it into the computer. Open up your command prompt and change your directory to whatever folder you created when you unlocked your bootloader. Then type fastboot oem lock. After doing this, you should be able to install your stock ROM either form your phone or via RUU on the computer. Let me know if you have any problems.
So heres the Update:
I finally got the phone jbeared. and installed jbear hboot. flashed devil toast and got no service or wifi. everytime i tried to connect to wifi the phone would reboot. did as mush reading and digging as i could to find out if anyone had the same prob. couldnt find anything. and wanted to go to bed for the night. so i just flashed back to clean rom dev edition because i had no problems with it before. but now I cant send or recive text messages. my data works fine. but no SMS at all. i get sms errors everytime i try to send one. i used one of my friends phones to send myself a text and i didnt receive it. what do you think the issue is?
djkozdefantastico said:
So heres the Update:
I finally got the phone jbeared. and installed jbear hboot. flashed devil toast and got no service or wifi. everytime i tried to connect to wifi the phone would reboot. did as mush reading and digging as i could to find out if anyone had the same prob. couldnt find anything. and wanted to go to bed for the night. so i just flashed back to clean rom dev edition because i had no problems with it before. but now I cant send or recive text messages. my data works fine. but no SMS at all. i get sms errors everytime i try to send one. i used one of my friends phones to send myself a text and i didnt receive it. what do you think the issue is?
Click to expand...
Click to collapse
Try reflashing the radio (PG86IMG.zip). Put it on your SD card, and boot into bootloader and follow instructions.
I never quite understood what radio I should use. How do I go about finding that out?
again sorry for being a noob.
So I tried reflashing the radio. No luck. Im still getting errors. "radio interface resource shortage" when I press details it says "cause code: 64, error class: 2" recommendations from here? I have tried updating PRL. nothing has worked so far.
djkozdefantastico said:
So I tried reflashing the radio. No luck. Im still getting errors. "radio interface resource shortage" when I press details it says "cause code: 64, error class: 2" recommendations from here? I have tried updating PRL. nothing has worked so far.
Click to expand...
Click to collapse
Did you activate the phone after bear?
Sent from my PG86100 using xda premium
djkozdefantastico said:
So I tried reflashing the radio. No luck. Im still getting errors. "radio interface resource shortage" when I press details it says "cause code: 64, error class: 2" recommendations from here? I have tried updating PRL. nothing has worked so far.
Click to expand...
Click to collapse
If you are on sprint and on a sense Rom , dial ##3282# click edit mode, enter your msl number (if you don't know what is your msl number, download msl reader from play store or anywhere and install it on your phone, it requires root access) then data profile then hit menu button and click restore . Your phone should reboot and it should do the hands free activation......
And for the issues you are facing , are you wiping every partition (except sdcard) before flashing a new Rom? and before doing s-off were you flashing boot.IMG manually from fastboot after flashing ROMs?
mnomaanw said:
If you are on sprint and on a sense Rom , dial ##3282# click edit mode, enter your msl number (if you don't know what is your msl number, download msl reader from play store or anywhere and install it on your phone, it requires root access) then data profile then hit menu button and click restore . Your phone should reboot and it should do the hands free activation......
And for the issues you are facing , are you wiping every partition (except sdcard) before flashing a new Rom? and before doing s-off were you flashing boot.IMG manually from fastboot after flashing ROMs?
Click to expand...
Click to collapse
Installing MSL now. to try that. I will update you once i have done it.
And yes. I wipe everything from the mounts and storage section except the sd card. as well as dalvic cache, and cache partition. in CWM befor flashing a new rom. and the way I have been flashing roms is from this method:
http://forum.xda-developers.com/showpost.php?p=17660133&postcount=1877
That is really the only way i know how to flash on the evo3d. I was also gonna see if there was a better way to flash roms. with out having to be at a computer to do so?
thank you for your help
djkozdefantastico said:
Installing MSL now. to try that. I will update you once i have done it.
And yes. I wipe everything from the mounts and storage section except the sd card. as well as dalvic cache, and cache partition. in CWM befor flashing a new rom. and the way I have been flashing roms is from this method:
http://forum.xda-developers.com/showpost.php?p=17660133&postcount=1877
That is really the only way i know how to flash on the evo3d. I was also gonna see if there was a better way to flash roms. with out having to be at a computer to do so?
thank you for your help
Click to expand...
Click to collapse
ok , tell us how it goes for you.
The phone refuses to do the hands free activation now. it did it right after i finished the jbear. but now its not doing it. it wont update the profile. wont update the prl. now my data is gone =[
djkozdefantastico said:
The phone refuses to do the hands free activation now. it did it right after i finished the jbear. but now its not doing it. it wont update the profile. wont update the prl. now my data is gone =[
Click to expand...
Click to collapse
try changing active profile from 0 to 1 in data profile to get data working again....
if data starts working , try updating prl and update profile too.
Is there a way to IM you?
Also, none of that worked. data is still gone. no activation. I just tried reflashing the rom. didnt work.
djkozdefantastico said:
Also, none of that worked. data is still gone. no activation. I just tried reflashing the rom. didnt work.
Click to expand...
Click to collapse
try making a call and you will be redirected to sprint for activation. if that doesn't work, try restoring data profile once again and then make a call
no luck. "error #16 switch 531" is what it says after ringing once. then hangs up. doesnt redirect me. tried up the same thing multipule times. no luck.
can you contact sprint from another phone? tell them about your activation issue.....don't tell them you s-offed your device .
Yea. I will call them tomorrow when I get off of work. Any advice on that I should say to them. like what caused the malfunction, ect...?
check if this helps support.sprint.com/support/article/...e-wh164052-20110615-165318?&INTNAV=SU:DP:HDIB
Ok, I have a rezound, unlocked and rooted with Amon Ra with the superuser binaries updated, all after installing the Global ICS RUU. I've been running this way pretty much since a few days after the Global RUU came out. Never had any problems or issues. Love this phone (except battery life but whatever). This morning before taking it off the charger I had it reboot (which I normally do every few days) and it did not reboot. It got stuck on the white HTC screen. The screen would come on, and then blink for a sec only to stay stuck on the HTC screen. No beats audio boot animation. I'm S-ON by the way. I use Mac so I was never able to get a windows computer to S-off, but I haven't wanted to flash any Roms since my days on the Dinc. I didn't have time to mess with it this morning so I just pulled the battery to shut it off. Now that I have a few minutes, I tried to see if it would boot, and same thing. Pulled the battery again, and powered up into the boot loader. Tried to enter recovery from there, and it just went blank. Pulled battery again, and tried it again. Same blank screen with no response from power button or anything. Now it is completely dead. Won't even go into bootloader. Won't even light up on the charger. SOME times when plugging it in it will light up for 5 seconds, but then turn off. Tried it with the battery out and pluggin it in to get into bootloader that way and nothing.
Is it completely fried? I bought it from VZW last April so it should be still under the 1 year manufacturer warranty. I'm hoping to find a fix as I haven't backed up in a while, but if not, hopefully they will replace it.
Even though I have a mac, it is set up to run adb commands, but everytime I try reboot or anything it just says "waiting for device". Clearly as it is not powered on.
Any ideas or help????
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
I just tried to do that and I can't get into the RUU zip file. I attached the kernel from the nandroid I made right after I ran the global RUU (4.03.605.2). If that's the version you are on you can try flashing this kernel and see if that does it.
Ugh... having trouble uploading it. If you have a nandroid from your global RUU you can pull the boot.img from that and flash it.
feralicious said:
The symptoms sound like you need to flash the kernel. Could be your phone took the recent OTA...?
Try pulling the kernel out of the RUU and flashing it in fastboot:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't know how to do that. I am not a newbie, but there is a lot I don't know. I follow directions well (being able to do the adb stuff with a mac) but pulling the kernel out of an RUU is not something I've ever read about doing.
I've read many threads about charging issues and what not, but I have the stock battery and the extended with a Seidio external charger so I know they both have plenty of juice in them. I know VZW will replace the thing, but I have stuff I'd rather not lose if I can fix it. If you could walk me through pulling the kernel out of the RUU.
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Once you have the kernel, pull the battery and put it back then boot into bootloader and put phone in fastboot. Attach to Mac, then use fastboot and this command:
fastboot flash boot boot.img (I named the one I'm trying to upload to ruuglobal_boot.img, you can either rename it or just flash using that name instead of boot.img)
feralicious said:
I edited my post above while you posted.
Do you have a nandroid of your stock global RUU? If so, you'll easily find the boot.img file in there. If not I'll try to upload the kernel again, or put it on dropbox if I can get back into my account (I never use it).
Click to expand...
Click to collapse
I hopefully have a nandroid backup on the SD card, but I will tell you it's been a long time since I installed the RUU. I've been out of the rom'ing rooting/ fiddling game for a long time. I haven't had the time recently and apparently it ain't like riding a bike. I've had to read a ton today to refresh myself.
My dinc was so easy, you didn't have to know a whole lot. Just download a zip, check the MD5, and flash it. Rezound was more complicated with the S-on, so I didn't even bother getting started....just the RUU to ICS before it was official, and then the RUU to Global. So yes, I am running the RUU you listed.
Anyway, I don't have a way of reading the SD card until I get home to find the nandroid.....and I've never looked at a nandroid made with Amon Ra....I only was used to CWM on the Dinc.
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
feralicious said:
I got into my dropbox account. Here's a link to the global RUU kernel.
http://dl.dropbox.com/u/55641774/ruuglobal_boot.img
If it works, can you please post a screenshot of your kernel and baseband info?
I'm curious to see what it says, if there's a way to see if it was the OTA that caused this.
Settings > About > Software Info > More
Click to expand...
Click to collapse
Was there an OTA recently?
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now. (Mine had a cracked screen so I couldn't get it replaced under warranty and had no insurance.)
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
feralicious said:
Yep. A week or two ago:
http://forum.xda-developers.com/showthread.php?t=2154288
You know, I apologize, but I somehow glossed over the end part of your first post where you are now dead. To be honest, that happened to me on my first Rez, and it happened a few days after the ICS OTA came out. I was never able to revive it and bought a used one which I'm using now.
I tried a new battery, had my old battery checked at Verizon to see if it would take a charge and it did but it wouldn't in my phone. Never was able to revive it. Hopefully you will be able to...
Click to expand...
Click to collapse
DAMN. Oh well. They will replace it most likely, and it seems like the easiest route to take. My wife's bootloader fried itself on here Moto D2 last year and it was LONG passed warranty and they replaced it......It was completely stock, but they had no way of knowing, so I'm sure they will send me a replacement phone. I just hope they still have Rezounds to send. I don't want to get stuck with something they determine for me because there are no more rezounds.
My wife's rezound is completely stock, never unlocked so I'll see if she got the update.
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
318sugarhill said:
ok, the phone has life again..... I got home, tried the other batteries and I'm back to the white HTC screen but no boot. I CAN get into recovery now so I will download the kernel and try that.
Before I do that, do you think something could have happened to recovery since when I select recovery from the bootloader it goes blank? Do you think flashing a rom like Nils could work? or can I just run the RUU again?
Click to expand...
Click to collapse
Ok, I loaded the boot.img and no dice. Still stuck at the white HTC screen. This is frustrating now. Now I do NOT want to go to the VZW store as my bootloader says tampered unlock. I guess I can always try to run the RUU again.
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
Well, if I can get into the bootloader I can relock to run the RUU correct? I hate to have to lose everything, but I do need the phone, and if it was toasted, I would have to start over with a replacement anyway. Nothing on there can't be replaced except some pictures, but it won't kill me. Just a hastle. Should I try to relock and run the RUU? or should I try to load a Rom like Nils business sense for S-ON? I was considering trying it.
feralicious said:
Well, don't give up just yet.
There was an unbrick thread in the dev section. It didn't help me and I'm not sure it applies to your situation, but it can't hurt to try it. I know it had [UNBRICK] in the title, so if you search for unbrick you should find it. You need to get a Linux live img and put in on a usb flash drive and boot into that and then see if it can find your device. It never found mine.
Click to expand...
Click to collapse
I gave up bro. This sounds way over my head. I relocked and am running the Global RUU again. I will unlock again and load amon ra, and run the su binary zip I have again. Not worth this much time. My 3 year old is tearing up the place while I bury my face in my computer.
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
feralicious said:
Yeah, I would go with that, not sure you have any other options.
If you haven't done the RUU yet you can try just doing the recovery first and see if you can get into it to save your files.
Click to expand...
Click to collapse
I tried pushing the recovery again, I tried the boot (all three that were in the nandroid backup) and some other things on here I saw. Nothing worked. Just stayed at the white HTC screen. Relocking and running the RUU made the phone usable again. Thanks for your help, but my stuff is gone. After spending what feels like forever setting up the phone to make it usable again, it will all be gone when I unlock again. Don't have time to do that tonight, but this weekend I'll get to it.
Not everything is gone. I do have titanium but I haven't backed up in a while, so they will be old backups, but still backups. Lesson learned....schedule backups more frequently.....reset my dropbox to auto upload pics again. Turned it off Christmas day, and never turned it back on. The cloud is there for a reason right?
I'm s-off, on hboot 1.19, my baseband is 1.12.11.1210.
I just tried to change roms from meanrom ics to paranoid 3.99. Everything went fine in twrp. When I rebooted the phone it ran thru "upgrading android apps" & when it got to the spot where you'd start entering all your info, I got an error saying unfortunately, the process com.android.phone has stopped. There was another message underneath that one. I couldn't really read it but it said something about IU issues. I've tried reflashing the rom but the same thing happens. I have backups made & went to them in twrp, but they aren't a flashable zip like I thought they'd be. I can still get into the bootloader, but when I select fastboot I can't get my phone to connect to my cpu anymore. It was working before I tried all this. I even tried reinstalling meanrom but it gets about a 1/3 of the way thru the install & reboots to the splash screen & it just sits there. I know I'm probably missing something minor, but I could really use some fresh eyes.
Thanks in advance for the help.
ETA...I'm on twrp v.2.6.3.0 & can still get into the bootloader & recovery. Fastboot USB just won't work. I've tried doing system wipes & installing different roms & they either fail or get stuck in bootloop. I found my backups in twrp but they all fail to install when they get to /data. Some of them don't even make it that far.
Well, I went ahead & booted up off of one of my b/u that said it failed. I got my phone back to where I could start entering wifi info,ect...but I'm getting another error unfortunately the process android.process.acore has stopped. I went into twrp & did the "fix permission" thing. I now get the same error as before...unfortunately, the process com.android.phone has stopped.
Well I've been wanting to leave sprint...I guess today is as good a day as any.
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
buddahj said:
As a last ditch effort, I did the factory reset in the bootloader. I then went into twrp & formatted my sd card thru windows. I then tried to install meanbean & it came up with no errors. I must've done something wrong when I tried to install paranoid android & got my sd card corrupted. Now I just have to figure out why I can't connect via fastboot usb...but that will be for another day. I'm just glad I don't have to switch carriers just yet. I'm holding out for the new htc one.
Click to expand...
Click to collapse
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
numel007 said:
By not beig able to connect to fastboot, do you mean you get a message saying no devices found?
Click to expand...
Click to collapse
So........I'm an idiot. I was forgetting to open the command prompt in the platform tools folder. My fastboot usb works fine. Right now, I'm just having trouble installing the htc mtp drivers.
Have the drivers been updated?
Took the red pill. HTC evo 4G LTE evilution red pill.