Hi guys,
Got an Optimus One from Koodo in June, rooted it and made a CWM backup with Rom Manager. Flashed a new rom on it for Gingerbread. Now, I would like to revert to the backup I made, but I am seemingly unable to.
It says "Restore Complete" after a couple minutes, then when I reboot the system, it stops at the Android splash screen and goes back to CWM.
Any help would be appreciated
have you wiped data/factory reset, cache, and dalvik cache?
crystaltable said:
Hi guys,
Got an Optimus One from Koodo in June, rooted it and made a CWM backup with Rom Manager. Flashed a new rom on it for Gingerbread. Now, I would like to revert to the backup I made, but I am seemingly unable to.
It says "Restore Complete" after a couple minutes, then when I reboot the system, it stops at the Android splash screen and goes back to CWM.
Any help would be appreciated
Click to expand...
Click to collapse
Did you made nandroid backup? You have to re-wipe your o1 and restore it again.
sweetnsour said:
have you wiped data/factory reset, cache, and dalvik cache?
Click to expand...
Click to collapse
Just done, problem persists.
mastershefis said:
Did you made nandroid backup? You have to re-wipe your o1 and restore it again.
Click to expand...
Click to collapse
Yup, nandroid. What is o1?
crystaltable said:
Just done, problem persists.
Yup, nandroid. What is o1?
Click to expand...
Click to collapse
Optimus One .. just your phone..
Maybe u have to use abd to erase system files, what still u have in your phone..
- get Android SDK (browse for it on google)
- boot your phone into recovery mode
- connect usb
- run 'adb start-server' or 'adb devices' (usually the 2nd does the start server automatically)
- run 'adb shell'
- run the command 'rm -rf /system/*
- run 'exit'
what rom are you trying to flash?
sweetnsour said:
what rom are you trying to flash?
Click to expand...
Click to collapse
I'm trying to restore an old backup, which is of stock Koodo.
Related
Ok, so I was trying to restore my V to its original condition and accidentally deleted my stock nandroid backup in the process, and now it only boots into CWM. I found two different stock zips online and tried installing one then the other. One installed but it's still booting into CWM, and the other just won't install. So I'm not really sure what I'm doing wrong. I actually still have my stock nandroid backup on my PC, but unless there's some way I can boot into the bootloader, I can't do anything with it. So basically I'm stuck and couldn't find any solutions after searching around awhile, though it's getting late so I may have missed something
Edit: I had a an aospCMod zip on another SD card and installed it, and it's still just booting into CWM. Not sure what I screwed up.
freedomispopular said:
Ok, so I was trying to restore my V to its original condition and accidentally deleted my stock nandroid backup in the process, and now it only boots into CWM. I found two different stock zips online and tried installing one then the other. One installed but it's still booting into CWM, and the other just won't install. So I'm not really sure what I'm doing wrong. I actually still have my stock nandroid backup on my PC, but unless there's some way I can boot into the bootloader, I can't do anything with it. So basically I'm stuck and couldn't find any solutions after searching around awhile, though it's getting late so I may have missed something
Click to expand...
Click to collapse
well in CWM i think you can enabled usb toggle...
terratrix said:
well in CWM i think you can enabled usb toggle...
Click to expand...
Click to collapse
Ah, thanks. Didn't realize that. I should just be able to plop my backup into the CWM backup folder.
I transferred the stock backup from my PC to the CWM backup folder and then restored it, and it's still only booting into CWM
freedomispopular said:
I transferred the stock backup from my PC to the CWM backup folder and then restored it, and it's still only booting into CWM
Click to expand...
Click to collapse
Yeah happened to me too.
Only way is to flash back via kdz...since the other roms can't work.
terratrix said:
Yeah happened to me too.
Only way is to flash back via kdz...since the other roms can't work.
Click to expand...
Click to collapse
Thanks. I'll have to check that out later.
freedomispopular said:
I transferred the stock backup from my PC to the CWM backup folder and then restored it, and it's still only booting into CWM
Click to expand...
Click to collapse
before trying to restore this backup, did you wipe data, cache, and dalvik cache?
sweetnsour said:
before trying to restore this backup, did you wipe data, cache, and dalvik cache?
Click to expand...
Click to collapse
Yes I did.
Hi,
Is there a way to Uninstall a custom zip package that was installed with xRecovery?
I installed a custom zip package, and my phone cannot boot...
Thanks
MagicHunta said:
Hi,
Is there a way to Uninstall a custom zip package that was installed with xRecovery?
I installed a custom zip package, and my phone cannot boot...
Thanks
Click to expand...
Click to collapse
The only option you have is to boot back into recovery and restore your last backup. If recovery is unavailable you'll have to use flashtool to flash a complete firmware package, root, install XRecovery and then restore your backup. If it's a 2.3 backup make sure that you're running baseband .71.
GreatBigDog said:
The only option you have is to boot back into recovery and restore your last backup. If recovery is unavailable you'll have to use flashtool to flash a complete firmware package, root, install XRecovery and then restore your backup. If it's a 2.3 backup make sure that you're running baseband .71.
Click to expand...
Click to collapse
Thanks for the quick reply!
What if I do not have a backup inside recovery..
Does that mean I have to Repair my phone using SEUS and lose everything?~~
PS. I am running 2.3.3 Stock FW
MagicHunta said:
Thanks for the quick reply!
What if I do not have a backup inside recovery..
Does that mean I have to Repair my phone using SEUS and lose everything?~~
PS. I am running 2.3.3 Stock FW
Click to expand...
Click to collapse
If you can get into recovery try this..... Do a backup first and then do a reinstall your current ROM. After you've done that do an advanced restore of your data and cache partitions from the backup you just made.
This should get you back to your ROM's basic system partition with your current data and cache. If everything works OK, you shouldn't even see any differences.
GreatBigDog said:
If you can get into recovery try this..... Do a backup first and then do a reinstall your current ROM. After you've done that do an advanced restore of your data and cache partitions from the backup you just made.
This should get you back to your ROM's basic system partition with your current data and cache. If everything works OK, you shouldn't even see any differences.
Click to expand...
Click to collapse
By "reinstall your current ROM", you mean reinstalling the stock SEUS ROM right?
I just made a backup inside recovery, I will go ahead and reinstall my phone now.
When I restore, are the texts, phonebook etc... being restored from recovery's backup? =) or will i lose those?~
MagicHunta said:
By "reinstall your current ROM", you mean reinstalling the stock SEUS ROM right?
I just made a backup inside recovery, I will go ahead and reinstall my phone now.
When I restore, are the texts, phonebook etc... being restored from recovery's backup? =) or will i lose those?~
Click to expand...
Click to collapse
I mean whatever rom you were using when you installed that zip that caused the problem. It actually should still be on your SD card as a Zip unless you removed it after you flashed it.
When you restore data you'll get everything back apps, texts, contacts, history etc.....
GreatBigDog said:
I mean whatever rom you were using when you installed that zip that caused the problem. It actually should still be on your SD card as a Zip unless you removed it after you flashed it.
When you restore data you'll get everything back apps, texts, contacts, history etc.....
Click to expand...
Click to collapse
Oh, I wasn't trying to install a rom, i was trying to install this on a SE stock 2.3
http://forum.xda-developers.com/showthread.php?t=1194266
After trying to install that zip, my phone cannot boot anymore~
I think I am left with reinstalling my whole phone?
Just thought i ask first,
in the Advanced Restore there are
Restore boot, Restore system, Restore data, Restore cache, and Restore sd-ext
I know for sure that i will not need to restore boot... lol, what else do i not need?
MagicHunta said:
Oh, I wasn't trying to install a rom, i was trying to install this on a SE stock 2.3
http://forum.xda-developers.com/showthread.php?t=1194266
After trying to install that zip, my phone cannot boot anymore~
I think I am left with reinstalling my whole phone?
Just thought i ask first,
in the Advanced Restore there are
Restore boot, Restore system, Restore data, Restore cache, and Restore sd-ext
I know for sure that i will not need to restore boot... lol, what else do i not need?
Click to expand...
Click to collapse
After you get back to your stock Rom and have root / XRecovery, just restore data and cache. Whatever you do, don't restore system or you'll have to start over
Sent from my X10i using xda premium
GreatBigDog said:
After you get back to your stock Rom and have root / XRecovery, just restore data and cache. Whatever you do, don't restore system or you'll have to start over
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Thank you very much for your help!!
Learned a few things here and there hehe
Just one last quick question. Is there a difference between recovery backup & titanium backup?
Thank you!!!
MagicHunta said:
Thank you very much for your help!!
Learned a few things here and there hehe
Just one last quick question. Is there a difference between recovery backup & titanium backup?
Thank you!!!
Click to expand...
Click to collapse
There are some big differences - But what exactly do you mean ? (In which way?)
Last night, I installed TW 4.5/TW Manager. I did a ClockworkMod backup first. I decided to restore it.
However, after restoration, the phone is in a factory state. Save for my lock pattern, which it remembered, the phone is in first-run setup mode, all my home screen layouts are gone, all my apps are not in the aop drawer except those the G2 ships with. Contents of the virtual SD card like photos are still there.
I tried restoring my only other CWM backup (a November backup that previously *restored ok* to undo a MIUI test, for example), but this, too, now boots in to the same state.
What has gone wrong here?
And is there any way of getting back the system that I assume/d is/was in the CWM backup files?
If I can't guarantee I can restore a CWM backup, it makes the world a very scary place to be.
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Wipe what?
You mean, choose Wipe Data and/or Wipe Cache?
Lennyz1988 said:
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Click to expand...
Click to collapse
Wiped data, Wiped cache, Restored backup - still doesn't retrieve the actual backup.
Now wiped again. In Advanced Restore, what should I do?
Lennyz1988 said:
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Click to expand...
Click to collapse
Restore the boot, system, data.
Lennyz1988 said:
Restore the boot, system, data.
Click to expand...
Click to collapse
This doesn't work either.
I had the same trouble early last month; even after a restore it was pretty much factory settings and I had to put everything back myself.
It was very irritating as I'd taken the precaution of making a backup but it still didn't work. I've pretty much recovered everything I needed to since then, though.
What excactly did you do prior to the restoring? Did you flash a new rom? If yes, what was your previous rom? Or is TW4.5 an app of some kind?
Lennyz1988 said:
What excactly did you do prior to the restoring? Did you flash a new rom? If yes, what was your previous rom? Or is TW4.5 an app of some kind?
Click to expand...
Click to collapse
I did this... http://forum.xda-developers.com/showthread.php?t=1365605
That is...
Installed TouchWiz 4.5, a modified TouchWiz launcher (left it alongside TouchWiz, set no default - home button press asked for confirmation of home screen each time)
TW4.5 comes with the TW4Manager app for controlling settings.
I downloaded the Suava theme for use with TW 4.5.
Before any of that, I made a CWM backup. Then I did the above. Now the backup (and even a backup which restored perfectly a month ago) will not restore to anything but factory new state.
And you are not getting an error message of any kind? How long does it take to restore? What is the size of the backup?
Lennyz1988 said:
And you are not getting an error message of any kind?
Click to expand...
Click to collapse
None.
Lennyz1988 said:
How long does it take to restore?
Click to expand...
Click to collapse
Seven minutes
Lennyz1988 said:
What is the size of the backup?
Click to expand...
Click to collapse
972Mb
The last thing I can think of is flashing an old stock rom and then rooting it with CF-Root. Then you have an older version of CWM.
A stock rom like KE2. Then try to restore.
If that does not work find a rom which has the latest CMW. Version 5 I believe. Then try restoring it.
Lennyz1988 said:
The last thing I can think of is flashing an old stock rom and then rooting it with CF-Root. Then you have an older version of CWM.
A stock rom like KE2. Then try to restore.
Click to expand...
Click to collapse
Hmm, are you talking about kernel?
If I'm correctly reading my rough notes from my rooting and tinkering, then my original kernel was KF3, I rooted in mid-October with an insecure equivalent (KF3) (CF-Root method), but quickly upgraded through Kies... I now have kernel XWKI4 (baseband XXKI1, build KI4).
So I moved from 2.3.3 to 2.3.4.
BUT - the backup and restore I did with CWM under the current system as recently as two weeks ago in November worked fine.
Lennyz1988 said:
If that does not work find a rom which has the latest CMW. Version 5 I believe. Then try restoring it.
Click to expand...
Click to collapse
So, you're saying there - you think a newer version of CWM might have eliminated a bug or something?
Might I find any FURTHER problems by changing the ROM and trying to restore?
Thanks for your help.
ClockworkMod - merry effing Christmas.
I really don't know. But I think it's worth the effort determining of your CWM is still functioning properly.
You can also try just flashing the KI4 CF-root kernel, then boot in recovery and then try to restore.
Make sure you have important stuff backuped of course
If you can boot to working phone backup data and copy clockwork mod folder to PC .
Then try posted below . boots to working phone root it with CWM and root copy clockwork folder back then try restore nandroid backup .#
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
JJElgan, thanks,
So let me clarify what you're essentially suggesting...
Store my ClockworkMod safely on the PC
Wipe cache, data, system and SD card in Recovery Mode
"Install correct firmware"
Then put the backup file back and try restoring
What do you mean by "correct firmware"?...
I currently have Baseband XXKI1, Kernel XWKI4, Build XWKI4. That is the firmware with which I made the backup. (I guess that's KI4?)
But the firmware I originally rooted with CWM was PDA: KF3, PHONE: KE7, CSC: KD1 (XEU). (I guess that was KF3?)
What's the aim of this here and what's the source of the info?
Thanks very much.
JJEgan said:
If you can boot to working phone backup data and copy clockwork mod folder to PC .
Then try posted below . boots to working phone root it with CWM and root copy clockwork folder back then try restore nandroid backup .#
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
Click to expand...
Click to collapse
You dont need to wipe before restoring. Just a quick note
Sent from my GT-I9100 using xda premium
CdTDroiD said:
You dont need to wipe before restoring. Just a quick note
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Ever?
How about after?
And how about in the advice the previous correspondent gave, to reinstall kernel/firmware?
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
rhrs1987 said:
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
Click to expand...
Click to collapse
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
tallman43 said:
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
Click to expand...
Click to collapse
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
rhrs1987 said:
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
Click to expand...
Click to collapse
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
tallman43 said:
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
Click to expand...
Click to collapse
Indeed have to get used to it... many thanks for response tallman43