Related
Hello, xda!
I've been around on the forums for some time, flashing and messing with ROMs before, but with an old HTC Touch Pro. So forgive me for seeming like a leecher.
I've come here to ask a few questions reguarding Andriod roms and flashing/upgrading procedures. I'm comfortable with using RUUs to upgrade, but who isnt...
I've had my HTC Hero for about 2 weeks now and I accidently bricked one already. I've rooted manually once, and got no signal on the stock Sprint ROM so I tried to go back to the original flash recovery but killed my phone instead.
Could someone help me out. I've read guides and been very, very anxious to upgrade and root but as you've read, I've already bricked my phone once so I'm pretty cautious now.
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
mjones832 said:
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
Click to expand...
Click to collapse
First off; we're happy you chose not to give up and came back a second time.
What you do need to do is; 1) Root and flash a Recovery image 2) Make a Nandroid back up, 3) Wipe ONLY your phone (not your SD Card, unless you want to do Apps2SD) and 4) Flash the ROM of your choice.
**The rooting guide I linked above is the way I prefer to do it; via adb commands. However, you could also you use Flipz's kitchen to do all of this for you.
.
For more information about Flipz's kitchen, please go here: Flipz's Kitchen
Also, do note -- for other tutorials/guides/references; go HERE
I was seriously nervous to start the process as well. As I told someone else, being nervous is a good thing. That just means you'll be careful.
I seriously recommend reading this thread and following instructions. Do not skip steps, do not pass go, do not collect $200. I've personally used the Windows guide and the Linux guide. Both are very well done and I can verify that they work.
Beyond that, the Search function is fantastic and provides lots of information. Don't be afraid to ask questions, either. Most of us are nice and like to help, even if we do call people n00bs.
WOW! Insanely quick replies. Thanks for that guys. This is what I wanna hear so I'll be doing the flash when I get home.
I'm using the 2.1update1 sprint beta ROM right now so should I revert back to the 1.56 and THEN do all this or can I just jump right in. I've always been confused as to which rom needs what flash rec root file or w/e.
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Thanks again guys!
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
mjones832 said:
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
Click to expand...
Click to collapse
Some people say to toggle airplane mode on and off. Some people say reboot. The last time this happened to me I just played a video game for ten or fifteen minutes and it fired up.
mjones832 said:
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Click to expand...
Click to collapse
I've not used apps2sd myself, but I'm told the higher class card the better, for obvious reasons.
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
mjones832 said:
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
Click to expand...
Click to collapse
Have fun! We'll be here when you get back.
yes.. a faster class sd card is highly recommended!!! other wise with a2sd, you might see more lag... and issues.
I personally, would not do a2sd at the same time as you upgrade. finish the upgrade first. make sure all is good...
then do the a2sd. and do a nandroid backup again before.
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
mjones832 said:
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
Click to expand...
Click to collapse
What steps did you take to use the Sprint RUU?
In order to run the Sprint RUU, you need to do:
**Make sure you have the appropriate drivers to detect HTC Sync**
1. Install HTC Sync on your computer
2. After install, open and leave the HTC Sync Window open
3. Connect your phone; and click on the sync option. You should be able to sync, if not - then you're having driver issues.
4. After you've successfully synced, NOW run the Sprint 1.5 RUU.
5. Upon a successful RUU, you'll have your phone back to its factory settings.
Now you can reroot, flash whatever ROM you like, and flash any/all add-ons.
As far as the signal goes, the following are from the Fresh 2.0d install page.
A reboot after the first bootup finishes is recommended, especially if you were previously having PRI/PRL problems.
Click to expand...
Click to collapse
If after flashing you end up with any data issues then first try rebooting. If that doesn’t resolve it for you then try updating your profile and PRL. This is a side effect of the different PRI’s and PRL’s that people have ended up on. You may actually need to update your profile and PRL a couple times to get everything going but I promise it will. You should end up on PRL 60663.
Click to expand...
Click to collapse
I personally had no problems, but I was flashing Fresh, not Damage.
Ok, I've got it rooted, and nand-backup stored on my PC.
DamageControl says to wipe before his install. Do I "wipe data/factory reset" or "wipe Dalvik-cache" or any other options?
If its the same as Fresh, they want you to do a Wipe data/factory reset
Thanks everyone! I'm installing DamageControl right now! I'll let you know how it goes.
Success! I've got the phone rooted, at least I think I do, and flashed to DamageControl v2.08.
My next task is I really want to get my apps to install to my sdcard. I've got a 8GB class 4 sdcard. Should and can I put my apps onto this? I've heard that the hero doesnt even read and write faster then 2Mbps so I'm good, right?
Not sure if I'm rooted. I've installed a few apps that require SU and when they try to do a "SU Request" the screen sits at a black screen with that title at the top.
Any idea on whats going on?
If you were able to flash a damage less rom you're rooted.
On the black window there should be am option on the bottom to allow, select it.
-------------------------------------
Sent via the XDA Tapatalk App
The black screen for SU is caused by not having USB Debugging turned on as it is required for superuser permissions. I have not tried A2SD because I only have a class 2, but have read that unless you have a class 6 it can be slow.
I did a search and couldn't find much help.
I recently dropped my phone and the screen got a slight crack, so the insurance company sent me a new one.
I figured I'd use ROM manager to backup my old phone, and restore it on my new phone.
New phone restores, reboots, and gets stuck at the black Vibrant screen.
I can get back into recovery mode fine, but nothing seems to work.
I let it sit at the Vibrant screen for about an hour before I try again.
Its attempt 3 when I decided to come on this site for some help.
Specs:
Stock
Rooted
Launcher pro
Nothing too much to be confusing and brick, so wtf?
Oh and I understand I could use odin to reflash my phone, please please please don't suggest odin, because I don't own a PC, I own a mac. Please don't tell me to go out and buy a PC or to download a program that costs $50 to use PC programs on a mac. I could have told myself that kind of information.
HELP, my brand new phone is destroyed wahhhh
From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App
a400meter said:
From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...
yelowbottlecaps said:
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...
Click to expand...
Click to collapse
The only way I can think of that a nandroid restore would soft brick you, is because you have restored a version of android with a different kernel.
If the original phone had the original firmware (JFD), and the replacement had the most recent (JI6), this is what would be expected to happen.
Since you seem unable and unwilling to use Odin, your going to have to tell us more details (i.e. which versions of the firmware as related above were actually in play) before we can begin to help. If you don't know, well....
You can also simply take it back to a local T-Mobile store and do another swap, or you can find a friend with a Windows PC and Odin (or Samsung's Mini KIES with JI6). These are your only real options...
both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.
so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?
yelowbottlecaps said:
both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.
Click to expand...
Click to collapse
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
[PROGRAM] Heimdall - Cross-Platform Open-Source Flashing Software (1.0.0 Available)
Heimdall's Website, with downloads...
XDA Dev Thread with JI6 Odin .tar file....
Best of luck!
s15274n said:
so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?
Click to expand...
Click to collapse
True that...Why didn't I think of that obvious ploy. If he can get into Recovery, and bounce over to clockwork...Well now's a good a time as any to try Bionix or Bionix Fusion...or a few other of the CW Recovery installable builds...Definitely easier than Heimdall or working out Odin on a mac....and definitely preferable to staring at a Vibrant logo...
{{facepalm}}
masterotaku said:
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
Best of luck!
Click to expand...
Click to collapse
If there was a step by step walkthrough, I have no problem trying this out.
But I downloaded it and have no idea what I'm doing. Therefore, still SOL
^ are you? You didn't answer my questions.
I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL
I just tried using Odin on my roommates PC. An error happened and now the phone is showing a picture of a phone, a couple dots, an exclamation mark, a couple dots, and a computer.
Nothing I can do is taking it out of this screen. Unplugged from computer, took out battery, took out sd card, put it back in... nothing
Am I bricked for good now?
This is a terrible day.
edit: i managed to be able to get the phone into download mode.
No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.
All~G1 said:
I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL
Click to expand...
Click to collapse
If someone can back this up with some instructions that would be amazing.
All~G1 said:
No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.
Click to expand...
Click to collapse
Thank you for the motivation!
yelowbottlecaps said:
Thank you for the motivation!
Click to expand...
Click to collapse
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.
All~G1 said:
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.
Click to expand...
Click to collapse
and in the midst of a roommate that needs his pc back.
I still need a fix that would work for macs... if not, I'd have to wait for my roommate to let me bum his pc again
Do my posts not show up or something? wtf.
s15274n said:
Do my posts not show up or something? wtf.
Click to expand...
Click to collapse
/me pats s15274n on the back....don't get mad...get even! =P
Honestly, sounds like yelow's focusing on getting all the help s/he needs from All~G1. I wouldn't worry about it.
~SB
After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic.
Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.
Many thanks in advance for any suggestions/fixes!
Phillip
Its not bricked if it boots...
That is strange though. May have to reflash stock images.
Try bringing everything back to stock?
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Gr3yghost said:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Click to expand...
Click to collapse
No push the images using adb
I figured it could be done. Could you please point me to a thread explaining how to push images using adb?
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).
Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.
[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
djsaad1 said:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
Click to expand...
Click to collapse
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!
Sent it back
Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.
So, I had been using my A500 for the last few days with no problems. Well, yesterday, I got home from work and powered it on. The lockscreen came up, but the screen was unresponsive. I turned it off and then back on, but screen still didn't work. Then I did a hard reset, which still didn't fix the problem. I put it into recovery, then did a wipe that still didn't fix the issue. I flashed the ROM again. Then a different ROM. All it does is is boot up and go to the lock screen, but the screen does not respond.
If I can avoid it, I don't really want to go through the hassle of returning it since I got it online. Hopefully it can be fixed without having to take it back. Thanks in advance for everyone's help.
Boot back into recovery.
Wipe your 3 things,
User Data
Cache
Dalvik
Then go to Mounts
Format the same 3 (user data, cache partition and Dalvak.
And Flexrom
Then flash your rom. Try and flash a basic rooted rom. No kernels, no gapps.zip
See what happens.
If you have a file called update.zip, on your sd, I would delete it. And anything else there except for the rom.
sounds like hardware failure. Has the tablet been dropped or banged around. The connector on the digitizer could have came loose.That would mean void warranty and take it apart ..
Send it back is likely your. Best option
Thanks for the quick responses! I'm gonna try these things, hopefully I don't have to take it back.
Guess it is a massive hardware failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
sikkboy626 said:
Guess it is a massive software failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
Click to expand...
Click to collapse
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Moscow Desire said:
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Click to expand...
Click to collapse
Thanks for all your help. I was able to get it back to stock. The return should go fine. You're awesome and I did not forget to use the thank you button.
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
You can use normal usb mouse with this tablet, you will get mouse pointer on the screen when you connect mouse...
erica_renee said:
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
Click to expand...
Click to collapse
I was able to flash using the physical buttons. I got it all back to factory specs so I can return it. you were correct I believe, it does seem to be a screen hardware failure. Everything else works but the touch response.
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
erica_renee said:
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
Click to expand...
Click to collapse
Guess I had to take one for the team
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
jimmydafish said:
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
Click to expand...
Click to collapse
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
minitele said:
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
Click to expand...
Click to collapse
you should join the G+ community for much better and more pointed help. The forums get cluttered.
1) download correct 4.2.2 (57-1) FXZ file
2) extract boot, system, recovery from the file
3) fastboot flash each of the partitions to your phone
(fastboot flash boot boot.img)
(fastboot flash recovery recovery.img)
(fastboot flash system system.img)
Doing this will put your phone in a state where it is ready to update.
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
jayboyyyy said:
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
Click to expand...
Click to collapse
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
jimmydafish said:
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
Click to expand...
Click to collapse
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
jayboyyyy said:
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
Click to expand...
Click to collapse
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
minitele said:
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
Click to expand...
Click to collapse
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
jayboyyyy said:
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
Click to expand...
Click to collapse
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
minitele said:
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
Click to expand...
Click to collapse
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
jayboyyyy said:
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
Click to expand...
Click to collapse
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
minitele said:
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
Click to expand...
Click to collapse
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
tracyde said:
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
Click to expand...
Click to collapse
To all,
The forums and people in our arena never fail, fastboot erase cache worked perfect. I have recovered all my data and now I will definitely continue to performing a full recovery with stock image.
Thank you again all for all of your help, I am glad to see at least this corner in the internet still is alive and kicking!