Hi.
I hope that I can get solution.
These are what I did:
1. I used CyanogenMod13 and I flashed GApps. After I booted it, I unrooted my phone and I removed busybox.
2. After that, I updated my phone to recently builds.
3. But after 09/09 build, I didn't updated it. So I just tried to update 10.01 build today.
4. I thought TWRP would be more better to control, so I flashed it on my phone and I flashed new cm update by TWRP.
5. After I flashed it, I formatted Dalvik(ART) Cache and Cache. (I didn't do it sometimes but i remember that it didn't make any problem.)
6. I got my phone keep bootanimaion forever so I flashed 09/09 build.
7. But it didn't works, so I flashed CyanogenMod13 recovery image and I flashed CyanogenMod13 10/01 build by CyanogenMod recovery.
8. Now it doesn't works (it keeps bootanimation), so I'm here to ask you.
I don't wanna lose my all DATA which involves my app data.
Thanks for reading.
minami_kotori said:
Hi.
I hope that I can get solution.
These are what I did:
1. I used CyanogenMod13 and I flashed GApps. After I booted it, I unrooted my phone and I removed busybox.
2. After that, I updated my phone to recently builds.
3. But after 09/09 build, I didn't updated it. So I just tried to update 10.01 build today.
4. I thought TWRP would be more better to control, so I flashed it on my phone and I flashed new cm update by TWRP.
5. After I flashed it, I formatted Dalvik(ART) Cache and Cache. (I didn't do it sometimes but i remember that it didn't make any problem.)
6. I got my phone keep bootanimaion forever so I flashed 09/09 build.
7. But it didn't works, so I flashed CyanogenMod13 recovery image and I flashed CyanogenMod13 10/01 build by CyanogenMod recovery.
8. Now it doesn't works (it keeps bootanimation), so I'm here to ask you.
I don't wanna lose my all DATA which involves my app data.
Thanks for reading.
Click to expand...
Click to collapse
Install TWRP and make a backup of your Data, Boot, System partitions
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
Install TWRP and make a backup of your Data, Boot, System partitions
Sent from my GT-S7580 using Tapatalk
Click to expand...
Click to collapse
Is that a only way to boot up my phone..?
minami_kotori said:
Is that a only way to boot up my phone..?
Click to expand...
Click to collapse
Yes, because it's required to clean flash CM 13 without losing data (because you can now do a clean flash when you have a backup)
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
Yes, because it's required to clean flash CM 13 without losing data (because you can now do a clean flash when you have a backup)
Sent from my GT-S7580 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying. I'm gonna do that.
Related
I first installed CM 10 nightly, didn't really like it, so I thought about restoring my old backup and going back to stock ROM, but, when I booted the phone, the logo came up then it rebooted.
Then I flashed Xperia Ultimate HD 2.0.3, Installation went fine, but the logo stayed for like 5 seconds then it went into a black screen, kinda abit blue'er than black.
The LED light went light blue.
What should I do now?
Thanks.
Fixed!
Finally, I managed to fix it.
I did this:
Locked bootloader: http://forum.xda-developers.com/showthread.php?t=1134335
Unroot with Flashtool.
Flashed boot.img from CM10.
Flashed 562 Android build. (or something :s)
And then the phone booted up. :laugh:
After/Before restoring your Backup, did you flash the right kernel for the software version?
Sent from my Nexus 7 running Android 4.2.1
mihahn said:
After/Before restoring your Backup, did you flash the right kernel for the software version?
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I bet he didnt
mihahn said:
After/Before restoring your Backup, did you flash the right kernel for the software version?
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I forgot. xD
Anyways the ROM I flashed is better than the stock ROM.
Thanks anyways.
Sadra.. said:
I forgot. xD
Anyways the ROM I flashed is better than the stock ROM.
Thanks anyways.
Click to expand...
Click to collapse
Just for your information:
If you want to flash a new rom, you have to flash a kernel that's compatible. So you do it like this:
1. Push rom zip (and gapps if needed) to sdcard
2. Boot in cwm and do a backup
3. Flash the new kernel (in the zip or if you can choose one, watch out: there are kernels for GINGERBREAD or ICECREAMSANDWICH and use the right one )
4. Boot in cwm
5. Wipe data/factory reset, wipe cache, advanced -> wipe dalvik cache
6. Install zip from sd card -> choose the zip
Reboot and you've got it
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Please give more details on how you flash it.
Enviado do meu GT-I9305 utilizando o Tapatalk now Free
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
If you did all required wipes and followed the instructions did you try a different recovery? I read in the SB thread for example of people having issues with TWRP
Sent from my Nexus 7 (2013)
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Try cwm 6.0.3.6 and after you install the rom and after its set up go to recovery and factory reset
nikolav75 said:
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Click to expand...
Click to collapse
That's strange, I run Philz recovery and every 4.3 flash till now went through without issue.
Sent from my GT-I9300 using xda app-developers app
I tried all the recoveries I could find. Including Philz. Still the same.
And something else strange. I installed CWM, CWM, touch and Philz and with them I made backups. After restoration of the backup the phone freezes. I also tried to install Omega 49 and the installation goes OK, but freezes before the first start-up.
The only solution was to install manually TWRP (Odin) to restore some of my old backups. I'm beginning to think that there is something wrong with my phone. It's black if it is important.
Suggest total wipe of phone install your stock rom and test
Hi,
I just want to say I'm also having the same problem.
Started using TWRP with full wipe, same issue on 4.3 and no issues on 4.2.
On latest CWM same problem and 4.2 wont even pass the first boot on Samsung logo.
Also had to use Odin to get back on TWRP and flash a 4.2 rom again.
Anyway there is one more thing I would like to try but haven't had the chance to do so, is installing the latest modem and ril. But I'm kind skeptic about that currently because there is also some risks and my S3 is my daily driver.
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
andrewwright said:
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
Click to expand...
Click to collapse
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
bla166 said:
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
Click to expand...
Click to collapse
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
andrewwright said:
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
Click to expand...
Click to collapse
yes tried that, also used the mega wipe zip thing
Start fresh and flash stock with Odin then try again after you root and install cwm.
andrewwright said:
Start fresh and flash stock with Odin then try again after you root and install cwm.
Click to expand...
Click to collapse
Tried to go stock and flashed a 4.3 rom again that fixed my problem. =)
Thanks! :good:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
nikolav75 said:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
Click to expand...
Click to collapse
http://www.sammobile.com/
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
nikolav75 said:
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
Click to expand...
Click to collapse
Hi, I think I did the following steps to get it working on my device.
1. Flash stock with odin
2. Hard reset
3. Boot up and finish first run menus
4. Flash twrp with odin
5. Format data with twrp
6. Flash 4.3 rom
Flash this recovery on the community build: http://forum.xda-developers.com/devdb/project/dl/?id=20236
And then flash the super SU file via recovery:
https://www.androidfilehost.com/?fid=24591000424944601
Let me know if this works or you need any help ?
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
From other posts in other topics it seams that it's the only twrp version that installs OOS 3.1.1
Sent from my ONE E1001
trendchanger said:
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
yes this is working
Jab_ said:
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
Click to expand...
Click to collapse
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Exodusche said:
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Click to expand...
Click to collapse
Maybe the problem is not xposed itself, maybe the issue is related to an specific module. I'll try one by one tomorrow and see what happens, thank you!
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Exodusche said:
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Click to expand...
Click to collapse
I know what the problem was. My xposed zip was correct. As I thought, it was because of a module. "Android N-fy", in recents, I just had to uncheck quick switch and change no recent image and that was it. I don't know if that module is optimized for this oos especific build, because in settings of the phone, the module does not change as much as in lollipop oos. Thank you tho
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Worked fine. Thanks OP.
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
TarushS said:
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
Click to expand...
Click to collapse
Oh lol, glad this helped
StraightEdgeKid said:
Worked fine. Thanks OP.
Click to expand...
Click to collapse
Np?
Sachin7843 said:
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Click to expand...
Click to collapse
What exactly are you looking to do?
marwan2704 said:
What exactly are you looking to do?
Click to expand...
Click to collapse
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Sachin7843 said:
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Click to expand...
Click to collapse
Make sure you have both .zip files on your phone, clean flash 3.1.1 then boot it up. If you don't like it, you can go back to 2.2.2 via stock recovery anytime. You don't even need twrp unless you want to root, install Xposed or backup.
might be a bit off-topic but...
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
error23 said:
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
Click to expand...
Click to collapse
Sounds like you forgot to wipe data. Wipe system, data, cache and just flash 3.1.1. As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Exodusche said:
As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Click to expand...
Click to collapse
It's not the place, but I can confirm that it didn't work for me. I still have the drain from time to time.
And if I don't have the Wifi drain I have a service Google Play service drain (33% for today's charge for example...).
And sometimes, I even had the wifi drain with Wifi completly switched off...
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Dileter said:
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Click to expand...
Click to collapse
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
Yes I am rooted and I tried flashing this ROM http://forum.xda-developers.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
I also dont really care if I lose photos or anything I already got all of them saved on my pc before I even started rooting the damn thing. I do need to ask tho how do you dirty flash and Do i just flash twrp normally since im already in it or ??? As I said im rlly new to this
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
DidierMoulin said:
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
Click to expand...
Click to collapse
Okay thanks a lot I will see if Any of it helps.
Please report.
DidierMoulin said:
Please report.
Click to expand...
Click to collapse
UPDATE I fixed it I just downgraded to the 2nd to lates version of twrp and it booted normally. Now I regret flashing the pixel one XDD If you have any idea for a good custom rom tell me Thanks for the help it actually helped a lot gave me the idea to downgrade the twrp recovery.
What you mean by pixel one xxd?
DidierMoulin said:
What you mean by pixel one xxd?
Click to expand...
Click to collapse
Its a 7.1.1 android rom from the google pixel
Dileter said:
Its a 7.1.1 android rom from the google pixel
Click to expand...
Click to collapse
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Pphish20 said:
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Click to expand...
Click to collapse
What he asked [emoji32]
It's happened to me too! Like three times lol. Just use UpperCut / LG UP to flash the latest nougat rom. That will fix the issue. You will need to re-root after that. There are instructions in this forum that tell how to do all of that. Good luck
Well and don't flash a ROM which is not for your device...
Here's my custom xTreme rom in the making for T-Mobile's 8" LG G Pad X.
Features:
**Debloated of most T-Mobile and Google Apps.
**Rooted thanks to Chainfire's SuperSU.
**XTREMEMusic Sound Mod thanks to androidexpert35.
**Quickboot from PlayStore
**Adaway thanks to the original dev
Must be at least 20f/g with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/sho....php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
Includes new 20H modem.
**********************
FLASHING INSTRUCTIONS
**********************
1. WARNING, MUST BE IN 20F/G. IF ON LINEAGE, DO NOT FLASH. YOU MUST KDZ TO 20F OR RESTORE 20F BACKUP FIRST.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20H-xTreme-v1.0.zip
Have been waiting for this! Thanks @MicroMod777
davenger1 said:
Have been waiting for this! Thanks @MicroMod777
Click to expand...
Click to collapse
Thanks. Nothing fancy. Been too busy using my Samsung S8+. )
Sent from my SM-G955U using Tapatalk
Flashed this just after following jdub01984's guide to update to 7.0, but ended up with a bootloop (not a twrp bootloop). Had to hard reset to force factory recovery. The build was at 20f before I installed, and I most definitely did not format system, just booted twrp, backed up, installed the rom, wiped cache, and rebooted. Install glitch? Should I try again? Was starting to panic when no combination of key presses seemed to interrupt the loop or cause a power down, then I found the hard reset sequence which got me back to twrp so I could restore (I'm using twrp 3.0.2 v2).
dooger said:
Flashed this just after following jdub01984's guide to update to 7.0, but ended up with a bootloop (not a twrp bootloop). Had to hard reset to force factory recovery. The build was at 20f before I installed, and I most definitely did not format system, just booted twrp, backed up, installed the rom, wiped cache, and rebooted. Install glitch? Should I try again? Was starting to panic when no combination of key presses seemed to interrupt the loop or cause a power down, then I found the hard reset sequence which got me back to twrp so I could restore (I'm using twrp 3.0.2 v2).
Click to expand...
Click to collapse
Sounds like a bad flash or download.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Sounds like a bad flash or download.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Yup, was a bad flash. Repeated the same procedure and it worked! Thanks! :good:
@micromod 777 What are the chances of you updating this rom to the latest firmware? Has been my go to since you released it.:good: