I have MOTO X 1053, unlocked bootloader. Runs Android 4.2.2 and this is where I want to stay (perfectly compatible with my car Bluetooth; I am not missing any features from later Android versions and don't want to deal with problems that come with them and potential incompatibility with my car after an upgrade considering downgrade is not possible).
Recently I noticed that phone is never in 4G LTE anymore - only in 4G. Before it was in LTE mode all the time. I downloaded an app from the market to force it into LTE and it worked but as soon as I reboot the phone is back in 4G (HSPA) mode.
I suspect the reason it was no longer in 4G was that I messed too much with Xposed toggle that toggles between 2G / 2G or 3G / 3G only but I am not sure.
So I made a TWRP backup (and a separate backup for Contacts, good thing that I did) and then tried to restore the backup from a year ago. Result: boot loop.
Tried to restore latest backup - same result, boot loop.
I then copied all I could (sdcard, /system, /data, /data/data) from the phone via ADB and returned to stock Android 4.2.2 using instructions from here: http://mark.cdmaforums.com/MotoX-ReturnToStock.html (option 5 using mfastboot)
After initial setup phone immediately connected to 4G LTE, so I flashed TWRP recovery (newer version than I had before), rooted and spent a day setting the phone up the way it used to be.
Nowhere near done I decided to see if TWRP restore will work now. So I take a backup and guess what? The same result. Restore (with MD5 verification) completes without any errors but then I am stuck in bootloop again.
I then booted into recovery, did factory reset from recovery and it worked - after reboot phone starts initial setup.
Can anyone suggest what I may be doing wrong? Why does restore always cause the boot loop?
Related
This is my first time to restore a nandroid backup i recently made. The load bar isnt animated any longer and its sitting on:
"restoring data...
[email protected]"
the first time i pulled the battery after about 5 minutes and rebooted into what appeared to be a partial restore, but the home button didnt work and i powered down before it finished synching my settings. Im on my second attempt, sitting at the same place and its been close to 10 minutes, is this normal or should i just try pulling the battery again and reflashing the rom altogether? I wiped the first time even though my searching said it wasnt necessary, no wipe the second time. here are my unhelpful search results:
http://www.google.com/search?source...s+nandroid+restore+take+on+nexus+one?&qscrl=1
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=did+my+nandroid+restore+freeze?&qscrl=1
Doesn't sound too good i'm afraid & I am of little help either as I too am new to Android ROM flashing - but rather, as a help to others, can you state what type & version of recovery you are using (ClockWorkMod / amon_ra), what Nexus you have (AMOLED / SLCD), whether you have the phone connected over USB when backing up / restoring, android version backed up, what charge level you had etc.
I believe all of these elements can affect your results in one way or another.
e.g, I believe for SLCD, you require amon_ra v1.8.0.1 & some people have reported issues if performing the operations while connected to USB.
Good luck & let us know how you get on.
Steve.
thanks, i ended up just reflashing the rom because restore kept freezing. I remember usb was not plugged in during backup, it may have been during the first restore, i dont recall, but it was definitely not plugged in the second time. Im just glad no serious damage was done though, i guess i just wont do nandroid anymore ill stick with the rom manager backup method. Im using clockwork recovery
AndroidPerson said:
thanks, i ended up just reflashing the rom because restore kept freezing. I remember usb was not plugged in during backup, it may have been during the first restore, i dont recall, but it was definitely not plugged in the second time. Im just glad no serious damage was done though, i guess i just wont do nandroid anymore ill stick with the rom manager backup method. Im using clockwork recovery
Click to expand...
Click to collapse
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
cmstlist said:
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
Click to expand...
Click to collapse
thanks im going to remember this, the more things i have to try when something goes bad, the better
cmstlist said:
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
Click to expand...
Click to collapse
I've run into a similar hangup before running Clockwork, and fixed it pretty much the same way you did. I've since gone back to Amon's recovery, as its nandroid functions seem to be more reliable.
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
In safe strap did you ever change to 'safe system' before you started wiping?
/Droid3
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Shwaguy said:
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Click to expand...
Click to collapse
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
beard0 said:
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
Click to expand...
Click to collapse
Non safe is the stock. Safe is the one you're flashing.
Sent from my XT862 using xda premium
Thanks beard0, I have not seen a sbf file for the 860 Bell. Found a system dump but thanks to the fbi it is unavailable.
Another problem popped up unfortunately. I lost connectivity. I just have wifi now. Last month when I got the phone I entered the apn info from the Telus website and everything was fine. Now when I try it I get a message saying that "mmc field must be 3 digits" I thought that info was grabbed from the sim? Regardless, I added the rest of the info required, saved, but it doesn't save the info?? I tried apn manager and it had Telus listed, selected that but still no luck. After much searching I just did the factory reset, added apn info and still have no connectivity.
I have spent so many hours on these problems and really don't know where to go from here. Going to root/safestrap etc now.
Out of curiosity I tried turning on simlock. It says no simcard detected. It worked fine for over a month and still works in my backflip though. I think the gf has a simcard in her phone so I am going to see if it reads hers when she gets here.
Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
Maybe dumb question..
After rthe steps did you Flashed the actual ROM????
Just askbecause i dont see it. Mentioned
Also, If you disable safe systemthen youshould be able to go back to regular stock.....
Enviado desde mi XT862 usando Tapatalk
Ya, I flashed the rom, tried the alpha 6 ics one also. It was after doing this then rebooting (still in safe) that i got the bootloop issue. I disabled safe system and went back.
Seems it doesn't really matter now though. It doesn't seem to be reading my simcard. No service (except wifi), Tried enabling simlock, says there is no card in it. Card works in my Backflip. I tried the g/f's Bell card and still no service, etc. Going to search around a bit and see if anything pops up but I may be sending it back. lol
Here's the story:
I bought an AT&T HTC One that had an unlocked bootloader and was rooted. I SIM-unlocked it so I could use T-Mobile. Everything worked perfectly fine.
Today I decided I wanted to try out AR HD. I use CWM to flash it, and have a few problems the first few times because of Aroma Installer. Eventually it installs fully, but when I rebooted, something went wrong. It wouldn't boot up. Eventually I had to wipe everything (including the internal storage, which had a backup of mine), and now I'm trying to flash a working rom on this phone.
So now I've tried pretty much everything. The main problem now is that in recovery, when I try to flash a ROM it says it can't mount the the sdcard. I've tried using Nocturnal's method of using the stock recovery to wipe the partitions and everything, but it still gives the the can't mount error.
If anyone could help me I would really appreciate it! Looks like I'm going to have to get a SIM adapter to use with my Galaxy Nexus until I can get this fixed.
aka757 said:
Here's the story:
I bought an AT&T HTC One that had an unlocked bootloader and was rooted. I SIM-unlocked it so I could use T-Mobile. Everything worked perfectly fine.
Today I decided I wanted to try out AR HD. I use CWM to flash it, and have a few problems the first few times because of Aroma Installer. Eventually it installs fully, but when I rebooted, something went wrong. It wouldn't boot up. Eventually I had to wipe everything (including the internal storage, which had a backup of mine), and now I'm trying to flash a working rom on this phone.
So now I've tried pretty much everything. The main problem now is that in recovery, when I try to flash a ROM it says it can't mount the the sdcard. I've tried using Nocturnal's method of using the stock recovery to wipe the partitions and everything, but it still gives the the can't mount error.
If anyone could help me I would really appreciate it! Looks like I'm going to have to get a SIM adapter to use with my Galaxy Nexus until I can get this fixed.
Click to expand...
Click to collapse
Download the All-In-One toolkit from the development section and follow the directions to ADB SIDELOAD a ROM onto your phone.
EDIT: now with a link to the thread: http://forum.xda-developers.com/showthread.php?t=2183942&highlight=all-in-one
Well, I got it to flash a ROM, but now there's a new problem...
I got it to flash the ROM by using CWM to flash a ROM after using Nocturnal's method instead of TWRP.
So now I'm in setup, and am prompted to select a WiFi network. I selected my network, put in the password correctly (it shows connected), and now when I press Next, it transitions forward and then straight back to the WiFi page. Won't let me progress past it.
I think it might have something to do with HTC Sync Manager (I have it installed and running just fine), but I don't know what to do about it.
aka757 said:
Well, I got it to flash a ROM, but now there's a new problem...
I got it to flash the ROM by using CWM to flash a ROM after using Nocturnal's method instead of TWRP.
So now I'm in setup, and am prompted to select a WiFi network. I selected my network, put in the password correctly (it shows connected), and now when I press Next, it transitions forward and then straight back to the WiFi page. Won't let me progress past it.
I think it might have something to do with HTC Sync Manager (I have it installed and running just fine), but I don't know what to do about it.
Click to expand...
Click to collapse
You can skip the wifi setup. Try changing the channel on the router sometimes phones and routers on certain channels don't get along.
I am having a hard time recovering from my curiosity with my XT1060, Developer's Edition (unlocked bootloader and all)
I had factory 5.1 ROM, xposed and all tweaked. But it's been months, phone's getting slow, and I'm itchy for MM...
So last night, I made a TWRP/nandroid backup onto my USB-OTG stuck, and then, installed Resurrection-Remix-M.
Works fine, until I tried to make a call. I can't hang up. After 30 seconds, the phone rebooted.
I had another guy call me. The phone rings, but the screen is blank. I cannot pick up the call. WTF? I tried turning screen back on, screen's blank. After a couple attempts to swipe blindly, power button, the phone rebooted.
At this point, I'm like WTF, that's enough. So I tried to plug in the USB-OTG and tried to restore.
TWRP does NOT see my backup. At this point, I realized that perhaps TWRP can't see the item due to MM's security structure.
So I engaged the RR's CM explorer and copy the Nandroid backup onto the built-in 32 GB . THere should be enough room.
I looked back X minutes later, the phone had rebooted itself (?!!) and it's stuck at the bootloader logo (I had replaced it with generic "White Google" logo)
I cursed a bit more, did the VOL-DOWN / POWER to bring up the Fastboot menu, and boot into recovery. I got the Team Win logo, then nothing. I waited 5 minutes. It's stuck too.
At this time, I'm cursing a blue streak. My phone has been dead for HOURS now, no end in sight.
I went back into Fastboot, did Factory (which I assume is "Factory Reset?") no effect. Still freezes both normal boot and recovery boot.
I boot back into Fastboot mode, I already have Minimal ADB and Fastboot loaded on PC, so I use that to flash the a new recovery.IMG (downloaded fresh off TWRP.ME for ghost) and rebooted. STILL FROZEN at TWRP. WTF?!?!?!
(FWIW, Ghost TWRP is still 2.8.7.0, while TWRP main is already at 3.0.2)
At this time I'm at a loss as on what to do.... I tried extracting one of the factory ROM's boot.img and flashed that via fastboot, nothing.
I just RSDLite the 292-ghost_verizon_51.... ROM onto the phone (with servicefile option). It rebooted to the bootloader warning, so flash did work, but it doesn't seem continue to boot either, but I guess I was supposed to have waited like 10 minutes just to get past the bootloader? I flashed the TWRP on there. Still waiting for TWRP to load. After a couple minutes, I decided it wasn't working.
I'm now using RSDLite with the Flashfile option (wipe out all the data). Wonder if this will do it?
EDIT: Now I'm past the bootloader logo and now it's kinda stuck on the Verizon logo, but I guess that's to be expected. Still charging... and waiting.
EDIT2: Verizon logo took about 5 minutes to boot into setup. I just hit skip / skip / skip until I got to launcher. Shut down, reboot into fastboot, flashed recovery again, and booted TWRP recovery successfully this time. (sigh)
Lessons to take away from this diversion that took HOURS away from my life... For no appreciable gain.
* Keep a flashable nandroid backup on the phone. I know it takes up GB's of space. But you'll be thanking yourself (and maybe me) when there's a problem and you need to recover, especially if you're into MM or N.
* And keep that nandroid backup UPDATED! (nightly, if possible)
* ALWAYS keep a copy of the stock ROM on your regular PC, and keep Minimal ADB/Fastboot (or whichever flavor recommended for your device) and Gapps loaded. Do update every once in a while.
* ALWAYS refer to XDA
ive used the xda tool for k50 to root and flash touch recovery, taken a backup and flashed xposed. there was no chance to recover after bootloop cause for whatever reason, it wasnt saved.. even rom flash wont work in recovery and a backup ive found is to big to load with bad connection (google storage has no resume feature). as the phone staid in this state some hours, it surprisingly fixed itself, coming up with stock but system updates arent working. no problem until yet. but now the settings app closes instantly without a message - any ideas?