Related
So, I've tried following the directions for the "nearly" one-step root, and the process completes, but I get no response when I run the Super app, just a blank screen. Is that normal?
Also, from what I've been able to find, it appears there are no released SBF's for the R2D2, so if I brick my phone, I'm SOL. I don't want to end up with a non-warranted paper-weight, so for now I unrooted it....however...did I do something wrong, and if so can someone fill me in?
Thanks!
which one step? I used the Z4root and had zero issues. Rooted within a minute.
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
osufans said:
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
Click to expand...
Click to collapse
Super user app is blank until root apps are used.
For now I wouldn't use a ROM manager you need Koush's Bootstrap to be able to do a backup. It's on the market. To use it just tap the Bootstrap button then wait for the success toast (box) and then tap Reboot Recovery and your phone will boot into Clockwork mod. Backup will take an img of the phone as it is at the point where you backed up. To restore if you mess something on a later install but if you can't get into clockwork for some reason you might be out of luck. Because there is no SBF specifically available for the R2D2 D2 but I've heard that the 2.3.20 might unbrick bricked R2D2's but you won' have the same verizon version you have now it'll be a step back.
OK. I do have bootstrap recovery installed and was able to perform a backup.
Also found a link to some of the bloatware you can "safely" remove. I'm still tweaking it....but that being said, what else can you do (i.e. - overclock, etc.)?
You can overclock, install libs and bins that access hardware features locked out by vzw, change roms and themes....yada, yada.....the 2.3.20 sbf is not a step back. The radio update and kernel tweaks for battery life are not in the 2.4.5 system. They had the rom version because some files are different between the two.
Sent from my DROID2 using XDA App
Longtime HTC user here (currently using a Nexus One). Figuring it would be very little issue to root my buddy's Moto Droid X, I set off on a trial of these "one click root" apps available.
While it seems I was able to get root access, I couldn't get a ROM to install due to signature errors. The reason I say I was seemingly able to get root was because I was able to access ROM Manager without warnings that I didn't have root.
However, when trying to use something as simplex as the WIPE function, it only rebooted the phone. Attempting to install a ROM was fruitless as well.
I am running Windows 7 64 bit with all the Moto drivers. I have attempted to use all of the different USB modes. I can ADB into the phone, but nothing else seems to work correctly.
I was about to switch carriers and buy a Moto phone. This just sold my N1 back to me. I loathe this proprietary garbage.
Well there's no need to connect the phone to the pc. Use z4 root then you need Droid x bootstrap from the market to gain access to clockwork. Rom manager wont work.
You can also download the Bootstrap Recovery for free from Koush's website.
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Once you get the Bootstrap installed you have to click the button to reboot into recovery. This one doesn't replace the stock recovery, so you have to specifically reboot to Bootstrap Recovery. Once there, MAKE A BACKUP. Then select Mounts and Storage, Mount System, back out and select Install zip from SD, disable signature verification in that menu, then Choose zip from SD and you're done. Most ROMs require a data wipe to boot properly.
Thanks guys. I will try this tonight when my buddy comes by again. Really appreciate the help
About to dig in on this now. I know it will be debatable, but what is the most refined ROM out for the X? He doesn't care about the flashy stuff, just wants to get his phone more reliable than it is stock.
Issues he has mentioned with the stock ROM:
*Slowing down of internet (clearing cache seems to help)
*Lock ups while trying to hangup/calls coming in.
*Lagging while texting to the point of a full lockup.
So a ROM that has focused on these issues would be grrrreat. Thanks again folks!!
What's his take on blur? If he doesnt mind the blur then i would suggest apex 1.4... you can add the blur you want, etc and to me it has the best battery life of the roms I've flashed on my phone...
Sent from my DROIDX using XDA App
On stock rom only Z4 rooted - .07p radio and .340
How can i get to the offical GB?
Also is there anything i can do to backup my apps and settings so i don't have to redownload and reset every app?
There are currently a ton of posts with these instructions. Search next time.
Anyways. Go to the following link and follow the 2 part instruction and it will work perfect and will still be rooted.
www.mydroidworld.com/forums/droid-x...-5-596-release-thread-something-everyone.html
Sent from my DROIDX using XDA App
Is there a method for people that don't have custom ROM managers, like Clockwork recovery? All I ever did was root my phone so I could run Titanium backup. I never installed Clockwork or any other custom ROM's... however, the 2.3 update is failing for me.
I am having the same problem. I defrosted all the apps and unrooted the phone but the update is still failing. Help!!!
version 2.3.340
BP_C_01.09.07P
www.google.com
Up until today I never did anything to my droid x as far as rooting and roms. I kept everything completely factory and android was at its latest version which is gingerbread 2.3.3 and system version 4.5.605.MB810.Verizon.en.US.
My goal today was to finally experiment this and install Liberty Rom. I completely failed because of all the version complications and plenty of other errors. Before I describe my final problem I should backtrack and let you know exactly what I did today so you can possibly get me out of this mess.
1. The very first thing I did was follow all of the steps at a forum on droid-life "How To: Get Rooted Gingerbread On DROID X" sorry it won't let me post the link.
After all of this I ended up with gingerbread again, but I guess a rooted version. No idea why this was the tutorial I followed when trying to install liberty. Throughout the tutorial I ended up buying "Droid X BootStrapper" because the tutorial had me use it.
Right after this tutorial I bought an app called Rom Toolbox for $5.00 downloaded Liberty through it and was trying to install through it. Every time it rebooted I would get a black screen. Never worked so many issues probably because I flashed the wrong sbf or something.
Here are the programs that I ended up buying today:
z4root (free), DroidXBootStrapper ($2.00), Rom Toolbox ($5.00).
That is everything I have done and all of the apps I own. Can someone please start fresh and give me short instructions to start from scratch on how to get the latest and greatest version of Liberty on my droidx from where I'm stuck at now. I want to completely start over and I am willing to do anything. I hope the apps I bought help and I also want to assume 2 of them probably do the same thing and I didn't need them.
Buying those tools will at least help support 2 members of the community (Koush & JRummy).
I'm pretty sure Z4Root does not work on the GB versions of DX firmware. That's probably why nothing is working. You aren't actually getting root.
you are on the .605 version of GB (when you see references to .602, .605, etc ...)
To get root, start here:
http://forum.xda-developers.com/showthread.php?t=1258599
You may also want to download the Droid2 recovery rather than the DX. The D2 version is a little newer and I think avoids a slight bug on later kernels when Debug is on. The D2 version works just fine on the DX. It can be downloaded free from here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Once you are rooted and have recover properly working, you should be able to use the Rom Toolbox to download and install Liberty. Just make sure you read carefully about the 'version' requirements on any ROM.
Oh ok so I was rooting it wrong.
I easily rooted the phone using Pete's Motorola Root Tools. I realized that Rom Toolbox Pro accesses clockwork recovery when the phone is rebooted instead of the phone just restarting fully. But, I still want to start fresh and do everything from the start again. Please let me know if you have any suggestions in the way or order I am doing things. My phone is currently up rooted at 4.5.596 and rooted by Pete's Motorola Root Tools but I want to start over from the beginning so here is what I am going to do:
Note: Before I do anything I am going to format my SD card for a fresh start.
1. Use RSD_Lite 4.9 to Flash my phone back to 2.3.340 using a file called VRZ_MB810_2.3.34_1FF_01.sbf. I always do this part with no problem.
2. Do a hold power+home then search and do a system wipe/restore. Then Activate service, sign into gmail etc.
3. Now that the OS is loaded (the old version with the grey bars 2.3.340) I am going to root my phone using Petes Root Tools. (I hope I can root it with this tool when the firmware is this version.)
4. Put the 3 zip files I have on my SD card to upgrade to GB 588. Also put my GB 596 file on here.
5. I will download 1 app. D2BootStrapper. Bootstrap recovery, reboot into recovery. Install all 3 zip files from SD card. Now I boot up in GB 588.
6. Now I go right back into D2BootStrapper. Bootstrap recovery, reboot into recovery. Install GB 596. Now I have GB 596 rooted and loaded.
7. After this, shouldn't I be able to download Rom Manager Premium and Rom Toolbox Pro and test as many roms as I want? always reverting back to my original backup.
I noticed after installing liberty I was getting all kind of force close popups. And the phone wouldn't connect to service. But then I just held power + home then hit the up/down arrows and did a wipe/restore and it loaded liberty and everything works. Is this normally what has to be done when installing roms?
If there is anything wrong with my process please let me know. Whew I can't believe all that I learned in 1 day.
You've got a lot of steps there that really aren't necessary. When you install a ROM like Liberty, it replaces EVERYTHING in /system. Thus, about all that is left from a .596, .588, .602, etc install is the kernel. The Kernel doesn't change very often in Motorola builds. The last change was on .602. Thus, for your purposes there is no difference between .602 and .605 (FYI, .605 was just a keyboard fix over .602).
So, if you search around, you should find an SBF or AIO flash file to get you to .602.
Or you can simply take the OTA update from VZW after SBF'ing to .340
Once you've flashed your Rom, be sure to clear data/factory reset. You should then start with a clean system.
Alright, if you don't mind can you please let me know what steps I can avoid.
I didn't think it was possible to have a rooted .605 but I guess I was wrong.
So my goal should be to get to .605, then root it. Then install roms from there?
On your first post you said you were on .605. I'm assuming that is still the case.
If so, then root it with pete's tool (I think you've already done that).
Install D2bootstrap, then ROM Toolbox and install your rom from there.
I have to be honest, in that I've not used Liberty in a while, nor have I used Rom Toolbox. It shouldn't be a problem, just make sure that the version of Liberty you are using is for the GB kernel. Some of the older versions of Liberty (Which I did use, and like) were for the Froyo kernel (in that case, stay on .340 and do your upgrades).
Make sure you wipe data in recovery after installing the ROM. Lots of 'Boot Loops' are due to not wiping data after flashing a new rom.
Yeah
Yeah I read up on all of that. I actually might not end up going with Liberty. Going to try others like ICX. But before I do any of this I need to get to .605.
No I am not at .605 I believe that's where my phone was before I started all of this.
Right now I am flashing back to 2.3.34
Once I am back up and running there. Can you please recommend the easiest way to get to .605 and that will be my final question.
.605 should update automatic. If not you can disable the updater using titanium backup by freezing system updater.
1. Use petes tools install cwm as well
A. Droid x bootstrap get this
B. Titanium backup. Backup your apps
2. Make a backup using cwm and backup apps with tb
3. Put the rom zip files on the sd card.
4. Reboot to recovery. Reformat system data etc
DO NOT REFORMAT THE SD CARD.
5. Wipe cache davik etc.
6 flash rom. And reboot.
7 run tb for your apps
Should be a smooth and clean install. The roms are already rooted so no need to worry about that. Hope this helps
Sent from my MyTouch 4G Slide using xda premium
We aren't supposed to link to other forums, so expect this link to get removed.
http://rootzwiki.com/showthread.php?399-UPDATED-GUIDE-LINKS-DX-SBF-s
I would point you to a link here, but couldn't find a quick/easy link to what I wanted.
In this list is an SBF file for .602. Since you seem comfortable with doing SBF's, I would just SBF straight to .602 and root it from there.
Don't know much about ICX, but would encourage you to look at the CM7DXGB thread over at Rootzwiki as well.
ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.
HunterT said:
ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.
Click to expand...
Click to collapse
Pete's Root tool should root .605 just fine.
One last thing
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Zaphod-Beeblebrox said:
Pete's Root tool should root .605 just fine.
Click to expand...
Click to collapse
Pete's will work on .605 I did two the other day
Sent from my MyTouch 4G Slide using xda premium
HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
Couple things most of the updates are to add support fix minor bugs etc.
I run the one from petes all the time I forget which version. I haven't had problems.
On my mt4g slide I had to flash a modified verson of clockwork due to my phone being newer and not as much support
With that said its not a difficult process to get a new recovery image. You would need terminal emulator and root explorer. Couple of great guides on here on how to do so. Also other methods as well.
All in all the ones that pete's give you should suffice. Unless your one of the extreame types of people who want the newest or like messing around.
Just remember backups can make the process and hassle of soft bricking your phone much easier to fix and takes a few mins to do.
Look around the forums lots of great information from the devs, experts, etc
Sent from my MyTouch 4G Slide using xda premium
HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
The newer version changes the way backups are stored. The new format is smaller and quicker.
Among other issues/bug fixes as mentioned before, but the backup issue is important as the new version will not restore the old style backups.
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<
I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up
Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.
I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.
If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on
No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.
Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser
If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.
Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up
The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium
MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later