I have searched all morning and tried endless things to correct the issue, but still no dice... so here goes.
Downloaded a new ROM this morning, was going to reboot into recovery and flash it, but the System Recovery app is constantly denied Root access. Tried going into the Superuser app and updating the binary, but it also is denied Root.
I found one solution where someone downloaded the latest SU binary file, rebooted into recovery and flashed this to correct the issue. This is all well and good, but I can't reboot into recovery. It's a vicious cycle! What do I do?
-Brian
sbf, then when you root make sure you go into the superuser app and update the binary before the app itself updates. re flash your rom
cm7dx2
Thanks
Thanks, that seemed to do the trick, once i researched what SBF was and how to do it.
Used this for SBF tutorial: http://forum.xda-developers.com/showthread.php?t=1175300
And this for installing a new ROM: http://www.androidauthority.com/droid-x2-miui-4-ice-cream-sandwich-52923/
After doing the SBF, the phone had no idea who I was and wouldn't connect to the network. I had to wipe the factory data / cache, then call the re-activation number, then re-sync my phone to the google account. After that I re-rooted it using the Motorola One Click Root, then installed the Bootstrap Recovery, then flashed the new ROM. Fairly simple all-in-all, just lots of research and time to figure this crap out.
Thanks again.
-Brian
bplacker said:
Thanks, that seemed to do the trick, once i researched what SBF was and how to do it.
Used this for SBF tutorial: http://forum.xda-developers.com/showthread.php?t=1175300
And this for installing a new ROM: http://www.androidauthority.com/droid-x2-miui-4-ice-cream-sandwich-52923/
After doing the SBF, the phone had no idea who I was and wouldn't connect to the network. I had to wipe the factory data / cache, then call the re-activation number, then re-sync my phone to the google account. After that I re-rooted it using the Motorola One Click Root, then installed the Bootstrap Recovery, then flashed the new ROM. Fairly simple all-in-all, just lots of research and time to figure this crap out.
Thanks again.
-Brian
Click to expand...
Click to collapse
It gets easier...when I first did it it seemed to take an hour, now I blink and it's done.
DROID DOES, Apple did...like I forgot when
you definately get used it i dont read at all for any kind of flashing I just do it from habit lol, biggest tip i can give you is to keep all your "rom files" organized in a folder on your x2 and the same for all the sbf files on your computer.
cm7dx2
Reflashing the ROM was easy, it was spending half the day banging my head on the desk wondering what happened to make SuperUser go all jenky!
But thanks again.
We've all been there man, that's why we're still here to help
cm7dx2
Related
I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
Okay, so I see there are many people that have the same questions I had yesterday trying to apply this update with a custom ROM already on my phone. Here is what you'll need and how to get your phone updated. This isn't the only way to do it, but it's what I did and it was pretty easy. It was harder finding out how to do all of this, and in what order than actually doing the process.
It will take a little while to do this, roughly 30-45 minutes.
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update on to your phone using RSD Lite, this will reset your phone completely to stock.
2: Run GingerBreak to root the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
This should get you all updated and with your custom ROM installed.
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Thanks a lot for this....
spitefulcheerio said:
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Click to expand...
Click to collapse
Yes, use Titanium Backup to backup your User Apps and Data, not the system apps or data. And make sure to backup to your SD Card as the flash with wipe your internal memory and your backup will be lost. I had that issue and had to reinstall all of my apps. It's minor, but still a pain in the ass.
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
IrateCustomer said:
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
Click to expand...
Click to collapse
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Swiftks said:
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Click to expand...
Click to collapse
Maybe because I was on 1.5.7, and flashed 1.8.3 instead of going back and OTAing the phone. That would make sense because the OTA process probably does a backup/restore during the process. As mentioned in the OP, it's only one way to do it, but there are other options.
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Datblkbro said:
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Click to expand...
Click to collapse
I've updated the link in the OP so you can download the correct file. My apologies.
Regarding 1.8.3 sbf, which of the sfb files from the link you provided is it? They vary in size. Thanks.
You want the one with the most hits and the ridiculously long filename.
It actually has 1.8.3 buried in the name of the file. It's a few from the top.
THANK YOU this has been a big question mark for me ever since 1.83 came out. Fantastic guide.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
Did the GingerBlur 3.1 get fixed when it comes to the Webtop mod? Cuz I read something about it having a problem with actually working on this Rom? Maybe that was on the 3.0, so I figure 3.1 fixed it?
PLease just a simple "yes it works" or "No, it doesn't" will suffice
Thanks
Just wanted to post my initial experience with using RSDlite to update afterting and gingerblurring it.
I followed your how to as much as I could (You should provide a link to RSDlite instructions, I had to search for it because I didn't know how to do it exactly... not a big deal but it would make it easier/idiot proof)
When I first updated via RSDlite, something must hve went wrong. At first, A triangle and lil android was haunting me on my screen... so I went to reboot.. **** [I thought I bricked it]... Then I restarted it again... DOUBLE ****... Couldn't load into recovery... I restarted a third time and it loaded up(**** YES). But for some odd reason, it said I still had to update (even though it said the firmware was @ 1.8.3.)
Everything seemed to work fine, and was able too root and ginger blur it. About a few hours later, wifi seemed wonky (kept randomly disconnecting and the update dialog came up every 15 minutes).
I ended up reflashing to 1.2.8 and OTA's all the way up to 1.8.3 and then re-rooted and blurred it. No problems since the full refresh
Hopefully everybody elses experience goes better than mine!
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
winky! said:
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
Click to expand...
Click to collapse
You can use Uninstaller for Root (I found it on the Market), and you can uninstall from there if you wish. Personally I see no real reason to remove it, but you can if you need to with the above referenced Uninstaller. There are a few others that can do it, but UfR is free, which is clearly a win.
564mb for the sfb??? Thats freaking huge
GreyBlur on 1.8.3
After following the steps I still show
"System Version 4.1.57MB860.ATT.us"
rooted and sideloading enabled by gladroot then flashed greyblur 2.1....little help for the n00b?
Members
2 posts
Posted Today, 02:13 AM
Hi there....i recently purchased a Razr and had many problems gaining root and flashing ROMS. It took me over 3 days to figure out, and i just want to post my experiences and advise people who may be struggling. I have a XT 910 model GSM as i live in UK. I originally rooted using Doomlord V2 Zergrush and that worked fine while i was on GB 2.3.5. I had an OTA update to 2.3.6 and i lost root. Zergrush didn't work on my model again, so i had to use motofail which worked perfectly.
When installing recovery, i installed safestrap first. I could enter CWR on reboot, but ROMS would not install. I would get a black screen, and then i would have to do a hard reset to get my phone working again. I would still be in stock. The reason for this is because safestrap isnt working on GSM phones. (International models, well some of them!) Safestrap works on CDMA models such as in USA. The reason for this is because the system partition on EU GSM models(XT910) is smaller than the partition on CDMA USA models (XT912). So, we have no choice but to use bootstrap.
If you installed safestrap and experienced these problems, make sure you boot into CWR, advanced, mounts and storage, and format system. Then uninstall. If you install bootstrap without doing this, you wont be able to enter CWR in bootstrap. You will end up stuck at the motorola splash screen and will have to hard reset everytime. You will not get any further.
If you uninstalled safestrap without doing this, reinstall it, and do this, then uninstall recovery from the app and make sure you completely remove it from the device system. Then install bootstrap.
There will be an additional file you will need to save to your SD card named RAZR-CWMonboot-Global-J.Y.Daddy.zip. Select bootstrap recovery and "success" should appear. Then, select reboot recovery, and hopefully, you should enter CWR mode on reboot. Make sure you install RAZR-CWMonboot-Global-J.Y.Daddy.zip file from your SD card. Everytime you flash a file ALWAYS flash this file before rebooting. Everytime you flash a file you are writing over you system, so it is important you do this or you wont be able to enter CWR if you ever get a bootloop or stuck etc....
Once you have flashed the ROM of your choice, and rebooted ,go into your Superuser app and toggle bootstrap into denied. There's a face at the bottom of Superuser app....make sure bootstrap is denied. Thats it!
This is what worked for me...UK model XT910 on O2 network. I'm by no means an expert, but i have worked on a couple phones. Motorola Atrix was my last one, so i have a bit of an idea. If i can help...please message me and i'm more than willing if i can. I dont have links to these files but you can google them. I had so many problems, but hopefully my post will help someone. If so, please "like".
Nice write up to help. One suggestion dont take this wrong but maybe separate into paragraphs. I had a hard time reading line by line.
Thanks. I will write paragraphs next time! I will bear that in mind. Sorry if anyone is struggling to read this line by line.
Droid
I'm new registered here in this forum, but i always read forums here, i own Droid Razr XT910, i rooted it following the instructions here, i install CMW, but i have a problem which is so annoying, everytime i power off my phone it always starts with CMW Recovery, it just will start normally after i reboot my phone i Recovery. Can you help me how to get rid of that..thanks a lot.
Sendoh28 said:
I'm new registered here in this forum, but i always read forums here, i own Droid Razr XT910, i rooted it following the instructions here, i install CMW, but i have a problem which is so annoying, everytime i power off my phone it always starts with CMW Recovery, it just will start normally after i reboot my phone i Recovery. Can you help me how to get rid of that..thanks a lot.
Click to expand...
Click to collapse
It's not annoying thing, but it's a feature thing. It useful when your RAZR got problem & cant boot to home screen. You can flash sbf or wipe from CWM Recovery
mgf8384 said:
Members
2 posts
Posted Today, 02:13 AM
Hi there....i recently purchased a Razr and had many problems gaining root and flashing ROMS. It took me over 3 days to figure out, and i just want to post my experiences and advise people who may be struggling. I have a XT 910 model GSM as i live in UK. I originally rooted using Doomlord V2 Zergrush and that worked fine while i was on GB 2.3.5. I had an OTA update to 2.3.6 and i lost root. Zergrush didn't work on my model again, so i had to use motofail which worked perfectly. When installing recovery, i installed safestrap first. I could enter CWR on reboot, but ROMS would not install. I would get a black screen, and then i would have to do a hard reset to get my phone working again. I would still be in stock. The reason for this is because safestrap isnt working on GSM phones. (International models, well some of them!) Safestrap works on CDMA models such as in USA. The reason for this is because the system partition on EU GSM models(XT910) is smaller than the partition on CDMA USA models (XT912). So, we have no choice but to use bootstrap. If you installed safestrap and experienced these problems, make sure you boot into CWR, advanced, mounts and storage, and format system. Then uninstall. If you install bootstrap without doing this, you wont be able to enter CWR in bootstrap. You will end up stuck at the motorola splash screen and will have to hard reset everytime. You will not get any further. If you uninstalled safestrap without doing this, reinstall it, and do this, then uninstall recovery from the app and make sure you completely remove it from the device system. Then install bootstrap. There will be an additional file you will need to save to your SD card named RAZR-CWMonboot-Global-J.Y.Daddy.zip. Select bootstrap recovery and "success" should appear. Then, select reboot recovery, and hopefully, you should enter CWR mode on reboot. Make sure you install RAZR-CWMonboot-Global-J.Y.Daddy.zip file from your SD card. Everytime you flash a file ALWAYS flash this file before rebooting. Everytime you flash a file you are writing over you system, so it is important you do this or you wont be able to enter CWR if you ever get a bootloop or stuck etc.... Once you have flashed the ROM of your choice, and rebooted ,go into your Superuser app and toggle bootstrap into denied. There's a face at the bottom of Superuser app....make sure bootstrap is denied. Thats it! This is what worked for me...UK model XT910 on O2 network. I'm by no means an expert, but i have worked on a couple phones. Motorola Atrix was my last one, so i have a bit of an idea. If i can help...please message me and i'm more than willing if i can. I dont have links to these files but you can google them. I had so many problems, but hopefully my post will help someone. If so, please "like".
Click to expand...
Click to collapse
thank u so much!
I've been struggling with this all day, many thanks for the advice! Can't believe it was that simple..
CWM and Stock Recovery
Please could some tell me if on my GSM Razr I update it with
Retail.en.EU ICS Leak 672.180.33 thru Stock Recovery, and afterwards I decide to flash J Y Daddy's CWM, would I now have access to both CWM as well as Stock Recovery? Or does it wipe Stock Recovery if CWM gets installed? thx
THANK YOU!
You are a Fuc*ing master man
No one could help me with my problem, but that solved it.
I'd installed safestrap when I bought the RAZR 7 Months ago and I didn't had a clue that the problem was there.
Did exactly what you wrote and now I can use CWM again with BootMenu Manager
THANKS
Great post mate, I like you, lost root and never got it back so stopped trying. There are so many versions of the phone out there, its really confusing which method, files etc to use for UK phone
I rooted my old htc desire and jumped between roms all the time and loved being able to do that, but the razr, I have tried a leak or a custom rom yet
Thanks Again
P.S. as for the comment on paragraphs that's been made, maybe you could edit your post to sort into these, this will then help everyone even more.
Sent from my XT910 using xda app-developers app
MylleZ said:
You are a Fuc*ing master man
No one could help me with my problem, but that solved it.
I'd installed safestrap when I bought the RAZR 7 Months ago and I didn't had a clue that the problem was there.
Did exactly what you wrote and now I can use CWM again with BootMenu Manager
THANKS
Click to expand...
Click to collapse
Glad it worked!!!
geemacd said:
Great post mate, I like you, lost root and never got it back so stopped trying. There are so many versions of the phone out there, its really confusing which method, files etc to use for UK phone
I rooted my old htc desire and jumped between roms all the time and loved being able to do that, but the razr, I have tried a leak or a custom rom yet
Thanks Again
P.S. as for the comment on paragraphs that's been made, maybe you could edit your post to sort into these, this will then help everyone even more.
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
i'll edit it in a few. Thanks for the feedback and glad it worked!
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Croda said:
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Click to expand...
Click to collapse
ok, noob found thread about activation and fixed that part.
now I'm hoping I can just go back to 2.3.5 and apply my backup.
Lol, first take a deep breath. Your phone is not hosed, it's actually working like it's supposed too.
After you sbf, you phone is back to it's factory state right? So remember when you got your phone for the first time you had to have it activated/programmed. If you're on Verizon then dial *228 and follow the directions, takes about 5 minutes. This will give you back service and your phone number.
Second, the droid x2 is unique and requires a few different steps than most phones to flash things because it has whats called a locked, encrypted bootloader. So with the X2 you will NEVER want to use Rom Manager (Clockwork Mod Recovery) or Rom Toolbox. They just do not work with our phone yet.
Your going to want to read this link: http://www.droidxforums.com/forum/droid-x2-support/41785-common-x2-questions-answers.html
It gives a good overview of how the X2 works and explains a lot of things.
Then go here: http://forum.xda-developers.com/showthread.php?t=1318083
This explains how to install and get into the X2's special Bootstrap Recovery. This is where you will make backups, restore backups, and flash new roms. The thread explains in great detail how to make and restore backups in Bootstrap Recovery.
oh man, thanks a bunch lead off.
that whole deal with the boot strap is something that I never saw in all the reading I did and probably solves a lot of my problems. I'll do what you said (starting with the deep breath) and begin again.
thanks again for the help.
Yea no problem
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....