After finishing a clean install of JB and restoring my apps, all was working perfectly on my Maxx. I have used TiBu Pro for a couple years, but I've never used its encryption feature. Now that I'm on JB, I thought it might be worth a try, so I enabled it, then rebooted into recovery, then ran a fresh nandroid backup. It completed correctly, but when it rebooted afterward I got an error message that the encryption failed and I needed to do another factory reset to be able to use my phone again.
While that's certainly a crap deal, I wasn't too upset since I'd (literally) just finished a new nandroid, so I figured I'd do the reset, restore the nandroid, then disable encryption again and be on my way. No dice.
When I hit the button to start the reset, it just reboots back to the same error every time. If I boot into the on-board recovery panel (the one with the white letters) and try to go into recovery mode from there, it only boots into the dead Android robot with the "!".
I looked at TiBu's website and tried contacting TiBu, but have found no useful information yet. Has anyone else experienced this? Got any ideas on how to recovery this thing or break out of the cycle I'm stuck in?
Thanks!
***UPDATE***
Here are some more details to see if anyone else can help me work through this. I can only get to two possible reboot states at the moment. The first (when attempting a normal startup) boots through the initial boot image, then the first part of the boot animation. I see the red eye for a few seconds, then I get:
Encryption Unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
Click to expand...
Click to collapse
Then there's a button that says "Reset phone" at the bottom (this is what makes me think the TiBu encryption is the culprit). If I hit that button, it just reboots to the same error every time.
The second reboot state is if I power down the phone completely, then boot into recovery by holding the Up/Down volume buttons and Power button for about 3 seconds. I get a black background with white text that says:
Boot Mode Selection Menu (0A.77)
Vol Up Selects, Vol down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Root AP
BP Tools
Click to expand...
Click to collapse
If I try "Normal Powerup" I circle back to the first reboot state. If I try "Recovery" then it goes to the picture of the Android robot keeled over with a red "!" in his chest and I have to manually reboot it again.
I'm thinking that I might need to go to the "BP SBF Flash" mode and try to SBF back to the .211 file that's still on my sdcard, but it's just a guess (and, admittedly, the only other option I can think of that's even available at this point).
Anyone have any thoughts?
***UPDATE #2***
By pressing both the volume up/down buttons at the dead Android robot, I've now accessed the recovery menu I'm used to seeing (when doing nandroid backups) that lets me perform the factory reset. Unfortunately, doing the factory reset doesn't change anything, and I still boot up to the encryption unsuccessful message.
Not Titanium's fault
This is a side effect of Android's encryption, not Titanium Backup's; Titanium's encryption should only be visible when restoring backups from Titanium itself.
Workaround guide thread here: http://forum.xda-developers.com/showthread.php?t=1447303
Android's page on phone encryption: http://support.google.com/android/bin/answer.py?hl=en&answer=1663755
Related
I had installed TNT Lite v 4.3.0 a couple of weeks ago and it was working pretty good. But today my tablet has gone into a bad state. Every app that I run results in FC. Even the ADW launcher EX that I had selected default is crashing. It then gives me the options: ADW Laucher, ADW Launcher EX, and the regular Launcher. The plain ADW Launcher also fails, but fortunately the regular Launcher still works so I can access the apps.
But unfortunately almost every app that I am trying fails. The only one that doesn't fail is the Web browser. The Settings starts and I can access Applications menu but once I choose say System Applications, after that if I try to choose some other option such as Installed Application, it crashes as well.
Last night however when I started the tablet the battery was probably down and while it was powering it up, it turned off and then restarted by itself and then turned off, without reaching the lock screen. I don't know if it has something to do with all this.
What do I do now? Any help will be appreciated.
Thanks.
A well known issue.
http://forum.xda-developers.com/showthread.php?t=896395
This is why I'm an advocate of people doing the partitioning right before they flash their first custom rom. This way, they won't have to wipe everything later on.
I could only wonder why people aren't mentioning this in every custom rom thread.
Thank you so much. Will try it out tonight.
Unfortunately it seems I have run into a worse issue (without even doing anything yet). Now when I power it on, it starts and shuts off within a few seconds, just shows the birds for like 5 secs and bang, black screen.
The tablet is fully charged (if I put it on charge the light turns green in no time). Looks like the battery is dead.
You might be dropping into APX mode. Do you know how to use nvflash?
Thanks for the reply. You are absolutely right. After multiple tries it did boot up and I was able to install clockworkmod and it all worked great. It wiped off everything but I could live with that. And I turned it off and back on and it was working fine.
But then it went back into the same mode - shutting off immediately after turning on. I decided to return this tablet thinking that it is bad. But before I would do that I thought to restore it or else Viewsonic won't honor the warranty. So I started reading the thread about restoring the tablet to stock using nvram flash. In that procedure it requires me to put the tablet in APX mode and that's when I thought that maybe it is going into APX without pressing the volume - button.
Anyway I was successfully able to flash nvram. Or so it said. I still have the output from the batch file. But now my tablet is totally bricked. It does not boot at all. No pretty birds for me.
I hope there is some way out of it. Please help.
Edit: After re-flashing and using a different file, it seems to have made it a little better. At least I am seeing the birds again. But the original problem of shutting off, or going into the APX mode without pressing Volume button, has returned. All I am getting is the birds for a few seconds and then black screen. I will continue to retry, and if I see it booting up successfully to the stock, this thing is going back to the factory.
1) What image did you use to nvflash?
2) What happened when the flash was finished? Did it boot normally at least once?
3) Does the screen just stay dark all the time now?
1) First time nvflash_gtablet_46_2010112600.zip and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Later I flashed nvflash_gtablet_2010110500.zip. This at least recovered it enough that it shows the birds, but soon after the screen turns black. I have confirmed that it is going in APX mode. If I have USB cable connected to my PC, the PC reports discovering the NVIDEA APX device.
2) It hasn't booted normally since I flashed nvram.
3) No I get the birds, but after that it turns dark.
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Thanks for your response. I tried it. Did not work. When you say Replace part9.img with the recovery.img, does it mean copy recovery.img into the NVFlash directory and rename it to part9.img or leave it as recevery.img. I renamed it to part9.img and backed up the original part9.img to part9.img.tmp. The size of recovery.img and the original part9.img are very different. I am confused. Please help.
K J Rad said:
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Click to expand...
Click to collapse
Yes, that is exactly what I meant.
Are you sure you're holding the volume UP key? Birds and then black screen is APX mode which is normally entered by holding volume DOWN.
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Any ideas?
I was thinking about formatting the gtablet. Please let me know if this is the right move, or there is something else I could try first.
shah123 said:
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Click to expand...
Click to collapse
A little more than "It did not work" would be helpful.
What step failed? Please tell me what happened after each step.
Did you get into CWM and repartition?
Did you get everything cleared?
What happened when it rebooted?
What was the original filename of the image you tried to flash?
What version of clockworkmod do you have installed?
Have you ever used ROM Manager?
All of this is important and no one can help you if you don't provide enough information.
Oh, I am sorry. Here are the answers to the questions you asked:
What step failed? Please tell me what happened after each step.
Ans: Out of the 7 steps you provided, the steps 1, 2 and 3 worked fine. It is the step 4 that failed (and of course I can't proceed with the steps anymore). In other words I cannot go into clockworkmod recovery.
Did you get into CWM and repartition?
Ans: No I was not able to do so. If I press power and Volume Up key at the same time, nothing happens, screen remains black, not even birds come up.
Did you get everything cleared?
Ans: I believe you are referring to step 6. No, I could not get to that step.
What happened when it rebooted?
Ans: Nothing showed up. Because when Volume Up is pressed while it is powered on, nothing shows up on the screen.
What was the original filename of the image you tried to flash?
Ans: Actually first time nvflash_gtablet_46_2010112600.zip (and this is before you provided the 7-step recipe - see post #6, 7, 8 of this thread) and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Maybe that was my mistake. I chose a wrong file. Later I flashed nvflash_gtablet_2010110500.zip. This recovered it enough that it shows the birds now, but soon after the screen turns black (goes into APX mode).
What version of clockworkmod do you have installed?
Ans: v08
Have you ever used ROM Manager?
Ans: No. What is it?
I really appreciate your help.
What happened at the end of step 3?
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 seconds after the flash starts.
When the flash was done did it say "Recovery Key detected" on the screen? If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
It sounds to me like you did the nvflash then tried to reboot into recovery.
Its unbelievable. Tonight when I powered it on it started booting up normal instead of going into the APX mode. I was glad. The stock UI came up, but some of my apps like Quadrant, File Expert etc were still there. It also notified me of the Update 3588. So I downloaded it and started installing it. Pretty soon it rebooted itself (sooner than I thought - I don't know if the remaining installation was supposed to happen after the reboot).
But instead of booting up into 3588 it is unfortunately gone back to the same old issue - the birds followed by black screen - aka APX mode. It never booted up after that. No matter how many times I tried to reboot, it goes into APX mode just like before. I don't know what caused it to complete bootup. One thing I noticed was that the battery was totally drained when I started tonight. I don't know if the drained battery somehow took it out of the APX mode. But now it has a little bit of charge because of hooking up to power supply. I have disconnected the power supply and will leave it in APX mode over night and try it again tomorrow when the battery would be totally drained and see if it boots up fully.
To answer your questions though:
What happened at the end of step 3?
The screen went black and after that it stayed black. No CWM.
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Yes, I did.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 secondsafter the flash starts.
Yes, I continued to hold it all the way until the flash completed and the screen went black and quite some time after that.
When the flash was done did it say "Recovery Key detected" on the screen?
I don't think it did.
If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
So I guess I need to give it another try. Tomorrow I will try to reboot the tablet again and if it continued to go into APX I will do the nvflash one more time.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
A black dark screen. No CWM or stock recovery.
It sounds to me like you did the nvflash then tried to reboot into recovery.
No at the time of nvflash I held the Volume UP button and nothing happened. Since then I have been trying to bootup or put it in CWM Recovery but only thing the tablet wants to do is go into APX mode.
So I guess my theory of "drained battery takes it out of the APX mode" is correct. I tried to reboot the tablet several times but it just kept on going into the APX mode until the battery was completely drained. And then it started booting up normally but it went into some installation (probably the stock 3588 that I had downloaded in the previous successful bootup). And then the green android with the exclamation sign came and the exclamation sign was rotating for a second or two and then stopped. And it looked like it was hung. I waited for a minute or two but nothing happened, so I pressed one of the buttons, I don't know if it was Menu or Back button, and all of a sudden clockworkmod recovery screen came up.
I have attached the picture of the screen. It still shows the green android with the exclamation sign in the middle of the screen, along with the CWM Recovery.
One other thing I noticed and I am not sure if it is normal is that if I choose say Reboot System Now from CWM menu and it shows like 10 entries with many No's and only one Yes. I can only use the volume Up + button to go down, if I try to go up using volume Down - button it does not go up. Is that normal? Is the only way to go is go down using Voume Up button in CWM menus? I have a feeling that my Volume Down button has gone crazy and it is not functioning properly and that is what is causing it to go into APX mode at the startup as well.
Anyway I first attempted "Apply SDCARD:update.zip" hoping that it might continue with the stock 3588 installation, but that failed. You can see the messages in the picture. Then I tried the Factory Reset and it was successful. I then rebooted the tablet. But now again it keeps on going up into APX mode. I will have to wait until tomorrow for it to completely drain battery again and then try to reboot again.
Any ideas? I know it is overwhelming and the behavior is very weird. At this point I am trying to bring it back to the stock firmware so that I can get this tablet replaced under warranty.
There are quite a few things that are not acting normal from what I see here.
Did you try to repartition 2048 and 0? If not, I would start with that then I would format everything and re-nvflash a stock ROM onto it. That might clear things up. If not you could be looking at a hardware reset.
Hey guys, I have a Star A2000 with Froyo rooted. While I was trying to modify my original status bar, the phone blocked and I had to reboot it. I rebooted it but for over one hour it's loading whithout booting into the homescreen. I tryed with the factory reset but nothing. I can't load any rom from Linux, and so I can't fully on the device. Any suggestion? I want to bring back everything! Anybody knows how I can do so? Without the flashing cable is it possible to restore or put back the original system and settings?
recovery menu
Turn off the phone
press vol up and power button in the same time
that will bring you to the recovery menu - press home key to see options
navigate trough options with vol up and down and meniu
take care - reset to factory my wipe your imei off. if you are lucky this might not happen
also read here:http://forum.xda-developers.com/wiki/index.php?title=Chinese_Clones_MTK6516
I've tried this way all the time but it seems to don't work
Is there not an update.zip in other to install the original rom? Because I'm not with the flashing cable so I can't use it to flash. Is there any other way I can do it?
If you cant access the recovery by using power button + volume up key at the same time when turning on the phone then the recovery partition is not working (should show up with android ! screen or custom recovery) - If you cant boot in to the recovery menu or the system partition containing the OS you have likely bricked your phone, the only chance you may have in my opinion is a factory reset - which you say has failed or connect usb while phone is booting and hope you can get an ADB connection (which is possible due to a bug but only seems to work intermittantly - I have managed to fix a brick via this stroke of luck before)
Having a backup as well as a working recovery or system partition is the key to playing with your phone - one partition should always be working to restore the other when or if it fails.
[email protected] said:
If you cant access the recovery by using power button + volume up key at the same time when turning on the phone then the recovery partition is not working (should show up with android ! screen or custom recovery) - If you cant boot in to the recovery menu or the system partition containing the OS you have likely bricked your phone, the only chance you may have in my opinion is a factory reset - which you say has failed or connect usb while phone is booting and hope you can get an ADB connection (which is possible due to a bug but only seems to work intermittantly - I have managed to fix a brick via this stroke of luck before)
Having a backup as well as a working recovery or system partition is the key to playing with your phone - one partition should always be working to restore the other when or if it fails.
Click to expand...
Click to collapse
HI !
I´m on the same situation.
After install de CW recovery, made 3 nandroid backups of different states of my phone and tryed to flash 3 different ROM MODs (including the ICS 4, hahaha) i bricked my A2000-GPS.
I´m able to enter CW recovery menu using PWR+VOL.UP and navigate as well. I wiped all data, cache partition and try to restore all my backups one by one... Nothing brings back my OS... I still stucked into boot screen (the first one, i´m not entering in the boot_logo image...
After many tryes, i wiped all data again and made a factory reset using CW recory: Nothing...
I notice that i´m loose the factory recovery mode (PWR + VOL.Down)... And i also never made an IMEI backup. Could be that?
I apreciate any help. Any light in the end of tunel, hahaha
Kind regards!
------------------------------
Updating:
- I´m using the ClockworkMod Recovery V4.0.0.5.
- My CWM recovery is able to read my SD card, so i can put any .img or .zip file inside it.
I format the folders:
/boot
/cache
/data
/system
Into "Mounts ans Storage" menu.
After I recovery one of my nandroid backups. Normal rebooting and.........................
NOTHING ! I´m still stucked into first boot img.
It´s normal this screen delays like 15 ~ 20min. to disapear?
Hi.
related with CWM I also have a weird issue.
My wife's old A2000 is now in my hands to play with it. The phone was virgin (stock rom no rooted).
I rooted the phone and installed cwm/rom manager.
The weird issue is:
1) If I click in Rom Manager option " Reboot into CWM" the phone reboot in CWM with all options working including rom backup.
2) starting with th phone off I press the keys power + vol.up Iget not the CWM but the "fatory Mode" green menu with 6 options (Full test, Test Report, Clear flash, version and Reboot).
3) pressing power + vol.down it simply boot normay the system.
What can be wrong with this "ex-virgin" A2000?
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
If I'm not mistaken, you would need to un-root your phone prior to installing any OTA Updates from AT&T. Also, you should only install the OTA Updates while using the stock recovery. So, you should re-flash the stock recovery and then attempt to complete the OTA Update. After that, you could re-install TeamWin, re-root and prosper.
Refer to this link on reverting back to stock... http://forum.xda-developers.com/showthread.php?t=2721435
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
an0ther said:
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
Click to expand...
Click to collapse
Just downloaded titanium back up. How do I freeze the update?
howyodoing said:
Just downloaded titanium back up. How do I freeze the update?
Click to expand...
Click to collapse
Try searching next time.. I see you are new here so i'll at least give you a link this time
http://forum.xda-developers.com/showthread.php?t=2752718
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
Click to expand...
Click to collapse
Good rule of thumb, do not install OTA updates on any modded Android device, without at a minimum doing thorough research on what will happen.
Depending on the device and the update in question, attempt to install an OTA on a modded device will remove root, possibly plug existing exploits (and render the phone unable to be rooted), or put you in a boot loop (as you have experienced).
In particular, OTAs require stock recovery in order to install. So if you have custom recovery installed, this is why the OTA install is failing (and why it keeps booting into TWRP).
Also, there is little (if anything) contained in the OTAs that doesn't get posted in a safe format (flashed from custom recovery) in the Development section soon after the OTAs start to roll out.
Solution for HTC OneM8 (continous restarting after update)
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Hi, i have a HTC One M8, and when my first update popped, i was very enthuziast.
I accepted to download the update, installed it, and... the problem appeared. The phone made his restart after update... and continued to do so over and over again. (Vibrate/HTC screen on for 30 secs/screen off and so on)
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button. The phone will enter in the Bootloader menu where you have some options. But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off. It gave me a hardtime to do that... Finnally, i managed to enter the Bootloader menu.
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
sergiu.dragan25 said:
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button.
Click to expand...
Click to collapse
This is not correct. To force a reboot, you hold power and vol up (not both vol buttons). Then, when its restarting (the moment the screen goes dark and before the white boot screen appears) you let go of both those buttons, and only hold vol down.
sergiu.dragan25 said:
But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off.
Click to expand...
Click to collapse
In the case of a bootloop (phone keeps restarting), all you need to do is hold vol down during one of the reboot cycles. The timing doesn't matter in this case. Just sit on the vol down button until the bootloader screen appears.
sergiu.dragan25 said:
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
Click to expand...
Click to collapse
First, the FASTBOOT selection in bootloader is not the same as "Fast boot" in Settings>Power. The latter just makes the phone start faster from power OFF. The former is an adb (Android Debug Bridge) special mode that allows you to flash partitions from a computer.
Second, in bootloader, you should have the following selections:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Of course, its the FACTORY RESET option you want if you want to wipe the phone. Scroll down to (using vol keys) and select with power button.
On the bootloader screen, the active selection is the blue box with white text below the green phone info (hboot number, radio number, etc.). FASTBOOT should only be the default "active" selection if your phone is connected to a computer by USB. Otherwise the default selection in bootloader should be HBOOT.
Third, the "Fast boot" option in Settings>Power does not make a restart "faster" by skipping any steps. It just makes a start from power OFF faster. Its kind of a trick, where power OFF is not really off, but just a deeper sleep mode. A restart is always a restart, regardless of whether "Fast boot" is selected or not in Settings>Power.
Apologies if some of the other threads answer this, but, I was concerned that they were device specific and I would appreciate reassurance that a solution is correct for my phone before doing anything else.
Oh boy, I think I am in deep doo-doos!
The plan was to install a custom ROM on my Samsung Galaxy S4 (GT-I9505).
So, I rooted the phone and installed TWRP.
I downloaded the latest nightly ROM from CyanogenMod, as well as the Gapps and copied them to the micro-SD card
I got into TWRP Recovery and did a full backup of all data to the micro-SD card.
Having done this I thought I had done enough to protect me from catastrophe (wrong!)
Still in TWRP I did a Factory Reset/Clear Data
I did an Install of the CM 12.1 ROM
I did an install of the Gapps
All seemed fine, with no errors showing up
Then I did a reboot and this is where it all went pear-shaped!
The Setup wizard started and the first indication of a problem was numerous messages like "Unfortunately Gmail service has stopped"
This happened for all sorts of apps - Gmail, Google+, Youtube, GooglePlay, etc.
Anyway, I plugged away with Setup and it connected to wi-fi and then I got the EULA screen. When I ticked boxes and clicked "next" the screen went blank and after a few seconds it said "Unforyunately, the setup wizard has stopped"
Argh!!!!
I thought that all was not lost as I could get back into TWRP and try again or, failing that, restore the backup.
However, I cannot get into Recovery mode/TWRP - If I hold down the Vol+, Home and power buttons then I see a few lines of very small colourful text in top-left, but, when I release buttons, the phone starts up Android rather than Recovery
I have tried starting by holding Vol+ and power and the same thing happens
I have tried starting by holding Vol- and power - this comes up with a warning about using a custom OS and gives an option to cancel or continue.
If I choose continue then I set a message "Downloading.... Do not turn off target!!" and then it sits there for ages (at least an hour)
Can anyone suggest what I can do to rescue my phone?
The ideal outcome would be to be able to restore the backup I made
If this is not possible then I would like to get it back to a useable state.
Any help would be most gratefully received!
First, enter the download mode by pressing vol-, homekey, and power key at the same time. Then tap the vol.+ button.
Then download the stock rom for your phone along with correct model number.
The downloaded romshould be in .zip format. So extract it on your pc. You must see a file of .tar.md5 or .md5 format. Now while in the download mode, connect your phone to pc Use odin to flash that file.the restart you phone.hope this helps..i dont take any responsibility if you further damage your phone....
Sent from my GT-I9500 using XDA Free mobile app
MysteryMan1 said:
Apologies if some of the other threads answer this, but, I was concerned that they were device specific and I would appreciate reassurance that a solution is correct for my phone before doing anything else.
Oh boy, I think I am in deep doo-doos!
The plan was to install a custom ROM on my Samsung Galaxy S4 (GT-I9505).
So, I rooted the phone and installed TWRP.
I downloaded the latest nightly ROM from CyanogenMod, as well as the Gapps and copied them to the micro-SD card
I got into TWRP Recovery and did a full backup of all data to the micro-SD card.
Having done this I thought I had done enough to protect me from catastrophe (wrong!)
Still in TWRP I did a Factory Reset/Clear Data
I did an Install of the CM 12.1 ROM
I did an install of the Gapps
All seemed fine, with no errors showing up
Then I did a reboot and this is where it all went pear-shaped!
The Setup wizard started and the first indication of a problem was numerous messages like "Unfortunately Gmail service has stopped"
This happened for all sorts of apps - Gmail, Google+, Youtube, GooglePlay, etc.
Anyway, I plugged away with Setup and it connected to wi-fi and then I got the EULA screen. When I ticked boxes and clicked "next" the screen went blank and after a few seconds it said "Unforyunately, the setup wizard has stopped"
Argh!!!!
I thought that all was not lost as I could get back into TWRP and try again or, failing that, restore the backup.
However, I cannot get into Recovery mode/TWRP - If I hold down the Vol+, Home and power buttons then I see a few lines of very small colourful text in top-left, but, when I release buttons, the phone starts up Android rather than Recovery
I have tried starting by holding Vol+ and power and the same thing happens
I have tried starting by holding Vol- and power - this comes up with a warning about using a custom OS and gives an option to cancel or continue.
If I choose continue then I set a message "Downloading.... Do not turn off target!!" and then it sits there for ages (at least an hour)
Can anyone suggest what I can do to rescue my phone?
The ideal outcome would be to be able to restore the backup I made
If this is not possible then I would like to get it back to a useable state.
Any help would be most gratefully received!
Click to expand...
Click to collapse
One of the spot you went wrong was not formating system and data instead of a factory reset.
Also make sure to have the proper gapps package for the rom you are using.
The instructions above will get you squared again.
Also next time try posting in the forum for the device. You have a far better chance of getting answers from people that have a better chance of working.
Try SAMmobile.com (you will have to make a free account) when you have made your account click the firmware button at the top of the screen then type in your phone model number. For example SM-G361F the choose your country. Then in the filter box seach your network provider ie. O2 then click download. Once you have downloaded it extract the file to a folder. Boot your phone into odin/download mode.then open odin 3.09 or any other similar tool. (You can download odin anywhere) extract the odin file then open it. Once opened Click BL or AP it dosent really matter then choose your file and wait for the blue bar on your phone to finish. Then it should restart
And should be stock rom. If your brick your device please note you have full responsibilty over your device. If you do mess up and brick your device just repeat the steps above.
I have the H933 variant of the V30. I want to wipe the partition cache after the Oreo update. I have tried the Pwr + down arrow. And then release power button and hold again at the boot screen. The only option I have is to factory reset the phone. I don't get the normal recovery options. Any help would be appreciated.
ern88 said:
I have the H933 variant of the V30. I want to wipe the partition cache after the Oreo update. I have tried the Pwr + down arrow. And then release power button and hold again at the boot screen. The only option I have is to factory reset the phone. I don't get the normal recovery options. Any help would be appreciated.
Click to expand...
Click to collapse
When I reboot into recovery, I am given the same choice on my US998. I choose factory reset, then I choose factory reset again. After all that, I get a screen that shows the "unlocked device" message for a moment and then finally TWRP.
I have had a situation where TWRP was NOT installed and when I did this my phone was completely erased...
Since then I have installed Quick Reboot Pro (free!) from the Google Play store. If your phone is rooted it gives you an option to boot into recovery. It goes straight to recovery and doesn't need any of the other (risky in my opinion) steps
ern88 said:
I have the H933 variant of the V30. I want to wipe the partition cache after the Oreo update. I have tried the Pwr + down arrow. And then release power button and hold again at the boot screen. The only option I have is to factory reset the phone. I don't get the normal recovery options. Any help would be appreciated.
Click to expand...
Click to collapse
Turn Off Your device.
Now Press and Hold Volume Down+Power button for 2-3 Seconds Until LG Logo Appears.
Release the volume down Button (hold power) Press and Hold them Again.
Hold the Buttons until the Recovery Mode Screen Appears.
Now You Are in the Recovery mode of Your device.
i succeeded only when gave up and approved Factory Reset then it finally switched to Recovery mode. Took 1 hour to find out, not a single guide on the internet or here was correct. I wonder if the reset really happened? Is reset prerequisite to run recovery mode?
doggydog2 said:
i succeeded only when gave up and approved Factory Reset then it finally switched to Recovery mode. Took 1 hour to find out, not a single guide on the internet or here was correct. I wonder if the reset really happened? Is reset prerequisite to run recovery mode?
Click to expand...
Click to collapse
Not if you are rooted. If the WTF guide I tell people to install a reboot recovery app that will take them straight to recovery.
doggydog2 said:
i succeeded only when gave up and approved Factory Reset then it finally switched to Recovery mode. Took 1 hour to find out, not a single guide on the internet or here was correct. I wonder if the reset really happened? Is reset prerequisite to run recovery mode?
Click to expand...
Click to collapse
worst case you could always use fastboot...
if your phone has twrp recovery, then it won't reset the phone. if you are running stock it will.
Agree with chazz though, assuming you have root and a bootable rom - reboot recovery is the best option
I never did really figure out why the lg phones can't boot directly into recovery using the buttons
If you install a terminal app, you can also get into recovery that way - "su" and then "reboot recovery".
I posted this on yt
I just realized magisk has the option to reboot to recovery. I've only used super su in the past.
well of course we have tons of apps, and recovery choice in power menu. but the boot shortcuts is the concern. those really suck.. can't even memorize them. need to write it down on the back of the phone
+1 here for confusion. I uninstalled Magisk after it strangely stopped working during the night and also could only to fastboot. After googling I also did the button dance to reset and yes then yes then got to twrp.
Nothing lost but strange way to go on (rooted device)
Actually, as I thought I had reset everything I updated to 21a so wasn't an entirely wasted 30 mins or so