Related
Hi all,
Issue with TWRP and restore. I've got a backup, but when I tried to restore it, it would crash and reboot while restoring the /data partition. I try wiping the /data partition (I have my backup on a server, too) and it crashes midway through that, too. Just reboots and returns to TWRP.
What should I do?
Thanks,
Ben
Wipe cache, dalvik cache, fix permissions, then restore.
Sent from my EVO using xda app-developers app
freshlysqueezed said:
Wipe cache, dalvik cache, fix permissions, then restore.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Tried that, no luck
I'm currently restoring the factory 4.2.2, then installing TWRP and adb'ing the files back over to try restoring again. Hopefully this works.
Thanks,
Ben
Fmstrat said:
Tried that, no luck
I'm currently restoring the factory 4.2.2, then installing TWRP and adb'ing the files back over to try restoring again. Hopefully this works.
Thanks,
Ben
Click to expand...
Click to collapse
This issue is mentioned over in the official TWRP forum under "Original Android Development" The Dev acknowledged it, saying he needs to fiddle with it... Might not be bad if you poked your head in there with any other information you could add...
*fingers crossed* Hope they get it patched up soon... I'm a little restore shy now. Up until I encountered this, I was swapping ROMs on a nearly daily basis... No anymore.
I started over again, like you, and it works ok now. But I don't know when/if the problem will rear its ugly head again, so holding off until I hear more.
DefinityX said:
This issue is mentioned over in the official TWRP forum under "Original Android Development" The Dev acknowledged it, saying he needs to fiddle with it... Might not be bad if you poked your head in there with any other information you could add...
*fingers crossed* Hope they get it patched up soon... I'm a little restore shy now. Up until I encountered this, I was swapping ROMs on a nearly daily basis... No anymore.
I started over again, like you, and it works ok now. But I don't know when/if the problem will rear its ugly head again, so holding off until I hear more.
Click to expand...
Click to collapse
I'm having the same problem with 2.5.5.0. Happens probably 30% of the time and always during the data restore. It completes on the second go-round, but I'm constantly holding my breath. I was under the impression that this was taken care of in this latest version.
Sent from my Nexus 10 using Tapatalk HD
mine crashes when I do simple wipes
on latest
happens about 30% of the time too
I had that happen a lot, I just 2.3.3.0 now and it is perfect.
http://techerrata.com/browse/twrp2/manta
Rom Toolbox app will let you install it too.
stonebear said:
I had that happen a lot, I just 2.3.3.0 now and it is perfect.
http://techerrata.com/browse/twrp2/manta
Rom Toolbox app will let you install it too.
Click to expand...
Click to collapse
Oh, good, I'll do that. Thanks.
Edit (5 min. later): Wow, that was easy, lol. Thanks again.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Oh, good, I'll do that. Thanks.
Edit (5 min. later): Wow, that was easy, lol. Thanks again.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Enjoy a recovery you can have faith in, lol.
stonebear said:
Enjoy a recovery you can have faith in, lol.
Click to expand...
Click to collapse
Ain't it the truth.
So I just tried doing the same with my phone and the installation failed, something about illegal instruction. I'm running CM 10.1 on an unlocked, S-OFF HTC Vivid.
Any ideas?
Sent from my Vivid 4G using Tapatalk 2
bruce7373 said:
Ain't it the truth.
So I just tried doing the same with my phone and the installation failed, something about illegal instruction. I'm running CM 10.1 on an unlocked, S-OFF HTC Vivid.
Any ideas?
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
Are you using Rom toolbox? If not, you aren't trying to flash the manta version are you?
Sent from my Nexus 10 using Tapatalk HD
stonebear said:
Are you using Rom toolbox? If not, you aren't trying to flash the manta version are you?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
No, I tried with RomToolbox, same method as with the N10. I choose 2.3.3 0 from the list, so I assume it was the Holiday version. The first time I tried, it claimed I didn't have permission, but I think that was because it was the first time I was using Rom toolbox since flashing CM so the permission popup came after the fact. I rebooted and that was when the message changed to invalid instruction.
Edit: Tried again with 2.4.1.0. Same result. But I located the files and they are holiday, so I can just flash with fastboot, I guess.
Sent from my Vivid 4G using Tapatalk 2
bruce7373 said:
Edit: Tried again with 2.4.1.0. Same result. But I located the files and they are holiday, so I can just flash with fastboot, I guess.
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
Yea that should work. Must be a Rom toolbox problem, I would think.
Sent from my Nexus 10 using Tapatalk HD
My N10 is rooted but with a stock ROM. Earlier on it said that there was an update (4.3) and it downloaded it, re booted and then came up with an error saying 'no command' while displaying the small pic of the Android. It sat there for 10 mins and then eventually booted back into the OS. When I checked the version, it was back to 4.2.2.
Now when I check for an update, it says that there's no update available.
What do I do?
Sent from my Nexus 10 using Tapatalk 4 Beta
Are you on stock recovery? Barring that, clear Google Framework data and try again maybe?
Sent from my MB855 using xda app-developers app
That message is okay. Nothing is wrong with your tablet, other than the fact that the update didn't take. Do as the above poster said, or manually install the OTA.
Sent from my Nexus 4 using xda premium
Homey said:
My N10 is rooted but with a stock ROM. Earlier on it said that there was an update (4.3) and it downloaded it, re booted and then came up with an error saying 'no command' while displaying the small pic of the Android. It sat there for 10 mins and then eventually booted back into the OS. When I checked the version, it was back to 4.2.2.
Now when I check for an update, it says that there's no update available.
What do I do?
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Why not try to check again for the OTA? No worries dude... That's not an unusual thing to happen . Also you can try doing what the other two said ,)
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Thanks guys. I cleared Google Framework Data and the download started again and failed again. This time, all it said was "error"!
I really don't want to zero the tablet again and lose all my data by doing the update manually. Is there any way to avoid that?
Also is there anything great about 4.3 that makes the update worth doing?
Sent from my Nexus 10 using Tapatalk 4 Beta
Homey said:
Thanks guys. I cleared Google Framework Data and the download started again and failed again. This time, all it said was "error"!
I really don't want to zero the tablet again and lose all my data by doing the update manually. Is there any way to avoid that?
Also is there anything great about 4.3 that makes the update worth doing?
Sent from my Nexus 10 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Its probably because your tablet is rooted. Try unrooting and then doing the update.
bortak said:
Its probably because your tablet is rooted. Try unrooting and then doing the update.
Click to expand...
Click to collapse
Yeah, I thought that was it too so I unrooted and tried again. It's still the same.
I really don't want to do a factory reset and manually update the bloody thing - I'll lose all my stuff!
Called Google support and sent them pictures of the Android screen (they asked for them!) and apparently they're investigating...
Yeah maybe you just need to wait a little more so you won't be like me. I just bricked mine today trying to do a factory reset .
Sent from my SGH-M919 using xda premium
Same problem
I have the same problem. Await Googles response..............
Same problem !!
Homey said:
Yeah, I thought that was it too so I unrooted and tried again. It's still the same.
I really don't want to do a factory reset and manually update the bloody thing - I'll lose all my stuff!
Called Google support and sent them pictures of the Android screen (they asked for them!) and apparently they're investigating...
Click to expand...
Click to collapse
You can manually update without performing a factory reset by just pushing boot and system, although you need to know what can go wrong before you try.
Same issue, rooted and custom recovery.
But if they are investigation, maybe I won't remove the custom recovery, too much work.
I got the 'error' screen too. pressed power and volume and it told me that build.prop failed the file check, pulled an fresh copy out of the old factory image, copied it to my n10 and tried the OTA again. All went ok, now on 4.3
Same error!!
Already did a factory reset and still have the error
Same problem here. Rooted on stock. Keep going to Recovery, then errors when trying to apply the 'untrusted' update, as it states.
Same problem here....rooted with stock recovery, tried three times clearing the data from Google framework but no luck so far...
Sent from my Nexus 10 using xda premium
Same here too
Unlocked boot loader
Rooted
Stock ROM
Stock recovery
Sent from my Nexus 10 using Tapatalk HD
Do you happen to have stickmount installed?
http://forum.xda-developers.com/showthread.php?t=2380620
I have this problem too, now trying to find the original file and try again.
Anyone know where can get that file for nexus 10?
boolim said:
Do you happen to have stickmount installed?
http://forum.xda-developers.com/showthread.php?t=2380620
I have this problem too, now trying to find the original file and try again.
Anyone know where can get that file for nexus 10?
Click to expand...
Click to collapse
I need that too. :crying:
For those with unlocked bootloader who want to update:
https://dl.google.com/dl/android/aosp/mantaray-jwr66v-factory-888d124e.tgz
This is the stock Android 4.3 from Google! If you know how to flash just do it .
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hey guys not affiliated in anyway but jcase in the development thread got root working for att and Verizon through a simple apk on the phone.. Tested and working great hit up his thread more info
Sent from my XT1058 using Tapatalk 4
So does root stick around after a reboot? The moto root app showed I wasn't rooted after a reboot. Just came back from iOS so I'm a little rusty
Let me double check.. Havent rebooted since the app rebooted the phone
Sent from my XT1058 using Tapatalk 4
OK just rebooted and root stuck just fine
Sent from my XT1058 using Tapatalk 4
Its not there immediately takes 5 or so seconds after boot to work.. Jcase is aware of the issue though and working on it..
The only downside with that is something like setcpu not being able to set on boot
Sent from my XT1058 using Tapatalk 4
rcklss1 said:
Its not there immediately takes 5 or so seconds after boot to work.. Jcase is aware of the issue though and working on it..
The only downside with that is something like setcpu not being able to set on boot
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Also effecting the exposed software since if you do a reboot instead of a soft reboot it kills part of the process
With this root method can you use the exposed mods to remove the ATT icon from top left of status bar? Or does that require a flashable zip?
Sent from my Nexus 7
phositadc said:
With this root method can you use the exposed mods to remove the ATT icon from top left of status bar? Or does that require a flashable zip?
Sent from my Nexus 7
Click to expand...
Click to collapse
Check out the motoexposed thread in the android dev section :good:
just being back from IOS, i may hold out on pursuing this till things get ironed out. I installed 1.1 and installed the chainfire su and rebooted to find the andriod on his back with a red exclamation point. Not sure what this meant but rebooted and all is fine so I've restored to factory till future times of solid dev. I donated to jcase so i'll be back once i'm versed in android again.
What in particular was the android pic i saw referencing?
Thanks guys! Good to be back! still getting used to things as you can see
mj0528 said:
just being back from IOS, i may hold out on pursuing this till things get ironed out. I installed 1.1 and installed the chainfire su and rebooted to find the andriod on his back with a red exclamation point. Not sure what this meant but rebooted and all is fine so I've restored to factory till future times of solid dev. I donated to jcase so i'll be back once i'm versed in android again.
What in particular was the android pic i saw referencing?
Thanks guys! Good to be back! still getting used to things as you can see
Click to expand...
Click to collapse
Sounds you like you tried rebooting to CMW or TW recovery. I clicked it to see what would happen and that's what I got. Rebooted normally after that and no issues.
rmead01 said:
Sounds you like you tried rebooting to CMW or TW recovery. I clicked it to see what would happen and that's what I got. Rebooted normally after that and no issues.
Click to expand...
Click to collapse
Good to know I wasn't on the verge of breaking my new moto
Thanks!
hi
ill been searching for weeks on the internet and here and i cannot find an answer to what is really causing the boot loop problem when i connect the charger or disconnect the charger.
to get the phone to work again i have to do the twist fix to get it to boot but as soon i connect the charger it restart it self and bootloop i have to twist again to boot, then when i disconnect the charger the same thing.
my question is do anyone ever find out what is causing this or where on the motherboard lies the problem?im assuming is probably close to the charging port. anyone have an idea where exactly the problem is?sorry if this been answered before but honestly i did not find it.
i know is an old phone but i like it is a good backup phone.thanks for taking the time to read this...
anyone?
What recovery do you have.
What rom are you running.
What is your emmc chip.
N_otori0us_ said:
What recovery do you have.
What rom are you running.
What is your emmc chip.
Click to expand...
Click to collapse
thanks for answering well im not 100% what recovery version is on i factory reset the phone then rooted unlock with gfree and if i remember well i use rom manager to install the recovery.
the rom im running now is Android_Revolution_HD-Glacier_7.0.4
and my emmc chip is SEM04G
Switch roms. Try out cyanogen 7 nightly.
If it still bootloops there then its a hardware issue
Sent from my HTC Glacier using Tapatalk now Free
N_otori0us_ said:
Switch roms. Try out cyanogen 7 nightly.
If it still bootloops there then its a hardware issue
Sent from my HTC Glacier using Tapatalk now Free
Click to expand...
Click to collapse
ill give that a try and report back thanks for your help.
N_otori0us_ said:
Switch roms. Try out cyanogen 7 nightly.
If it still bootloops there then its a hardware issue
Sent from my HTC Glacier using Tapatalk now Free
Click to expand...
Click to collapse
well i did install cm7 nightly the latest and still when i connect the charger it reboot and bootloops i still have to do the twist fix to boot completly
i guess is hardware problem and im assuming is around the charging port because with the twist fix thats where most of the pressure is put on.
anyone knows exactly where it is so i can do a permanent fix and not twisting the phone every time to boot, i know it works now but for how long before something get damage inside by doing this.any help will be appreciated or i might have to give up on this phone.
i know for sure the emmc chip is fine because a few days ago i flash stock rom successfully. . thanks everyone
Ive never actually heard of that problem but it might be a loose flax cable that signals something and causes it to bootloop.
Do a logcat and then.show us the output.
Also instead of saying thanks press the thanks button.
Sent from my HTC Glacier using Tapatalk now Free
I've been reading through other threads here on XDA about a common boot loop issue that N900T users are experiencing, but nowhere was it mentioned that the Canadian variant users had a similar problem, but I do.
I was wondering if there were any other SM-N90028 users out there that were stuck in a boot loop?
Here is my situation:
I have a Canadian SM-N900W8 (it is, also a Qualcomm LTE version) and I'm in a boot loop... it all started when I tried to restore a Stock-Rooted Rom with TWRP.
I can't, however get it out, and I've tried all of the versions of TWRP, I've also used odin like 30 times... nothing.
I successfully restored a Rooted stock ROM through TWRP, but it wasn't until I re-installed a factory un-rooted one that things got ugly..
So I was thinking about this and perhaps the cause of this is KNOX... since the first thing I did when I rooted my phone initially was uninstall KNOX and all of its files. I know these didn't carry over when I did a TWRP backup, which is perhaps why my restore of that backup worked the first time. The second time, I just went and downloaded everything stock and used Odin, and that's when the bootloop occurred.
if anyone knows of a way to solve this, I'd be forever grateful!
I really hope I will be able to fix this...
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
force70 said:
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thank you, but I've read them all and most are regarding the n900t, I felt it appropriate to ask about the n900w8 variant.
Also, I know that would have been better, but it's too late for that now. I just thought I'd share my experiences here with this issue so that others will know better.
So I tried a different stock ROM, and with the latest version of Odin, but it still is in a boot loop.
However there is one difference; this time it will boot past the Samsung logo and into android, but then a window will pop up saying "Process system isn't responding" and ask me to wait for it to respond or close it. Regardless of what I select, it will end up rebooting seconds later.
In the very short time that everything stays booted for, I can access the two pull-down menus from the top, but selecting anything will yield me no results.
Perhaps this can tell us more about this issue?
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
force70 said:
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
c_est_la_vie said:
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
Click to expand...
Click to collapse
Check post #350 in this thread and read forward. http://forum.xda-developers.com/showthread.php?t=2467001&page=46
this worked!
Hey guys, I'm not sure if anyone's checked this out yet, but I managed to get myself out of the boot loop!
here is the solution:
http://forum.xda-developers.com/showthread.php?t=2471421
Glad your back up and running!
Sent from my SM-N900W8 using xda premium
Thanks!
Sent from my Nexus 7 using XDA Premium 4 mobile app