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 !
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 am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
UsoftTech :: WwW.UsoftTech.CoM ::
TWRP asking for password
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
TWRP asking for password
Click to expand...
Click to collapse
I now fear that i maybe without both a rom and all my files such as my music that was stored on my phone.
Is there any way for me to undo the damage i may have done to to my phone?
You can't recover the data. But you can push files over with ADB.
Sent from my Nexus 7 using Tapatalk
JoJostar said:
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
Wrong thread.
d
Click to expand...
Click to collapse
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
Hi,
I'm trying to bring my N5 to life. It has bootloop on Google logo (sometimes stuck on android animation). When i got it it was stock and unrooted. Computer can see the device, adb and flashtool works fine. What i tried to do:
- erase cache and userdata,
- factory reset
- change recovery to TWRP (tried CWM too, both works)
- flashing the factory images (all from 4.4 to 6.0.1)
- flashing factory image using this tool: http://forum.xda-developers.com/goo...kit-v2-2-kwonggers-nexus-5-one-t2508817/page5
- fix persist partition using this solution: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 -when I'm doing this, adb see my device and after using these commands I got only something like: clean, 15/1024 files, 1109/4096 blocks, it is not asking my about repair or change anything...
Unfortunately, it still has got bootloop. I can't go into recovery when I'm using usb cable, I can start it only without cable and then plug it in. (When it is on and I'm trying to turn on recovery mode it has bootloop on Google logo).
Have you got any ideas what can I do now? Is there a way to fix it?
Try this: manually flash every partition from the stock ROM, including the userdata.img.
After flashing the userdata.img file, immediately boot into stock recovery using the power and volume buttons and perform a factory wipe.
Hey, thank you for your answer. Unfortunately after flashing every partition and factory wipe it still has bootloop. But before i did it, it wanted to charge my Nexus, I just plug USB and suddenly I realised that there is a Welcome screen! Everything was running good, WiFi was working... I turned on USB debugging and reboot it to check what happens, but it won't turn on again, now it is again with bootloop Any other ideas?
Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.