Related
Hey guys, Im new to this but I got a phone. Its a Samsung Infuse 4G for AT&T. It was running cyanogen... it was jellybean 4.2.1 I believe? Anyway, now it is stuck on "CW based Recovery v6 .0.3.2" and Im stumped!!
It also isn't registering on my PC so I cant drag any files to it. It comes up that there is 2 drives, but they are grayed out, like I cant open or click on them. Ive heard of NVflash but cant figure out how to use it, not sure if I can since I cant drag and drop files on my droid.
Please help me...
Bender9406 said:
Hey guys, Im new to this but I got a phone. Its a Samsung Infuse 4G for AT&T. It was running cyanogen... it was jellybean 4.2.1 I believe? Anyway, now it is stuck on "CW based Recovery v6 .0.3.2" and Im stumped!!
It also isn't registering on my PC so I cant drag any files to it. It comes up that there is 2 drives, but they are grayed out, like I cant open or click on them. Ive heard of NVflash but cant figure out how to use it, not sure if I can since I cant drag and drop files on my droid.
Please help me...
Click to expand...
Click to collapse
Here is what it looks like...
Bender9406 said:
Here is what it looks like...
Click to expand...
Click to collapse
Try wiping data & cache if possible and then system reboot..
Hit thanks rather than typing it
parkourkarthik said:
Try wiping data & cache if possible and then system reboot..
Hit thanks rather than typing it
Click to expand...
Click to collapse
I wish it was that easy. No restore option. Reboot just sends me back to same thing. The cache has been cleared so many times.... no luck
Bender9406 said:
Hey guys, Im new to this but I got a phone. Its a Samsung Infuse 4G for AT&T. It was running cyanogen... it was jellybean 4.2.1 I believe? Anyway, now it is stuck on "CW based Recovery v6 .0.3.2" and Im stumped!!
It also isn't registering on my PC so I cant drag any files to it. It comes up that there is 2 drives, but they are grayed out, like I cant open or click on them. Ive heard of NVflash but cant figure out how to use it, not sure if I can since I cant drag and drop files on my droid.
Please help me...
Click to expand...
Click to collapse
I got the same problem.. have you figured out how to fix it?
Same thing here
I've got exactly the same problem with my LG P720 (3D MAX) after installing the ICS ROM (and I'm already looking for a new phone). But I'm willing to donate to whoever can help me with this. :crying::crying::crying:
endeavor2908 said:
I've got exactly the same problem with my LG P720 (3D MAX) after installing the ICS ROM (and I'm already looking for a new phone). But I'm willing to donate to whoever can help me with this. :crying::crying::crying:
Click to expand...
Click to collapse
Reflash the boot loader of you device using Odin if you can. It will solve the problem. Since im on a different device I can't tell where you can find it. Just search for it.
Sent from my GT-I9001 using xda premium
About odin
Sewrizer said:
You can go in cwm recovery->mounts and storage-> mount sd card or usb storage then connect phone to PC. After connecting it, you copy a rom to sd card and gapps if necessary and then perform a full wipe and flash the rom along with gapps.
If the mounts and storage thing doesn't work, put your sd card in an adapter or another phone and connect it to pc and move the rom and gapps there then put the sd card back in your phone, full wipe and flash.
If this doesn't work, do a restock with odin with a rom from sammobile. If you don't know how to do it, send a reply to my post and I will give you some instructions.
Click to expand...
Click to collapse
Ok so, I've download ODIN and I have the ROM in a zip file in the internal memory but ODIN just takes .tar, .md5, smd, gz and tgz and I don't get odin to cominucate with the phone, ID COM never gets blue and Sammobile seems to be for Samsung phones
I would just perform a factory reset, wipe cache and dalvik cache. then try a reboot, if that doesn't work then you can mount the SD Card via mounts and storage> mount usb storage and then try a few different roms and if possible try find a stock recovery that someome else has posted and the correct Gapps. Try reflashing CWM too. Hope that helps
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Insight67 said:
I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Click to expand...
Click to collapse
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
billysam said:
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
Click to expand...
Click to collapse
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Insight67 said:
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Click to expand...
Click to collapse
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
billysam said:
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
Click to expand...
Click to collapse
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Insight67 said:
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
Click to expand...
Click to collapse
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
homephysician said:
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. I have tried that, but TWRP will not install. I am unable to install anything unfortunately.
billysam said:
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
Click to expand...
Click to collapse
Yeah, I figures it might be that. It makes sense as to why I can't install anything and why fastboot won't recognize the device. My confusion was that my laptop does recognize it as at p5110 device and I can access the drive and it's folders on my laptop. I just can't delete anything. I don't know of any viruses and I had only a few select video streaming apps on it. I tried the p5110 and the p5113 from sam mobile so if you know of any other stock firmware links or toolkits I would love to try them. I hate to get rid of a tablet that isn't really bricked.
Insight67 said:
I hate to get rid of a tablet that isn't really bricked.
Click to expand...
Click to collapse
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
billysam said:
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
Click to expand...
Click to collapse
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Insight67 said:
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Click to expand...
Click to collapse
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all all the p51xx, I was going through the same right now. so no chance of getting wrong pit partitioned.
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
That is a good idea. I have been using the same laptop for all of this. I will try a different PC and let you know how it goes.
Thanks again!!
billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
I tried a different computer but still got the fail from odin. If I come up with anything that works I'll be sure to post it. Thanks for all your help!
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
PanchoPlanet said:
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
Click to expand...
Click to collapse
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Insight67 said:
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
billysam said:
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
Click to expand...
Click to collapse
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Insight67 said:
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Click to expand...
Click to collapse
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
billysam said:
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
Click to expand...
Click to collapse
Thank you!
So after a few weeks after the launch of the Marshmallow uptade, I flashed the stock image with fastboot using a Mac and everything gone flawlessly, until I saw my internal storage. My 32Gb nexus became a 16Gb model.
I search in EVERY Forum I found on the internet, and I have good skills on recovering android phones with software problems, all the "how-to's" I found were with very easy instructions, but NONE of then worked for me.
Ive tried EVERYTHING I found on the internet. Do a factory reset, tried to resize the partition using TWRP, flashed manually all the partitions, flashed the stock image again and again many times, flashed customs roms, tried to erase the userdata, cache and system partitions tons of times using flashtool on windows, mac and linux and NOTHING worked. In all the process my phone started with no problems, but my internal storage stayed 12,55gb. My Bootloader shows 32Gb model, the IMEI on LG database shows 32Gb model AND the logic board indicates a 32Gb model... I really don't know what to do! Anyone can save me???? Thanks!
In advance information, I followed every step on this guide at least 10 times, and didn't work:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I was thinking in the possibility of an custom Userdata partition, only for the 32Gb model, that I can flash manually or a program, like GParted, that I can manually resize the data partition.
I'm really desesperate here, so sorry for any english mistakes, since I speak portuguese, or any dumb idea.
Thanks for any help!
-------------------------------------- FOUND THE SOLUTION! ----------------------------------------------
After WEEKS trying to realize what the hell happened and rethinking every possible form to regain my full storage, I've found the solution.
Fiddling with the partitions on the phone, i learned that there is a partition on the system, that "informs" the userdata that the phone is a 16Gb or a 32Gb variant, and it's called "Primary GPT".
I realized that the guy who sold to me, recovered the phone from an brick it suffered, but he used a 16Gb model GTP partition to reinstall the bootloaders and the system, so, no matter how many different process I tried, I would NEVER recognizes the 32Gb, because THIS partition was telling the system that it was a 16Gb model.
(Little of a noob explain but that was the way I got it...)
So all I had to do was use this thread to reflash the correct GPT partition:
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
And then, reflash the complete system image file, and after the boot, my phone recognized the 32Gb internal storage again!
Thank you guys for the effort in sorting out any way to help me, I hope this thread can help someone else facing the same problem in the future!
Peace!
Did you flash the userdata.img file too?
audit13 said:
Did you flash the userdata.img file too?
Click to expand...
Click to collapse
Tried everything I could do... Flashed userdata partition, erased the partition with fastboot then entered in recovery mode (stock and custom) and then format the userdata from there, doing that by doing a factory reset and wiping cache partition and nothing...
Any other idea what it could be?
Unfortunately, I have no idea why this happened or how to fix it as I only have the 16 GB version.
seriously guys, anybody to save my day?
audit13 said:
Unfortunately, I have no idea why this happened or how to fix it as I only have the 16 GB version.
Click to expand...
Click to collapse
Thanks anyway bro!
Have you tried factory reset and wiping cache from STOCK recovery? That always works for me.
Try using flash-all.bat in Windows. Part of the stock favor image. Make sure to take backup before doing it though
Had this happen once and had to factory reset from stock recovery like he said above. Worked like a charm!
redsmith said:
Have you tried factory reset and wiping cache from STOCK recovery? That always works for me.
Click to expand...
Click to collapse
shri_chanakya said:
Try using flash-all.bat in Windows. Part of the stock favor image. Make sure to take backup before doing it though
Click to expand...
Click to collapse
Nevermindthelabel said:
Had this happen once and had to factory reset from stock recovery like he said above. Worked like a charm!
Click to expand...
Click to collapse
Ive tried with stock recovery, custom recovery, CWM, TWRP Resize partition and no use...
I lost the count of times Ive tried to flash manually, flash-all.bat in windows, flash-all.sh on mac and linux, really nothing work.
There is no toolkit, even knowing its a bad idea to use those things but, since Im out of options, anyone can tell me one that can help me?
Thanks guys btw!
I had this problem with a couple devices on lollipop, typing the command below in a terminal fixed it. Reboot afterwards.
su
restorecon -FR /data/media/0
lynnux said:
I had this problem with a couple devices on lollipop, typing the command below in a terminal fixed it. Reboot afterwards.
su
restorecon -FR /data/media/0
Click to expand...
Click to collapse
can you explain what is the function of this line? Tried here and everything stayed the same
Thanks!
Damn... that's weird.
Is it possible to format userdata? Like, for example, "fastboot format userdata"? I don't really know, just shooting in the dark by this point now.
nameless-- said:
can you explain what is the function of this line? Tried here and everything stayed the same
Thanks!
Click to expand...
Click to collapse
I believe it's a way of restoring data or storage to it's original configuration. Also had this problem on my 32gb N5 early on, unfortunately I can't remember what I did that time to get it back.
redsmith said:
Damn... that's weird.
Is it possible to format userdata? Like, for example, "fastboot format userdata"? I don't really know, just shooting in the dark by this point now.
Click to expand...
Click to collapse
Yes, I did this process three times I think, format userdata and erase userdata, none of then resolved the issue
lynnux said:
I believe it's a way of restoring data or storage to it's original configuration. Also had this problem on my 32gb N5 early on, unfortunately I can't remember what I did that time to get it back.
Click to expand...
Click to collapse
I tried this code using the terminal on the phone, rebooted and the storage stayed the same, I'll try to do the same process using adb shell from my windows computer, since I have the "light"version of adb and fastboot installed on my mac and the adb shell comand is giving me the "offline" error...
I'll get back here with any updates.
thanks in advance guys! Hope this comand works! :highfive:
Well... Tried with my windows computer, and next with my Mac, with the command line given and.... Nope. Nothing changed.
I know it's not great but if your desperate....
I've always done things manually but there comes a time when your willing to try whatever to fix your phone as they don't come cheap, so if I could recommend a toolkit that has saved my ass more than once and has worked flawlessly for me every time maybe it could help you too.
http://www.wugfresh.com/nrt/
It's called Nexus Root Toolkit and its by the developer wugfresh. Try this if you'd like, if not I hope you find a solution. This kit has everything you can think of that could help you with rooting, or returning to stock and relocking. Best of luck with your journey!
MechanicalMecca said:
I've always done things manually but there comes a time when your willing to try whatever to fix your phone as they don't come cheap, so if I could recommend a toolkit that has saved my ass more than once and has worked flawlessly for me every time maybe it could help you too.
http://www.wugfresh.com/nrt/
It's called Nexus Root Toolkit and its by the developer wugfresh. Try this if you'd like, if not I hope you find a solution. This kit has everything you can think of that could help you with rooting, or returning to stock and relocking. Best of luck with your journey!
Click to expand...
Click to collapse
I'll try this as soon as possible, thanks!
Hey Nameless--,
I tried everything possible as you did, but when i tried your steps i am facing an issue. I cannot see Qualcomm HS-USB QDLoader 9008 under device manager
Can you help me?
Dhaval Raichura said:
Hey Nameless--,
I tried everything possible as you did, but when i tried your steps i am facing an issue. I cannot see Qualcomm HS-USB QDLoader 9008 under device manager
Can you help me?
Click to expand...
Click to collapse
The wrong size memory issue, 16 Gb instead of 32, is an old issue. It can be solved by booting into the stock recovery then clearing cache and then doing a factory reset. Note, this will wipe your device.
Sent from my Nexus 9 using XDA Free mobile app
Hey, i have oneplus 6.I have unlocked the bootloader,i have stock rom and my phone was rooted with magisk. Few days ago i unrooted my phone, clicked uninstall in magisk and it started unrooting. Then if it was done i clicked reboot and after that my phone was only able to boot into twrp. It couldnt boot into ROM.Nothing on the internet helped,so i flashed my stock ROM again (i was on my stock rom already) from flash drive. It went well and my phone booted up. But since that my phone doesn't show internal storage. In file manager it shows 10/128 GB used, but if i try to look into my storage it doesnt show anything. Also if i try to take photos, it cant,and i also cant download and update several apps in play store.
Can somebody help me? Can somebody explain what happened?Does somebody know how to fix it if its even possible?
Ty for help :')
It happens to me once. I think storage encryption is broken. try factory reset
kimmix05 said:
It happens to me once. I think storage encryption is broken. try factory reset
Click to expand...
Click to collapse
Hi kimmix, and thx trying to help. I havent done the factory reset yet, but i want to say that my phone doesnt have root either twrp anymore. Unlocked bootloader is ofc still there. Do i need to do factory reset from phone settings then(settings/system/recovery and resets/factory reset), somehow from my stock recovery or i need to put twrp again to my phone (from pc)?
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Hey, ty for help. I'm gonna try this as soon as possible :')
Hope it helps. Otherwise you always can use msmdownloadtool to fix issues.
abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Hey again, one little question. Did understand you correctly...
1. Put twrp again to device (i have done this for now)
2. Do factory reset (havent done)
3.Do 'fix contents' (havent done)
Ty for help
Zenquad said:
Hey, ty for help. I'm gonna try this as soon as possible :')
Click to expand...
Click to collapse
Zenquad said:
Hey again, one little question. Did understand you correctly...
1. Put twrp again to device (i have done this for now)
2. Do factory reset (havent done)
3.Do 'fix contents' (havent done)
Ty for help
Click to expand...
Click to collapse
Skip step 2 for now, if it does not help then sure flash oos on both slots then use fix contents again
abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Hey, sry for so many queations but...
I looked around in this forum and saw people having same-kind of problems. The replys told to do the 'format data'. Will it help my problem to be fixed?
And if it does, so i nees to just:
1. Boot to twrp
2. Select wipe then format data then confirmation
3. Then reboot
Is it just simple, am i missing some steps, please tell me. And thank you very much for help
abasba said:
Skip step 2 for now, if it does not help then sure flash oos on both slots then use fix contents again
Click to expand...
Click to collapse
Ty for answering, did you mean :
1. Boot to twrp
2. Do 'fix contents'
3. Boot to system
And if doesnt work then
1. Boot to twrp
2. Do factory reset
3. Flash stock rom to A
4. Boot to B
5. Flash stock rom to B
6. Wipe cache
7. Do 'fix contents'
8. Reboot
Am i right?
abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
Talking about 'fix contents'.
If i try do this it shows "it can cause system unable to boot up". Can you tell me, in wich situation or what can cause that after doing 'fix contents', device is not able to boot up.
Ty for help :')
abasba said:
Skip step 2 for now, if it does not help then sure flash oos on both slots then use fix contents again
Click to expand...
Click to collapse
And if 'format data' helps to fix this problem also then wich solution should i choose:
1. Fixing contents
2. Formating data
Zenquad said:
And if 'format data' helps to fix this problem also then wich solution should i choose:
1. Fixing contents
2. Formating data
Click to expand...
Click to collapse
I have no idea if formatting data helps or not actually. You can try it
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
Zenquad said:
Talking about 'fix contents'.
If i try do this it shows "it can cause system unable to boot up". Can you tell me, in wich situation or what can cause that after doing 'fix contents', device is not able to boot up.
Ty for help :')
Click to expand...
Click to collapse
I am not a dev nor I have no idea what does fix contents actually do. It just fixed my issue so I thought it could solve yours too
or you could just reflash stock rom from msmdownload tool to lessen the hassle lol.
blaspheme000 said:
or you could just reflash stock rom from msmdownload tool to lessen the hassle lol.
Click to expand...
Click to collapse
Hey, ok ill try )
abasba said:
This happened me a day or two ago.
Drove me really crazy, tried bunch of stuff flashing full zips over and over. Nothing fixed it.
Then inside twrp I used fix contents button (if I recall correctly it should be under advanced menu)
And that totally solved my problem, It should solve yours too.
Before factory resetting boot twrp via fastboot and try.
Hope this helps because that gave me some sleepless nights.
Click to expand...
Click to collapse
After decrypting the cell phone I have the same problem. I did what you suggested and it all turned out. Storage came back a thousand thanks
avirale123 said:
After decrypting the cell phone I have the same problem. I did what you suggested and it all turned out. Storage came back a thousand thanks
Click to expand...
Click to collapse
Hey, i saw 'fix contexts' fixed your problem. What is "phone decrypting" and how did you do that? Maybe i did something similar that made my internal storage "go away".
Zenquad said:
Hey, i saw 'fix contexts' fixed your problem. What is "phone decrypting" and how did you do that? Maybe i did something similar that made my internal storage "go away".
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
avirale123 said:
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
Click to expand...
Click to collapse
Hey again!
So i see you did that, what was in the instructions. And then your internal storage "was gone"? Then you did 'fix contexts'? Am i right?
Zenquad said:
Hey again!
So i see you did that, what was in the instructions. And then your internal storage "was gone"? Then you did 'fix contexts'? Am i right?
Click to expand...
Click to collapse
exactly. If it does not help you do not waste more time and use the tool to recover the system