Please help I don't know what to do. I did a stupid thing. I have a rooted droid X and I used root explorer to follow the instructions on the below website to try and get arabic font support, but now after reboot it is stuck at the M boot screen. Is there anything I can do to go into recovery mode and then what commands can I run to rename the files back without having to do a factory reset. I did make a copy of them before overwriting them. Please help.
How To Add Arabic Font Browser Support to the Nexus One | Android Devs
Thanks.
Please anyone??
I pulled the battery, but that didn't help. Before I do a factory reset, what does "apply sdcard:update.zip" in the recovery mode do?
Maybe try deleting the cache in recovery. Not sure if that'll do anything but there's a chance I suppose.
Sent from my PC36100 using XDA App
david black said:
Maybe try deleting the cache in recovery. Not sure if that'll do anything but there's a chance I suppose.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks for the reply, but what does deleting the cache do?
It won't hurt anything.
forum.androidcentral.com/htc-evo-4g/35832-what-does-wipe-cache-do.html
Sent from my PC36100 using XDA App.
Fresh Evo 3.3.0.1
hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt
You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App
You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk
google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition
Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App
mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk
well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.
if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App
Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App
If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App
thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.
i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?
It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App
oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol
Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!
yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.
I downloaded maderstcok 340 and updated. I then did a factory reset and re-rooted using z4. I then tried to download the gummyjar rom using rom manager. My droid x is now stuck,on boot up,the pic of flashing 4 android figures and saying gummyjar
I suppose I need to flash back but dont k now how and need to flash from the .340
Can anyone give me detailed instructions on how to fix my X and how to flash
Try booting into moto recovery (hold down the menu button along with the power button, when the picture of the green android guy comes up, push the search button)
Do another wipe data/factory reset and reboot. If that doesnt work then you will need to sbf
Sent from my DROIDX using XDA App
SysAdmin-X said:
Try booting into moto recovery (hold down the menu button along with the power button, when the picture of the green android guy comes up, push the search button)
Do another wipe data/factory reset and reboot. If that doesnt work then you will need to sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Exact.
Wipe your data and you should be good to go. Same thing happened to me with GJ 2.0.
if none of this works and you really messed up your phone msg me on AIM: XxMMZxX . I have files to unbrick your phone on .340 guarunteed to work!!!!!
smyers1012 said:
if none of this works and you really messed up your phone msg me on AIM: XxMMZxX . I have files to unbrick your phone on .340 guarunteed to work!!!!!
Click to expand...
Click to collapse
Unless this guy ^^^^ works for Verizon or Moto and is holding out on the rest of the Android community... anyone can get access to the files to unbrick your phone. Check out mydroidworld for the 2.3.32 full sbf and the 2.3.34 system only sbf. If you need more help with sbf files, post back, and myself, or one of many other people are likely to help you out.
PS... to smeyers1012...unless you have "Secret files" please just offer the help in the forum... it makes it easier for everyone =) Thank you
wb1960 said:
I downloaded maderstcok 340 and updated. I then did a factory reset and re-rooted using z4. I then tried to download the gummyjar rom using rom manager. My droid x is now stuck,on boot up,the pic of flashing 4 android figures and saying gummyjar
I suppose I need to flash back but dont k now how and need to flash from the .340
Can anyone give me detailed instructions on how to fix my X and how to flash
Click to expand...
Click to collapse
If I'm reading this correctly ??
After reloading the Market programs, if you want to stick with the full "Maderstcok SBF".
You must do a full reboot BEFORE Rooting, Rom's, breathing, Or anything else.
IMHO kick the Rom manager to the side of the road , Again IMHO.
Then do what you wish.
When I use Maderstcok's SBF I bypass the market downloads so that I can then
get to the new Rom i,m really trying to get to.
Maderstcok SBf, full reboot, Root, Rom
Wouldn't it be the home key and power, not the menu one?
billymac122 said:
Wouldn't it be the home key and power, not the menu one?
Click to expand...
Click to collapse
Yes. I may have mispoke. It is the home button
Sent from my DROIDX using XDA App
Hope you guys can help with this.
I updated to the rooted Gingerbread leak. Didn't really like it so I made the retarded mistake of just flashing Liberty to my phone. Completely forgot that if I wanted to go back I had to SBF.
So I went to SBF back to Froyo. The SBF went through with no issue but now my phone won't boot. When booting normally or going to recovery I get this. I've tried two computers and can't get either to recognize my phone, but my phone does recognize that it's plugged in.
Now I understand that if you have bootloader 30.04 and try to go back to Froyo you'll basically get a brick. Is this true or is there some way to fix this that's been documented that I'm oblivious of? Thanks very much if you guys can help me.
I have bootloader 30.04 and I have SBF'D back to froyo twice with no issues, are you sure you have the complete SBF file and not the system only file?
Sent from my DROIDX using XDA Premium App
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
UPDATE: I had the system-only SBF. Found the SBF full and it worked.
Now try to figure how to install the zip files because my phone is not letting me
Venc said:
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
Click to expand...
Click to collapse
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
bigshotrob22 said:
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hey,
Is it even out? I don't see it online
EDIT: I think I found the full SBF. I'll try it. Thanks
UPDATE: bigshotrob22 you are awesome!! Thank you it worked!!! Now I have to cancel my order for the replacement LOL
That happened to me. I SBF'd back to .340 and still had the Red M logo from the Gingerbread .595.
I was unable to get into recovery at all. I eneded up not having the phone for the day and did the SBF again when I got home, you can still access the bootloader, just not recovery (or atleast I was able to) to do the SBF back to .340.
You said you have done the SBF before..my issue with was I did not go into the factory recovery FIRST and wipe all data. I have since done three SBF's and wipe data (in stock recovery, not BOOT STRAP) first. I wiped data, DID NOT REBOOT device. Powered off, and went straight into the bootloader to SBF.
That seems to work for me now.
If it is the samething that happened to me...the wipe did not completely do its job. I make it a habit to wipe 3-4 times before doing anything.
try pushing the volume button up& down at the same time instead of search
Sent from my DROIDX using XDA App