Database Info

Completely Bricked Phone (?)

Hi smart people!
Just to throw it out there, I am not very tech savvy so excuse me if I misuse terms and such.
I believe I completely bricked my phone (I hope I'm wrong). After I downloaded Cyanogen through ROM Manager, my finger stumbled on the "continue" or "next" button or whatever WITHOUT checking the boxes to clear data, etc. I believe this is where I went wrong as I think I followed all other steps correctly (fyi I used the one click recovery flasher and made a back up).
Now when I turn on my phone, it goes from the stock LG loading screen to a modified LG loading screen (Cyanogen's I'm assuming) but it gets stuck there.
I've been searching on the different threads for quite a while and pressing the different combinations of volume up/volume down/power don't seem to do anything. I cannot get to the recovery screen.
Please help! I will forever be indebted to all of you. I am stupid and shouldn't have tried to do this on my own. Thanks in advance

What you will need to do is flash CWM via NVflash then boot into CWm and install your ROM.
If you flash CWM via ROM Manager it causes problems like what you're describing, I know from my own experience of following a friends instructions and doing that then having that exact issue. After getting my phone working again I then started to frequent the boards here.

As soon as I read the first couple lines I saw rom manager and saw the problem, you to search something that you have typed out all within this thread... I'm not near a computer but you should just search through these threads and you find your solution in detailed description. You need to get recovery from nvflasher just search that
Sent from my LG-P999 using xda premium

thanks for your replies
thank you to both of you for your prompt replies. i will try doing this within the next couple hours and post any results. this is the thread i found with the information you guys gave: http://forum.xda-developers.com/showthread.php?t=1058649
thanks again

No, that's not for G2x. Go here: http://forum.xda-developers.com/showthread.php?t=1056847

Ya it needs to be the one that gunnman wrote out for people.
Sent from my LG-P999 using xda premium

Hey guys...on step #10, it says to "select 'have disk'" but i do not see that option in the list.
Thanks

okay now i realize i should have been doing the cwm recovery. sorry guys and thanks again

reboot error
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!

The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.

justintheshark30 said:
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
Click to expand...
Click to collapse
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
P.S. for future reference, you did not brick your phone, you got stuck in a boot loop, you know your phone is bricked when you don't see anything on the screen when you turn it on, usually it's just a software issue, but sometimes it could be hardware, for example I burned the motherboard on my previous android phone trying to customize it lol

jj_z1 said:
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
Click to expand...
Click to collapse
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.

Волк said:
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Click to expand...
Click to collapse
I really hate posting anything that doesn't have to do with anything phone related but I just couldn't stop myself from replying to your post!
1) I actually read all posts in the thread!
2) I did not in any way suggest that he didn't flash CWM the right way, I merely asked if he had done a full wipe before restoring his backup!!
3) Your reply was submitted while I was typing mine, so I'm sorry I didn't check the thread again before submitting my reply!!!
4) I'm well aware of what he tried to do already, but thanks for repeating it!!!!
5) If YOU read all previous posts you'll notice that my post does not exactly replicate any other, there's some new information in there that the OP might find useful!!!!!
6) From what I can tell, you need to work on your english and comprehension skills!!!!!!
To the OP, sorry for trolling your thread with this post, but I just couldn't help it, and to Bonk I hope you'll be the mature one and not reply to this post.

Is that to say you're immature? If one were to judge by the number of exclamation marks you have I'd say yes.
The only "new" thing was asking if he wiped before the restore, which, at this point, would be useless to ask as I already told him to make sure to wipe.
To the OP: How goes everything thus far?

thank you
that's what i ended up doing and it worked. thank you so much for all your help!

Волк said:
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
Click to expand...
Click to collapse
And dalvik cache for good measure, even though it is stored on the cache partition and will probably get wiped when you wipe cache. Sometimes it's good to overdo thing's.

Unable to do anything!
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?

efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Start over. Do what it states here: http://forum.xda-developers.com/showthread.php?t=1248644

efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Did you battery pull and start over?
Sent from my LG-P999 using xda premium

UNROOT help
Hello again smart people,
I was hoping we would never meet again (for the better) but unfortunately i must unroot my phone to receive work emails. I have tried unrooting my LG G2x multiple times but to no avail thus far.
Here is the process I have tried:
1) boot into recovery - wipe cache/data factory reset, wipe cache partition, wipe dalvik cache
2) restore - using stock rom i found online
3) flash stock recovery image using nvflash
4) (attempt to) unroot using superoneclick - AFTER GOING THROUGH MULTIPLE STEPS, IT SAYS "TRUE" UNDER "CHECKING IF ROOTED". (also, i know it is rooted because it says the phone already appears to be rooted when i try to root again).
Do you guys have any idea what the issue could be?
Thank you in advance...

[Q] Guess I've bricked my phone, again

I was running CM10, downloaded the nightly released on 1/13.
Installed it, it rebooted, then got stuck looping again. I couldn't get it to do anything. Eventually my boot screen would go away, it would go to a blank black screen. I could see backlight, but I had absolutely nothing.
I managed to get into my bootloader, could get into recovery as well. I'm using TWRP.
I couldn't get it to do anything at all.
I eventually wiped my SD card, reformatted it, downloaded AOKP, flashed the ROM. It's started, got to the AOKP Loading screen, which it is now looping. I can't get it to do anything. I'm lost and frustrated as can be.
Any fresh ideas from anyone?

If the screen is on, its not bricked. Not knowing what to do is not a brick.
Did you factory reset, wipe data and wipe cache (all from TWRP, do not factory reset from hboot, whatever you do) before flashing?
If on hboot 1.14 or higher, did you flash boot.img via fastboot?

I restarted the entire process. I actually ended up having to do it a few times. No change in the process.
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
On another attempt it worked just fine. No change in the way I did things. I'm unsure of what the difference was or why, but its working, for now. I may end up getting a different phone instead of my Onex to see if things run smoother on my process. I have an old captivate I may try to use as a trial/error experiment.
Sent from my One X using xda app-developers app

i factory reset from hboot is there anything i can do? had the same issue with cm10

mfc1288 said:
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
Click to expand...
Click to collapse
Why do people keep wiping their SD card when flashing? I understand there are some people that do it deliberately because they like to make a "fresh" start. But it seems that the majority of people doing it are n00bs that for some reason think its "required" when flashing a new ROM, which it is not. Factory reset, wipe Dalvik, wipe cache. Nothing else "needs" to be wiped when flashing.
Remember on most devices the SD is removable, and doesn't really have much of anything to do with the flashing process, aside from the fact that you put the new ROM zip file on there (and backups go there). Its like saying you "have to" format your external hard drive every time you want to change or upgrade your PC operating system.
mfc1288 said:
I have an old captivate I may try to use as a trial/error experiment.
Click to expand...
Click to collapse
Completely different hardware, so I'm not sure what you would trying to accomplish with that experiment. I think you just had some bad luck, and bad flashes just happen occasionally. I've flashed many different ROMs on the One X, and have never had issues booting up.
CM10 seems to be giving more headaches than other ROMs, so that may have something to do with it. Not to insult that ROM or its devs. But when things change nightly, there can be glitches. And it just seems there are a lot more complaints about not being able to boot after flashing CM10 than other ROMs (despite having correctly flashed boot.img and wiped). Or maybe the number of people posting this issue is just a testament to how popular CM10 is?
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
sinzish said:
i factory reset from hboot is there anything i can do?
Click to expand...
Click to collapse
This has been discussed on many threads already. Plug the phone to a PC, and it should show up as new hardware. Select it, and choose the option to format FAT32. After that, you should be able to mount as a USB drive.

Need Help

I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."

Justintoxicated said:
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Click to expand...
Click to collapse
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.

dottat said:
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
Click to expand...
Click to collapse
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.

Justintoxicated said:
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Click to expand...
Click to collapse
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.

dottat said:
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
Click to expand...
Click to collapse
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though. I did not install lolipop because I need to get the phone to USB mode to copy it over, which I cannot do because it will not start up.

Justintoxicated said:
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though.
Click to expand...
Click to collapse
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?

dottat said:
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
Click to expand...
Click to collapse
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
TWRP is now version 2.8.5.0, so apparently it updated correctly (I think before it was 2.8.1)

Justintoxicated said:
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
Click to expand...
Click to collapse
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.

dottat said:
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
Click to expand...
Click to collapse
Ok my internet is not working on my laptop at work (only of the PC I'm on and no way to transfer files without my phone), so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.

Justintoxicated said:
Ok my internet is not working on my laptop at work, so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Click to expand...
Click to collapse
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.

dottat said:
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
Click to expand...
Click to collapse
Update, restarted the computer and I was able to restore the old firmware. I re-installed the old rom afterwards (not my nandroid) and I am unable to get into the OS. Well technically I get prompted to select a language, after which the phone reboots back to the S-off androids with skateboards bootloader. Does this mean my phone is toast?

Hey guys, should I S-on the phone load the stock bootloader and try to return it? It is over a year old so I think I will need to use my insurance ($100). What is the best way to go about doing this?
Also when I get my replacement phone will there still be a way to S-off?
Thanks,
- Jusitn

The problem appears to be something wrong with my micro SD card! I removed the micro SD card and I can boot up fine. I guess I need to find another way to copy the rom to the micro SD install the rom then remove the micro SD card.
edit:
Oh this is worse than paying $100 for a new phone. It appears that creating a backup instead of creating a backup, actually corrupted my memory card. Now all the photos are backed up to the cloud but it will take me hours and hours to get all my apps back to the way they were. Some Security camera settings, Rifle target hand load development all gone. Audio book place holders, all notes taken etc. Nothing life or death but those security cameras will take me forever to figure out. I know I know, why not create a backup right? Well that's what I was trying to do!

So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?

Justintoxicated said:
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Click to expand...
Click to collapse
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.

robocuff said:
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
Click to expand...
Click to collapse
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.

Justintoxicated said:
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Click to expand...
Click to collapse
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.

dottat said:
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
Click to expand...
Click to collapse
I don't remember, probably missing a file or something.

Unencrypt 60450? Help would be greatly appreciated!

Ok. So I thought I would give encrypting my phone a test drive, as I have never done it before, and read a lot about the pros and cons, and decided to see for myself since having the code, I could always factory reset, worse case scenario, right? WRONG! The problem is that even performing a factory data reset, it refuses to mount data, resulting in no change whatever. So I'll just TWRP wipe, and restore nandroid right? WRONG! Nothing I do will allow the data to be mounted, so I always end up back where I started. I read that flashing a custom kernel is a workaround, but I am on stock rooted, with stock SE Linux enforcing, so I don't think I can flash a kernel. I'm afraid to use the upgrade tool, as I am afraid that it will either fail or brick my device. If I am wrong, or have missed anything in my searches, please correct me and help if you have knowledge in this area. Apparently, one thing Touchwiz got right is a decrypt option in their settings. AS it is, I am unable to backup, restore, or flash another ROM, because data will not mount to be wiped. UGH! Worst mistake I have made. Ever. Thanks in advance for any help with this. I have no problem in losing everything, as I have important stuff backed up physically and in the cloud.

Finally got formatting data to work, and restored backup from external SD, which I removed before format, just in case. Sorry for posting for help a little too quickly, but maybe my exploits will save someone else from headache I went through. :victory:

[HEEEEEELP]-TWRP stock Backup deleted - Xiaomi mi a2 lite

Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.

manna.davide87 said:
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
Click to expand...
Click to collapse
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Click to expand...
Click to collapse
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.

manna.davide87 said:
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
Click to expand...
Click to collapse
Mate @Droidriven you're a monster!
I found it in data/media in the internal storage! thanks a lot mate!
I'll run it and see if all comes back as usual.
Infinite thanks!

Good to go.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Good to go.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide

manna.davide87 said:
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
Click to expand...
Click to collapse
I don't know anything about any of the ROMs for your device, I don't have your device.
Sent from my LGL84VL using Tapatalk