Related
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Maybe its the busybox that you downloaded. You should hit up recovery and do a full wipe! The start up again. What rom are you running, most roms have busybox included so when you download it I've seen phones get the white screen of death. Grab a rom and reflash it. Since you put busybox that nandroid you made probably is no good. Reason I'm telling you all this is because has happened to me before. Good luck
Sent from my PC36100 using XDA Premium App
ravissimo said:
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Click to expand...
Click to collapse
Well, I'm not sure what exactly went wrong for ya, but I might suspect it was something to do with some of the apps you downloaded prior to making your backup. The first thing to try, would be to boot to recovery, and wipe cache, and then go to 'advanced' and wipe dalvik cache. Then try to reboot. If that fails, then you're next option (without flashing a new ROM) is to do a data/factory reset. You will however lose all of your apps, settings, contacts, texts, etc. You unfortunately don't really have any other options, unless wiping cache's helps you out. If a factory reset doesn't allow you to boot, then you're most likely going to have to flash a new ROM. And also, I thought that Unrevoked flashed the latest clockwork recovery, which would be 3.0 or somehting like that, no?
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
You don't need to download busy box, I would delete that app. If you flash a rooted rom it should already have busybox; if you just rooted your phone and want to download busybox on your current stock rom then it will be ok. I would wipe and flash a new rom just to be safe.
Sent from my PC36100 using XDA Premium App
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
Well, I'm not exactly sure why you want to download busy box so badly. Any rom comes with busy box cooked in. I have only once installed busy box. The only time i remember having to do it, was Immediately after I rooted with Unrevoked, i went to use Titanium, and had some error. I hit the problems button and that updated busy box from there. Other than that, I've never messed with it.
And yes, most likely your nandroid backup is not going to be of any value to you. You could try restoring it if you'd like, but I predict it would be a waste of time. And I'm not sure that it matters that you didn't 'open' and click install on busy box. If you downloaded it from the market, wouldn't it just download and install itself automatically? I would just flash a rom, and be done with it. Roll with whatever version of busy box comes with the ROM you flash. As you said, you're only option is a factory reset now, and if you're going to do that, you certainly may as well flash a custom rom at the same time. You just need to download a rom, and put it on your sd card. You can mount the sd card as a disk drive to your computer from within recovery. I use amon ra, and its called USB MS TOGGLE. I'm not sure what it's called in clockwork, but the option is there. So put the rom on your sd card, perform a complete wipe, (i'd flash calkulin's format all.zip as well), flash a rom, reboot, and forget about anything with busy box. It will be installed on the rom already.
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
If you can get a logcat that should show what is causing it to bootloop. It's 'adb logcat > logcat.txt' to do it, run that and wait for it to loop 3 or 4 times before pushing Ctrl+C to stop it.
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
ravissimo said:
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
Click to expand...
Click to collapse
Right. But unfortunately now, your data seems to be lost. Did a factory reset help anything? If not, you got to wipe and reflash a rom.
Sent from my PC36100 using XDA App
ravissimo said:
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
Click to expand...
Click to collapse
I understand that. As I stated, I'm not sure what's causing your problem. As xhausx said, try getting a logcat
Sent from my PC36100 using XDA App
What method of rooting did you use? What recovery do you have right now? As hausx said you could do a logcat and he'll check it out!
Sent from my PC36100 using XDA Premium App
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
ravissimo said:
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
Click to expand...
Click to collapse
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
xHausx said:
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
Click to expand...
Click to collapse
OK, so I downloaded and extracted the auto-root tools only zip from your sig, and then ran OpenShell.bat and typed as you said "adb logcat > logcat.txt" with my phone plugged in. said "waiting for device" and then i turned on my phone and let it boot 4-5 times before ctrl+c and pulling the usb. all the logcat.txt says is...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
am i doing something wrong?
my apologies, i've only throughly read on how to root, i hadn't gotten into flashing or anything else yet. just been on xda site for a few days now reading all i could about rooting (which went fine, but now i'm screwed).
dirkyd3rk said:
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
For the hell of it I did just that and it did bork it.... lmao
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
Did it really? Lol It did it to me man I was pissed!
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
man, for the life of me, i can't believe i didn't do a nandroid before i downloaded the app. for some reason i thought only downloading an app from the market, not flashing anything or whatever, would not screw up my phone.
anyway, since my data is lost, i wanted to try again. can i flash the unrevoked S-ON utility and then the latest Sprint RUU and then re-root? i read somewhere else that it won't remove my wimax/RSA keys or SD card, is that correct? is there a way to backup my RSA keys before I do anything else? should i do that, re-root, then nandroid, then mess with stuff? i basically wanted a stock Sprint EVO but one that's rooted so i can run root-based apps, that's what I want to get to.
Flash the Amon Ra recovery via the AR pc36img.zip file in hboot method, then reboot to recovery, do a full wipe/factory reset and try to boot to system.
I used AlphaRevx to achieve S-OFF and when it asked if I wanted the CWM recovery, I said yes. It installed the recovery properly. I have SU. However, if I try to run Titanium, it says that there is no root access. I have rebooted several times. I tried to flash CM7 and it was stuck in a bootloop. Downloaded from the mirror and it booted up fine. I tried playing around with ROM Manager while I was booted into CM7 and it told me there was no recovery image on the root of the SD card.
Hopefully it's just something simple that I'm overlooking. Any suggestions?
Another thing I though was weird is that I couldn't sync to Gmail while booted into CM7.
To gain root access on the stock rom, you first have to flash thisthrought recovery.
I actually did flash that as well. Still had the same results.
Should I have removed the SU file that was already installed on the sd card and then flashed the patch?
Hmm weird, maybe try flashing one of these 2 roms
this
or
this
Both are based off the stock froyo rom, debloated and rooted.
I'll probably give that a try in a little bit. I suspect that it will not work as I didn't even have root access with CM7 installed.
Maybe before you flash clear all the data at least 2 times, do a factory reset, and clear the dalvik cache. If nothing works try the manual way to flash CWM and reflash it.
I only wiped data/cache once before I flashed each time. I'll try wiping more than once next time.
Do you think I could have flashed a corrupt file for SU?
brocksdad said:
I only wiped data/cache once before I flashed each time. I'll try wiping more than once next time.
Do you think I could have flashed a corrupt file for SU?
Click to expand...
Click to collapse
Make sure you wipe /data, /cache, /system before you flash any rom. If you do this it removes the chances for errors to occur. if you flashed CM7 over the original /system, you might have corrupted the su file.
I don't think that I did, but it is possible. I'll first start by removing the SU file that is on there now and then flashing the patch that you posted up. I'll update after I do that.
I have to wait though, my battery is dead.
Thanks for your help!
No problem. If you didn't format the /system before you flashed CM7, you flashed over the original /system, sometimes it makes no difference, sometimes it messes stuff up. Kinda hit or miss.
Yah normally doing a Factory wipe then a wipe data/cache/dalvik should get her done try rerunning alpharev utility and see what you get
Update: I removed the su-2.3.6.1-ef-signed.zip from the SD card and then flashed the patch. Still having the same issues. I tried to run AlphaRevX again and it came back saying something like "You already have S-OFF with AlphaRev. What do you think you're doing?"
Any other suggestions?
First of all i s-offed and cwmed with alpharev.
Then in cwm i wiped phone + cache + dalvik .
Then flashed this http://forum.xda-developers.com/showthread.php?t=1138274
Then after phone boots and so on i restart in cwm again and flashed this
http://forum.xda-developers.com/showthread.php?t=1160745
After all i got SU in programs and got root for all my apps.
Try this )
The whole point of this is to have Titanium backup installed so I backup all my apps before I flash a ROM.
brocksdad said:
The whole point of this is to have Titanium backup installed so I backup all my apps before I flash a ROM.
Click to expand...
Click to collapse
Hey brocksdad,
Why not give this a shot as this is what I had to do:
-Alpharevx s-off which you've done
-flashed CWM via fastboot adb which seems like you've done: http://forum.xda-developers.com/showthread.php?t=1134520
-flash this patch which will install superuser, busybox, and rooter kernal in the correct places /system/xbin: http://forum.xda-developers.com/showthread.php?t=1134520
-reboot and you should be good to go.
I think you were having the same issues I was in that the SU app would not update the binaries for me, so I had to install the manual patch I found in the development forum.
Let me know if this works for you....
If I wanted to manually put the CWM recovery in there do I just flash OVER what I already have or do I need to remove the recovery that is already installed? If I have to remove it, how do I go about doing that?
brocksdad said:
If I wanted to manually put the CWM recovery in there do I just flash OVER what I already have or do I need to remove the recovery that is already installed? If I have to remove it, how do I go about doing that?
Click to expand...
Click to collapse
You would just reflash over the recovery. I'm hoping you used the recovery that was posted for us and not the one with Rom Manager as that is an older recovery that hasn't been updated for Inc2 support yet.
In any case, it wouldn't hurt to go and do the process over again. You should have fastboot.exe in the same folder as your adb and might as well have the CWM flash .img in that same folder as well to make things easier. once you do that you can flash the SU patch in recovery and you should be good to go.
Update: By the way if you need adb, you can just download the files from the "Temp Root" post in development and download fastboot.exe by searching in google.
I used the recovery that the AlphaRev tool gave me.
I'll give that a try and see how it goes.
Thanks!
brocksdad said:
I used the recovery that the AlphaRev tool gave me.
I'll give that a try and see how it goes.
Thanks!
Click to expand...
Click to collapse
Okay then you should be fine. Go ahead and flash that SU zip in recovery mode. Once you reboot, open up superuser and go to settings. Check the SU binary and make sure it says v2.3.2-efgh (eclair, froyo, gb, honeycomb).
If it does then you should be good to go. Also make sure when there are md5 sums provided by the uploads that you check those to make sure they match so that you don't try flashing corrupted downloads. There's a free app in the market for checking the md5 sums right on your phone, it's called AFV (Android File Verifier)
I just looked at the SU information. It says v2.3.6.3. Underneath it says SU binary voutdated. I tried to update and it comes back with an error saying that su-2.3.1-bin-signed.zip has been placed on the sd card. Please reboot into recovery mode and flash it to update the SU binary.
hello, i just got my first android phone so I'm new to this sort of stuff, though I love being able to unlock hidden potential of different devices, so naturally I discovered the ability to root smart phones and all that good stuff.
The model I have is the Samsung Galaxy Gio GT-S5660M. It's running 2.3.4. Gingerbread version.
I've been reading a lot of guides and for the most part rooting and adding additional utilities like flash, etc. seems pretty simple. However, I have not yet been able to find out how to create a back of up of my stock firmware when I bought the phone in case I end up bricking it, or decide I want to return to stock.
I've read many guides that claim to show how to create back ups and recovery points, but I'm still having trouble understanding it.
To be more specific, I would like to create as opposed to download, a back up of the phone in it's current state which is, as I said earlier, stock. I did a factory reset since I had some stuff installed while I was fiddling with it for the first time.
thx
You have to root it before you can back up stock rom so, firstly you root it (you can find guides here on xda)
Then install clockworkmod recovery: warning: DON'T EVER USE ROM MANAGER TO INSTALL CLOCKWORKMOD ON YOUR GIO, IT WILL BRICK YOUR PHONE!! use one of the recoveries found in xda, you will also find guides to install them there.
Then third; backup in clockworkmod using "backup and restore"
Sent from my GT-S5660
iok1 said:
You have to root it before you can back up stock rom so, firstly you root it (you can find guides here on xda)
Then install clockworkmod recovery: warning: DON'T EVER USE ROM MANAGER TO INSTALL CLOCKWORKMOD ON YOUR GIO, IT WILL BRICK YOUR PHONE!! use one of the recoveries found in xda, you will also find guides to install them there.
Then third; backup in clockworkmod using "backup and restore"
Sent from my GT-S5660
Click to expand...
Click to collapse
so first of all, what I'm looking for is called a ROM right?
what I don't get though is how come I need to modify the device before creating the backup. Isn't the phone modified at that point? Or is the stock configuration being stored somewhere on the phone that I can't see without clockwork?
You cannot create a backup without the recovery mod CWM Clockwork Recovery Mod. But to install this you need your device rooted (modified so you can modify and view system files)
gfyrdr said:
so first of all, what I'm looking for is called a ROM right?
what I don't get though is how come I need to modify the device before creating the backup. Isn't the phone modified at that point? Or is the stock configuration being stored somewhere on the phone that I can't see without clockwork?
Click to expand...
Click to collapse
1 - you don't need to search for a rom to backup your stock rom
2 - you need to root your phone in order to be able to backup your rom
3 - you need to install a more advanced recovery (program "similar" to pc BIOS) in order to do a nandroid backup
4 - after you flash that more advanced recovery (aka CWM -> ClockWorkMod), you backup your rom in "backup and restore" menu, backup. It will then store your rom in a folder.
5 - you should strongly consider after that, to install a custom rom made by many of the devs here on XDA in order to have a better experience with your phone...
0M3G4_ said:
1 - you don't need to search for a rom to backup your stock rom
2 - you need to root your phone in order to be able to backup your rom
3 - you need to install a more advanced recovery (program "similar" to pc BIOS) in order to do a nandroid backup
4 - after you flash that more advanced recovery (aka CWM -> ClockWorkMod), you backup your rom in "backup and restore" menu, backup. It will then store your rom in a folder.
5 - you should strongly consider after that, to install a custom rom made by many of the devs here on XDA in order to have a better experience with your phone...
Click to expand...
Click to collapse
+1 That was what I wanted to say
I've already uploaded a stock ROM backup last fall of the same Gingerbread ROM you're running, along with instructions on how to make one yourself or flash mine.
The best advice I can give you is: research, research, and more research.
Good luck,
Darkshado
Sent from my Nexus S using XDA
What software do you recommend to clockworkmod Gio with?
s!mon said:
What software do you recommend to clockworkmod Gio with?
Click to expand...
Click to collapse
I use px-cwm-v2.zip recovery.
You flash it using stock recovery.
thx for the replies. I will give it a try.
Darkshadow, whats the thread's name where you posted the ROM and instructions? I'd like to check that out too.
Also, whats a good rom to consider upgrading to? Something that has the ability to play flash videos.
EDIT:
If I understand correctly, roms are basically whole operating systems that have been customized by the developer. So a rom can be already rooted and have clockwork as well as other custom stuff, and I just need to flash it. The alternative to this is to do everything manualy... root the current OS, add clockwork and whatever else. Correct?
Also, I'm not sure yet if a rooted phone has any extra options on it's own, or if it's only a set up that's sole purpose is to allow other applications to be installed who then will give the user better control over his device.
I've run into a little problem.
I'm following this guide: http://forum.xda-developers.com/showpost.php?p=16963172&postcount=1
I've got Odin and the tar downloaded, but when I go into download mode with my phone and connect it to the PC, it says that the device driver was not successfuly installed, and I get no confirmation in Odin that a connection has been made between the phone and the program.
What am I missing?
Thx.
EDIT:
Nevermind, I needed to install Kies. Don't even need to run it. Apparently it has the driver that's needed.
Okay, I've rooted my phone successfully. Now the next step is to install Clockwork and create a back up.
Now that I understand a little bit the way Odin and flashing ROM works, I think it would be better to just download a stock ROM and in case something goes wrong, I can just flash it the way I flashed the rooted one.
(I think I saw a completely stock ROM somewhere for my model but I don't remember where. A link would be appreciated if it exists.)
Correct me if I'm wrong pls.
Also, if I do that, then is there any reason to install Clockwork since I've read that many ppl have issues with installing it and it's riskier than rooting or installing other software.
Right now I think what I'm most interested in is installing Adobe Flash Player 11 or something of the sort that can play flash videos and streams.
^
http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
taken from the sticky
i'm also thinking of installing cwm
looking at the sticky, http://forum.xda-developers.com/showpost.php?p=20397988&postcount=8
how outdated is this cwm?
I'm using Opera as my browser so from what I've learned, flash doesn't work with it period. Is skyfire a good alternative?
Also, like I said, I don't think I need the clockwork if I can get a clean stock ROM that I can just flash if something goes wrong. As I don't intend to download many apps or add many phone numbers (memorized instead), a backup isn't really needed.
nvmd, i just went ahead and installed the cwm in that link, there's a 5.0.2.7 though if that is even the newest one
now, i cant seem to backup my phone
it says it cannot mount /system
try dolphin browser
anonxlg said:
nvmd, i just went ahead and installed the cwm in that link, there's a 5.0.2.7 though if that is even the newest one
now, i cant seem to backup my phone
it says it cannot mount /system
try dolphin browser
Click to expand...
Click to collapse
Did you pick the ext4 + rfs version?
Sent from my GT-S5660
Clockwork is not riskier than other things you do. Just follow steps and you see no problems.
anonxlg said:
^
http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
i'm also thinking of installing cwm
looking at the sticky, http://forum.xda-developers.com/showpost.php?p=20397988&postcount=8
how outdated is this cwm?
Click to expand...
Click to collapse
its an older version, its 5.0.2.7, theres also 5.0.2.8 but these give some problems after installing/wiping, so some people still use the older version.
Hello guys,
I'm new here. I have the same problem as anonxlg. It says can't mount system. I also used the version from the big thread for new users. Can anyone enlighten me on what to do? I've been searching the forum and google, but can't make it work. I feel like a compleet noob now, and I don't feel special about it.
RJ88
Edit: I kept searching, and finally found a working 5.0.2.7 version. First I had another 5.0.2.7 version, but when I tried to install it didn't work. I finally found "signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip (Flash from Recovery)" on http://forum.xda-developers.com/showthread.php?t=1421650 (through google actually. I have to get used to this site), and I'm making my backup now.
thanks RJA88, backup worked
edit/update
i used the cwm linked and backup worked, i tried installing cm9 beta8 (galaxyics), and it would get stuck after samsung bootscreen (it flashes a white pick or soemthing before full back screen)
i tried restoring backup i made, and it didnt work, some mount error again
i reverted back to 5.0.2.6 and did the restore backup again, and this time it goes up the the galaxy gio gt5660m screen and just stop..
note that i do not know what the rfs/ext4 is for for the gio if that is what is causing problems
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
I've owned a Galaxy S II before, and had it rooted. I followed all the steps, did the odin CWM push, flashed su in recovery, phone has su on it, but locks up when requesting root permission. Use su fix, and it says not rooted. In recovery if I go to one of my older back ups from my old s II, it flashes 1 of them, it boots, but it's a very old version, not ICS which I want. I try to flash a new rom, and within seconds it says it's completed. I've tried MIUI, and CM10 stable version. They get to the boot screen, but goes no further. I let both of them sit for over 10 minutes, each time I would go back into recovery factory wipe, and davlik wipe multiple times to make sure the wipe went through, fix permissions, but still won't boot. I've tried to odin CWM again, and reflash su, and it always says it works, but I still don't have root. Any advise? I basically just want to get a good stable version of CM10. If anybody has a way to upload me a restore point I can flash, I'd be much appreciative of that. I don't know a whole lot to the rooting scene, but I've done it quite a few times, so I'm pretty sure I didn't screw up. The phone works fine, I just noticed after using su fix, my battery drains a lot faster now on stock rom, and that's only with wifi enabled, and bluetooth. I'll lose over 50% in less then 2 1/2 hours with maybe 20 min. of heavy use. I'm sorry if someone already posted this same issue, but I've been searching and searching and can't find a solution. Thank you for any help, or taking the time to read the post, I love XDA, it's the best forum, and you guys are amazing.
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
nashy10 said:
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
Click to expand...
Click to collapse
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Dagouk said:
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Click to expand...
Click to collapse
Clean flash again, if it hangs again, go back to recovery, clear cache, reboot, might help
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
drakulina said:
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
Click to expand...
Click to collapse
The links are dead links, I've already tried that post. I used the original cwm I users with my first have, just a different su.
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
sinfulgray said:
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Did the play store su update already. Other then that don't see a way to update the binaries.