I just rooted my friends evo, same hardware as my own, but there's all kinds of issues.
First, volume up + power doesn't boot into recovery like mine, It vibrates 3 times and that's it. You need to pull the battery and use volume down to get it to boot. If you use quickboot from within android, then it can reboot into recovery and everything seems to work normally.
Second, I loaded the Sprint lovers rom but now the phone doesn't answer every other call. For example, first call you can't hear me, second you can, third you can't etc...
Whats going on? I have a feeling it has to do with the different recovery version then i have on my own evo. I used the "z4root" method i found on here for his, for my own android I used that old flash based browser hack.
Also It just occurred to me, I think I deleted the wimax backup I made. Is that really essential? I never had to do that with my own evo
Sent from my PC36100 using XDA App
Could really use some help. If I flash with the ru, will that erase s-off?
Sent from my PC36100 using XDA App
acme64 said:
I just rooted my friends evo, same hardware as my own, but there's all kinds of issues.
First, volume up + power doesn't boot into recovery like mine, It vibrates 3 times and that's it. You need to pull the battery and use volume down to get it to boot. If you use quickboot from within android, then it can reboot into recovery and everything seems to work normally.
Second, I loaded the Sprint lovers rom but now the phone doesn't answer every other call. For example, first call you can't hear me, second you can, third you can't etc...
Whats going on? I have a feeling it has to do with the different recovery version then i have on my own evo. I used the "z4root" method i found on here for his, for my own android I used that old flash based browser hack.
Click to expand...
Click to collapse
acme64 said:
Also It just occurred to me, I think I deleted the wimax backup I made. Is that really essential? I never had to do that with my own evo
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
First of all, let me say I'm not familiar with the z4root method. I have followed the unrevoked methods, and also Zikronix's thread on hboot s off.
Also, there's not really any way to help you without more info. You said he has the same hardware of you, but never specified what hardware you have. We need to know the hardware version, software version that the phone was shipped with, radio versions would be nice. Way too much left out. All of that matters for various troubleshooting reasons. What recovery are you using? Clockwork or Amon RA? What bootloader version is it? Oh yea, to get to the bootloader, hold volume down, not up. So vol+down+power button. That is how it has always worked for me. When you get to the bootloader, record the version number, radio(baseband) version, and if you are s-on or s-off. Report back wth all of that, then we'll have a direction to look in.
acme64 said:
I just rooted my friends evo, same hardware as my own, but there's all kinds of issues.
First, volume up + power doesn't boot into recovery like mine, It vibrates 3 times and that's it. You need to pull the battery and use volume down to get it to boot. If you use quickboot from within android, then it can reboot into recovery and everything seems to work normally.
Second, I loaded the Sprint lovers rom but now the phone doesn't answer every other call. For example, first call you can't hear me, second you can, third you can't etc...
Whats going on? I have a feeling it has to do with the different recovery version then i have on my own evo. I used the "z4root" method i found on here for his, for my own android I used that old flash based browser hack.
Click to expand...
Click to collapse
do this to solve your problem
1. download this file
2. place it on the root of your sdcard
3. rename it to PC36IMG.zip
4. reboot into bootloader
5. when it loads choose yes to flash the pc36img.zip
6. reboot into rom and delete the pc36img.zip
7. power off your phone
8. reboot into bootloader, select recovery from the menu.
this should fix your recovery problem as for the other, i suggest flashing a different rom afterwards
t3project said:
do this to solve your problem
1. download this file
2. place it on the root of your sdcard
3. rename it to PC36IMG.zip
4. reboot into bootloader
5. when it loads choose yes to flash the pc36img.zip
6. reboot into rom and delete the pc36img.zip
7. power off your phone
8. reboot into bootloader, select recovery from the menu.
this should fix your recovery problem as for the other, i suggest flashing a different rom afterwards
Click to expand...
Click to collapse
Or you can flash another recovery. Use the latest Amon RA Recovery.
As for your ROM issues, did you wipe data/cache/dalvik? If you did you might want to try doing it about 3 times. The recoveries are not wiping cache, dalvik and data properly until you do it a few times. Also the latest Amon Ra fixes that I believe
That is another recovery in pc36img.zip format. Specifically amon_ra 2.1.1
Just a word of advice, never use vol up & power to turn on your phone. That will put it in diag mode if your nand is unlocked and that is something you really don't want to do.
Sent from my PC36100 using XDA App
xHausx said:
Just a word of advice, never use vol up & power to turn on your phone. That will put it in diag mode if your nand is unlocked and that is something you really don't want to do.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
LOL!!! Sometimes its good to know what your doing specially before messing with a friends phone.
Related
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Bump.....ANYONE?!
So the following questions would need to be answered:
1) What version of stock were you running before you rooted? (i.e. 1.47, 1.32)
2) What root method did you use?
3) What recovery do you have?
4) If you have wireless tether working than you would need to have installed a custom kernel, which one did you install?
I'm sorry that no one else has tried to assist you in this, however, next time please post this in Q&A as this is for development purposes.
~Jasecloud4
nova0387 said:
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Click to expand...
Click to collapse
my personal experience sometimes if your using the rom mangager to flash roms it doesnt always wipe it fully so i use amon recovery all the time now
Im honestly not sure which version i was running b4 I just my Evo about 4 days ago...I used the SimpleRoot 1.47 to root my phone...all went fine for rooting...I didnt install any custom kernal...I pretty new at this so bare with me a bit if you could
and thnx for your time for even replying man!
nova0387 said:
Im honestly not sure which version i was running b4 I just my Evo about 4 days ago...I used the SimpleRoot 1.47 to root my phone...all went fine for rooting...I didnt install any custom kernal...I pretty new at this so bare with me a bit if you could
and thnx for your time for even replying man!
Click to expand...
Click to collapse
i honestly dont know anything about that simple root i have heard that it does work though i rooted in the beginning with toast's method. anyway what happens when you try and get to recovery mode IE powering the the phone off, then holding the volume down button while powering the phone on?
danon.brown said:
i honestly dont know anything about that simple root i have heard that it does work though i rooted in the beginning with toast's method. anyway what happens when you try and get to recovery mode IE powering the the phone off, then holding the volume down button while powering the phone on?
Click to expand...
Click to collapse
Well when i try to go into recover mode it first gives me a black screen that shows a cell phone and a triangle with a exclamation point then i hold the volume up keyand press power and it says "e can't open cache recovery command" n then takes me to a screen where it says
Android system recovery <2e>
use d-pad to highlight; center to select.
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
nova0387 said:
I did the root and I have the WiMAX setting and Wifi Tethering is working somewhat but I cant figure out how to flash my rom..I dl'd DamageControl 3.2 but i dont know what to really do now...When i try use ROM Manager I get the error..."an error occurred while attempting to run priviledge commands!" I'm just lost as to what i do now to start using a different rom
Click to expand...
Click to collapse
Okay during the process of rooting my device, ebo 4g, v1.3x
I ran into the same problem, you have to or I'm sure on this forum just do some research,.....
In RA, dalvik wipe, cache wipe and phone wipe. Then I flashed the rom via sd card, using clockwork custom recovery. If you used Simple root 3 click process you should have clock work.Via step 2.
Rename the Rom to update.zip and place in root sdcard.
Adb reboot recovery
Update.zip from SD card
Finnish do full system wipe and dalvik cache.
Make sure you are nand protected before flashing.
Via step 3
I don't know if this mighhelp just some recent stuff I ran into. Rooted my g1 a WHILE back. Hope these noobietips help lol
Sent from my PC36100 using XDA App
Do this! It's the fastest and easiest way.
Once you get 1.47 and singed sigs then do DC ROM again.
http://forum.xda-developers.com/showthread.php?t=715915
elitekernel said:
Okay during the process of rooting my device, ebo 4g, v1.3x
I ran into the same problem, you have to or I'm sure on this forum just do some research,.....
In RA, dalvik wipe, cache wipe and phone wipe. Then I flashed the rom via sd card, using clockwork custom recovery. If you used Simple root 3 click process you should have clock work.Via step 2.
Rename the Rom to update.zip and place in root sdcard.
Adb reboot recovery
Update.zip from SD card
Finnish do full system wipe and dalvik cache.
Make sure you are nand protected before flashing.
Via step 3
I don't know if this mighhelp just some recent stuff I ran into. Rooted my g1 a WHILE back. Hope these noobietips help lol
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
stewie-droid said:
Do this! It's the fastest and easiest way.
Once you get 1.47 and singed sigs then do DC ROM again.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
I ttried that and it works fine until i get to the part about the su file...it doesnt let me go into recovery mode it shows me the black screen with a cell phone and a triangle with an exclamtion point
nova0387 said:
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
Click to expand...
Click to collapse
adb reboot recovery just reboots your phone into recovery mode. once your in that do all the wipes i think its 3 dlvk, data and something else. power off the phone once more then boot to recovery again. now one of the options is flash from zip go there and you should find whatever rom your trying to flash. also you should be putting your zipped rom files in the root directory of your sdcard. on a side not if your on a mac dont download them with safari use firefox or something else
nova0387 said:
Ok when i go to SimpleRoot and i click extras it says flash recovery...then i can select from Clockwork or RA...I've tried both and they just say flashed successful but nothing different happens...I'm not really sure what ADB reboot recovery is?
Click to expand...
Click to collapse
also clockwork and ra are 2 different types of recovery you wont notice anything until u actually reboot the phone into recovery mode
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
nova0387 said:
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
Click to expand...
Click to collapse
you forgot to wipe something common problem.. reboot to recovery again.. go to the wipes part and do all of them.. reboot one last time to recovery then flash DC it should work then
wipe the first 3 if your on RA 1.7.0.1 data/factory, cache, and dalvik.. then reboot into recovery again and flash
nova0387 said:
Ok i clicked flash rom on the simple root again and this time it brought up a black and green screen and more options...I selected apply zip from sd card and went down and selected the Damagecontrol zip...it said it installed successfully but now when i go to reboot my phone it keeps reloading the sprint 4g screen and wont boot all the way up!?
Click to expand...
Click to collapse
nova,
I had the same boot loop issue. My thread for it here:
http://forum.xda-developers.com/showthread.php?t=728955
The issue was that I wasn't totally 100% rooted. By carefully following these directions, I was able to resolve my issue:
http://forum.xda-developers.com/showthread.php?t=721055
I hope this helps also, I did it using the "PC" method. If you have questions regarding those instructions I'd be happy to share my personal experience.
Ok Ok Ok!!! I think I jsut got it my dood! How do i know tho? It booted up and everything just fine and i have wayy more apps including like Dconfig ad superuser permission...is that kinda how i kno?
nova0387 said:
Ok Ok Ok!!! I think I jsut got it my dood! How do i know tho? It booted up and everything just fine and i have wayy more apps including like Dconfig ad superuser permission...is that kinda how i kno?
Click to expand...
Click to collapse
Errr... maybe? Superuser permission, etc. certainly doesn't come with stock. It depends on the ROM you installed. Here's one way to find out...
Go to Settings -> About Phone -> Software Information and check the "Build Number". AFAIK it's impossible to install DamageControl without full root (I tried to myself before fixing my root and going to Fresh 1.0.1) so if that's what you have I'd say you're good.
There may be a better way but that's all I know.
aikeru said:
Errr... maybe? Superuser permission, etc. certainly doesn't come with stock. It depends on the ROM you installed. Here's one way to find out...
Go to Settings -> About Phone -> Software Information and check the "Build Number". AFAIK it's impossible to install DamageControl without full root (I tried to myself before fixing my root and going to Fresh 1.0.1) so if that's what you have I'd say you're good.
There may be a better way but that's all I know.
Click to expand...
Click to collapse
Yep my Build Number says DamageControl v3.2.3! Thnx again everyone who tried to help me and def a special thnx to Danon.Brown! Hollllllla
So I have an incredible. FLAWLESS root and easy install for everything.
I just rooted a friends EVO, have root permission, and full root. I've tried both clock and supersonic recoveries. When i try to flash a rom VIA rom manager OR manually, i click it, hit yes and it writes one line and instantly goes back to the options. It seems as the phone just will not take ANY rom at all... what could be the problem??
eddiimonster said:
So I have an incredible. FLAWLESS root and easy install for everything.
I just rooted a friends EVO, have root permission, and full root. I've tried both clock and supersonic recoveries. When i try to flash a rom VIA rom manager OR manually, i click it, hit yes and it writes one line and instantly goes back to the options. It seems as the phone just will not take ANY rom at all... what could be the problem??
Click to expand...
Click to collapse
Try re-downloading the ROM, you may have a bad download. Also, try flashing with Amon RA recovery.....it's never let me down. Make sure your battery is fully charged, too.
+1 for Amon Ra, though it looks like you've already tried it (that is what you mean by "supersonic", right?).
Try flashing the recovery manually. Download a PC36IMG.zip of Amon Ra and put it on the root of the SD card - don't rename it. Boot into the bootloader (hold the vol down + power buttons simultaneously until the phone boots into bootloader) and wait for it to scan. While you're there, double check that the phone is actually s-off & not s-on. When it asks you to update, choose yes. Say no to reboot, then choose recovery from the bootloader screen and try again.
Give me a minute & I'll post the file. I'm using the app atm.
It won't upload, so here's a link:
http://db.tt/rBcdNoW
Most devs post md5s with the download, I'd verify it matches.
Sent from my PC36100 using XDA Premium App
nope, still getting the same problem. updated everything, flashed serveral pc35imgs and still i go to install zip from sd card and it starts but instantly stops and wont flash the rom.... what else to do....
Do you mind posting all of the info on the phone? Whatever it says in the "About Phone" menu & what it says in the bootloader. Maybe we can figure something out from there.
Also, from where are you downloading the roms? As someone else mentioned, check the md5s.
Oh, and what roms have you tried flashing... I'm just curious. This is going to bother me if I can't figure it out, lol.
eddiimonster said:
nope, still getting the same problem. updated everything, flashed serveral pc35imgs and still i go to install zip from sd card and it starts but instantly stops and wont flash the rom.... what else to do....
Click to expand...
Click to collapse
The file should be named PC36IMG.zip, not PC35IMG. Also, it should be ran from the Bootloader, not recovery.
It is slowly driving me mad. I can get into recovery and restore my current ROM (leaked GB base). However, if I flash a new rom - any rom - it flashes, reboots into white HTC boot screen, and just hangs there.
I'm using ROM manager, clockwork.
What do I do? It doesn't make sense.
Thanks for any advice.
Later.
1. Stop using ROM Manager
2. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
3. Shutdown your device.
4. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
5. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
6. Go to the flash menu and flash the rom you desire to flash.
posting & replying via the XDA Premium app.
Did you try it? If so, how did it for for you?
posting & replying via the XDA Premium app.
I have had it take 3-5 min to get past the white screen, it happened with some custom roms. I thought it was hung also but it finally continued..how long did you wait?
Sent from my secret place where no-one can find me.
Oh wow, you are awesome. I really appreciate you taking the time to tell me that. Worked perfectly. If I could buy you a beer I would. Have a good one!
dougjamal said:
1. Stop using ROM Manager
2. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
3. Shutdown your device.
4. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
5. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
6. Go to the flash menu and flash the rom you desire to flash.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Sprockethead said:
Oh wow, you are awesome. I really appreciate you taking the time to tell me that. Worked perfectly. If I could buy you a beer I would. Have a good one!
Click to expand...
Click to collapse
(Laughing)...You're very welcome. I'm glad I was able to help. Enjoy the rest of your day.
posting & replying via the XDA Premium app.
Was having the same trouble. I think Rom Manager has some flaws cause it works fine from Recovery
Raehtz10 said:
Was having the same trouble. I think Rom Manager has some flaws cause it works fine from Recovery
Click to expand...
Click to collapse
ROM Manager has its uses, but, in my opinion, it is far too easy to simply boot or reboot into recovery and flash, especially with amon RA. It has a common sense menu layout.
posting & replying via the XDA Premium app.
Just MY opinion, but ROM Manager is useless. I see more people have issues because of ROM Manager. My advice, dump it and do everything in Recovery.
+1
Sent from "The" Evo using XDA Premium VIA your moms house. ™
Hmmm, so what happens if I'm still having this problem after trying this fix? I've been having the "can't flash any other roms because they all hang at the white evo4g screen" problem and have been stuck on the same rom for over a month now. Is there something else I can try if this doesn't work?
superhiro415 said:
Hmmm, so what happens if I'm still having this problem after trying this fix? I've been having the "can't flash any other roms because they all hang at the white evo4g screen" problem and have been stuck on the same rom for over a month now. Is there something else I can try if this doesn't work?
Click to expand...
Click to collapse
I would do a clean wipe, factory/data, cache, and dalvik, then go to the bootloader, select the clear storage for overkill, then try to flash a rom.
jayharper08 said:
+1
Sent from "The" Evo using XDA Premium VIA your moms house. ™
Click to expand...
Click to collapse
+1.....again
Thanks for the quick reply man. Tried the wipe of data, cache and dalvik, rebooted to bootloader and cleared storage. Tried to install a rom and still hung up at the htc evo 4g white boot screen. Anything else I can try?
Which rom are you trying to flash? I would re-download it to make sure its not corrupted in any fashion.
Hmmm I was wondering if that might be the problem, because I've gotten this rom to flash ONCE before. It's the End of Days rom from Magnus. I got it to work the first time I tried to flash it but then at some point I rebooted it and it started boot looping to the point where I couldn't get it to load anymore. That's when I wiped, tried to reflash the rom and all this madness started. I'll try to redownload, but I figured if the ROM worked once, it should be able to work again... right? I mean I'm not flashing it any differently.
superhiro415 said:
Hmmm I was wondering if that might be the problem, because I've gotten this rom to flash ONCE before. It's the End of Days rom from Magnus. I got it to work the first time I tried to flash it but then at some point I rebooted it and it started boot looping to the point where I couldn't get it to load anymore. That's when I wiped, tried to reflash the rom and all this madness started. I'll try to redownload, but I figured if the ROM worked once, it should be able to work again... right? I mean I'm not flashing it any differently.
Click to expand...
Click to collapse
It should work.
http://dl.dropbox.com/u/19699565/PC36IMG.zip Place that on your sdcard, boot into the bootloader and flash it. That'll reflash the amon_ra 2.3 recovery, then try flashing the rom again.
Yea I tried the Pc36img thing already too. Let the bootloader find it, applied the update, rebooted into recovery, reflashed, nothing. Same results, hung up on white evo screen.
I'm actually noticing that when I try to wipe the "sd ext" in Amon Ra's wipe menu, it just says "skipping format sdext" or something like that, is that normal?
superhiro415 said:
Yea I tried the Pc36img thing already too. Let the bootloader find it, applied the update, rebooted into recovery, reflashed, nothing. Same results, hung up on white evo screen.
I'm actually noticing that when I try to wipe the "sd ext" in Amon Ra's wipe menu, it just says "skipping format sdext" or something like that, is that normal?
Click to expand...
Click to collapse
That's normal; it only says that because you don't have that partition. The only thing I can think of at this point would be to backup everything, quickly unroot, then re-root.
My Evo is doing something similar. I flash ANY of the new Sense 2.x (or Sense 3.0) ROMs, and they just reboot on the white HTC EVO 4G screen. Ive wiped everything, used Calks Format All, Im using the latest Amons, etc to no avail. However, all AOSP GB ROMs (MIUI,CM7, EoD, etc) work like a charm! Any kind soul that knows what the hell is going on with my phone?
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo
1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....
Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful
---First off, let me preface this by acknowledging the fact that, yes, I am indeed a noob. And I'm sure some of the info I'm going to put in here probably isn't needed, but as I said, I am a noob, and thus am not entirely sure what is relevant and what is not. I also apologize if some of what I say and/or what I did doesn't make sense and/or is idiotic, but again, noob. That being said I don't have any techie friends and never really had a nack for this kind of stuff, but hey gotta start somewhere right? So, that being said, here's my dilemma:
This all started last week when I was downloading the CyanogenMod Nightlies *Rom. The download started and was going along just fine when my phone suddenly turned off and starting vibrating and then wouldn't turn back on. Everything I would press power it would just start vibrating in regular one second intervals over and over. Finally I remove the battery. It turns back on fine. Download resumes. And... Bam! Happens again. This time I try the same remove to no avail and about 15 minutes later I'm thinking that this is it for my phone when it finally reboots. So I decide, alright, lemme just download this Rom and try to flash it, or at the very least just restore the phone and hope this is a software issue. So I had also just downloaded Rom Manager and was going into recovery via Clockworkmod recovery as the instructions prompted me to in the CyanogenMod tutorial. Now every other time I have installed a new Rom I just manually boot into recovery as the phone turns on. This time I boot into the Clockworkmod recovery though cuz I wanna follow the directions to the "T" and I proceed to selecting the factory reset and it wipes the data and freezes when wiping the cache. So I'm sitting there like, "Oh s**t, what do I do now?" I let it sit for fifteen minutes hoping it will magically unfreeze and all will be right in the world, but it doesn't and I reset the phone via the power button. Then it boots up and tells ne there a issue with my custom OS and I'm not really are what to do here. So, i reboot it and it acts like the reset was successful and prompts me to set up my phone like I just flashed the Jedi Mind Trick Rom I've been using. So I tried again, and same thing. Got stuck on clearing the cache. Luckily it lets me set up the phone again after I interrupt the frozen factory reset. This time I try to boot into recovery manually, pressing the hard keys, and all the phone does is restart. So I try again. And again. And again to no avail. I look up the key sequence thinking I may have forgotten it and am doing it wrong, but after trying every combo I can find online, it still doesn't work. So I give up and go into recovery via clockworkmod and restore my phone to my very first nandroid backup I made before I ever started messing with custom roms, and everything goes fine it seems until it gets to a command about something revolving cache and it freezes again! I eventually have to reset it and it gets stuck in a loop where the Samsung logo comes up, it makes a loud annoying beeping noise for a few seconds before it turns off and does it all over again. Now I'm sure I've bricked my phone. I take out the battery, wait, put it back in, but still nothing. I do this a few more times, wait and hour, and it finally boots up. So now I try to go into recovery manually again, but still just get the phone resetting. I try to go uninstall clockworkmod and go into recovery via Rom toolbox pro, but I still get the clockworkmod recovery rather than the phone's normal recovery I used to be able to get to before I ever installed clockworkmod. So I'm stuck here. I know that's a lot of info, but I didn't want to leave anything out incase it was important. Thanks in advance for any advice and/or directions you can give me. *
P.S. I read in someone's post here that the first issue of the phone turning off and vibrating could be the result of a bad power sensor. So I wanted to add that since this two mysterious restarts and vibrations, nothing like that has happened in the... Approximately 5 days since (for whatever that's worth). *
Thanks again, and I apologize for any ignorance you have encountered while trying to read this post.
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
whatiznt said:
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Ok. Checked it out and got twrp. I clicked install openrecoveryscript. It downloaded. Didn't restart or anything. Now can I just flash the new Rom I want directly from there then? All it says it that I must have installed the recovery script. Just wanted to know though, is it still right that when I reboot into recovery it goes to the cwm recovery? Just wanna make sure before I go messing up my phone.
Thanks!
mintharis said:
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
Click to expand...
Click to collapse
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
VoiD_Dweller said:
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
Click to expand...
Click to collapse
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
jalight27 said:
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
Click to expand...
Click to collapse
Yes, the darkside scripts were used in older cwm recoveries because the default wipes didn't do the job. As for switching away from cwm I'm guessing you want to jump to twrp. You can do that by following the instructions at http://teamw.in/project/twrp2/101
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Thanks for the steps there. Pretty much did a combo of what everyone was saying. Went back to an older version of cwm and used darkside wipes. Then wouldn't you know? It worked! Yay for me. So I'll just keep my older version of cwm, for now at least. Well, anyway, thanks to everyone for helping me figure this out. Much obliged!
jalight27 said:
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
Click to expand...
Click to collapse
Forever like being 10 minutes min, maybe 15
ClaireH said:
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Click to expand...
Click to collapse
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
fe1ixs said:
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
Click to expand...
Click to collapse
Yep, same thing I ended up doing, thought I posted that but I guess I never did. I ended up using the darkside wipes and going back to an older version like you and someone else said. Now everything's just fine. And btw, to get into recovery from boot just restart it holding power, volume up, and volume down at the same time. Then once you see the Samsung logo let go of the power button but keep holding volume up and down till you see the recovery menu.