Related
I decided to try rooting my phone, and initially had succeeded using ROM Manager. Flashed ClockworkMod Recovery and successfully flashed a custom ROM (CM7).
However I decided to revert, so I did a restore of the nandroid backup I made using ROM Manager before flashing the custom ROM.
In the process my bootloader got locked, so I tried unlocking it using Fastboot. it worked, but once I unlocked it I lost everything - including my nandroid backup. it looks like my SD Card got wiped.
Is this normal, that doing a fastboot oem unlock would wipe everything, including the sd card? or am I missing something and is there some way to restore?
edit: curiously, it's still using my previous wallpaper in the launcher. that and the superuser app seem to be the only things that did not get wiped.
Yes its normal. Every time u unlock the boot loader it will wipe everything on your phone including your SD card. It says it right when it ask u the yes or no thing. I think. But its normal. Sorry to hear u lost all your data
Sent from my Nexus S 4G using xda premium
It's normal
Sent from my Nexus S using Tapatalk
Fastboot unlock wipes like others have stated.
What makes no sense is how the bootloader get relocked. Simple put you can not relock the bootloader period on the device it self. Nandroid restore cant do that. You either relocked manually or used a one click root unroot thing from a computer.
Of course unlock boot loader will wipe everything including SD card. But I wonder how you get relocked boot loader when you restore nandroid backup.
thanks for the replies. I don't know if it says it on the screen where it asks yes or no, but I assumed it was ok since the first time round it didn't wipe my sd card.
I didn't use a one-click unroot; although I did hit "Unroot" by accident once in SuperOneClick, but that was before I actually rooted my phone.
Fortunately I didn't lose any important data, since I had most of it backed up before I rooted the first time (I was super cautious that time, got a little cocky the second time round since the SD card was ok after the first time).
Is there a way to recover it?
Esteway.619 said:
Yes its normal. Every time u unlock the boot loader it will wipe everything on your phone including your SD card. It says it right when it ask u the yes or no thing. I think. But its normal. Sorry to hear u lost all your data
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Guy, do you know a way to recover it. I made the process without pay attention in this thing. I already tried 2 differents recover software, but didn't work. Do you know a way?
I don't know the reason of software, because its scan the blocks even if the initial blocks has been erased.
Thanks a lot!
marmundo said:
Guy, do you know a way to recover it. I made the process without pay attention in this thing. I already tried 2 differents recover software, but didn't work. Do you know a way?
I don't know the reason of software, because its scan the blocks even if the initial blocks has been erased.
Thanks a lot!
Click to expand...
Click to collapse
I don't recall ever seeing anyone post a way to recover the data, but I felt compelled to hit your thanks button since it appears you used the search button unlike so many other newer users here!
Sent from my Nexus S 4G using xda premium
Title says it all. Please read the whole post. I've done a lot up to this point, and I just don't want to go any further without confirming that what I'm doing is right, because everything that should have worked up to this point hasn't and I fear I'm about to hard-brick the phone.
MY SETUP:
Rooted and locked Atrix 2 (AT&T MB865)
Official 2.3.6 OTA upgrade
No backup/CWM/nandroid/anything other than stock recovery that came with the phone (but see below)
32bit Linux from which to adb and fastboot
THE PLAN:
Flash the boot.img and possibly system.img to maintain my user data so I don't have to reinstall stinkin' everything, and factory reset if absolutely necessary.
HOW I BRICKED IT:
Gained root, installed ROM Toolbox Lite, changed my boot animation, rebooted into a bootloop at the animation screen.
WHERE IT STANDS:
I can get into fastboot with Power+Vol Down, or the boot menu with Power+Vol Up+Vol Down, but I can now only select normal boot from the boot menu (see below).
WHAT I HAVE TRIED ALREADY:
I started with the noob guide: http://forum.xda-developers.com/showthread.php?t=1396650
I got the FXZ from here: http://forum.xda-developers.com/showthread.php?t=1607083
My battery was nearly dead and wouldn't charge, so I did this without actually hooking the battery to the phone: http://forum.xda-developers.com/showthread.php?t=892026
I booted into flashboot with Power+Vol Down
I tried to use the fastboot that came with the Android SDK and got "Preflash validation error" when running
Code:
fastboot flash boot boot.img
I found out about moto-fastboot and got the 32bit Linux version from here: http://forum.xda-developers.com/showpost.php?p=15024312&postcount=48
I got "INFOPreflash validation error" when running
Code:
moto-fastboot32 flash boot boot.img
I booted into the boot menu with Power+Vol Up+Vol Down and selected BP tools, which lead to the bootloop again, and I pulled the battery.
I decided to give up and booted into the boot menu again to try to just do a full factory recovery, only to discover that I was now not able to scroll through the other options, and that Normal bootup was my only option, which lead to the bootloop
WHAT I HAVE YET TO TRY:
RSD Lite, with or without the fix for the 2.3.6 OTA upgrade from the noob guide, primarily because I don't have easy access to a Windows box and I already have all the files and appropriate setup on my Linux box (but is an eventual option)
This, even though it's for a different phone: http://forum.xda-developers.com/showthread.php?t=1295839
This, even though it supposedly works for 2.3.6: http://forum.xda-developers.com/showthread.php?t=1539167
Flashing system.img before flashing boot.img
Again, the only reason I'm stopping where I am to ask for help is because everything that should have worked up to this point just hasn't, and I don't want to hard-brick my phone.
Thanks for getting me this far, guys and gals. Your work is truly extraordinary.
You're first "oops" was not having installed the ATRIX Bootstrap and the CWM Recovery. What you need to do now, is download the Return To Stock script and boot into AP Fastboot, plug in USB, and run the Stock Restore.bak -this will flash 2.3.5 back to your device. Then, you'll have to OTA to 2.3.6. and then I HIGHLY recommend you install the bootstrap.apk along with CWM Recovery.
Sent from my MB865 using xda premium
You will need to make sure you patch the fxz with this:
http://forum.xda-developers.com/attachment.php?attachmentid=887221&d=1328375358
Unzip this, then move these files into the directory with the fxz, and allow them to be replaced.
At this point it is MUCH better to use RSDlite, unless you REALLY know what you are doing here.
It is not your boot.img that is corrupted it is your system.img, that is where all of the programs, and "user level" operations sit. The boot.img is just the OS kernel, and it is not user accessible, so there is really no need to even flash it.
You will need erase the data partition, sorry but you HAVE to do this, or you WILL get FCs left and right.
Here is the exact commands to get you whole again:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash boot boot.img
moto-fastboot reboot
Apex_Strider said:
You're first "oops" was not having installed the ATRIX Bootstrap and the CWM Recovery. What you need to do now, is download the Return To Stock script and boot into AP Fastboot, plug in USB, and run the Stock Restore.bak -this will flash 2.3.5 back to your device. Then, you'll have to OTA to 2.3.6. and then I HIGHLY recommend you install the bootstrap.apk along with CWM Recovery.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Hindsight is 20/20, and I am kicking myself SO HARD for not having done the first two things. As soon as I am back up and running I will do these things. You may consider me duly chastised
I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1539167
I further assume that I can run that script from Linux, possibly with a little doctoring. I see that it uses two erase commands, and when I tried to erase boot.img earlier, I was told that the erase command was restricted. Is that only for certain images?
Sorry for nagging, but I just want to be perfectly clear. I'm pretty solid with Linux but a little green with Android and a lot nervous about the whole thing.
jimbridgman said:
You will need to make sure you patch the fxz with this:
http://forum.xda-developers.com/attachment.php?attachmentid=887221&d=1328375358
Unzip this, then move these files into the directory with the fxz, and allow them to be replaced.
At this point it is MUCH better to use RSDlite, unless you REALLY know what you are doing here.
It is not your boot.img that is corrupted it is your system.img, that is where all of the programs, and "user level" operations sit. The boot.img is just the OS kernel, and it is not user accessible, so there is really no need to even flash it.
You will need erase the data partition, sorry but you HAVE to do this, or you WILL get FCs left and right.
Here is the exact commands to get you whole again:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash boot boot.img
moto-fastboot reboot
Click to expand...
Click to collapse
I'm pretty confident that I can properly patch the FXZ and run those commands (no sarcasm intended), and I can come to terms with the wipe if it gets my device back up and running. Thanks for checking in, Jim (can I call you Jim?), from what I've seen thus far you're pretty highly respected here
EDIT: No disrespect, Apex_Strider, once I saw your avatar I recognized you from around the forum
wormmd said:
Hindsight is 20/20, and I am kicking myself SO HARD for not having done the first two things. As soon as I am back up and running I will do these things. You may consider me duly chastised
I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1539167
I further assume that I can run that script from Linux, possibly with a little doctoring. I see that it uses two erase commands, and when I tried to erase boot.img earlier, I was told that the erase command was restricted. Is that only for certain images?
Sorry for nagging, but I just want to be perfectly clear. I'm pretty solid with Linux but a little green with Android and a lot nervous about the whole thing.
Click to expand...
Click to collapse
NO!!!! do NOT erase any partitions before flashing them...
I am also a Linux user, use the commands I gave, Please be very careful, you can erase things, and not get them to flash back!
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
wormmd said:
I'm pretty confident that I can properly patch the FXZ and run those commands (no sarcasm intended), and I can come to terms with the wipe if it gets my device back up and running. Thanks for checking in, Jim (can I call you Jim?), from what I've seen thus far you're pretty highly respected here
Click to expand...
Click to collapse
Yeah It's Jim, No worries I was not trying to insult you here, I kind of have to think in terms of as if someone does not know the subject well, and make assumptions on their behalf, sort of like tech support... but more knowledgeable... LOL.
wormmd said:
Thanks for checking in, Jim (can I call you Jim?), from what I've seen thus far you're pretty highly respected here
Click to expand...
Click to collapse
Well you got that right.. he's a genius, has experience and more importantly is very helping natured.. always saying "here to help".. lucky to have him onboard..
Sent from my MB865 using Tapatalk 2
wormmd said:
EDIT: No disrespect, Apex_Strider, once I saw your avatar I recognized you from around the forum
Click to expand...
Click to collapse
No disrespect taken, and please accept my apologies if I came across in a 'chastizing' manner -I was only trying to stress the importance of having CWM (on boot, preferably), because it has saved my A$$ and many other's as well.
Sent from my MB865 using xda premium
Apex_Strider said:
No disrespect taken, and please accept my apologies if I came across in a 'chastizing' manner -I was only trying to stress the importance of having CWM (on boot, preferably), because it has saved my A$$ and many other's as well.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You misunderstood: anyone undertaking this kind of work needs to be chastised for not having backups in place before doing stupid things like I did, in my opinion. In addition, I've been doing these kinds of things with computers and software development and such for long enough that I should have known better. I need a swift kick in the butt every once in a while to get me back on the right track
I got all the way to flashing boot. It send successfully, then when trying to write spat out an INFOPreflash validation failure.
I patched the FXZ I got from the OP with the link Jim provided, but there was no boot.img in the patch.
Should I try a fastboot continue or just fall back to this method: http://forum.xda-developers.com/showthread.php?t=1539167?
wormmd said:
I got all the way to flashing boot. It send successfully, then when trying to write spat out an INFOPreflash validation failure.
I patched the FXZ I got from the OP with the link Jim provided, but there was no boot.img in the patch.
Should I try a fastboot continue or just fall back to this method: http://forum.xda-developers.com/showthread.php?t=1539167?
Click to expand...
Click to collapse
I think at this point you might need to use RSDlite, this has happened to a few of us, and there is really not a good way around it if it fails like that.
You will need a Windows 7 install to use, XP will not work, neither will Vista.
I know, I HATE windblows, but for this, it is really the ONLY way to get back to fully stock 2.3.5, and the rest of us Linux users have had to do it at least once. Once this happens, it will NOT let you fully boot, with out that nagging you, and you having to get into recovery and do a "normal" boot EVERY boot. The ONLY way around it is RSD lite and the n00b guide.
jimbridgman said:
I think at this point you might need to use RSDlite, this has happened to a few of us, and there is really not a good way around it if it fails like that.
You will need a Windows 7 install to use, XP will not work, neither will Vista.
I know, I HATE windblows, but for this, it is really the ONLY way to get back to fully stock 2.3.5, and the rest of us Linux users have had to do it at least once. Once this happens, it will NOT let you fully boot, with out that nagging you, and you having to get into recovery and do a "normal" boot EVERY boot. The ONLY way around it is RSD lite and the n00b guide.
Click to expand...
Click to collapse
Man, if that's not the second lamest thing I've ever heard, I don't know what is. The first lamest thing would be losing my phone over something silly like that, but at least it's fixable.
Will the restore script method not work, if I just ran all the commands from that .bat manually? Is it worth trying at least? Is it worth not trying for the sake of not hard-bricking the phone? This restore script method, that is: http://forum.xda-developers.com/show....php?t=1539167
If not, I'll hop on Windows when I get home today. Thanks again for all of your help.
wormmd said:
Man, if that's not the second lamest thing I've ever heard, I don't know what is. The first lamest thing would be losing my phone over something silly like that, but at least it's fixable.
Will the restore script method not work, if I just ran all the commands from that .bat manually? Is it worth trying at least? Is it worth not trying for the sake of not hard-bricking the phone? This restore script method, that is: http://forum.xda-developers.com/show....php?t=1539167
If not, I'll hop on Windows when I get home today. Thanks again for all of your help.
Click to expand...
Click to collapse
With the issue you are having, that script will most likely not fix it. RSDlite really is the best way to go at it... I have had that same thing and I tried everything under the sun and the thing is that there are some binary files that ONLY RSD lite can process correctly and get fastboot to flash, not sure what they have built into RSDlite to do it, but it does what it is supposed to.... Moto is not very "hacker" friendly, and ALL of their junk is windblows centric, at least with other phones there are ways around issues like this in Linux, but between moto locking the phone down, and thier widblows mind set this is the last moto product I buy even with google at the helm... and I LOVE my Xoom, it is unlocked and everything and I have been running CM9 on it for almost a year now. I really honestly bought the A2 for the webtop functionality, but even that was such a pain for me to get all hacked up, and working as it should... that webtop hack of mine took way more time to work out than it should have, thanks to all the "safeguards" Moto put in.
If you try the commands in the script and it works let us know, but I have heard others have issues too once the preflash fail has come up, and have HAD to use RSDlite.
jimbridgman said:
With the issue you are having, that script will most likely not fix it. RSDlite really is the best way to go at it... I have had that same thing and I tried everything under the sun and the thing is that there are some binary files that ONLY RSD lite can process correctly and get fastboot to flash, not sure what they have built into RSDlite to do it, but it does what it is supposed to.... Moto is not very "hacker" friendly, and ALL of their junk is windblows centric, at least with other phones there are ways around issues like this in Linux, but between moto locking the phone down, and thier widblows mind set this is the last moto product I buy even with google at the helm... and I LOVE my Xoom, it is unlocked and everything and I have been running CM9 on it for almost a year now. I really honestly bought the A2 for the webtop functionality, but even that was such a pain for me to get all hacked up, and working as it should... that webtop hack of mine took way more time to work out than it should have, thanks to all the "safeguards" Moto put in.
If you try the commands in the script and it works let us know, but I have heard others have issues too once the preflash fail has come up, and have HAD to use RSDlite.
Click to expand...
Click to collapse
I'm going to give it a go because I'm stubborn as a mule, and I'll be sure to let you know how it goes, but yeah, I'm basically resigned to having to use Windows. This phone had the best hardware for the money when I got it, but I'm getting pretty annoyed with most of what's annoying everyone else too.
Wish me luck!
Once again, got all the way up to flashing boot and then got an INFOPreflash validation failure. Not pleased, but hey, what can you do? Windows, here I come...
UPDATE: it boots
I can boot into the OS by booting to the bootloader with Power+Vol Up+Vol Down, and also I can access other menu option in the bootloader menu now. The new plan is to select "Recovery" from the bootloader menu to see if that'll fix my boot.img, since I'm already wiped as it is. Thoughts?
wormmd said:
Once again, got all the way up to flashing boot and then got an INFOPreflash validation failure. Not pleased, but hey, what can you do? Windows, here I come...
Click to expand...
Click to collapse
I know this doesn't help much, but the last time I tried to FXZ through AP Fastboot it was unsuccessful. I had never run RSDlite before, but had to that time. Worked like a charm...
Sent from my MB865 using xda premium
Apex_Strider said:
I know this doesn't help much, but the last time I tried to FXZ through AP Fastboot it was unsuccessful. I had never run RSDlite before, but had to that time. Worked like a charm...
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
No, it's plenty help. It's good to have confirmation that I'm not crazy and that someone else is having issues I'm having, ya know?
I'm just glad it's semifunctional now. I'll post probably once more tonight after I run it through RSDlite.
wormmd said:
I can boot into the OS by booting to the bootloader with Power+Vol Up+Vol Down, and also I can access other menu option in the bootloader menu now. The new plan is to select "Recovery" from the bootloader menu to see if that'll fix my boot.img, since I'm already wiped as it is. Thoughts?
Click to expand...
Click to collapse
jimbridgman said:
it will NOT let you fully boot, with out that nagging you, and you having to get into recovery and do a "normal" boot EVERY boot. The ONLY way around it is RSD lite and the n00b guide.
Click to expand...
Click to collapse
That is what I was referring to above ^^^
You can still work, until you RSDlite, but I would not re-install everything, because this should just let you do what you need to like make calls, until you RSDlite back to full stock.
jimbridgman said:
That is what I was referring to above ^^^
You can still work, until you RSDlite, but I would not re-install everything, because this should just let you do what you need to like make calls, until you RSDlite back to full stock.
Click to expand...
Click to collapse
Oh, of course, I'm just glad that it's working(ish) for now
On a related note, is RSDlite open source? How do they do what they do and why is it any different, know'm'sayin'? If they can do it, why can't we? Investigating...
Hey guys. I recently had my Atrix 2 soft brick on me. I can (and have) search this site and google on how to use RSD Lite or "MacGyver" it. But the only processes that I am seeing in performing myself all leads to flashing it first. Now to my knowledge, that simply means that I will be wiping the thing clear and instal a new ROM (either stock or custom). But does that mean that I can't access the data thats still there before its formatted? I think I still have contacts on there that I still need to get off. Any info you can give will be appreciated. Thanks guys, later.
Sowden said:
Hey guys. I recently had my Atrix 2 soft brick on me. I can (and have) search this site and google on how to use RSD Lite or "MacGyver" it. But the only processes that I am seeing in performing myself all leads to flashing it first. Now to my knowledge, that simply means that I will be wiping the thing clear and instal a new ROM (either stock or custom). But does that mean that I can't access the data thats still there before its formatted? I think I still have contacts on there that I still need to get off. Any info you can give will be appreciated. Thanks guys, later.
Click to expand...
Click to collapse
Contacts? you know google backs them up right?
But either way, only thing you can do is get crap off your sdcard. data on phone, is gone if not backed up to the cloud or sdcard.
MotoMudder77 said:
Contacts? you know google backs them up right?
But either way, only thing you can do is get crap off your sdcard. data on phone, is gone if not backed up to the cloud or sdcard.
Click to expand...
Click to collapse
Yeah, I never did that cloud stuff. I was weary of where my information went out to since I had no idea where this "cloud" was (yeah, I'm one of those people). But anyway, gone...? What if I MacGyver the battery to get it to charge enough? I should at least be able to turn it on at that point. I just need it on long enough to get the information to my SD card. What do you think? Thanks man.
Sowden said:
Yeah, I never did that cloud stuff. I was weary of where my information went out to since I had no idea where this "cloud" was (yeah, I'm one of those people). But anyway, gone...? What if I MacGyver the battery to get it to charge enough? I should at least be able to turn it on at that point. I just need it on long enough to get the information to my SD card. What do you think? Thanks man.
Click to expand...
Click to collapse
depending on what you did to "brick" your phone, it might be possible to fix it w/o FXZ'in back.
But if you must FXZ, and cant boot the phone, your SOL. sorry man.
IMHO, In this day and age, your gonna have to use the cloud. New devices are all leaning that way. Look at it like a safety measure incase crap like this happens.
break phone, crap is gone, SDcard screws up, all your pictures and files are gone.
The times of storing contacts on SIM cards is long and gone.
MotoMudder77 said:
depending on what you did to "brick" your phone, it might be possible to fix it w/o FXZ'in back.
But if you must FXZ, and cant boot the phone, your SOL. sorry man.
Click to expand...
Click to collapse
Well, I really didn't do anything wrong. I was working real late with it trying to get an app to coralate with my phone and my tablet. Just let it run out of batteries, and since I was busy, I figured I could charge it back later. Little did I know it wouldn't turn back on again. I am attempting to charge it manually right now, but if that doesn't work, then my last resort will be to take it somewhere locally to try to bring it back. Unless there is someone on the boards here that does a repair over local screen control (logmein.com type thing) (um, anyone on here does that? I had a guy work on my tablet once the same way). Thanks man for you're help.
Edit: Due to my n00bness, I realize that this thread has mutated into something that should go into the "Think you bricked your phone?" thread. Apologies.
So your phone just died?
What happens when you attempt to charge it? With a wall charger, not usb.
Do you get the led lit up?
Sent from my MB865 using Tapatalk 2
Alright, so heres my story. I own two different batteries for my phone. One that came with it that I think I fried the life on it by charging it with an USB OTG (I used it as my entertainment system at the time). The other one I got at batteries+Plus. That was the one I have been using currently. With my newest battery (Batteries+Plus) attached to my phone, I can get it to my "M" splash screen and freeze when I plug it in to the wall. That one I have to work at getting AP Flash on, but I can get that open. It gives me the dreaded "Battery Low - Cannot program" sign. And oddly enough it doesn't give me a selection screen like it usually does, I have been trying to charge that battery manually and checking it with a voltage meter. It seems that its not holding the charge correctly. So I then theres my old battery (that came with the phone). With that attached, I can get past the "M" screen to the "AT&T" splash screen before it freezes. That I don't really have to work hard to get to the AP Flash recovery while plugged into the wall. It is really no help either. I can connect it to my laptop and it says that its USB Transfer ready (but I can't get that with the other battery). They both start the splash screen immediately when I plug it into the wall, I haven't had my phone brick on me like this, so I hope I'm making some kind of sense. Thanks for listening to my story man.
Sowden said:
Yeah, I never did that cloud stuff. I was weary of where my information went out to since I had no idea where this "cloud" was (yeah, I'm one of those people). But anyway, gone...? What if I MacGyver the battery to get it to charge enough? I should at least be able to turn it on at that point. I just need it on long enough to get the information to my SD card. What do you think? Thanks man.
Click to expand...
Click to collapse
Just flash the system partition only.
You have to have some command line skills, which is not hard...
1) get your phone back to being charged.
2) get the phone into fastboot mode.
3) connect your A2 to your computer
4) download the correct fxz file for your region.
5) unzip the fxz and save the system.img file in same dir you have the android SDK installed in
6) run cmd.exe
7) cd to the directory you unzipped the fxz system.img file to, from the command line
8) run the following:
Code:
fastboot flash system system.img
fastboot reboot
That should save all your data, since it is stored in /data and not /system.
That should save you from a bootloop if you were on stock, if not you are kind of SOL, unless you can do some install script hacking to only flash /system for the ROM you are on without clearing /data.
jimbridgman said:
Just flash the system partition only.
That should save all your data, since it is stored in /data and not /system.
Click to expand...
Click to collapse
Oh, alright, because in order to flash your phone correctly you have to flash system.img, data.img, and (something else? I've seen it done in a video I just can't remember what it was) right? Alright, I should just google Atrix 2 AT&T USA SFZ and I should find my right one? Thanks for your help guys, I'm going to try to avoid taking it to a shop tomorrow.
Wait a second, sorry to ask another question. If I just update the system img, as you said, can I apply a Gingerbread kernel
and still have it operate the same, or should I find a matching ICS as it was on my phone? Thanks.
Sowden said:
Oh, alright, because in order to flash your phone correctly you have to flash system.img, data.img, and (something else? I've seen it done in a video I just can't remember what it was) right? Alright, I should just google Atrix 2 AT&T USA SFZ and I should find my right one? Thanks for your help guys, I'm going to try to avoid taking it to a shop tomorrow.
Click to expand...
Click to collapse
No you do not have to flash all the partitions. Since all your data sits in its own partition, you can save it by only flashing the system partition and not using RSD, which WILL erase the /data partition, which you want to keep.
I would advise you to take a backup of just your data and save it to your sdcard in case this happens again, if this works for you.
The fxz files are in the developer section or here:
http://sbf.droid-developers.org/edison/list.php
You must know which region and version of android you were on before.
jimbridgman said:
Just flash the system partition only.
That should save all your data, since it is stored in /data and not /system.
That should save you from a bootloop if you were on stock, if not you are kind of SOL, unless you can do some install script hacking to only flash /system for the ROM you are on without clearing /data.
Click to expand...
Click to collapse
Yeah, no dice. I flashed the system.img and the boot.img and I still got the same thing. I guess I'll take it to some local store to see if they can do something to help recover it. Thanks for your help, and I guess that a "cloud" situation is a new reality I will have to consider. Thanks guys, later.
Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium
First off, yes I have done my research before posting and having found anything helpful.
So here's my issue, my phone randomly restarted and now is stuck in a boot loop. Not too sure what to do. Im not familiar with ADB. How can I go into recovery and access my stuff in my phone because I have a bunch of pics and videos id like to keep before I just flash a new ROM? I know I can do a backup, But I dont have enough space on my phone to do one. Any help or advise would be greatly appreciated.
Ruki_Uki said:
First off, yes I have done my research before posting and having found anything helpful.
So here's my issue, my phone randomly restarted and now is stuck in a boot loop. Not too sure what to do. Im not familiar with ADB. How can I go into recovery and access my stuff in my phone because I have a bunch of pics and videos id like to keep before I just flash a new ROM? I know I can do a backup, But I dont have enough space on my phone to do one. Any help or advise would be greatly appreciated.
Click to expand...
Click to collapse
By now have you learned anything about adb? You must know how to get into recovery. I'm not sure by your info if you have a custom recovery or if you're stock? Hell man you're a senior member so must have learned something along the way
Sent from my Nexus 5 using XDA Free mobile app
Ruki_Uki said:
First off, yes I have done my research before posting and having found anything helpful.
So here's my issue, my phone randomly restarted and now is stuck in a boot loop. Not too sure what to do. Im not familiar with ADB. How can I go into recovery and access my stuff in my phone because I have a bunch of pics and videos id like to keep before I just flash a new ROM? I know I can do a backup, But I dont have enough space on my phone to do one. Any help or advise would be greatly appreciated.
Click to expand...
Click to collapse
First of all, try booting into recovery.Then wipe your cache and reboot. If the bootloop isn't gone, then I see no other option but to try and dirty flash your rom again.Try the cache method and write back so I can send you a guide.
Sent from my Nexus 5 using Tapatalk
[info] Storage: Nexus 5 Data (info / loss / recovery / prevention)
http://forum.xda-developers.com/showthread.php?t=2534010
Sent from my Nexus 5 using Tapatalk
Are you on custom recovery? If so do you have a previous backup or any rom zips on your storage? If so dirty flash the rom zip or restore system only of a backup and you won't lose data
Sent from my Nexus 5 using Tapatalk