have an LG 290 with CWM installed 6.0.1.9 installed
When trying to reboot from either power on (with or without pressing the volume keys) or from the recovery menu, the phone boots into the CWR menu. It never boots to the OS. I have flashed with OptimusRS JellyCream Rom v2_p920 using CWR's install from internal SD card. I wiped the cache and dalvik, but It still keeps rebooting to the CWR menu.
Any suggestions on how to boot into the OS would be appreciated.
bran1 said:
have an LG 290 with CWM installed 6.0.1.9 installed
When trying to reboot from either power on (with or without pressing the volume keys) or from the recovery menu, the phone boots into the CWR menu. It never boots to the OS. I have flashed with OptimusRS JellyCream Rom v2_p920 using CWR's install from internal SD card. I wiped the cache and dalvik, but It still keeps rebooting to the CWR menu.
Any suggestions on how to boot into the OS would be appreciated.
Click to expand...
Click to collapse
So from my past experiences, and from what I can tell, you're suffering from an issue I suffered from before.
I'd recommend immediately swapping to a new baseband for safety issues, and ROM support, and then working from there.
From what I understand though! You went to flash a ROM that wasn't completely supported for the baseband you're using, and this causes the following, or can cause the following errors.
-1. Phone will boot into OS, but no signal - FIX: WAP Points need to be fixed for your Carrier.(Can be found by an easy Google Search)
-2. Phone will boot up, but has a constant Boot Loop meaning the phone just keeps resetting itself, and never opens the actual OS, a few issues can cause this, either an improper ROM install, or the ROM IS NOT supported for the current device.
bran1 said:
have an LG 290 with CWM installed 6.0.1.9 installed
When trying to reboot from either power on (with or without pressing the volume keys) or from the recovery menu, the phone boots into the CWR menu. It never boots to the OS. I have flashed with OptimusRS JellyCream Rom v2_p920 using CWR's install from internal SD card. I wiped the cache and dalvik, but It still keeps rebooting to the CWR menu.
Any suggestions on how to boot into the OS would be appreciated.
Click to expand...
Click to collapse
I had same issue just reinstall bootloader
Related
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.
Downlods mode
Then flash new firmware
sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!
Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app
Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!
For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse
I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.
I had katkiss 4.3 running on my pad and tried to update to ktkiss 4.4 and it came up with error . Then when I rebooted it hung in start up screen. So I rebooted into twrp recovery and reinstalled the backup I had made before I started . all seemed to go ok until I rebooted now all I get is
First the asus startup screen comes on then the twrp screen comes up but I get no menu its on a couple of seconds then goes blank I then get the following come up in bottom corner.
Verifying file system
Verifying partition size
Formatting/ data
wiping data without wiping /Data/media
Formatting cache
It then keeps repeating this again in a loop. I have tried to use easy flasher but because it keeps restarting it will not recognise the drivers on my pc. Can anybody help or have I bricked it
With thanks
Mickr
Easyflasher uses APX mode, did you make sure the TF was in APX mode first ? (Volume Up & Power)
If it is rebooting even in APX mode, sounds like a more serious hardware error
*Detection* said:
Easyflasher uses APX mode, did you make sure the TF was in APX mode first ? (Volume Up & Power)
If it is rebooting even in APX mode, sounds like a more serious hardware error
Click to expand...
Click to collapse
I have managed to reinstall twrp recovery and now want install the katkiss rom , do I have install the standard asus rom first and then reroot it before I can install the katkiss rom
with thanks
No, just flash any custom ROM you like from TWRP, forget about stock ROMs now
Just make sure you wipe everything first if your coming from Stock, then flash ROM & Gapps, then wipe Cache & Dalvik Cache, then reboot
*Detection* said:
No, just flash any custom ROM you like from TWRP, forget about stock ROMs now
Just make sure you wipe everything first if your coming from Stock, then flash ROM & Gapps, then wipe Cache & Dalvik Cache, then reboot
Click to expand...
Click to collapse
Thanks for that now up and running
Mickr
Good stuff
Here are the particulars.
rooted
Display JZO54K
Fingerprint = motorola/tervigon/wingray:4.1.2/JZO54K/.....
Loaded elementalx - xoom- v1.3 three months ago ran fine. Stupidly, I did not flash a backup. Now after deleting cache, factory reset, stuck in "loading apps" after splash, the boot loops back to motorola screen where I can launch CWM v4.0.0.4 - I want to get a ROM on there and continue using this mission-critical dinosaur. Can someone help?
I guess the real question is can a rom be copied onto the ext-sd card via windows out of the xoom? If so will CWM see it and will it work?
Have not tried connecting and using ADB. Not feeling confident enough at this point. ext SD still has data but when in CWM device does not show up in Windows.
TIA for any help
Geoff
sasquatchgeoff said:
Here are the particulars.
rooted
Display JZO54K
Fingerprint = motorola/tervigon/wingray:4.1.2/JZO54K/.....
Loaded elementalx - xoom- v1.3 three months ago ran fine. Stupidly, I did not flash a backup. Now after deleting cache, factory reset, stuck in "loading apps" after splash, the boot loops back to motorola screen where I can launch CWM v4.0.0.4 - I want to get a ROM on there and continue using this mission-critical dinosaur. Can someone help?
I guess the real question is can a rom be copied onto the ext-sd card via windows out of the xoom? If so will CWM see it and will it work?
Have not tried connecting and using ADB. Not feeling confident enough at this point. ext SD still has data but when in CWM device does not show up in Windows.
TIA for any help
Geoff
Click to expand...
Click to collapse
I pushed a stock rooted rom via ADB (I found the internal sdcard is accessible via the ADB shell) . The stock rom showed up in the CWM select zip file list. Installed the rom and the xoom animation freezes then continues the boot loop - regardless of rom installed. Cleaned system cache and davik cache as well after factory wipe. I am beginning to think hardware issues. No amount of cajoling will get this thing to boot into its OS. Either memory or processor - when it worked, I did have it running incredicontrol and 1.4 ghz and the max memory limitation upped to 64MB in order to run a lecture player for school.
So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!
One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.
Are you getting any errors while wiping partitions
sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.
Hi,
Yesterday i was trying to switch from lineage os to the last version of resurrection remix, so I downloaded the file on RR's website, and did a nandroid back up on my OPO (i'm rooted with TWRP installed) including system, data and boot partitions.
I did a full wipe (system, cache, dalvik cache and data), then I flashed the RR's zip file, gapps, and restored only the data partition. When I boot on RR there's a black screen showing an error message "System UI has stopped working" and another "com.android.phone has stopped". So I just long pressed my power button, restart -> recovery, and restored the boot partition from my nandroid back up. Then when I try to boot I'm stucked in a bootloop and I can't go back to recovery since my volume buttons are broken (broke the flex cable when repairing my screen).
Now I think there are 2 solutions, either changing volume buttons (which means desoldering and soldering :/ ) or there is a solution with adb.
If you have any solutions, thank you in advance !
Had the same issue with the same processes and I just had to factory reset from recovery to fix it. Now the real issue are the volume buttons now, because if you didn't enable adb and gave permissions to your PC you can't use it.
Ok so i managed to replace the volume flex cable, but now i have another problem : after i failed to flash RR, i did a factory reset and tried to restore a nandroid back up (that i made just before i repaired the volume butttons) and now the phone won't boot and keeps booting on twrp... That is REALLY frustrating, please help !
croustiman27 said:
Ok so i managed to replace the volume flex cable, but now i have another problem : after i failed to flash RR, i did a factory reset and tried to restore a nandroid back up (that i made just before i repaired the volume butttons) and now the phone won't boot and keeps booting on twrp... That is REALLY frustrating, please help !
Click to expand...
Click to collapse
Try dirty flashing the ROM zip, data won't be touched and boot/system will be re-flashed. Hope it works.
I can flash roms : i flashed lineage os, tugapower... etc
For example yesterday, i pushed the latest lineage os zip file (via adb push) and flashed it. TWRP says installation is sucessful then when I reboot, its still TWRP... I went on several forums, and flashed a stock oneplus recovery. Now my phone is stuck on a bootloop with oneplus logo only, and I can't access the recovery or fastboot mode even pressing the volume keys I'm afraid I have to buy another phone...
Also i noticed that when i try to reboot with the phone being connected to the computer via USB, the phone just shuts down and i have to disconnect and reconnect the battery ribbon inside the phone so it can reboot
Up !