Related
Hi,
I accidentally updated to Gingerbread on my Thunderbolt, and I forgot I rooted my phone, by the time I remembered it already had a blue android and an explaimation mark. So I did some random crap, and probley made it worse.
First I did the vol down power thing went to factory reset it loaded CWM v4.0.1.4
I wiped cache patition
Dalvick cache
and Battery stats
then I wiped data/factory reset
It loaded like it was brand new everything seemed fine till I updated and did same thing so I wiped the data again and now it keeps auto updating so I have to keep my internet off
and it's annoying as crap
I'm a noob so I don't understand stuff
should I go ahead with this guide:
http://forum.xda-developers.com/showthread.php?t=1009423
I couldn't understand it and if your not rooted why would you unroot I don't get that part...
Do I still have root?
What does flash exactly mean?
Current Specs (I don't know what to give but I'll guess)
Thunderbolt
Top says
Mecha XD S-OFF
HBOOT 6.04.1002
eMMC-boot
Android Version 2.2.1
(tell me if you need any other info)
Should I upgrade to gingerbread any way
Download a customer rom, put it on your sd card and flash it in CWM. I'm running BAMF forever and like it. There are plenty of roms to choose from. This should stop the update. After running the rom if you decide you like stock better you can flash the stock rom back and take the update. You will loose root.
Pull the update off the SD. It will stop flashing it
Sent from my ADR6400L using xda premium
Kidney Poker said:
Pull the update off the SD. It will stop flashing it
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I had a friend who's phone auto updated and is stuck on the htc boot screen. Will deleting the update off the sd card work also? Her phone is not rooted, just hoping to save her from having to replace it.
And how do you forget you rooted your phone?
If pulling the update off the sd what do i need to look for
i have a similar problem
my wifes phone is rooted though. it had a stock rom and she autoupdated
now i can only go to recovery mode.
is there a way to fix this and save the stuff on her phone
waltersobchak96 said:
i have a similar problem
my wifes phone is rooted though. it had a stock rom and she autoupdated
now i can only go to recovery mode.
is there a way to fix this and save the stuff on her phone
Click to expand...
Click to collapse
1) The phone will not boot all the way up?
2) is the recovery stock or CWM?
3) do you have a recent back up made?
4) do you have s-off?
jett2314 said:
1) The phone will not boot all the way up?
2) is the recovery stock or CWM?
3) do you have a recent back up made?
4) do you have s-off?
Click to expand...
Click to collapse
1. it boots up all the way, turns off after 10-20s each time, regardless of what action i'm taking
2. cwm recovery
3. no backups recent or not
4. i don't know if i 'have it' but when i load hboot the status is 's-off'
Does it crash or shut off? Maybe a hardware problem?
It powers down the normal way.
waltersobchak96 said:
It powers down the normal way.
Click to expand...
Click to collapse
If you clear the cache, the shutdowns will stop.
But the OTA will download again, and in a few days you will have to repeat the process.
A custom ROM fixed me, but now the same thing poped up.
May go back to stock .... trying xdabolt, but in the process lost my data.
Kidney Poker said:
Pull the update off the SD. It will stop flashing it
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
What am I looking for on the SD card to remove?
sounds like you still have s-off. Anything you are trying to save like app data is gone if you do not have a back up. I would down load a customer rom or even one of the rooted stock versions with the latest OTA and flash that with CWM recovery. Be sure to clear cache and dalvick wipe first when you flash it. There are RUU you could use to return it to stock, but you will lose root. I'm running BAMF forever 1.0.9 and like it. Play around with some roms and if you don't like them use a RUU to restore you back to stock. Most important is make sure you read up on things first.
Hey I endded up just unrooting using this video
(can't show video url)
(Search how to unroot on youtube you should see it by nat3mil and I think that's only if you have revolutionary)
and I guess the video would work too.
If you restored to factory settings using power and vol down buttons and wiped the data in the revolutionary thing, and then followed the video...
phones working now and the video's idiot-proof
just posting this if anyone else needded to unroot
syed2007 said:
and the video's idiot-proof
Click to expand...
Click to collapse
You would think but I have seen people who after being on here a year still don't know the difference between flashing something in ROM manager or recovery.
Sent from my ADR6400L using XDA App
unrooting is good and all, but if that happens again, just look around for the newest ruu and find a rooted version. most ruu get rooted that day... heck i had 2.11.605.5 rooted b4 verizon released it (the 2nd leak, the one WITH working vm notifications) thanks to eris of course. then you'd be up to date, stock, rooted... all you'd have to do is wipe dalvik, cache, and system... keep the data (if coming from sense 2.1 rom) and you'd be good.
i don't mess with sense 2.1/3.0 hybrid or 3.0 roms anymore, for this very reason. a ton of incompatibilities between the roms and framework, causing you to have to wipe data when switching... what a pita! i haven't wiped data in months. keep the data always to make life easier...
if you have problems, use clockwork's "fix permissions" and reboot. problem not solved? then retry rom installation WIPING EVERYTHING, then at least you tried to keep your stuff. titanium backup is great for backing up apps + data, so you can import the data back when you're stable on the new rom... just restore the apps + data for the necessary apps, and app only for the stuff that doesn't mnatter... never restore system apps + data for roms with severely different basebands or from completely different roms. unrooting won't be necessary next time
I had my phone half rooted, OTA came and I selected to defer, well I forgot and now I have the security warning.I tried flashing through the bootloader on my SD card the stock file and I still have the security warning. I use my phone as my internet source so it's been a big PITA. The phone starts, goes to 1x, then 4G, then restarts over and over.
Won't load into recovery, won't factory reset, using HBOOT USB and the command prompt the device isn't recognized.
Right now its as follows:
S-ON
1.04.0000
1.16.0223r
Feb 23 2011, 20: 42:55
Back to using my OG Moto DROID and I am going insane!! Any help would be GREATLY appreciated!!!
Wiped dalvik and flashed a new rom. Works fine now. Had to use a new radio but still.
tapatalk on thunderbread
flip218 said:
I had a friend who's phone auto updated and is stuck on the htc boot screen. Will deleting the update off the sd card work also? Her phone is not rooted, just hoping to save her from having to replace it.
And how do you forget you rooted your phone?
Click to expand...
Click to collapse
If the phones rooted you can prolly get into recovery VIA hboot.
If its not rooted you can prolly find a ota ruu and flash it in hboot. U can do that if its rooted too but ull lose root. Or if its a locked s off there's methods to roll back to factory and turn s on. And yes delete the orig update off the card
RobsCavZ24 said:
I had my phone half rooted, OTA came and I selected to defer, well I forgot and now I have the security warning.I tried flashing through the bootloader on my SD card the stock file and I still have the security warning. I use my phone as my internet source so it's been a big PITA. The phone starts, goes to 1x, then 4G, then restarts over and over.
Won't load into recovery, won't factory reset, using HBOOT USB and the command prompt the device isn't recognized.
Right now its as follows:
S-ON
1.04.0000
1.16.0223r
Feb 23 2011, 20: 42:55
Back to using my OG Moto DROID and I am going insane!! Any help would be GREATLY appreciated!!!
Click to expand...
Click to collapse
Anyone, or flash to Gingerbread? I really need my 4G my OG DROID battery is f**ked, I NEED THIS PHONE WORKING!
I'm sorry if the answers to my question have been answered but I can't find them after searching for a few days.
I need to send my Atrix in for a repair or replacement. It is unlocked and rooted running Turl's CM9 right now. Obviously I can't send it back as is, so how should I go about everything?
Flash an SBF, flash a fruitcake rom, or something else that I haven't stumbled upon?
The only threads I could find are from a year ago and so much has changed since then. I just want to be sure I go about this the correct way. And should I go through ATT or Motorola? I know my phone is still under warranty with both.
Thanks for any help! It is much appreciated!
"Always have an exit strategy"
You can flash a fruitcake but the "unlocked" text will remain so you can hope for the best.
Or you can try an SBF (Disclaimer: at your own risk).
How long have you had it? Usually if you have had it for more than 30 days AT&T won't help but if you are still under "warranty" with them I would try AT&T first.
If you can't find a way to return your phone back to stock you can try Motorola, they might just overlook the modifications you have done.... or they might charge you a service fee...... or they might just send the phone back to you. It really depends on who ever is processing your claim and the mood they're in.
Also, please don't start multiple threads on the same topic.
http://forum.xda-developers.com/showthread.php?t=1549599
scarbutt11 said:
I'm sorry if the answers to my question have been answered but I can't find them after searching for a few days.
I need to send my Atrix in for a repair or replacement. It is unlocked and rooted running Turl's CM9 right now. Obviously I can't send it back as is, so how should I go about everything?
Flash an SBF, flash a fruitcake rom, or something else that I haven't stumbled upon?
The only threads I could find are from a year ago and so much has changed since then. I just want to be sure I go about this the correct way. And should I go through ATT or Motorola? I know my phone is still under warranty with both.
Thanks for any help! It is much appreciated!
Click to expand...
Click to collapse
OK thanks. I had read that if I use the Motorola Software Update tool it will erase the "unlocked" text. I don't know how true that is though.
And sorry about the multiple threads, its just annoying not being able to use half my keyboard in portrait. Just was hoping for some quick answers.
Thanks again for the quick response
Sent from my MB860 using XDA
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
LeroyVold said:
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
Click to expand...
Click to collapse
Ok, you don't happen to have a stock sbf file? I can't find one anywhere.
Also, why is it that we shouldn't flash sbf files? It seems that people have success with them but everyone keeps saying not to do that. But I can't find a stock flashable zip and the fruitcake links are dead so sbf seems to be my last resort.
I'm just stuck scratching my head because of all this confusion?
scarbutt11 said:
Ok, you don't happen to have a stock sbf file? I can't find one anywhere.
Also, why is it that we shouldn't flash sbf files? It seems that people have success with them but everyone keeps saying not to do that. But I can't find a stock flashable zip and the fruitcake links are dead so sbf seems to be my last resort.
I'm just stuck scratching my head because of all this confusion?
Click to expand...
Click to collapse
Look in the firmware superthread, in the last pages someone have a link in his sign to a page of many stock sbf files. I found there my updated one.
I always got succes with rsd lite but only with a full wipe with fastboot before it say "pass" at the end. Otherwaise it say to 'manually reboot'.
Don't know why people say "do not use sbf", probably there is a reason, but i think it is the only way to remove the 'Unlocked'
Here links to froyo sbf
and to GingerBread sbf
also you need to delete any folder about apps that need root to work and su folder and anything that presume you have rooted your phone
Sent from my MB860 using xda premium
Depending on what build you are currently on you do not want to "downgrade". So if you are on a Gingerbread build (4.5.91 or 4.5.141) do not flash the Froyo SBF. And probably if you are on the 4.5.141 build (2.3.6), it is not recommended to flash the ".91" build. That is where the issues can occur.
I have also used RSD Lite to flash back to stock (a few times) but always use caution. So, for @scarbutt11, do you happen to remember what build you were on before you unlocked the bootloader and flashed a custom ROM?
LeroyVold said:
Look in the firmware superthread, in the last pages someone have a link in his sign to a page of many stock sbf files. I found there my updated one.
I always got succes with rsd lite but only with a full wipe with fastboot before it say "pass" at the end. Otherwaise it say to 'manually reboot'.
Don't know why people say "do not use sbf", probably there is a reason, but i think it is the only way to remove the 'Unlocked'
Here links to froyo sbf
and to GingerBread sbf
also you need to delete any folder about apps that need root to work and su folder and anything that presume you have rooted your phone
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, I was running stock 4.5.91/2.3.4. I'm on a cm9 build now. I'm not sure if that will matter at all for flashing back to GB? I know I tried cm7 to see if it was just cm9 causing the problems, but it seems it is hardware related.
Sent from my MB860 using XDA
Yeah, it depends on what "Official" build you were last on. Since you were on "4.5.91" then I would just use that SBF. Like someone else mentioned, it is possible to use RSD Lite, just use caution.
scarbutt11 said:
Yeah, I was running stock 4.5.91/2.3.4. I'm on a cm9 build now. I'm not sure if that will matter at all for flashing back to GB? I know I tried cm7 to see if it was just cm9 causing the problems, but it seems it is hardware related.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Thanks so much for the help. I'll go ahead and give it a shot. I'll let y'all know the outcome.
Sent from my MB860 using XDA
Took a little pulling of my hair while I waited but fastboot wipe and then flashing the stock sbf worked like a charm. I am back on stock GB, the unlocked text is gone and now I can hopefully get my phone fixed or replaced.
Thank you so much @live4nyy and @LeroyVold!!! Without you guys I would have been still scratching my head. I owe you both big time
No problem man, i need to do the same.
my touchscreen is more and more often unresponsive, so i'm flashing my stock sbf as i write.
Finally got a chance to swing by the AT&T store. They replaced the phone no problem thanks again guys!
Sent from my MB860 using XDA
i need to do the same. im sending this phone in and already got my new atrix sitting here.
Freaking Motorola phones, they break without you even touching them. I gotta figure out how to send mine to att as well.
u need to do a write up in here of how u did it. it might be redudant to some but to others like myself, it will be like having my hand held doing a scary process...your guidance as having it done yourself would help...with a how to..
scarbutt11 said:
Finally got a chance to swing by the AT&T store. They replaced the phone no problem thanks again guys!
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Free or did you have to pay?
LeroyVold said:
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
Click to expand...
Click to collapse
this isnt working for me. and i need to send my phone in within a day.
Atrix_Owner said:
Free or did you have to pay?
Click to expand...
Click to collapse
For free, I bought the phone through them less than a year ago. All I said was that the screen was unresponsive and they looked at it for less than 10 minutes and then said they would replace it for me.
jahizen said:
u need to do a write up in here of how u did it. it might be redudant to some but to others like myself, it will be like having my hand held doing a scary process...your guidance as having it done yourself would help...with a how to..
Click to expand...
Click to collapse
Thats not a bad idea. I have never done one before but now that I'm thinking about it I am sure there are others that need to do what I just did. I will try to write one up in the next few days. Thanks for the idea!
live4nyy said:
Depending on what build you are currently on you do not want to "downgrade". So if you are on a Gingerbread build (4.5.91 or 4.5.141) do not flash the Froyo SBF. And probably if you are on the 4.5.141 build (2.3.6), it is not recommended to flash the ".91" build. That is where the issues can occur.
I have also used RSD Lite to flash back to stock (a few times) but always use caution. So, for @scarbutt11, do you happen to remember what build you were on before you unlocked the bootloader and flashed a custom ROM?
Click to expand...
Click to collapse
hello i guess you could help me with a doubt i have..i used to be on stock 4.5.141 Gb 2.3.6 atrix 4g..im new on this things..and i installed succesfully cm7.2 but its not stable as i expected..i wanna go back to stock rom but im not sure what to do...i tried to go back using CWM restore...¨yes i made my backup before everything¨ but the restore didnt work...its stuck on moto booting logo..then i had to install again cm7 but the ba2tf wich its a bit more stable but not enough comparing to stock i had.. then my question its...
should i flash my phone with sbf 4.5.141?? or what do you recommend me..i dont wanna make a downgrade just be at 4.5.141 again
thanks
My X2 starting losing signal. Today I did a hard reboot and when the phone comes back on it makes it to the black screen with the Motorola logo and says Modem did not power up (2) starting RSD protocol support. Verizon is sending me a warranty replacement. I have already done a factory reset. Phone was rooted would the factory reset erase the root so that it's safe to send back.
Phone was rooted with Pete's root tool.
redfish10 said:
My X2 starting losing signal. Today I did a hard reboot and when the phone comes back on it makes it to the black screen with the Motorola logo and says Modem did not power up (2) starting RSD protocol support. Verizon is sending me a warranty replacement. I have already done a factory reset. Phone was rooted would the factory reset erase the root so that it's safe to send back.
Phone was rooted with Pete's root tool.
Click to expand...
Click to collapse
try dialing *228 option 2 This will reconfigure your signal from cell towers
http://support.verizonwireless.com/faqs/Wireless%20Service/faq_prl_preferred_roaming_list_update.html
I tried that. The phone will not make it past the black screen with the Motorola logo. And I get the modem message across the top.
Sounds like the radio is burned out. No fix for that unless you want to break out the soldering iron
That's what I figured. I have another phone on the way. I was able to do a factory reset. Would this remove the root. Phone was rooted with Pete's one click root tool.
Sending phone back so I have to make sure root is removed.
redfish10 said:
Sending phone back so I have to make sure root is removed.
Click to expand...
Click to collapse
I think there's an app for that
I know but my phone is useless right now. I can't see anything but the black boot screen.
Sbf and send it in. Problem solved
Sent from my GT-P3113 using xda premium
SBF = wipe everything. This is like doing a total factory reset; it clears and re-writes almost every partition. Root access would be wiped out from it.
****@Reddish****
Try resetting ur super user
Go to app manager and clear data I found that to be my problem in the past and then turn off ur x2, not reset your phone. Than repower.
Hope it works.
What are you running?
Sent from MB870 W/ Cm7.2 Rc1 MASHUP V2
SUCESS I THINK YES...
Dudes stuck @ red m. No way to reset superuser. Have to SBF.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Omega360 said:
SBF = wipe everything. This is like doing a total factory reset; it clears and re-writes almost every partition. Root access would be wiped out from it.
Click to expand...
Click to collapse
Not ENTIRELY true.
While flashing a sbf file using RSDlite, you are setting all the system and proprietary things back to completely stock. It will remove root access, and all that junk, along with all, the things that came from mods/tweaks/hacks/roms
BUT flashing sbf BY ITSELF alone will NOT wipe away ANY user data. You MUST data wipe from stock recovery to do that. This is why sometimes you boot loop,after sbf flash , and you need to data wipe to cure those boot loop blues, cuz sometimes there are things left over that you tweaked that didn't get wiped out after flashing the sbf, but they get removed from a data wipe from stock Android recovery.
To sum up:
For a TRUE OUT OF BOX FACTORY CONDITION(i.e. You just bought and opened the box) MUST flash sbf file using RSDlite with a computer. AND THEN after that, you wipe data/cache from stock Android recovery.
I'm willing to bet that would have also fixed you issues with not being able to boot past Motorola screen as well. Cant hurt to get a new one, but if you can compare them to see which is in better working order, then it couldn't hurt to do.
Either way, if youre going to send it in, and want to erase traces of root and such, then you need to do more than just data wipe. You NEED to sbf AND data wipe.
From my nexus tappin the talk
<edit post successful>
That's why I said ALMOST every partition
Just do recovery...
Pull your battery/replace
And plug it in... to the wall that is
Screw an sbf
Sent from MB870 W/ Cm7.2 Rc1 MASHUP V2
SUCESS I THINK YES...
Modem Did Not Power Up (2)
ashclepdia said:
I'm willing to bet that would have also fixed you issues with not being able to boot past Motorola screen as well. Cant hurt to get a new one, but if you can compare them to see which is in better working order, then it couldn't hurt to do.
Either way, if youre going to send it in, and want to erase traces of root and such, then you need to do more than just data wipe. You NEED to sbf AND data wipe.
<edit post successful>
Click to expand...
Click to collapse
This is absolutely true. The error "Modem did not power up (2)" is something that I have been dealing with as well. I'd love to work with someone to figure out the problem, but it is probably not hardware. I encountered this error for the first time 2 weeks after installing Eclipse 2.2.1. I solved it by SBF to Stock. Once I had re-installed a stock ROM the error went away and the phone operated normally. I just had this error pop up again almost exactly 2 weeks after installing CM7 RC1. When I get home I'm going to SBF to stock and hopefully that will correct the issue (again). I tried clearing my cache and then clearing my data through stock recovery, but that won't correct the error - and unfortunately the error happens before BSR boots so I can't Nandroid back to a healthy setup and see where the problem is. Both times I lost signal on the phone, re-booted, and then got stuck at the Red M with the Modem error. :crying:
I'm going to try to load CM7 again, but it's pretty awful to have this happen at work and suddenly be without a functional phone. (Maybe I have to install RSD Lite on my work computer ...)
Any thoughts on this would be appreciated but I can tell you that ashclepdia is right, it is probably not a hardware problem. It seems to be a problem with rooting/flashing on certain handset builds.
okay i have an mx2 2.3.6 rooted and rerecovery installed flashed miui 4 everything was fine until i played around with motomizer and adjusted the lcd density now the miuihome has stopped and will not let me get to my apps i can use sms somewhat and get to the browser using the statistics opt in message i have tried to recover but it doesnt boot into it even though i flashed rerecovery i have done a fatctory data reset in android recovery nothing helps i even tried to sbf back to 2.3.5 and the flash fails any ideas how to fix it. this is my 2nd one already warranted it out once.
okay i have tried everything i know with no luck. i can use the phone to receive calls and texts just cannot send either. can use the voice search to get to the browser. still cannot load the screens just get miuihome has stopped message. i somehow lost the recovery and cannot get back into it to do anything. i used the android recovery to wipe data and cache with no luck. ive tried to use adb and fastboot to flash things with no luck. im really at my wits end. no sbf files will work
flash fails either it wont enumerate or product id fails im using rsd lite. i love this phone and miui but this sucks and i know its my fault for tweaking stuff but there doesnt seem to be an answer. any help is greatly appreciated.
if there is no solution oh well.....:crying:
ionicone said:
okay i have an mx2 2.3.6 rooted and rerecovery installed flashed miui 4 everything was fine until i played around with motomizer and adjusted the lcd density now the miuihome has stopped and will not let me get to my apps i can use sms somewhat and get to the browser using the statistics opt in message i have tried to recover but it doesnt boot into it even though i flashed rerecovery i have done a fatctory data reset in android recovery nothing helps i even tried to sbf back to 2.3.5 and the flash fails any ideas how to fix it. this is my 2nd one already warranted it out once
Click to expand...
Click to collapse
If you can boot into RSD try sbf for 2.3.4 or even back to 2.3.3. I had issues before with 2.3.4 not performing a clean sbf. It would say it was completed but it would not wipe the phone. But when I would sbf 2.3.3 it would work fine. Worth a shot.
bump
bump for help
ionicone said:
bump for help
Click to expand...
Click to collapse
Can you only see part of the screen? If you hit your home button, what do you see?
Sent from my MB870 using xda premium
Travisdroidx2 said:
If you can boot into RSD try sbf for 2.3.4 or even back to 2.3.3. I had issues before with 2.3.4 not performing a clean sbf. It would say it was completed but it would not wipe the phone. But when I would sbf 2.3.3 it would work fine. Worth a shot.
Click to expand...
Click to collapse
Mx2 brother
DROID DOES, Apple did...like I forgot when
try this power down your phone then hold the power and volume down buttons until fast boot shows up on the top of the screen then push the volume down button down 7 times to android recovery then reflash miui 4 then factory restore and all that
Shpoople said:
try this power down your phone then hold the power and volume down buttons until fast boot shows up on the top of the screen then push the volume down button down 7 times to android recovery then reflash miui 4 then factory restore and all that
Click to expand...
Click to collapse
This should work. Reflash the from and it should cancel out you dpi settings.
Sent from my MB870 using xda premium
CadenH said:
This should work. Reflash the from and it should cancel out you dpi settings.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I thought you could only install signed packages in the stock recovery. Is this different with the MX2?
nothing works
cant flash anything from stock recovery other than signed packages. is there anyway to flash a recovery from adb or fastboot. i can get to both of them along with rsd but cannot sbf as i have found out i have an mx2 stock with 2.3.6 and cannot sbf down to anything else. im reeally stuck here.
ionicone said:
cant flash anything from stock recovery other than signed packages. is there anyway to flash a recovery from adb or fastboot. i can get to both of them along with rsd but cannot sbf as i have found out i have an mx2 stock with 2.3.6 and cannot sbf down to anything else. im reeally stuck here.
Click to expand...
Click to collapse
You cant flash anything using the stock recovery. You need a custom recovery. I dont know what the milestone x2 uses, but if its the same as the Droid X2, its the bootstrap recovery.
i cant get to my apps to run the recovery app. i really dont know what to do at this point, but i can use the phone to receive calls and text just cant make any because i error saying phone or messaging has stopped. can i flash the bootstrap in fastboot or adb i have tried but not real proficient with either.
okay done some reading im using rsd lite 5.4.4 and have been trying to flash the zips, just read the i must extract it first. is this so....
ionicone said:
i cant get to my apps to run the recovery app. i really dont know what to do at this point, but i can use the phone to receive calls and text just cant make any because i error saying phone or messaging has stopped. can i flash the bootstrap in fastboot or adb i have tried but not real proficient with either.
Click to expand...
Click to collapse
Someone else chime in if its different for the Milestone X2.
ionicone, bootstrap is not a flashable zip. it is an .apk file (app). Put it on your sd card and install it like a normal app. Then open it and follow the directions. I don't know how different the Milestone X2 is from the Droid X2 but thats how what we use and thats how we do it.
I may be misunderstanding but if nothing else works, SBF and start over.
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
And SBF should work as long as you can get into the normal recovery mode. I dont know why else SBF files wouldnt work for you.
i may not be very clear on my problem, but i cant install anything on the phone because of the error message it wont go away just says miuihome has stopped. everything i try to sbf through rsd lite fails but im in the process of extracting and trying that one has already failed trying another now.
ionicone said:
i may not be very clear on my problem, but i cant install anything on the phone because of the error message it wont go away just says miuihome has stopped. everything i try to sbf through rsd lite fails but im in the process of extracting and trying that one has already failed trying another now.
Click to expand...
Click to collapse
What exactly did you change to make this happen in the first place?
If it was just the LCD density, try pushing the original build.prop file into the system folder. Since, I believe thats where the DPI is controlled. Or if you can get into with root explorer or something, change it back manually.
it was the lcd density property. can i rip this from the backup i have stored on my pc and push it through adb.
as far as sbfing this is what my phone says
SVF:106:2:3
sec_exception: b655, eddc, eb
thanks for replying btw
ionicone said:
it was the lcd density property. can i rip this from the backup i have stored on my pc and push it through adb.
as far as sbfing this is what my phone says
SVF:106:2:3
sec_exception: b655, eddc, eb
thanks for replying btw
Click to expand...
Click to collapse
You should be able to. Just make sure the permissions are rw-r--r--
You can get it from your backup or pull it from the ROM you flashed
Why don't you just factory restore and cache then reboot from the menu and it should be fixed
Sent from my MB870 using xda premium
tried that it does nothing, and now after trying to flash stuff through fastboot i may have bricked it. going to cspire today to see if i can warranty this one out.
update
cspire will let me warranty this one out, i will not root again until things are more stable as in an unlocked bootloader. thanks to everyone that tried to help.
They won't unlock the bootloader for a long time so don't get your hopes up and wasn't this your own fault?
Sent from my MB870 using xda premium
ionicone said:
cant flash anything from stock recovery other than signed packages. is there anyway to flash a recovery from adb or fastboot. i can get to both of them along with rsd but cannot sbf as i have found out i have an mx2 stock with 2.3.6 and cannot sbf down to anything else. im reeally stuck here.
Click to expand...
Click to collapse
http://www.droidxforums.com/forum/droid-x-help/5581-lcd-density-changer-problems-droid-2.html
maybe this helps " If your rooted go into root explorer and open System > Build.prop in text editor. Find the line labeled ro.sf.lcd_density= and change it to 240." from: Doahh droidx forums
It's the first response to the thread.
Good luck!
Edit-------------
Looks like Im a bit late
Hello everyone, Forgive me if I seem a bit flustered, but I am. I was adding a few fonts with an app from the play store. It would restart after each fine, and there was no issue. On the final one, it restarted, but then got hung up for 10 minutes on the ATT logo. I have restarted it with the power button numerous times now, and it has done nothing different. I have only rooted the phone, I have no custom recovery or anything. I booted into the LG stock recovery, canceled the reset, and it still hung up at the ATT logo.
What might have happened, and how can I fix this? I would rather not hard reset, but if I have to, I have to. Please respond with anything at all that might help me. I'm using my old GSII right now, and the newer sim doesn't fit quite right in it. I can make calls and stuff, but i want to get back on the OG as fast as possible. PLEASE respond with anything helpful. Thanks.
I am running stock Jellybean (The initial jellybean we got, I think it was 4.1.1), rooted. No custom roms, no custom recovery.
UPDATE: I did a factory reset (by holding power and volume down). It is still doing the same thing. It gets to the ATT logo and plays the music "Dee dee dee dee 'click'", then stops. Nothing more happens. At all. I've let it sit for a while and nothing is happening. So now the question is, how can I save it with that in mind?
chrisphoenix7 said:
UPDATE: I did a factory reset (by holding power and volume down). It is still doing the same thing. It gets to the ATT logo and plays the music "Dee dee dee dee 'click'", then stops. Nothing more happens. At all. I've let it sit for a while and nothing is happening. So now the question is, how can I save it with that in mind?
Click to expand...
Click to collapse
Sound like you need to use LGNPST or use a teenybin then flash a custom ROM. Factory reseting ( I think) only clears out the /data partition which is where all user and app data is saved. If something in the /system partition is not allowing it to boot, that is why the factory reset didn't work. To fix you have to restore the /system partition back to stock.
To do so, flash a full bin. Which will reset the phone to complete stock (no root, no unlocked bootloader).
Or you can flash a teenybin. Which is smaller and safer. Flashing a teenybin unlocks the bootloader and puts a custom recovery. From there you can just flash a new ROM.
Joecascio2000 said:
Sound like you need to use LGNPST or use a teenybin then flash a custom ROM. Factory reseting ( I think) only clears out the /data partition which is where all user and app data is saved. If something in the /system partition is not allowing it to boot, that is why the factory reset didn't work. To fix you have to restore the /system partition back to stock.
To do so, flash a full bin. Which will reset the phone to complete stock (no root, no unlocked bootloader).
Or you can flash a teenybin. Which is smaller and safer. Flashing a teenybin unlocks the bootloader and puts a custom recovery. From there you can just flash a new ROM.
Click to expand...
Click to collapse
Thanks. Do you know if there's an accurate guide on how to do the teenybin? It's been ages since I've done anything more than root, and I'm not sure what to search for.
chrisphoenix7 said:
Thanks. Do you know if there's an accurate guide on how to do the teenybin? It's been ages since I've done anything more than root, and I'm not sure what to search for.
Click to expand...
Click to collapse
The directions to use the Teenybin are in the OP found here: http://forum.xda-developers.com/showthread.php?t=2230994
The hardest part is getting LGNPST working properly. But that's easy now thanks to the auto install.
Did u fix your phone?
Going to assume teeney bin worked for op. It did for me when I had issues
Sent from my LG-E970
Apologies all, yes I got it working... Mostly. WiFi quit working completely (refused to connect), phone calls took forever to go through, and other odd issues. I'm running it off an old backup of ICS on my external SD. The issues were too much for me to handle, and I was scared to do anything more, so I've got a Moto x. I'm going to try to correctly fix the OG now, so hopefully by documenting the process I can help someone else.
Sent from my XT1058 using xda app-developers app
chrisphoenix7 said:
Apologies all, yes I got it working... Mostly. WiFi quit working completely (refused to connect), phone calls took forever to go through, and other odd issues. I'm running it off an old backup of ICS on my external SD. The issues were too much for me to handle, and I was scared to do anything more, so I've got a Moto x. I'm going to try to correctly fix the OG now, so hopefully by documenting the process I can help someone else.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
i was scared to use teenybin like you but 4.4 lured me into trying. Give teenybin a try its not that bad. you just need to install it, download the teenybin, launch the program, boot your phone into download mode and run the program with the dll and bin files selected.
optimusv45 said:
i was scared to use teenybin like you but 4.4 lured me into trying. Give teenybin a try its not that bad. you just need to install it, download the teenybin, launch the program, boot your phone into download mode and run the program with the dll and bin files selected.
Click to expand...
Click to collapse
I used the Teenybin. It worked enough so I could install my backup. The OS got wiped completely, so I think the kernel just couldn't handle all the stuff it had to anymore.
Sent from my XT1058 using xda app-developers app
I used LGNPST to make full recovery and i dont have any problems with this software.. if want help just ask me.. i will guide you..