Hi, first post here.
So I bought a Nexus S that was rooted and updated to Jellybean. It's an unlocked phone originally locked to Wind Mobile.
So it's been having issues with getting stuck on the google logo after reboot, so I decided to sell it. Problem is when I go to factory reset the phone it shows the reset bar but then that turns into a big triangle with an exclamation mark on it with a little android guy next to it. The phone gets stuck there. All I can do from there is remove the battery.
From there I tried going on bootloader using power and volume up (says unlocked btw), and from there I load recovery. On recovery there is an option to factory reset and I click on there, however it doesn't do it. This is what I says:
"--wiping data...
formatting /data...
E:format_volume: make_extf4fs failed on /dev/blo/ck/platform/s3c-sdhci.0/by-name/userdata
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/ .android_secure!
Skipping format...
Data wipe complete."
So I think the error might be accociated to the sd card because the Nexus S doesn't come with an sd card, it has built in memory? Also on recory when choose "mount sd card" it says"Error mounting /sdcard!".
So how do I go about fixing my problematic phone? I have a dude that wants to buy it but I can't even reset the damn thing, let alone fix the freezing at start up issue. I am also totally new to this.
Extra info: When the phone freezes at the google logo at start up I get passed that by using a blow dryer on the phone. That's the only way I start up the phone after the battery comes out. This is the gt-i9020t model.
Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!
gunner49 said:
Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!
Click to expand...
Click to collapse
I don't know if it's a custom recovery because the previous owner installed everything/rooted.
When I press power and vol. up, It looks identical to the uploaded picture's bootloader/recovery.
Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.
gunner49 said:
Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.
Click to expand...
Click to collapse
In advanced there is no option that worked.
*Solution*
Ok so for those having this problem this is what I dug up:
Internal SD card error causes the boot freeze/factory reset error. When you try mounting SD card it fails, this is also what makes me think it's a fault with the phone's internal SD card.
I do not know how to "fix" this fault, however I'll tell you what I did to get passed this issue.
1) Heating up the phone helps bypass the frozen screen. On Boot it goes to the google logo and freezes, but you can get passed this by heating up the phone (using a blow dryer) before hand and it's relatively successful.
2) I believe that before factory resetting the phone (whether using recovery or the actual reset option on settings), if you heat up the phone, it might work the same way it works when booting up.
I did not try 2) because I managed to "reset" my phone manually by uninstalling all apps, deleting all files/cache/photo's/accounts, and by clearing all app data. This works just as fine if you ask me.
Overall this solution has not been "fixed", I encourage people to find a real fix, but for now using the blow dryer and manually resetting is one way around the problem.
Related
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Have you tried to reinstall firmware?
Regards.
GReddySetGO said:
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Click to expand...
Click to collapse
No need to panic.
When you rooted, did you install CWM Recovery, and if so, do you have a recent nandroid backup? Have you tried rebooting into recovery?
What steps have you followed to get out of your bootloop?
Yes, I have Clockword Mod Recovery 3.2.0.0 R4c 100611-1150
Upon attempting a restore everything appears to work properly until the end when it gets to restoring data, I get an error, regardless of which restore image I use(I tried all the ones I have). It reads as follows:
"Restoring data...
Error removing /data/data/com.noshufou.android.su/cacheError while formatting /data!"
I also attempted a clean wipe/factory reset with similar unsuccessful results. I get an error during formatting data, which reads:
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheFormatting /cache..."
The rest of the formatting appears to run successful for /sd-ext and /sdcard
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
jerrycycle said:
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Can you please provide me with more detailed instructions?
From the advanced menu I see:
Reboot Recovery
Wipe Dalvik Cache
Wipe Battery Stats
Report Error
Key Test
Partition SD Card
Fix Permissions
Sorry, we're forgot talking about Cwm. It's under mounts and storage.
Still the same result as before... I went to mounts and storage > format /data
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheError formatting /data!"
Try format system first then data and cache.
My suggestion would be to go back to stock and then re-root. You can find the stock download on the Moto Dev home page.
+1. Restocking link. MOTODEV > Produ / Software http:/.ly/sQtpKQ bit cts > Device. Then use universal root method reroot.
Sent from my Xoom using Tapatalk
Thanks everyone! I was hoping I would be able to fix it without going back to stock, but since I was unable to I just went that route.
Going stock worked, and I am back to where I was before, so thank you for the advice! In case anyone else may have this problem, this is what I did:
Went back to stock using this: http://forum.xda-developers.com/showthread.php?t=1049485
Then rooted using this: http://forum.xda-developers.com/showthread.php?t=1242241
Then got back to 3.2.1 using this: http://forum.xda-developers.com/showthread.php?t=1278214
I hadn't touched my tab for a couple weeks since I only really use it in my car as a GPS and Entertainment center but when I grabbed it to charge it up, it was completed drained. No problem here since this has happened before and I'd just charge it up. So I boot it after the full recharge and it's stuck on the Samsung Galaxy Tab logo. After a little while I check it again and I'm like, "Crap, it's bricked. I'll need to reset it with Odin."
I proceed with Odin and nothing. It's still bricked. I do a factory reset and this is where I notice my big problem. When I do a factory reset or reboot I get
E:Can't open /data/log/recovery.txt
E:copy_kernel_file :: Can't open /data/log/recovery_kernel_log.txt
I tried reflashing the kernel, pit and firmware and I'm getting nowhere. What gives?
try removing the SD card and see if it boots up.
DigitalMD said:
try removing the SD card and see if it boots up.
Click to expand...
Click to collapse
Still no go but this did give me an idea. I just tried a simple reboot from recovery WITHOUT the SD card and got the error:
E:Failed to mount /sdcard
E: is the SDcard so I will create the directory with the files I mentioned above. I found the files on a different thread regarding a Samsung Galaxy phone. This may work.
I'm also going to try another flash without the SD installed to see if I have any luck there.
Thanks.
Issue is fixed
I decided to reflash while the SD card was removed and it got passed the initial splash screen. It was stuck at some wierd lock screen asking for a password. I went into recovery to do a wipe and factory reset and that brought the tablet back to life on reboot.
All is good again.
So, got the 4.4.2 update , downloaded it and then it asked for a reboot. I did reboot. I am completely stock , no root nothing. Now the update was installing but in the end I got error :/ the image was robot kinda looking like he had heart attack... anyways, it gave me 4 options, so i cliked volume button .. I don't know all the options but from the 2 of them, one was reboot and other was clear cache or something. I thought clearing cache may **** up something on phone so I tried scrolling back on the top.. but to my surprise from volume buttons phone didn't let me go up at all :/
I didn't had any choice but to choose clear cache.. I thought it may help. But it didn't... so I forced reboot it with power button hold for 10 seconds.. Now phone is working but no sim on it starts.. no signal whatsoever. If I try to open my gallery, it doesn't open. says "No storage, no external storage available" .. when I try to connect usb to phone and try to backup my pics and stuff from pc it doesn't open anything. PC does show "Internal memory" but there's nothing in it. My phone doesn't let me even use wifi. So I thought it was time to factory reset, but to my surprise when I click erase everything, it does nothing. So, I thought of rebooting and clicking "power+volume down" , still nothing.. it shows the same robot pic having heart attack... I doesn't have knowledge of root and stuff for now, I am a simple user of nexus 5 who is still on stock. Any help please? I am worried here now
Think you're gonna need to follow one of the guides to flash stock system again
Sent from my Nexus 5 using Tapatalk
nevermind. Working again.
What did you do to get it Woking I got mine in a box ready to RMA if you got a suggestions I'm open to try one more time beforrv I be without my phone for s long time
Sent from my Inspire 4G using Xparent Green Tapatalk 2
How did you get it working?? F**k mine has no signal at all too! Damn I am really pissed!
---------- Post added at 04:09 AM ---------- Previous post was at 03:59 AM ----------
I did a factory reset and its working now. What a headache Google!
Mistake 1: not allowing the phone adequate time to clear the cache when finished installing the ota. If you force the phone to restart during this process, it will corrupt your cache which causes all of those issues listed above (loss of signal, no baseband info, loss of access to mountable storage, etc).
Cache clearing takes considerably longer than on any other device I've owned prior to this phone, so messing with the phone during that important cache clearing process is the issue.
Mistake 2: reflashing the entire phone to stock. In the event you become impatient and decide to force your device to restart, you DONT HAVE TO revert to stock to get the phone working. What you have to do is restore functionality to the cache portion of the phone. All of your files are in fact still on the phone and accessible, you just have to unbreak your phone. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites), and then you fastboot flash the file in the boot loader (look up adb commands to do this). Once this is done, reboot the phone and everything should be hunky dory after your applications cache is rebuilt and android boots.
Note: you might need to check for root again. Also if you corrupted your cache you will have to set all of your ringtones and notifications again because this cache corruption process unlinked the ability of yours apps that use notifications to "see" the sound files you have on your SD card.
Sent from my Nexus 5 using xda app-developers app
delete
What a savior ... wiped the cache again , gave adequate time this time and it booted again fine
I had the exact same problem! Cleared cache in recovery mode in 4.4.4 and then thought it stalled because it was running for 1 minute (which normally took 2 seconds in previous devices) so I forced a restart. Then I had all sorts of errors: couldn't connect with my SIM card, couldn't download our see my pictures, screen rotation but working, constant Google Playstore crash popups, and more.. I thought I'd bricked it. A few more attempts to clear cache in recovery mode, still took longer than 1 minute (also the same errors in my recovery mode like stated above: "E: failed to mount /cache" ... that sort of things)
A few days later I'd had it. My steps for the SOLUTION:
1. Cleared cache in my settings: settings -> storage -> cache (don't know if this has influenced the outcome but I did it).
2. Went back to recovery mode, errors still displaying, but tried again to clear cache. The only difference now was that I left it running without touching my Nexus 5 for about 10 MINUTES(!).
..........To my surprise it ended with "clearing cash complete" WOW! So I rebooted and everything worked fine again! The only thing was that I had to set some notification sound again. That wasn't too hard
Let me know if it helped in your case
xybur said:
Mistake 1: not allowing the phone adequate time to clear the cache when finished installing the ota. If you force the phone to restart during this process, it will corrupt your cache which causes all of those issues listed above (loss of signal, no baseband info, loss of access to mountable storage, etc).
Cache clearing takes considerably longer than on any other device I've owned prior to this phone, so messing with the phone during that important cache clearing process is the issue.
Mistake 2: reflashing the entire phone to stock. In the event you become impatient and decide to force your device to restart, you DONT HAVE TO revert to stock to get the phone working. What you have to do is restore functionality to the cache portion of the phone. All of your files are in fact still on the phone and accessible, you just have to unbreak your phone. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites), and then you fastboot flash the file in the boot loader (look up adb commands to do this). Once this is done, reboot the phone and everything should be hunky dory after your applications cache is rebuilt and android boots.
Note: you might need to check for root again. Also if you corrupted your cache you will have to set all of your ringtones and notifications again because this cache corruption process unlinked the ability of yours apps that use notifications to "see" the sound files you have on your SD card.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I did that. The fastboot flash cache.img and still have the error...
Try flashing a stock rom, including the userdata.img file. Flash the userdata file last, right after flashing, boot into recovery and perform a factory reset.
. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites),
where to get the cache.img from.
i have searched the folder of the stock rom after extraction,couldn't find one.
and my phone is soft bricked.
also its a asus zenfone 5(501 cg) with 4.4.2 not a nexus but with similar problem(rebooted phone without waiting for cache wipe to finish )
please reply asap
thanks
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
I'm still stuck in this situation...
Any help plz?
IYaWonaRoo said:
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
Click to expand...
Click to collapse
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
savagevegeta said:
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
Click to expand...
Click to collapse
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
IYaWonaRoo said:
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
Click to expand...
Click to collapse
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
savagevegeta said:
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
Click to expand...
Click to collapse
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
IYaWonaRoo said:
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
Click to expand...
Click to collapse
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
savagevegeta said:
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
Click to expand...
Click to collapse
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
IYaWonaRoo said:
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
Click to expand...
Click to collapse
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
savagevegeta said:
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
Click to expand...
Click to collapse
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
IYaWonaRoo said:
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
Click to expand...
Click to collapse
The steps to fix storage 0mb are clearly posted in the TWRP thread.
ashyx said:
The steps to fix storage 0mb are clearly posted in the TWRP thread.
Click to expand...
Click to collapse
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
IYaWonaRoo said:
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
Click to expand...
Click to collapse
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
ashyx said:
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
Click to expand...
Click to collapse
I probably was doing it wrong lol. But its fixed now so dont worry
IYaWonaRoo said:
I probably was doing it wrong lol. But its fixed now so dont worry
Click to expand...
Click to collapse
Your data partition will still be unmountable and remain 0mb, which means you are unable to make a backup.
However if you're happy with it in that state...
Re: bootloop
have you tried grabbing the no verity/encrypt form the rooting forum, this solves seandroid problem
Hello,
Anyone else having problems after this update? I did it now and my phone does not start anymore. Or at least it hangs in the loading screen with the red and 2 white dots.
I shut it down with power and vol + twice but with no effect. It does not react on the power cable being inserted. When it's powered off and I insert the cable it starts to the loading screen, currently showing 14 %.
How to solve this?
Thank you!
I can boot into recovery or fastboot. Not sure how helpful that is though.
try to format data if you're able to go to recovery. as long you have recovery and fastboot intact, it's basically not ****ed up yet
dewa5227 said:
try to format data if you're able to go to recovery. as long you have recovery and fastboot intact, it's basically not ****ed up yet
Click to expand...
Click to collapse
But how can I save my data? I mean when I'm in recovery I have to enter the password before, so the data gets decrypted. But with USB attached I can only see 5 files on my desktop computer.
I emptied the battery and loaded it fully, then restarted. After a long time it say "This device has entered an unstable state. Please try rebooting your device using the exit button below..." and so on.
I hope a data recovery company isn't the only solution.
Also, is there no way to repair it? Like running the update again or something?
Why is there no „apply update from adb“ option in the recovery menu of OnePlus? Apparently I could have used that to backup all my data from the phone.
I tried wiping the cache partition without success so far.
So did Android squeeze security so much that not even the owner can save his data in this status now anymore? A bit sad when they themself break the phone with an update then.
What about these recovery services that also recover data from harddrives? Do they break the phone when they do their thing?