I recently got the rooted gingerbread update to my X well thought it would be sweet to get a rom for it. Tried to install it well went through fine, but when I tried to reboot it got stuck on the M logo and tried wiping data and cache, yet nothing seems to fix it. Any help would be great not used to the X as my main phone is the TB.
(also sorry I did checking of how to fix but didn't quite follow how to use I see I need rsdlite and full VRZ_MB810_2.3.34_1FF_01.sbf is there any other files I will be needing?)
While reading RSD lite is windows ran correct?
So im kind of in the same boat you are. I am unable to flash liberty 1.5 because it gets stuck on the boot screen.
First off can you get into recovery?
If yes did you back up your original rom before trying to flash the new one?
If yes the best way I found to flash a backup is to do: wipe data/factory reset, wipe catch partition, then under mounts and storage format: system, data, catch. Then try installing your backup.
If you have no for any of these tell me and I might know a way around them. Like I said im in the same boat and have dealt with some of the stuff your experiencing.
BrownEye02 said:
So im kind of in the same boat you are. I am unable to flash liberty 1.5 because it gets stuck on the boot screen.
First off can you get into recovery?
If yes did you back up your original rom before trying to flash the new one?
If yes the best way I found to flash a backup is to do: wipe data/factory reset, wipe catch partition, then under mounts and storage format: system, data, catch. Then try installing your backup.
If you have no for any of these tell me and I might know a way around them. Like I said im in the same boat and have dealt with some of the stuff your experiencing.
Click to expand...
Click to collapse
Unfortunately I cant get into the recovery it seems to be broken I can only get into the stock bootloader I believe the blue one where you can update clear cache and wipe data. Wish I could get into recovery would be cake walk then.
Sounds like you both need to sbf. There are stickies at the top of this forum with instructions for Windows and Linux.
If you intend to flash a froyo rom after installing the GB update, you have to SBF back to stock first.
Sent from my DROIDX using XDA Premium App
Related
I posted this on DamageLess' page in hopes that he could help me, but I haven't gotten a reply yet. I figure someone on this forum can help me.. Just read the paragraph and you'll know my problem...
Hey man, I really need your help
I tried using your new DCUpdater (which is a fantastic idea btw) and i'm having a major issue. My phone won't boot. At first I was having problems with SuperUser, but I fixed that by enabling USB debugging, then unplugging the phone, then using the Updater. That worked. But when I tried to reboot the phone, it wouldn't boot. I wiped, restored to my most recent backup, and it still won't boot. I wiped, manually installed your new ROM, and tried to reboot again, and that's where I am right now. It had the Quietly brilliant screen, flashed the sprint logo screen, and now it's back to the Quietly brilliant screen. I think it's in an endless boot, because as I was typing this, the screen flashed grey for a second, then it flashed the sprint logo, and now it's back to quietly brilliant. Please please PLEASE get back to me asap, because I don't know what to do.
dereklane said:
I posted this on DamageLess' page in hopes that he could help me, but I haven't gotten a reply yet. I figure someone on this forum can help me.. Just read the paragraph and you'll know my problem...
Hey man, I really need your help
I tried using your new DCUpdater (which is a fantastic idea btw) and i'm having a major issue. My phone won't boot. At first I was having problems with SuperUser, but I fixed that by enabling USB debugging, then unplugging the phone, then using the Updater. That worked. But when I tried to reboot the phone, it wouldn't boot. I wiped, restored to my most recent backup, and it still won't boot. I wiped, manually installed your new ROM, and tried to reboot again, and that's where I am right now. It had the Quietly brilliant screen, flashed the sprint logo screen, and now it's back to the Quietly brilliant screen. I think it's in an endless boot, because as I was typing this, the screen flashed grey for a second, then it flashed the sprint logo, and now it's back to quietly brilliant. Please please PLEASE get back to me asap, because I don't know what to do.
Click to expand...
Click to collapse
do a wipe/ factory restore and then restart phone. dont flash any other rom or anything. samething happened to me the other night when i flashed the rom. it was an endless boot loop. i tried a wipe and reflash. wipe nandroid, nothing worked until i said screw it ill wipe and go back to factory and then try after phone boots up. to my surprise when phone started back up it was the 2.1 rom that i tried to flash. dont ask me why but it worked
Try wiping the ext partition.
-------------------------------------
Sent via the XDA Tapatalk App
david279 said:
Try wiping the ext partition.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Do I re-flash the ROM after I wipe, or do I try to do a restore????
dereklane said:
Do I re-flash the ROM after I wipe, or do I try to do a restore????
Click to expand...
Click to collapse
id say do not flash a rom. do a factory wipe then restart. read my comment under ur original post
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
cbarlan said:
id say do not flash a rom. do a factory wipe then restart. read my comment under ur original post
Click to expand...
Click to collapse
So you're saying wipe everything and then just reboot the phone?
Jus10o said:
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
Click to expand...
Click to collapse
I just did a factory reset, wiped my Dalvik cache, and wiped my sc card option thingy. I went straight from there to rebooting my phone. I'll say something if it boots now
i'd say wipe settings, wipe ext, wipe dalvik, flash rom, boot. if that doesn't work, wipe again and again then boot.
Jus10o said:
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
Click to expand...
Click to collapse
can i flash a new rom now?
Thread Moved as it isn't development.
if this is the wrong place for this SORRY IN ADVANCE
ok so after rooting my shift i followed all the steps got the recovery on there and downloaded a ROM and wiped everything and when the rom flashed it said error 7 instalation aborted so i hit reboot system now just to see what would happen because i did wipe everything so i was expecting to be stuck at the boot img..no problem was just playing around but the thing actually booted in a rom that looks 100% stock....what happened
even tho the ROM looks 100% stock it is def not i have adfree and esfile explorer added to app drawer now if its gonna flash the rom anyways why does cw 2.5.1 tell me its a no go with a stauts 7 i have even formatted my card to wipe it 100% and the same thing happens>?
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
RyteSyde said:
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
Click to expand...
Click to collapse
yeah it must have just been an issue with the rom i was flashing because i flashed another one no problem thanks for that bit of info though
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
JKILO said:
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
smoothtaste said:
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
Click to expand...
Click to collapse
Ok my fault...never took notice..thanks
Sent from my PG06100 using XDA App
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
HolyShift said:
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
Click to expand...
Click to collapse
Its good practice to always wipe. You may get by without it a few flashes. But eventually you'll be haunted by force closes, boot loops, etc.
Personally when I flash a new rom after the data, cache and dalvik wipes I format my boot, system, data and cache partitions manually via the mounts menu.
From experience, to truly see changes in rom updates or properly enjoy an entirely different one, this eliminates most problems before they ever manifest.
Sent from my Speedy Shift.
I had and htc incredible phone before and I know its because of the locked bootloader for the droid x but it is impossible for me to install roms on this phone. I feel like I am a failure at life lol. I have it rooted with petes root tool, I have bootstrap recovery installed. But when I go into clockwork recovery to install the zip file and that goes OK, the phone reboots and I am stuck in the bootloop. I know I can sbf back to stock and do it all over again because I am smart to always do a backup of the current stock rom I am on.
There has to be something I am missing that I am hoping you guys can help me with. I am dying to put a CyanogenMod or OMFGB rom on here but like I said...I am a failure lol..
Jon2datymuls said:
I had and htc incredible phone before and I know its because of the locked bootloader for the droid x but it is impossible for me to install roms on this phone. I feel like I am a failure at life lol. I have it rooted with petes root tool, I have bootstrap recovery installed. But when I go into clockwork recovery to install the zip file and that goes OK, the phone reboots and I am stuck in the bootloop. I know I can sbf back to stock and do it all over again because I am smart to always do a backup of the current stock rom I am on.
There has to be something I am missing that I am hoping you guys can help me with. I am dying to put a CyanogenMod or OMFGB rom on here but like I said...I am a failure lol..
Click to expand...
Click to collapse
Try booting into recovery and doing a data wipe.
Sent from my DROIDX using XDA App
infazzdar said:
Try booting into recovery and doing a data wipe.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ya I have done those steps also. wiped data/cache/battery stats. Still was a no go.
Wipe data factory reset, wipe data partition and then go to advance and wipe davlik data. Then flash rom the new rom. Hope this helps.
FrostyIcy said:
Wipe data factory reset, wipe data partition and then go to advance and wipe davlik data. Then flash rom the new rom. Hope this helps.
Click to expand...
Click to collapse
Thanks I will try this out. I finally had enough and called Verizon to send me another phone. Now when I use the bootstrap it reboots goes to the moto icon and then I get a black screen to nothing, I have to do a battery pull and restart the phone. So now I really have no way to get to clockwork recovery. Like I said I called them up and on Tuesday they are sending me a Droid X2, so hopefully I will have better luck with that phone and deal with it for a few more weeks then upgrade to the Nexus Prime because that phone looks sweet.
I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?
I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.
Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk
Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam
samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.