Related
I rooted my HTC Desire CDMA from USCC okay, flashed a Froyo ROM with USCC stuff, and everything was okay. I made a nandroid backup, flashed CyanogenMod 7 RC4 and it seem to work okay, except I was having trouble entering my password when checking voice mail. Anyway, I decided to go back to Froyo. I used ROM Manager to restore the backup and got into ClockworkMod. However, none of the options work. If I go down to recovery, I go to the next screen, but no matter which option I select I end up with a black screen and nothing happens! I can't restore my backup! If I just try to press power on, I end up with the blue CyanogenMod screen and the arrow just goes round and round. Nothing happens. Please, if anyone has any suggestions, it would be greatly appreciated.
I remember hearing that because CM7 is a Gingerbread mod, it must use ClockworkMod v3 and to go back to your Froyo backup you'll need to downgrade to Clockwork Recovery 2.x. I'm not sure if things has changed, though, this was what I read a month or two ago.
Are you by any chance able to fastboot?
Reflash your CWM (if you are using NAND version) or get it again on your SD (if your are using SD version).
The problem is I can't do anything in ClockworkMod (version 2.5). Every option I select gives me a blank screen! I made a nandroid backup before flashing CyanogenMod, but I have no way of getting to my backup if I can't use ClockworkMod. Also, if I try to boot the phone, i just get the CyanogenMod 7 startup screen with the arrow going round and round. It will still be there 30 minutes later. I have to do a battery pull to start over with anything.
I was able to boot my phone after wiping all user data. I would like to use my nandroid backup to return to the previous ROM, but clockworkmod doesn't seem to work. I tried reflashing it in ROM manager and it only downloads a second or so and isn't really doing anything. I'm wondering if clockworkmod is defective. Is there any other way to flash it again without using ROM Manager?
If you are able to fastboot, you could try to restore a nandroid by flashing three files (boot.img, system.img, data.img) from your nandroid backup using:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
Disclaimer: I've not actually tried this procedure before! I got this info from here
You could use a similar procedure to flash a new ClockworkMod since your recovery may be corrupted: fastboot flash recovery recovery-clockwork-3.0.0.5-vision.img
You can download the image from Koush's website, under HTC G2.
This happened to me yesterday trying out the Alpha Build for the Fascinate. I was getting a dev block error and datadata would not mount. I had to go back to stock on heimdall. I don't know if this helps for your phone, but maybe somone with more knowledge can tell you if this may be happing to you and what the fix is, if that's not a fix for you.
I have a desire S, Which is S-Off through revoltionary and rooted! But i don't have a nandroid backup and my phone will no longer boot up. what can i do? I've tried to do a factory reset in recovery mode but that doesnt work.
How can i flash a stock rom on it to get it back to normal, i think its bricked... can someone help me?
1st of all i suggest you download a custom rom from the development section here.
then flash that via recovery. then hopefully your phone will load up into the new rom.
after you confirm this to me i will help you further to get back to stock rom
Thanks for the reply.
I did what you said, i tried to install a custom rom in recovery but it ends up aborting after a while, i dont think i can get any rom to work now, its not looking good
Fingers crossed
See this thread
Attempt the commands that are shown within the first #1 of it and you should be able to determine whether or not you have a fried eMMC chip.
See links in my signature for adb & fastboot drivers and the thread you need to see.
What recovery are you using? and what rom are you trying to flash?
I suggest downloading this rom http://forum.xda-developers.com/showthread.php?t=1048203
Once you have done this follow these steps below to the letter
1. Boot into recovery
2. Format System (not wipe option but format option !!!)
3. Format Data
4. Format Cache
5. Wipe Data/Factory reset (1st option in wipe/format menu)
6. Wipe Dalvik Cache
7. Now install zip from sd card and flash the rom
8. Reboot
It was the Saga LBC mod that i was trying to install but it didn't work, nothing works that i try. i've formatted my sd card nom. basicly ive screwed everything up i've got no back ups of any rom and i cant get anything working
pumpernickel77 said:
It was the Aage LBC mod that i was trying to install but it didn't work, nothing works that i try. i've formatted my sd card nom. basicly ive screwed everything up i've got no back ups of any rom and i cant get anything working
Click to expand...
Click to collapse
can you give me a step by step explanation of what you are doing and what messages/error messages you are getting at each stage?
I will try to help you the best i can. But i need to try to understand what the main issue is 1st. Don't worry just yet!
pumpernickel77 said:
It was the Saga LBC mod that i was trying to install but it didn't work, nothing works that i try. i've formatted my sd card nom. basicly ive screwed everything up i've got no back ups of any rom and i cant get anything working
Click to expand...
Click to collapse
You need to give specifics and preferably screen pictures....(if possible) did you try the commands from the thread that I posted above, or what happens when you attempted the commands layed out by Eclipse_Driod above?
The more you tell us, the more we have to work with!?
I'm sorry but I dont know how to do the command thing, i'm a newbie when it comed to that I've basicly got a desire s that wont boot up and a SD card with nothing on, i think i need to somehow put a recovery image on my phone before i can install a rom
Is there any way i can install a recovery image to the sd card from the pc, that will then allow me to install a rom?
pumpernickel77 said:
I'm sorry but I dont know how to do the command thing, i'm a neebie when it comed to that I've basicly got a desire s that wont boot up and a SD card with nothing on, i think i need to somehow put a recovery image on my phone before i can install a rom
Click to expand...
Click to collapse
I believe that you already have a fully working recovery on your device, otherwise you wouldn't have been able to flash LBC ROM in the first place....so I suspect that the problem is else where....(possibly damaged eMMC chip) but unless you help us, by running the commands and testing this we are un-able to confirm this for you.
You can find the adb and fastboot commands as a link in my signature simply download and then put these on you PC and run the commands that were in the thread I posted earlier (thats also in my sig Fried eMMC?)
Although I also believe that if you're able to get to S-OFF then you're able to enter the commands from your PC that will enable you to flash a recovery onto your device.
See this post where I've previously instructed some one else how to do just this.
Any questions then just and try to take screen captures or cut 'n' pastes of all errors encountered.
Good luck
pumpernickel77 said:
I'm sorry but I dont know how to do the command thing, i'm a neebie when it comed to that I've basicly got a desire s that wont boot up and a SD card with nothing on, i think i need to somehow put a recovery image on my phone before i can install a rom
Click to expand...
Click to collapse
does it not even boot into recovery?
you need to hold down the volume down button and keep it held down while you power on the device. This will make it boot into recovery mode.
But before you can do that i would advise you take the sd card out of the phone, connect it to your computer with a card reader and copy over the lbc mod rom.zip file straight onto the card, then put it back into the phone.
then turn the phone off and boot into recover as mentioned above and select install rom from sd card and select the zip file you transferred over.
after it has installed reboot phone by selecting the "reboot" option in the recovery mode.
all should now be well.
report back how this goes
and don't forget to hit that thanks button
Thanks for your patience.. I'm going to try and explain in full what i've done
I got S-off on my Desire S using "Revoluntionary" (after watching how to do it on YouTube) and after domwloading ClockWorkMod from market place I sucessfully installed Saga LBC ver 5.3. Everything was fine i was very pleased. I had a back up of the old stock ROM saved on my SD card which i did through Clockworkmod too.
Then this morning I got a update message from clockworkmod saying ver6.0 was available to download so i did. My phone never turned back on again I could get into recovery mode but nothing would work (wipe data, factory reset, Even tryin to install the old backed up rom didn;t work) it just kept freezing.
So i took my sd card out and plugged it into the pc to try to look for anothr rom to try out, thats when i ended up formattig the SD card (god knows why) So now ive got no backup, no clockworkmod, no nothing on my SD card...Am I screwed??
Thanks for your patience.. I'm going to try and explain in full what i've done
I got S-off on my Desire S using "Revoluntionary" (after watching how to do it on YouTube) and after domwloading ClockWorkMod from market place I sucessfully installed Saga LBC ver 5.3. Everything was fine i was very pleased. I had a back up of the old stock ROM saved on my SD card which i did through Clockworkmod too.
Then this morning I got a update message from clockworkmod saying ver6.0 was available to download so i did. My phone never turned back on again I could get into recovery mode but nothing would work (wipe data, factory reset, Even tryin to install the old backed up rom didn;t work) it just kept freezing.
So i took my sd card out and plugged it into the pc to try to look for anothr rom to try out, thats when i ended up formattig the SD card (god knows why) So now ive got no backup, no clockworkmod, no nothing on my SD card...Am I screwed??
from what you have told me u still have clockwordmod recovery as it is on the phone itself. not the sd card. So you are ok there. What i need you to do next it to see if you are able to boot into recovery?
if you can then try again to format data, system and cache.
then try installing a rom from your sd card.
if it is still freezing while trying to perform a format then look back at bens previous posts about using adb through your pc to find out if your emmc chip is damaged
I can boot into recovery no probs there, but when i format data, system and cache it goes so far and then aborts
Ive just tried to install the LBC rom again i renames it PG88IMG ind it asked me to install so i did. It says 'update in progress' and the bar on the right starts to fill up but it stops near the top and eventually aborts
right, the only thing i can think of to try next is following the same method you said you followed to s-off through revolutionary.
it will say you are already s-off or something but click proceed anyway. and make sure from there that you type "y" when it asks if you want it to install clockworkmod recovery. as this will reinstall a fresh recovery image for you.
this is the only thing i can think of.
let me know how it goes
did you look at my post#11 above...
The second half of it contains instructions on how you can flash a new recovery image......from your PC.
Ive just tried to do the s-off again the way i did before but i can only go as far as the part when i connect my phone and open the revolutionary programme and it doesn't detect my phone
Ok, it looks like the last option to try is flashing a new recovery image manually.
For this you will need to download and install adb. which can be found here
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
along with instructions of how to set it up and use it.
after you have done this you will need to download this
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-saga.img
which is the latest clockworkmod recovery for your phone. and rename it to recovery.img
then copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Power your device off and reboot it in fastboot mode. (holding volume down whilst pressing power on button) then select "fastboot" from the list of options you get.
Connect your device to your computer via USB and wait till you see ‘fastboot USB’ on the screen.
Launch Command Prompt and type the following command:
fastboot flash recovery c:\recovery.img
Wait for the process to finish and reboot your device once it’s done.
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
When I attempt to go to Cofface's Baidu page to download his 5.1 TWRP version, I get a message saying the content is no longer available. Specifically, Google Translate shows "Lol, you visit the page does not exist." Does anyone happen to have a copy they're willing to share? Or is there some issue with the 5.1 version that would suggest that I shouldn't use it? If I shouldn't ask for some reason, I apologize. Otherwise, thanks in advance.
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/TWRP
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
wpennhokie said:
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
Click to expand...
Click to collapse
Did you unlock your bootloader?
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
wpennhokie said:
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
Click to expand...
Click to collapse
Thats the same problem I have. I used the other twrp recovery https://mega.nz/#!l5kmUByA!41uExNuasZRgLBML9TTSp8myX-_F6UgQZuE2F2BRZUE
This one worked with out boot loops for me. you can give it a shot.
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
I had that exact same problem twice on Kangvip B015. When I would restart it would all of a sudden automatically boot into TWRP every time and never boot into the OS. When that happens, in TWRP make a backup, then Fastboot flash the stock ROM (system, boot, cust, recovery, user data etc) then when it boots do a factory data reset, then reroot, flash TWRP and restore from the backup you made. The OS will boot from your backup. I dunno why this happens, maybe it has something to do with with Kernel.
I've tried it a couple of times now, and I'm still not getting it to boot past TWRP once I flash the recovery. It was able to take a backup with TWRP, but when I restored it, I still had to restore the stock recovery before I could boot into the system. At worst, at this point, I can always flash TWRP, take a backup, flash the stock recovery, and then have my system back. It's a few extra steps, but I think I'll do this until I find a custom ROM that I like. I greatly appreciate the help so far.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
Reflash the stock b106 recovery and wipe user data and cache, Then reflash twrp recovery and restore your backup. It should boot then.
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
wpennhokie said:
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
Click to expand...
Click to collapse
By any chance, did you delete anything from the Cust Folder at any point?
ajsmsg78 said:
By any chance, did you delete anything from the Cust Folder at any point?
Click to expand...
Click to collapse
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
wpennhokie said:
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
Click to expand...
Click to collapse
I don't think so. It's weird how some of us have different problems than others. I've had zero issues with TWRP but lately my screen has been going crazy. My touches don't work, things jump it's like my digitizer is messed up but when I restart everything is fine again. So I reloaded everything and the problem went away. I guess I debloated too much last time.