Related
Hey guys. Before I get to my issue and seek your help , please allow me to give you a bit of background about my self wrt Android OS and nexus devices. I have been a Nexus device user since the N1 days. OS flashing , Custom rom's , kernel patching , etc are nothing new to me. I can safely say that I am a custom rom addict , hence I know the mods for my devices intricately well. With this out of the way , I'd like to share the sequence of events that took place yesterday , which lead to this new thread , wherein I desperately need some expert advice.
- I was running the latest Bigxie 5.0 rom for my 32gb N5. It had root and TWRP and elementalx kernel
- I wanted to upgrade to the 5.0.1 without losing any data , so I first tried to sideload the OTA zip file , which failed with some error. I then followed this guide (http://bit.ly/1wNT36l) . I was able to therefore flash the 5.0.1 without losing data. I re rooted my phone , re flashed the recovery and the kernel
- At the same time I was upgrading my LG g3 to Lollipop. I wanted to try the "Tap & Go" data transfer feature , so I used that process to transfer the data from my current N5 to the new G3. Here is when the issue started. The data transfer didn't go through , as only the email accounts transferred to the G3. At the same time , I got this notification on the Nexus that Tap and Go was used to transfer my email accounts , and this notification couldn't be cleared from the notification panel. For some odd reason , I decided to jump back into recovery and wipe cache and dalvik cache to get rid of this notification
- As soon as I did that specific wipe and restarted the phone , the phone would just loop at the nexus image boot screen. 15 minutes later I went back into recovery and decided to use the "factory reset wipe". That too didn't solve my problem. Frustrated at the turn of events , I reflashed Bigxie's 5.0 rom from my internal storage , via twrp.
- The phone finally booted! But now the problem was that my Sdcard was showing no files. It was all blank. I checked with root explorer / es explorer and even when I hooked up my phone to my pc , the sdcard was showing no files. I could , however , see all my files in the root -- data -- media -- 0 folder. I tried my best to extract all my files from there , but each time I got an error that pretty much meant that no files could be moved from there. Interestingly , when I went into twrp , and went into file manager in the advanced options , it showed all my files on the sdcard as though nothing went wrong. So I could see everything on the sdcard in recovery , but nothing if i booted into the OS.
- Since I had made a backup of most of my data prior to any this happening , with the exception of certain whatsapp data , and after having spent almost 5-6 hours in figuring out where I had possibly gone wrong , I decided to wipe my device clean and just install the stock OS and pack this device away for good
- I downloaded the stock factory image for 5.0 from the official site and went back into bootloader and fastboot flashed each and every file. The phone booted , BUT , now my phone showed only 12GB as the size of the storage with 11GB available. This frazzled me beyond words! How did I reach this stage wherein my internal storage was screwed to this level?
- I again went back into bootloader , flashed 5.0.1 , wiped the device and now the phone is again stuck in a bootloop on the nexus bootscreen
I have finally decided to send the device to the LG service center near my office , but I wanted to share this experience with the community hear and seek their guidance on where I possibly went wrong and what I can do now to put things back together to some degree of normality. Have I somehow damaged something at the hardware level that a change of motherboard may be warranted or is this a pure software screwup?
Thank you for your patience in reading this loooooong story , but I had to explain each and every step in perfect detail.
after flashing stock image.. there is no need to wipe anything... just boot it... takes around 5-10mins max but comes up.....
When it does 12GB on a 32GB device, you just have to factory reset using the option from inside the ROM.
Sent from my Nexus 5 with the N5X LRX22C ROM
tip, just because you know and read rom´s instructions and such, dosent mean you are an experiencied user.this 99% would have save you
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
opssemnik said:
tip, just because you know and read rom´s instructions and such, dosent mean you are an experiencied user.this 99% would have save you
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
Well said , and understood. I followed a different set of instructions and flashed back to stock and fixed my device. Thank you for your help.
ecksreturns said:
Well said , and understood. I followed a different set of instructions and flashed back to stock and fixed my device. Thank you for your help.
Click to expand...
Click to collapse
haha no problem, i thoguth i was an experienced user too, but then i bricked mine by flashing lg g2´s rpm partition to get a different partition layout. lol. glad you got your n5 back
Hi guys, wasn't sure where to post this and I've been searching the web for hours without coming up with an answer with the best way to fix the problem I've got.
So yesterday my sister gave me her phone saying it was shat and slow and generally rubbish (S4 i9505 running 4.4.2). So I had a brief look at it and she had absolutely no room on the phone at all, it was completely clogged. So I deleted all the cache data (4 gigs!!), as soon as I did this the phone came back to life and started updating everything it could, then made a backup in CWM. Thought while I'm here I may as well put the official Lollipop firmware on it from Sammobile. All was good until I realised that she has never backed anything up to google or any other cloud storage (pretty dumb!) and all of her important stuff I couldn't get back.
So I then had to try and extract some data from the CWM backup... couldn't do it. I just couldn't find the files that she wanted restored. Mainly whatsapp messages and pictures and also Smemo. These are all she needs, there's really important memos apparently, why the hell she never backed them up or had another copy of them is beyond me if they were that important!
So I tried restoring just the data part of the 4.4 CWM restore to the 5.0 rom, looking back now I see this is where I went wrong and was asking for trouble.
So I then tried rolling back to the full CWM backup, all went well so I assumed and it said it was successful. This was until the phone booted. Constant spamming of gapps has stopped working, and no matter what I did I couldn't get it to stop, the phone was unusable with it constantly pinging up, every app was failing, and then it would turn itself off and reboot.
So I Factory reset again and wiped everything, installed the backup again, same thing happened again. Even tried flashing the latest version of gapps, but nothing had any effect.
So now I'm thinking oh feck... I didn't make a backup of the Lollipop install as I thought the rollback would have just cured it, and she had already started messing about with it, making it look pretty and getting people to send her some of the important files she had.
So I thought balls, tough luck and you'll have to start again, your fault for never backing anything up. So I reflashed Lollipop, and for some reason it wouldn't boot. Would just hang at the Samsung logo, this was 4am, I was panicking as I'd effectively bricked her phone. So after lots of boot loops and countless flashes I was looking on ebay for a new phone for her, then suddenly it finally boots on one of the flashes.
Anyway after a lot of faffing about, flashing 4.4 which worked, so flashed 5.0 again, and luckily it booted, I don't know what happened, maybe I missed something as I was so tired, so I signed her into google and let all the apps download while I slept.
Now the question is, I seem to have found a site that explains how to extract individual files vaguely, I just need to get the smemos and whatsapp files and I'm not entirely sure where to look and extract these files. Also, will they corrupt if I try to install them on the 5.0 firmware?
Any help would be much appreciated as I'm really in the stinky brown stuff.
Morning bump if anyone can shed some light on this :crying:
Hi
Thanks for writing to us at XDA Assist. Have you tried using this tool?
[Tool] Cwm nandbackup file Extractor ( .img/ .tar files )
It should extract exactly what you need. If you're only reinstalling those specific apps with their data you should have no issues, just don't restore any system data, that's what caused your problems after restoring the KitKat backup on top of the Lollipop ROM.
No response in two days, thread closed, thanks.
Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.