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
Related
Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.
Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.
Hello I'm sending this post now because I'm going to need somebody's assistance. A quick story I have been doing this for about 3 months as far as my first root to a flashaholic. I have successfully got around my bootloader. The problem is I'm not 100% sure how. I have a good idea of what I did but I don't know exactly as I am NOT a dev and I am new to this. I catch on rather quickly though and have found a passion for modifying my android and this site has been my number one contributor. My goal is to give back and help others out as well. I started off by editing permissions in my system file along with floating feature, csc, features and the customer XML. It was somewhere right in one of those files that I did this.. I simply changed the permission or function and immediately when I did I was prompted by super user to let boot animations by JRummy apps creator of the toolbox to allow permission which I did. The problem is as I didn't realize what I did at the time until I reset it as I changed about 10 different things. About a week prior I tried installing the boot animation into different file folders which was the two options that they suggest. Nothing happened of course my bootloader is locked and i wasn't surprised. Well I changed the permissions that shouldn't have in the calling feature section and I got stuck with force close force close so I hard reset into the factory recovery and trief to clear the cache partition which was unsuccessful. I then decided to install philz custom recovery so I could do a good clean out because obviously the factory recovery is garbage but every time I tried to change it it would stick me in a boot loop after being successfully flashed and in use for at least 24 hours. After I wiped the dalvik cache and the cache partition with Phils I then decided to try one last flash with a custom ROM and everything flashed fine. But once it rebooted I noticed a completely different boot animation and to my amazement it ended up booting and upgrading all my apps it started up normal. The rom I installed was real rwilco's mostly stock version 1.2 G900PVPU3BOG1. After that I decided I was going to take another chance and flash a few modification files. Once again succesfull. This morning I decided I was going to try to do a backup and restore. I backed it up with Phil's recovery and then I restored it. Restoring gave me a bit of a problem as I had to delete the cache and the dalvik cache. I then restarted the system the first time it didn't work or I didn't wait long enough I'm not sure. The second time I hard reset it introduced a normal boot and it started back up and was upgrading all 590 something after they have. Before I did any of this I was working away at a stock rom that I managed to modify a file in. This would be the aboot.mdn i believe. I was able to open it up into a notepad and replace it with the older version in the text part only so the file name itself stayed the same. I don't know if that played a major part to it or not. But I have sense flash recovery and files without getting stuck into a bootloop and with this new firmware almost every time I turned it off and on it would put me in a boot loop just because I was rooted. I attempted to simply change a new battery that I ordered powered off replace battery powered back on and was stuck in a boot loop. I have been making it my goal to somehow crack this thing. This is where I need help because I am still a noob I always just happened to poke in the right places I could care less about reaching 10 posts so I can post links if you like after I upload my information you can go ahead and reset that. I am here because I can seriously help and this website has been a major contributor to me becoming a flashaholic. I am at work right now and have already attempted but I'll go down to a 3G signal if that. I have absolutely no reliable internet here but within 5 hours I will be home uploading to my Google Drive a copy of my manifest and CSC, permissions, and features files. I have also created a clockwork recovery which I am going to upload as well I need somebody to help me go through these and pinpoint exactly what I did so we can get a legit thread with the fix. I somehow basically flashed a new boot animation which i think is blocking my other boot. I have confirm this working I have 2 screenshots I'm going to upload. Anybody with real experience and actually knows what they're doing I would appreciate your help in this matter.. And actually knows what they're doing I would appreciate your help in this matter. I just need to get home to my laptop to upload. Thanks xda you guys are awesome and I hope this is finally my opportunity to contribute and give back.
i ran out of time and couldnt proofread. sorry about that lol'
in my drive account i have a 1) factory rom that i modded aboot.mbn. 2) The backup "philz" cwm recovery. its my full backup apps and all down to the boot image that replaced the sprint yellow screen and the samgsung boot logo. 3) The system files that i have modified.. csc, features, floating feature, customer xml... 3) screenshots of rom info and adding others of some of the mods as we speak. still need 15 mins to finish uploading the sys files
if someone can figure out exactly what i did we have a fix. i have since flashed 30+ mods with no bootloop. email is [email protected] just incase for contact purposes
h t t p s: // drive. google. com / drive / folders / 0B5AfudcH1XDQMVFZdFhVTFdYQ0U---has many spaces only way to fit link
the system files have been diificult to et into my drive. most did not want to copy and the size themself. the full custom restore is in my drive already along with some screens. i have also set my boot animations to random and have about 20 or so cycling. also after restore make sure to wipe dalvick cache and cache. also some of the apps might fc i didnt have them fully restored when i created backup. i added a backup file in drive that has full copy.
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?
So day before yesterday my dads phone asus zenfone 2 (Z00AD) went into bootloop. it kept booting repeatedly never making it to the home screen. anyway, he took it to asus repair and we got the phone back today. its back to normal but all data is lost. (We had not backed up anything) I downloaded a few android data recovery softwares like mobikin and dr fone but they require the android to be rooted to scan for lost data.
Now my question is, do you think its possible to recover data once the phone has been flashed? I am apprehensive to do the rooting and will only go ahead with it if there is a real chance some lost data may be recovered through such android data recovery softwares.
Please advise. Should I go ahead and root and give it a try?
thank you so much in advance.
You should have backed up before taking it the center(you could have flashed a custom recovery and enable mtp mode and backed up to pc).after a stock ROM is flashed chances of recovery is almost nill.
Just one question, why did you take it down to the shop? It is easy as hell to fix a bricked device. I remember taking down my device to the shop twice and got a new one twice but I managed now to fix it. You will most likely have gotten a replacement for your device. Also, if there is root availible for your device, there are stock rom images to flash via fastboot.
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.