Related
I just rooted my evo 2.2V following the incredible instructions outlined on XDA. now i have ROM manager installed. I did a backup using the ROM manager app and also downloaded the CM6 ROM using the same app. butwhen i tryed to flash the rom it did not go through. The phone rebooted but gave an error even befour the process could start. I tried it again using the ROM manager with the same results. What could be the issue? the original ROM was downloaded by ROM Manager and is still in the memory and every time i try flashing it, it just comes up with an error and i have to restore the backup. Could this be due to a corrupted dowload or something else. Thanks in advance for the help guys.
I recently used ROM Manager to d/l and flash CM6, no issues. But now when I use it to backup the ROM, it freezes up on a f/c screen after the backup is completed and is rebooting. Replicated the issue twice to be sure. Have to pull the battery. So much for not having to do a real nand, lol.
Still searching for the right thread for my issue.
Update: Cleared d/l cache, flashed RA 1.8 then reflashed Clockwork, all better.
ISIDHU said:
I just rooted my evo 2.2V following the incredible instructions outlined on XDA. now i have ROM manager installed. I did a backup using the ROM manager app and also downloaded the CM6 ROM using the same app. butwhen i tryed to flash the rom it did not go through. The phone rebooted but gave an error even befour the process could start. I tried it again using the ROM manager with the same results. What could be the issue? the original ROM was downloaded by ROM Manager and is still in the memory and every time i try flashing it, it just comes up with an error and i have to restore the backup. Could this be due to a corrupted dowload or something else. Thanks in advance for the help guys.
Click to expand...
Click to collapse
I'm not qualified to tell anyone how to do anything, but you can find directions on how to d/l and place the rom on the root of your sd card, then flash it with recovery. Search out flashing roms and I'm sure you'll get it done.
Clearing and reflashing clockwork on rom manager before you try might not do any harm as well. Never know. Read up, don't trust my word, lol.
ISIDHU said:
I just rooted my evo 2.2V following the incredible instructions outlined on XDA. now i have ROM manager installed. I did a backup using the ROM manager app and also downloaded the CM6 ROM using the same app. butwhen i tryed to flash the rom it did not go through. The phone rebooted but gave an error even befour the process could start. I tried it again using the ROM manager with the same results. What could be the issue? the original ROM was downloaded by ROM Manager and is still in the memory and every time i try flashing it, it just comes up with an error and i have to restore the backup. Could this be due to a corrupted dowload or something else. Thanks in advance for the help guys.
Click to expand...
Click to collapse
Have you tried other roms besides cm6? You will need the .76 hboot with that one. If you are having issues flashing any rom, then you will meed to try unlocking your nand again with toasts Eng bootloader.
Sent from my PC36100 using Tapatalk
So today after flashing a new rom and then going back to my nandroid backup of my previous rom SetCpu said I do not have root. I'm extremely worried. My phone is/was rooted of course seeing I could flash roms and SetCpu would work just about 25 minutes ago. Would anyone know what to do, rooting my phone previously was such a pain in the a**. Do I have a basta*d Desire HD? Someone be my savior!!
Check other apps that need root, like titanium backup. Still no root message? What ROM are you running? Did you do a full while when you flashed?
I always wipe data before restoring a NAND backup. You could try clearing data for superuser.
Superuser
Do you have the Superuser application?
The superuser app is still there just not working i guess and no app that uses root is working I don't know what to do. Will I have to re-root my device
Did you do what I suggested and do a full wipe then reinstall the backup? Did you try clearing your data for the superuser app?
MeNaCe2s0cieTy said:
So today after flashing a new rom and then going back to my nandroid backup of my previous rom SetCpu said I do not have root. I'm extremely worried. My phone is/was rooted of course seeing I could flash roms and SetCpu would work just about 25 minutes ago. Would anyone know what to do, rooting my phone previously was such a pain in the a**. Do I have a basta*d Desire HD? Someone be my savior!!
Click to expand...
Click to collapse
It happened to me today after I had done what you did. I dont have setcpu. Titanium on my Unity said it doesnt have root. tried everything the guys mentioned here, apart from clearing the data of superuser.
Anyway I did a full wipe, with system format as well, and reflashed Virtuous Unity. All seems fine now.
I had the same problem. Fortunately I had a flashable superuser zip that worked every time. I always keep it on the root of my SD card now just in case. Let me know if you want it and I'll upload it tomorrow from my laptop.
Sent from my Desire HD using xda premium
michael_duvalle said:
I had the same problem. Fortunately I had a flashable superuser zip that worked every time. I always keep it on the root of my SD card now just in case. Let me know if you want it and I'll upload it tomorrow from my laptop.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I'd sure love to have it...you never know when you get hit by another no-root issue.
Try clearing Superuser data if you have access to Settings Menu (i was suggest but if you did or not )
<Menu>, <Settings>, <Applications>, <Manage Applications>, select the <ALL> tab, wait for everything to load, scroll down and select Superuser, <Clear Data>
I don't know what is wrong with Superuser app, but it keeps locking new apps from root automatically without asking.
are you sure that the new ROM is rooted ? try rooting it by visionary+
There you go mate. This always worked for me. Flash in recovery.
mak3040 said:
Try clearing Superuser data if you have access to Settings Menu (i was suggest but if you did or not )
<Menu>, <Settings>, <Applications>, <Manage Applications>, select the <ALL> tab, wait for everything to load, scroll down and select Superuser, <Clear Data>
I don't know what is wrong with Superuser app, but it keeps locking new apps from root automatically without asking.
are you sure that the new ROM is rooted ? try rooting it by visionary+
Click to expand...
Click to collapse
Did not work for me. I lost root again when I restored a different rom.
michael_duvalle said:
There you go mate. This always worked for me. Flash in recovery.
Click to expand...
Click to collapse
Worked like magic.
michael_duvalle said:
There you go mate. This always worked for me. Flash in recovery.
Click to expand...
Click to collapse
i have a similar issue. i rooted my sensation using revolutionary
towards the end it kept restarting the phone and going into the boot screen, and then restarting it again. it did this about 3 times, and then it said it failed. i restarted my phone to the boot menu, and it shows s-off. i tried running the revolutionary program again to make sure, and it confirmed this.
i then got the leedroid mod and flashed that to my phone. the leedroid mod works well, just whenever i try to access superuser it crashes. i tried accessing titanium backup and adfree and when these request for permissions, i get an android notification that superuser has crashed and the request times out.
i tried using this fix, but this errors as well...
any assistance in resolving this will be greatly appreciated
thanks
hi
i had the same problem with trying some new roms and restoring nandroid.
i fixed this problem with: Rom Manager -> correct permissions -> reboot
best regards
Ok so for some reason. When I try to backup my ROM. it just goes to clockwork recovery. And sits there! any ideas? Was working great before! Thanks
Killing Zombies With My Samsung Galaxy S2
How do you backup your rom? I'm going to guess you're using rom manager, based on the very little information you gave in the OP.
If you're in clockworkmod already, all you need to do is go down to the backup/restore, then backup.
If you normally used rom manager, and it used to backup automatically for you once rebooted into cwm, then it's a rom manager problem most likely. Did you just update it or something? (I never use rom manager, while it's a nice interface, it causes problems too often for my taste. I've tried it across a wide range of devices too.)
If none of these are the answers you were looking for, a bit more information would help. (Again, these are all guesses based on what you gave me to work with )
Yea I was using clockwork mod to make a backup of my Rom but now it won't work.just boost me into the recovery screen. So Im going to just use that to make a backup from now on! Only used it because you can name it! Easy to keep track of the backups that way!
Killing Zombies With My Samsung Galaxy S2
Any news on what's up with Rom Manager/clockwork mod recovery? Still not backing up roms. Just boots into the recovery menu but won't start backing up for some reason.yes I know I can just use recovery to back up my rom.but I already paid for the pro version so I want to use it.any ideas? Thanks!!
Killing Zombies With My Samsung Galaxy S2
reinstall clockwork recovery
This is also happening to me. I try to back up my current ROM and it just reboots, starts CWM recovery mode, then does nothing.
i was having a similar problem before, but then i went into recovery mode and backed it up there instead, worked flawlessly.
Glad im not tge only one that noticed. I like using it because you can name your back ups before they happen. I get lost trhing to find backups with their default names.
Sent from my SGH-T989 using XDA App
My problem its the opposite,I was able to make to nand backups just before changing the stock rom, installed Juggs and then wanted to go back to stock and both my backups failed in the mdsum.
I have the same issue but its not that serious once in recovery just manually do it the old fashion way .
Sent from my SGH-T989 using XDA App
same issue on skyrocket...
I have been experiencing the same issue on my skyrocket for about 5-6 days I would guess.
Same issue for me. Won't even bring up my old backups but I see them with root explorer. Any help on resolving this issue would be appreciated....
UPDATE- Seems to be an app issue - look at the feedback left. Hopefully they will fix it soon. In the meantime, I am just doing it the old fashioned way as someone posted earlier.
a lot of people are mixing up clockworkmod recovery with rom manager...
your "RECOVERY" IS CWM, so yeah do your backups and restores in CWM not rom manager. rom manager doesn't work right...
you can always rename the folder for your backups.
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
edit: CWM v5.5.0.4
do you try "wipe cache" and "advanced->wipe dalvik cache?"
Thanks, I just tried, it took quite a while to clear the cache. When I booted up it went through a whole Optimizing Apps process, I'm not sure if that was due to wiping the dalvik cache? But it still didn't fix the Rom Manager issue.
Its probably not yet compatible if you have the touch version of cwm installed, so it wants to flash the standard one. Or you could always just let rom manager just reflash cwm overtop and then you may be good to go.
EvanVanVan said:
Rom Manager doesn't seem to know that I've got CWM installed. When I rooted and installed CWM I didn't do it through Rom Manager originally. Now CWM won't let me use it to manage my backups and keeps asking me if I want to install CWM? I've got Google Wallet installed so I'm a little nervous flashing things needlessly.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
I don't have the touch version installed (doesn't seem to be the touch version anyway). I should have said this in the first post but it CWM v5.5.0.4.
Herman76 said:
Maybe it can't detect it? I know we had to set which CWM version we had installed on the SGS.
Maybe try to run the install?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Flashing CWM over CWM shouldn't wipe my phone right? It's only the stock bootloader that requires a full wipe?
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Clancy_s said:
I installed ROM manager and then CWM via ROM manager last night and its CWM v5.5.0.2 which ROM manager thinks is the latest: perhaps it can't deal with 5.5.0.4 yet...
Click to expand...
Click to collapse
ah, that would probably do it...guess i'll just wait it out a little longer, thanks
I have the exact same issue as this Rom Manager refuses to see I have CWM installed so just keeps telling me I need to install it it also can't download and flash its own version and just freezes after download
So any updates on this or more users experiencing it ?
I think I've found the solution. In ROM Manager tap the menu button at the top and then tap Manual Flash Override. Next it'll ask you if you've flashed CWM manually so tap OK because that's what we've done. Next pick which GN you have and then choose CWM 3.x+. There you have it, it should work now.
Don't use ROM Manager - problem solved!!
Seriously, though, it's a TERRIBLE piece of software
I'm fairly new to using it but it seems decent, why is it so terrible? I had an eris before this and did everything manually through recovery, this seems like it's a lot better than that.
It's just more trouble than it's worth. Why not just manually flash CWM using fastboot and get your head around that as opposed to an app which can - frankly - break things?
Flashing it via fastboot is what causes the above issue. Since you flash it manually rom manager can't see it, that's why I posted the above steps to kind of "force" rom manager to see the manually installed version.
But if you're not using ROM Manager then what's the issue? Copy ROM to SD card, reboot to recovery, flash ROM...where is ROM Manager needed in that equation?
If you're not using it then there is no issue, but this thread isn't about using it or not, it's about getting it to work with the galaxy nexus when you manually flash CWM.
I like it for the backup and restore feature and being able to change the names used to backup
I searched and looked at other threads with people having the same problems, but none helped, and none of those threads had an OP with the Galaxy S3.
So here's the thing, I got rooted yesterday, and it was all good. Then today, I flashed the LiquidSmooth ROM and GApps with ROM Toolbox, and it went fine. Then I decided I wanted to try a different one, so I flashed to my backup, and that went fine. So I downloaded and put both the PACman ROM with GApps 4.1 from like 12/12, and RootBox with the newest 4.2 GApps onto my internal SD. However, I'm using ROM Toolbox, and when I added RootBox and the 4.2 GApps to the queue, in the right order, and told it to install them, and to wipe the devik cache (I think that's what it's called) and to delete all the data and stuff like you are supposed to, it booted into recovery, wiped the data, and then just stopped. So I had to restore to my backup, which the newest one vanished, so I had to use the day old one.
Next I booted into recovery, to manually add the files myself, however, they weren't there. The only thing that showed up was the old 4.1 12/12 GApps, and nothing else. I then tried to install PACman and the 4.1 GApps from ROM Toolbox, but it did the same thing, and I had to restore to my back up.
Can anyone maybe shed some light to why the ROM's aren't coming up?
When you looked for the ROMs in TWRP, which directory did you look in? Did you download the ROMs via ROM Toolbox?
Sent from my SGH-T999 using xda app-developers app
GhostIsBaked said:
When you looked for the ROMs in TWRP, which directory did you look in? Did you download the ROMs via ROM Toolbox?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I looked in the sdcard directory I'm pretty sure. And I just downloaded RootBox from ROM Toolbox, and tried to install it, but it did the same thing and didn't work.
My phone only had like, 35% battery when I did this, could that be a problem?
NorNichols said:
I looked in the sdcard directory I'm pretty sure. And I just downloaded RootBox from ROM Toolbox, and tried to install it, but it did the same thing and didn't work.
Click to expand...
Click to collapse
If you're going to manually flash it through recovery, Root box should be in directory /sdcard/romtoolbox/download/ or something similar since ROM toolbox creates its own folder
Also when you say it just stops, what do you see on your screen?
Sent from my SGH-T999 using xda app-developers app
Well, if I start it through ROM Toolbox, it reboots into recovery, and then says like, wiping data or something similar, and then it goes back to the TWRP home screen, and then if I boot back into the system it's just stock, and then I have to restore to my backup.
And if I flash it manually, wont' it not matter where it is, or isn't it supposed to be in the root of the sdcard? Like, I can see if I was doing it through ROM Toolbox, but when I do it manually, it shouldn't matter, right?
Okay, so I just tried again, and it the last thing it says is (this isn't word for word, closest I can remember) Something cash make4ext.something or something close to that. Then it just goes to the home screen of TWRP.
Okay, so this is what just happened, I went to install LiquidSmooth again, and it said, Unable to locate zip file '/sdcard/romtoolbox/downloads/blahblahblah(doesn't show full directory)
E: Error installing zip file
Checking for MD5 file
E:No MD5 file found
Error flashing zip
NorNichols said:
Well, if I start it through ROM Toolbox, it reboots into recovery, and then says like, wiping data or something similar, and then it goes back to the TWRP home screen, and then if I boot back into the system it's just stock, and then I have to restore to my backup.
And if I flash it manually, wont' it not matter where it is, or isn't it supposed to be in the root of the sdcard? Like, I can see if I was doing it through ROM Toolbox, but when I do it manually, it shouldn't matter, right?
Okay, so I just tried again, and it the last thing it says is (this isn't word for word, closest I can remember) Something cash make4ext.something or something close to that. Then it just goes to the home screen of TWRP.
Okay, so this is what just happened, I went to install LiquidSmooth again, and it said, Unable to locate zip file '/sdcard/romtoolbox/downloads/blahblahblah(doesn't show full directory)
E: Error installing zip file
Checking for MD5 file
E:No MD5 file found
Error flashing zip
Click to expand...
Click to collapse
What version of TWRP are you on?
Try flashing it through TWRP without using toolbox
Download liquid smooth
Download
Steps:
1.Boot into recovery
2.create backup if needed
3.wipe dalvik cache
4.wipe cache
5.wipe factory reset
6.wipe system
7.install- Select the ROM .zip and install
8.Install the 4.2 gapps (12-12)
9. Reboot system
Sent from my SGH-T999 using xda app-developers app
Well actually, I wanted to try the PACman ROM next, so could I just download that and do all the same things, but with that, and instead of the 4.2 GApps, use the 12/12 4.1 GApps?
Also, I'm using 2.3.3.1, and I see that there is a newer one. Can I just flash that one over this one using ROM Toolbox?
NorNichols said:
Well actually, I wanted to try the PACman ROM next, so could I just download that and do all the same things, but with that, and instead of the 4.2 GApps, use the 12/12 4.1 GApps?
Also, I'm using 2.3.3.1, and I see that there is a newer one. Can I just flash that one over this one using ROM Toolbox?
Click to expand...
Click to collapse
Yea but make sure it's specifically for this device (d2tmo/sgh-t999)
The 12-12-12 gapps are 4.2 which are the correct ones to use for PAC Man as well.
DO THIS FIRST
Easiest way to update it is to download GooManager from the playstore. Once, installed, press menu button and install the open recovery script. Latest is 2.4.1.
Sent from my SGH-T999 using xda app-developers app
rnedkle and
It's still not there, I dragged and dropped it into my phone on my computer, but I don't see it. GApps is there, but not the ROM.
I'll try GooManager now, just weird that ROM Toolbox was working earlier and so was TWRP, but now TWRP can't find the ROM and ROM Toolbox can't install things. I went from thinking, wow this isn't hard at all, to, why won't this work! I'll download GooManager in just a bit, my phone is restoring to a backup.
NorNichols said:
It's still not there, I dragged and dropped it into my phone on my computer, but I don't see it. GApps is there, but not the ROM.
I'll try GooManager now, just weird that ROM Toolbox was working earlier and so was TWRP, but now TWRP can't find the ROM and ROM Toolbox can't install things. I went from thinking, wow this isn't hard at all, to, why won't this work! I'll download GooManager in just a bit, my phone is restoring to a backup.
Click to expand...
Click to collapse
OK. I'm gonna catch some sleep for a bit. I'll check back in the morning. Hope everything goes alright man :thumbup:
Sent from my SGH-T999 using xda app-developers app
GhostIsBaked said:
OK. I'm gonna catch some sleep for a bit. I'll check back in the morning. Hope everything goes alright man :thumbup:
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Okay, I appreciate the help. Sleep well.
For anyone who see's this next, just tried GooManager, also didn't work, so I'm pretty much going to give up for the rest of tonight and see what any of you have to say tomorrow. This is a bummer, but oh well, it's just weird that it was working fine and now it won't. I'm going to bed.
You putting these on intsd or extsd? You can't see them through TWRP, the phones file browser, or the computer? Unmount/remount the extsd in Storage settings.
Don't flash through an app. Flash things manually through recovery. If you always use an app to flash for you, you don't learn how to fix problems when you run into them.
You can Odin TWRP from my signature (hopefully you have Mobile ODIN), or here's a zip: http://db.tt/0SzQ0aK7
I bet all of your ROMs are still on your phone. The latest JB creates partitions in your memory. These partitions are for multiple users. Your problem is amplified by having an old recovery. You can locate all of your stuff by going to your memory and going through the folders that start with emulated/0. The latest recovery will fix this issue and you'll be able to use ROM toolbox to flash.
GBP85 said:
I bet all of your ROMs are still on your phone. The latest JB creates partitions in your memory. These partitions are for multiple users. Your problem is amplified by having an old recovery. You can locate all of your stuff by going to your memory and going through the folders that start with emulated/0. The latest recovery will fix this issue and you'll be able to use ROM toolbox to flash.
Click to expand...
Click to collapse
How do I get into the memory to find emulated/0?
Edit: I flashed CWR, and it worked just fine...but then I decided I didn't like the PACman ROM, so now I'm back to restoring back to normal...I guess next I'll try Carbon or Rootbox.
Edit2: Aww dangit, guys I'm a failure. It's stuck on the Samsung logo after you pass the tmobile one, so now I am back into recovery and reset everything and formatted and stuff, and now I'm trying to restore from the backup again...I think if I fix it, my flashing ROM days are done for awhile.
Edit 3: Ended up using Odin to get a rooted stock build on there, then downloaded ROM Toolbox, flashed TWRP, put the backup back on my phone since I have a copy of it on my computer, restored, and now we are all good.