Related
I've just done the JB update on my TF700, and it's now dead... :crying:
Update downloaded OK, went into the update process. Seemed to go fine. Did the "Optimising applications" bit, rebooted, and stuck on the boot screen with the spinnywheel.
I let that run for half-an-hour (tablet was getting very warm) then did a paper-clip reset (no response to buttons). Same thing, won't boot.
It's an unmodded device apart from being rooted. I've encrypted the storage; I've set the default browser to Dolphin. I have Titanium installed, but not frozen any apps.
Suggestions for how to recver from this gratefully received ....
Thanks
Alan
[UPDATE: Oh, and I did not have the tablet in the dock when I updated. Significant??]
Same problem here. Please help!!
Did the update and it went all ok.. untill first reboot (stuck on boot screen with the spinnywheel).
Unmodded rooted device. Tried cold boot, but nothing changes.
Tried to download some files for recovery and didn´t work:
TF700T WW_10.4.4.16-20120927 OTA.zip
WW_epad-user-9.4.5.30.zip
any ideas?
Piruelo said:
Same problem here. Please help!!
Did the update and it went all ok.. untill first reboot (stuck on boot screen with the spinnywheel).
Unmodded rooted device. Tried cold boot, but nothing changes.
Tried to download some files for recovery and didn´t work:
TF700T WW_10.4.4.16-20120927 OTA.zip
WW_epad-user-9.4.5.30.zip
any ideas?
Click to expand...
Click to collapse
try booting into bootloader and selecting the "wipe data" option. This will delete all your files on the devices but will also mean you can use it again
Piruelo said:
Same problem here. Please help!!
Did the update and it went all ok.. untill first reboot (stuck on boot screen with the spinnywheel).
Unmodded rooted device. Tried cold boot, but nothing changes.
Tried to download some files for recovery and didn´t work:
TF700T WW_10.4.4.16-20120927 OTA.zip
WW_epad-user-9.4.5.30.zip
any ideas?
Click to expand...
Click to collapse
To recover from that just wait until Asus post the full JB update on their site and use that to do a Factory Restore with stock recovery (follow the how-to guide in my signature for more details).
Thanks!!
Will the 'Factory Restore with stock recovery' erase my internal storage?
Piruelo said:
Thanks!!
Will the 'Factory Restore with stock recovery' erase my internal storage?
Click to expand...
Click to collapse
It shouldn't wipe the sdcard, only the Wipe Data option from the stock recovery should do that.
Pretoriano80 said:
To recover from that just wait until Asus post the full JB update on their site and use that to do a Factory Restore with stock recovery (follow the how-to guide in my signature for more details).
Click to expand...
Click to collapse
Thanks for that.
A newbie question, though (I'm a Windows dev, and Android is quite new to me) - what would happen if did this with the .30 ICS firmware with the device in this state?
SpooRancher said:
Thanks for that.
A newbie question, though (I'm a Windows dev, and Android is quite new to me) - what would happen if did this with the .30 ICS firmware with the device in this state?
Click to expand...
Click to collapse
You can try to do that,but i guess it will just fail to install...You could also try the "Wipe Data" thing from the recovery ,but i don't think it will work.
Pretoriano80 said:
You can try to do that,but i guess it will just fail to install...You could also try the "Wipe Data" thing from the recovery ,but i don't think it will work.
Click to expand...
Click to collapse
OK, many thanks. I'll give it a go - otherwise it's just wait for Asus to post the files
SpooRancher said:
I've just done the JB update on my TF700, and it's now dead... :crying:
Update downloaded OK, went into the update process. Seemed to go fine. Did the "Optimising applications" bit, rebooted, and stuck on the boot screen with the spinnywheel.
I let that run for half-an-hour (tablet was getting very warm) then did a paper-clip reset (no response to buttons). Same thing, won't boot.
...
Click to expand...
Click to collapse
I have the same exact problem.
Most probably, it's because of the encryption.
Perhaps ASUS thought that nobody would use Android encryption ...
i have exactly the same problem, was stock and only rooted. i did a backup with titanium backup and one of my internal sdcard via the dock sdcard and adb now but i'm still trying to find a way to boot without wiping because i fear that i will lose root and so goes my titanium backup..
anyways, it seems i've got adb access (no root because su crashes) during this neverending spinning wheel. i've dumped logcat during the boot process. maybe someone has a suggestion what's wrong here? i have a good understanding of linux but not the logcat output or android boot phase. it seems many services can't find files and many things fail (wifi, gps, tethering, ...), no idea if that's also the case for a valid boot, and then after some time nearly all services die.
logcat part1: http://pastebin.com/HTSULj59
logcat part2: http://pastebin.com/ncgjzwsY
logcat part3: http://pastebin.com/071hWwRm
i also tried to wipe cache via fastboot, but it didn't help.
i also think it has to do with encryption because it says something like:
"E/VoldConnector( 401): NDC Command {6 cryptfs checkpw $pwd} took too long (10418ms)" and then services get restarted or die
Oops
0x000 said:
i also think it has to do with encryption because it says something like:
"E/VoldConnector( 401): NDC Command {6 cryptfs checkpw $pwd} took too long (10418ms)" and then services get restarted or die
Click to expand...
Click to collapse
Does this imply that it's not possible to recover from this without completely resetting the SD card? Does a Wipe Data do that?
Two extra things I've thought of here: I changed the encryption password from screen lock PIN to something else with EncPasswdChange; however, the "enter encryption password" screen accepted the correct password and rejected anything else. I also have BusyBox installed.
Personally I'm not bothered about having to reset everything - I'm sure JB will be rootable soon, and I have no data I care about. Very annoying for those that do have valuable stuff, though.
ASUS have the JB files on their website now (US and WW SKUs) [Sorry, system won't let me post a link...]
Downloaded from asus, renamed to 'EP201_768_SDUPDATE.zip' in microsd card,and succesfully unbriked, without loosing any data :victory:
Updated fine. Rebooted fine.
Stock, locked and rooted. Supersu+voodoo, unencrypted.
After update I had extreme laggyness only after a sleep. Cold boot seems to have fixed that.
I would like to encrypt. Has anyone successfully encrypted AFTER updating?
I've managed to unbrick mine too
However I had to do a Wipe Data - trying without gave me the dead android with the red triangle as soon as the upgrade started.
Never mind, it's back and running JB. There wasn't any data on it I cared about, so apart from losing root I'm happy.
Thanks for all the advice, everyone. Very much appreciated.
i've also tried to fix the problem in recovery by using the zip file posted on the asus servers. it did something, had some blue progress bar, then it rebooted, had to enter my encryption password and.. it did not work :crying: still spinning wheel and it hangs. i can still use adb, my old su binary is gone, but i'm stuck as i don't want to wipe my data. i need root for using titanium backup again. and yeah, i don't want to unlock for now too :/
did it work for anyone who has their tablet encrypted?
[edit]
i've tried to downgrade to ICS .30 firmware via recovery method and it worked (although i'm not unlocked). it did wipe my whole data though and the tablet is not encrypted anymore. at least i can root again now, upgrade to JB and then encrypt (i hope..)
[/edit]
Piruelo said:
Downloaded from asus, renamed to 'EP201_768_SDUPDATE.zip' in microsd card,and succesfully unbriked, without loosing any data :victory:
Click to expand...
Click to collapse
was your internal storage encrypted?
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
0x000 said:
...
i've tried to downgrade to ICS .30 firmware via recovery method and it worked (although i'm not unlocked). it did wipe my whole data though and the tablet is not encrypted anymore. at least i can root again now, upgrade to JB and then encrypt (i hope..)
Click to expand...
Click to collapse
How did u downgrade to ICS?
did u placed the .zip from asus again in sd card and powered on with pressing volume donw?
How did u downgrade to ICS?
did u placed the .zip from asus again in sd card and powered on with pressing volume donw?
Click to expand...
Click to collapse
yes, i placed the (extracted & renamed) zip from asus to my external microsd card and used stock recovery (volume down).
i've already installed JB now with root and i'm currently restoring my apps with titanium backup
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Justintoxicated said:
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Click to expand...
Click to collapse
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
dottat said:
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
Click to expand...
Click to collapse
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Justintoxicated said:
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Click to expand...
Click to collapse
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
dottat said:
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
Click to expand...
Click to collapse
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though. I did not install lolipop because I need to get the phone to USB mode to copy it over, which I cannot do because it will not start up.
Justintoxicated said:
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though.
Click to expand...
Click to collapse
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
dottat said:
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
Click to expand...
Click to collapse
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
TWRP is now version 2.8.5.0, so apparently it updated correctly (I think before it was 2.8.1)
Justintoxicated said:
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
Click to expand...
Click to collapse
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
dottat said:
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
Click to expand...
Click to collapse
Ok my internet is not working on my laptop at work (only of the PC I'm on and no way to transfer files without my phone), so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Justintoxicated said:
Ok my internet is not working on my laptop at work, so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Click to expand...
Click to collapse
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
dottat said:
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
Click to expand...
Click to collapse
Update, restarted the computer and I was able to restore the old firmware. I re-installed the old rom afterwards (not my nandroid) and I am unable to get into the OS. Well technically I get prompted to select a language, after which the phone reboots back to the S-off androids with skateboards bootloader. Does this mean my phone is toast?
Hey guys, should I S-on the phone load the stock bootloader and try to return it? It is over a year old so I think I will need to use my insurance ($100). What is the best way to go about doing this?
Also when I get my replacement phone will there still be a way to S-off?
Thanks,
- Jusitn
The problem appears to be something wrong with my micro SD card! I removed the micro SD card and I can boot up fine. I guess I need to find another way to copy the rom to the micro SD install the rom then remove the micro SD card.
edit:
Oh this is worse than paying $100 for a new phone. It appears that creating a backup instead of creating a backup, actually corrupted my memory card. Now all the photos are backed up to the cloud but it will take me hours and hours to get all my apps back to the way they were. Some Security camera settings, Rifle target hand load development all gone. Audio book place holders, all notes taken etc. Nothing life or death but those security cameras will take me forever to figure out. I know I know, why not create a backup right? Well that's what I was trying to do!
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Justintoxicated said:
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Click to expand...
Click to collapse
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
robocuff said:
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
Click to expand...
Click to collapse
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Justintoxicated said:
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Click to expand...
Click to collapse
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
dottat said:
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
Click to expand...
Click to collapse
I don't remember, probably missing a file or something.
what i did so far. used odin to flash h1 baseband rom so i can root. rooted with cydia. downloaded e-z recovery. installed cwm. that didnt read my storage and nothing in it would work. installed twrp with e-z recovery. same problem.(edit: when I got to twrp it said "no o.s. found" so I then had to reboot into download mode and flashed the stock rom) Then downloaded android terminal emulator. downloaded cwm and installed by typing in the commands. got into cwm and made a backup. wiped data, cache, dalvik. tried to install "cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte". it installed but went into a boot loop and would end up back at cwm every time. wiped data, factory reset, restored backup. tried again, same thing, restored again. tried installing "cm-12.1-20150915-NIGHTLY-d2vzw" this time. it got stuck saying "patching system image unconditionally.....". wiped data, restored stock, tried again this time with "cm-10.0.0-d2vzw". it didnt even install. now im restoring again to stock.
the reason im trying vzw roms also is because i have a verizon note 2 on straight talk and was gonna try to use that sim card in my s3.
http://forum.xda-developers.com/galaxy-s3-verizon/help/straight-talk-sch-s986c-t3036314/page3
^^this thread has some info about it but im new here and havent found anything else about it. before i try getting it to work with my verizon cdma sim card i at least would like to just get cyanogenmod working on my s3.
am i using the wrong roms? is this in the right forum?
thanks
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
cory733 said:
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
Click to expand...
Click to collapse
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mount our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Droidriven said:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mou t our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Click to expand...
Click to collapse
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?
i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.
i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.
also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.
btw this phone has android 4.1.2
cory733 said:
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?
i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.
i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.
also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.
btw this phone has android 4.1.2
Click to expand...
Click to collapse
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.
If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.
SuperSU won't show as an app, its built in to system settings.
Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.
Yes, the 3G disappears when you don't have service and need to renew time on the device.
Here is the TWRP for d2tfnvzw
https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu
Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
Droidriven said:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mou t our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Click to expand...
Click to collapse
Droidriven said:
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.
If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.
SuperSU won't show as an app, its built in to system settings.
Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.
Yes, the 3G disappears when you don't have service and need to renew time on the device.
Here is the TWRP for d2tfnvzw
https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu
Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
Click to expand...
Click to collapse
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)
i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.
since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
cory733 said:
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)
i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.
since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
Click to expand...
Click to collapse
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.
Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.
Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.
The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.
Is any of this making any sense yet?
I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
Droidriven said:
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.
Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.
Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.
The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.
Is any of this making any sense yet?
I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
Click to expand...
Click to collapse
yeah i dont use verizon its just a verizon phone on straight talk.
my copy of the stock rom is this one that im sure youve seen before
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.
so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
cory733 said:
yeah i dont use verizon its just a verizon phone on straight talk.
my copy of the stock rom is this one that im sure youve seen before
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.
so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
Click to expand...
Click to collapse
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.
I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.
If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
Droidriven said:
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.
I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.
If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
Click to expand...
Click to collapse
kinda forgot about this project for a while but decided to finish it. i installed the version of TWRP you showed me and it and cyanogenmod installed just fine this time. i actually just installed this twrp from twrp itself. tried putting the sim from my note 2 in my s3 just to try. it didnt work. i didnt dial *288 or anything. but i ordered another sim. will see if everything works when i get the sim.
thanks for your help
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it
edit: works when enabling advanced reboot options and rebooting to recovery from phone
cory733 said:
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it
edit: works when enabling advanced reboot options and rebooting to recovery from phone
Click to expand...
Click to collapse
Hmm, sounds fishy. Try going back to the TWRP you already had if it worked fine, why the d2tfnvzw is acting funny I couldn't tell you. When you put the SIM in it the ROM should work without having to do anything, dialing *228 and setting APNs is only to get MMS working and only works with the Verizon 4G LTE SIM that I know of.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Hmm, sounds fishy. Try going back to the TWRP you already had if it worked fine, why the d2tfnvzw is acting funny I couldn't tell you. When you put the SIM in it the ROM should work without having to do anything, dialing *228 and setting APNs is only to get MMS working and only works with the Verizon 4G LTE SIM that I know of.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
the twrp i had before couldnt install cm correctly for some reason. now that im on cm12 can i still install that twrp?
the rom seems to be working fine, i can still get into everything else without the sim, it just says no sim. With that sim i didnt get service, i got the "welcome to verizon wireless" when trying to make a call. installing apps seems slow.
somehow ive lost root. supersu wont install the binaries either, im gonna try to figure out how to do that with twrp.
cory733 said:
the twrp i had before couldnt install cm correctly for some reason. now that im on cm12 can i still install that twrp?
the rom seems to be working fine, i can still get into everything else without the sim, it just says no sim. With that sim i didnt get service, i got the "welcome to verizon wireless" when trying to make a call. installing apps seems slow.
somehow ive lost root. supersu wont install the binaries either, im gonna try to figure out how to do that with twrp.
Click to expand...
Click to collapse
As for your root being gone, its probably not, you've got to go into developer settings and set root access to "apps and adb", do that and verify whether you have root after that, also get ES file explorer and set your mount permissions to R/W
If the SIM is a Verizon SIM it should work.
I recommend flashing the newest OctOS d2vzw CM12 has always been too buggy in my opinion, OctOS is super stable, its the best ROM out if all the d2vzw ROMs. The SIM will probably work with OctOS, myself and hundreds of others have been using it with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
As for your root being gone, its probably not, you've got to go into developer settings and set root access to "apps and adb", do that and verify whether you have root after that, also get ES file explorer and set your mount permissions to R/W
If the SIM is a Verizon SIM it should work.
I recommend flashing the newest OctOS d2vzw CM12 has always been too buggy in my opinion, OctOS is super stable, its the best ROM out if all the d2vzw ROMs. The SIM will probably work with OctOS, myself and hundreds of others have been using it with no issues.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ok cool got root, you were right, the root access setting was set to disabled. the sim is a straight talk CDMA for verizon. its from the bring your own phone sim card kit that has sims for every carrier. i didnt want to try *288 since you said it could ruin it for my Note 2. but another one is on the way theyre $1.07 from walmarts website.
do you have a link for octos? its based off cm12? im also trying to get an app called drivedroid to work since i cant do much with my note 2's useless locked bootloader. google search for OctOs is bringing me to liquidsmooth.
cory733 said:
ok cool got root, you were right, the root access setting was set to disabled. the sim is a straight talk CDMA for verizon. its from the bring your own phone sim card kit that has sims for every carrier. i didnt want to try *288 since you said it could ruin it for my Note 2. but another one is on the way theyre $1.07 from walmarts website.
do you have a link for octos? its based off cm12? im also trying to get an app called drivedroid to work since i cant do much with my note 2's useless locked bootloader. google search for OctOs is bringing me to liquidsmooth.
Click to expand...
Click to collapse
teamoctos.com ,find the download page and get the newest d2vzw.
I'm not sure that the straight talk SIM will work like the actual Verizon SIM does, in the year that I've been following development on this device I've seen no posts that say the ST BYOP 4G SIM works. I recommend an actual Verizon one, they are only $2-4 on eBay, that's cheaper than the ST SIM and guaranteed to work.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
teamoctos.com ,find the download page and get the newest d2vzw.
I'm not sure that the straight talk SIM will work like the actual Verizon SIM does, in the year that I've been following development on this device I've seen no posts that say the ST BYOP 4G SIM works. I recommend an actual Verizon one, they are only $2-4 on eBay, that's cheaper than the ST SIM and guaranteed to work.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
should i try switching TWRP's before installing this rom?
cory733 said:
should i try switching TWRP's before installing this rom?
Click to expand...
Click to collapse
No, try the d2tfnvzw one first
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, try the d2tfnvzw one first
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ok im on OctOs now. stayed with the same TWRP d2tfnvzw version. Same thing with the sim. "welcome to verizon wireless, your mobile number is either not active, or invalid" does *228 do anything besides getting mms to work?
edit: the signal bar icon has a ! in it and when i click on it it says Verizon Wireless 2 GB warning
cory733 said:
ok im on OctOs now. stayed with the same TWRP d2tfnvzw version. Same thing with the sim. "welcome to verizon wireless, your mobile number is either not active, or invalid" does *228 do anything besides getting mms to work?
Click to expand...
Click to collapse
It is supposed to auto program the SIM. I'm not sure it will work on the ST SIM, I know it works for the Verizon SIM, don't try it on the ST SIM, I might fry it and make it useless.
Verify you still have IME, has the phone itself been activated on straight talk, your IMEI has to be registered and activated on the straight talk network. Are you showing any signal bars or the 3G symbol?
Sent from my SCH-I535 using Tapatalk
Hi,
My phone and all my personal data (4 years of photos, videos, and other app data) just got WIPED.
Here's how it happened:
* I was on OS 5.1.5 till yesterday. Had TWRP as my recovery and Magisk as my root method. Everything was hunky dory.
* Oxygen OS 5.1.6 hit my phone today. I downloaded the update and installed it. Before installing - it clearly stated that my phone will be unrooted by the update. I was ok with that, as I would have simply installed Magisk again from TWRP.
* After the reboot, I opened Magisk manager and saw that Magisk wasn't installed.
* So I did a reboot to recovery from the phone's reboot options (advanced reboot was ON in developer options)
* It did not boot to TWRP. Instead, I saw a stock recovery type screen (black background, OnePlus logo).
* There was a single text called "Decrypt" and a terminal type basic keyboard displayed on the screen.
* At this point I knew TWRP is gone and this would definitely be the stock recovery, asking me for my PIN, to decrypt storage.
* I entered my PIN and pressed ok. IMMEDIATELY after that the screen displayed the message - "Wiping" along with "do not turn off your device while this happens" or similar.
* I was shocked to see this, as all I had done was enter my PIN in a stock-looking recovery with the OnePlus logo.
* The phone rebooted, and lo and behold - I see the new installation screen saying "Hello" to me!
ALL MY DATA IS GONE. Without any fault of mine! I simply did an OS update, and boot to recovery!
PLEASE HELP!
So you went 4 years without doing a backup? I think your out of luck.
First, I am pretty sure all your data is gone absent some expensive recovery.
Second, when you took the ota, you went back to stock, which is why twrp and magisk disappeared. This is actually how the system is supposed to work.
I don't know what you did in the stock recovery to cause a wipe. You should have rebooted to bootloader and reinstalled twrp from fastboot.
iElvis said:
First, I am pretty sure all your data is gone absent some expensive recovery.
Click to expand...
Click to collapse
is it possible to recover encrypted storage on an android? i have simply turned the phone off immediately on seeing the new install screen boot up.
iElvis said:
Second, when you took the ota, you went back to stock, which is why twrp and magisk disappeared. This is actually how the system is supposed to work.
Click to expand...
Click to collapse
Fair enough. I knew that.
iElvis said:
I don't know what you did in the stock recovery to cause a wipe. You should have rebooted to bootloader and reinstalled twrp from fastboot.
Click to expand...
Click to collapse
This is exactly where it's just crazy wrong. It just booted up to a recovery, with a screen saying "Decrypt" and a keyboard! NO mention of the next step being "Wiping".. ! This is just plain crazy, if that's how its designed!
94burns said:
So you went 4 years without doing a backup? I think your out of luck.
Click to expand...
Click to collapse
pretty much. was just migrating data from one phone to the next using titanium backup/restore.
How could 4 years of photos and vids be gone? The phone is only weeks old. Surely you have backed these up to a cloud or even a pc at some stage? If you habe data backup turned on, you should have all your apps ready to reinstall.
You should have booted into bootloader, flashed twrp and magisk after the update. The OTA will always resort any custom recovery to stock.
hallo dare said:
How could 4 years of photos and vids be gone? The phone is only weeks old.
Click to expand...
Click to collapse
I just kept migrating it from the previous phones to the next phones. Google photos does have backup of photos and videos. But there was so much more: SMS, call logs, whatsapp photos (the ones which were unlinked due to being moved to SD card earlier), screenshots, voice recordings, telegram images/videos, google authenticator tokens, and many apps whose data doesn't get backed up as part of android/google backup.
angadsingh said:
is it possible to recover encrypted storage on an android? i have simply turned the phone off immediately on seeing the new install screen boot up.
This is exactly where it's just crazy wrong. It just booted up to a recovery, with a screen saying "Decrypt" and a keyboard! NO mention of the next step being "Wiping".. ! This is just plain crazy, if that's how its designed!
Click to expand...
Click to collapse
I don't have answers for either question. You might have more luck posting in the OP community, or in the official firmware thread.
angadsingh said:
Hi,
My phone and all my personal data (4 years of photos, videos, and other app data) just got WIPED.
Here's how it happened:
* I was on OS 5.1.5 till yesterday. Had TWRP as my recovery and Magisk as my root method. Everything was hunky dory.
* Oxygen OS 5.1.6 hit my phone today. I downloaded the update and installed it. Before installing - it clearly stated that my phone will be unrooted by the update. I was ok with that, as I would have simply installed Magisk again from TWRP.
* After the reboot, I opened Magisk manager and saw that Magisk wasn't installed.
* So I did a reboot to recovery from the phone's reboot options (advanced reboot was ON in developer options)
* It did not boot to TWRP. Instead, I saw a stock recovery type screen (black background, OnePlus logo).
* There was a single text called "Decrypt" and a terminal type basic keyboard displayed on the screen.
* At this point I knew TWRP is gone and this would definitely be the stock recovery, asking me for my PIN, to decrypt storage.
* I entered my PIN and pressed ok. IMMEDIATELY after that the screen displayed the message - "Wiping" along with "do not turn off your device while this happens" or similar.
* I was shocked to see this, as all I had done was enter my PIN in a stock-looking recovery with the OnePlus logo.
* The phone rebooted, and lo and behold - I see the new installation screen saying "Hello" to me!
ALL MY DATA IS GONE. Without any fault of mine! I simply did an OS update, and boot to recovery!
PLEASE HELP!
Click to expand...
Click to collapse
You have a rooted device with a custom recovery so how did you install those in the first place and not loose data then? That wipes your phone doing that. It wiped again because it was being unlocked and relocked that always wipes it. Don't claim this is no fault of your own your running a modified device so yes it is your fault don't come on here and play victim it's really annoying
---------- Post added at 11:50 AM ---------- Previous post was at 11:47 AM ----------
94burns said:
So you went 4 years without doing a backup? I think your out of luck.
Click to expand...
Click to collapse
Wants to go 4 years without a backup then mod his phone and claim it's not his fault he lost data ??? what a joke
That happened to me too, but I solved it because after I flashed stock and then upgraded to 5.1.6 I installed TWRP in fastboot before booting to recovery.
angadsingh said:
I just kept migrating it from the previous phones to the next phones. Google photos does have backup of photos and videos. But there was so much more: SMS, call logs, whatsapp photos (the ones which were unlinked due to being moved to SD card earlier), screenshots, voice recordings, telegram images/videos, google authenticator tokens, and many apps whose data doesn't get backed up as part of android/google backup.
Click to expand...
Click to collapse
Surely you have those titanium backup files though still right? Just restore from that, sure you may lose a week or two but it's better than 4 years.
Sent from my ONEPLUS A6003 using Tapatalk
TechOut said:
You have a rooted device with a custom recovery so how did you install those in the first place and not loose data then? That wipes your phone doing that. It wiped again because it was being unlocked and relocked that always wipes it. Don't claim this is no fault of your own your running a modified device so yes it is your fault don't come on here and play victim it's really annoying
Click to expand...
Click to collapse
Android is supposed to wipe data only on unlocking the device. Once it's unlocked there's no reason Android should automatically wipe data.
It did not get relocked. It is still unlocked. How did you come to that conclusion?
Also, I root my device ONLY to install TitaniumBackup and Helium. I do not meddle with anything else being root (no ROMs, tweaks, etc.). Is it my fault that Android STILL doesn't have a way to backup everything without having to root your phone and install special backup apps?
How can the OS just wipe the data partition without user consent? With NO message displayed whatsoever. Just ask a password go on "Wiping.. please wait". What the hell.
geoff5093 said:
Surely you have those titanium backup files though still right? Just restore from that, sure you may lose a week or two but it's better than 4 years.
Click to expand...
Click to collapse
Yes I could recover some data from the SD card of my previous phone. Not the TB backups though.
I really need a way to (a) image the phone so that I can possibly recover/pay for recovery in the future (b) recover the data from the phone
I did a little reading. Apparently forced encryption is something that Android Oreo comes along with. All the data files are now by default encrypted (at a file level not a partition level). It is apparently encrypted with some randomly generated encryption key decided by Android, and not the PIN you have set to lock the phone. The PIN is just associated with that key. I'm pretty sure that key got deleted as well when the device was wiped (I'm assuming it must have been implemented like that as a security measure). So I have a wiped data partition with encrypted files!
NateDev said:
That happened to me too, but I solved it because after I flashed stock and then upgraded to 5.1.6 I installed TWRP in fastboot before booting to recovery.
Click to expand...
Click to collapse
You knew the data partition would get wiped otherwise? I've been rooting for years and never seen such behavior
angadsingh said:
Yes I could recover some data from the SD card of my previous phone. Not the TB backups though.
I really need a way to (a) image the phone so that I can possibly recover/pay for recovery in the future (b) recover the data from the phone
I did a little reading. Apparently forced encryption is something that Android Oreo comes along with. All the data files are now by default encrypted (at a file level not a partition level). It is apparently encrypted with some randomly generated encryption key decided by Android, and not the PIN you have set to lock the phone. The PIN is just associated with that key. I'm pretty sure that key got deleted as well when the device was wiped (I'm assuming it must have been implemented like that as a security measure). So I have a wiped data partition with encrypted files!
You knew the data partition would get wiped otherwise? I've been rooting for years and never seen such behavior
Click to expand...
Click to collapse
Take this as a lesson, always have a backup. Especially if you mod your phones
Sent from my ONEPLUS A6003 using Tapatalk
angadsingh said:
Android is supposed to wipe data only on unlocking the device. Once it's unlocked there's no reason Android should automatically wipe data.
It did not get relocked. It is still unlocked. How did you come to that conclusion?
Also, I root my device ONLY to install TitaniumBackup and Helium. I do not meddle with anything else being root (no ROMs, tweaks, etc.). Is it my fault that Android STILL doesn't have a way to backup everything without having to root your phone and install special backup apps?
How can the OS just wipe the data partition without user consent? With NO message displayed whatsoever. Just ask a password go on "Wiping.. please wait". What the hell.
Click to expand...
Click to collapse
It did have consent when you took the OTA with your modded device and it said decrypt and asked for your password it was about to wipe. Again you modded your phone and didn't keep a back up this is no one's fault but yours
Yeah I always back up my messages, photos, etc.. To a PC before any type of flash or update, I use smsbackup and have it uploaded to Google drive also titanuim backup and move the files to PC and just back ur DCIM folder. Sorry for ur luck but we all learn lessons the hard way, and no u Cannot recover, but if u have ur old phone may still have the texts on them and use oneplus switch to move them over
I guarantee this post is from a troll, nobody is dumb enough to do any or all of the idiotic things the OP claims.
Got the (important parts) of my data back. It only wiped the "data" partition - which contained internal app data and sms/calls, etc. It did not wipe the "sdcard" partition (also called "internal storage"). Found this out when I was installing TWRP again (before going through the OS welcome process) to create a dd image of my device for possibility of a future recovery. Android file transfer (thanks to TWRP's MTP support) popped up and showed all my files on the sdcard partition. Immediately backed it up.
To all those senior members who're making fun of this, thanks for all the help, really. You guys were really helpful.
angadsingh said:
Hi,
My phone and all my personal data (4 years of photos, videos, and other app data) just got WIPED.
Here's how it happened:
* I was on OS 5.1.5 till yesterday. Had TWRP as my recovery and Magisk as my root method. Everything was hunky dory.
* Oxygen OS 5.1.6 hit my phone today. I downloaded the update and installed it. Before installing - it clearly stated that my phone will be unrooted by the update. I was ok with that, as I would have simply installed Magisk again from TWRP.
* After the reboot, I opened Magisk manager and saw that Magisk wasn't installed.
* So I did a reboot to recovery from the phone's reboot options (advanced reboot was ON in developer options)
* It did not boot to TWRP. Instead, I saw a stock recovery type screen (black background, OnePlus logo).
* There was a single text called "Decrypt" and a terminal type basic keyboard displayed on the screen.
* At this point I knew TWRP is gone and this would definitely be the stock recovery, asking me for my PIN, to decrypt storage.
* I entered my PIN and pressed ok. IMMEDIATELY after that the screen displayed the message - "Wiping" along with "do not turn off your device while this happens" or similar.
* I was shocked to see this, as all I had done was enter my PIN in a stock-looking recovery with the OnePlus logo.
* The phone rebooted, and lo and behold - I see the new installation screen saying "Hello" to me!
ALL MY DATA IS GONE. Without any fault of mine! I simply did an OS update, and boot to recovery!
PLEASE HELP!
Click to expand...
Click to collapse
I think this is impossible.. First the phone didn't return to me the root message before updating like oneplus 5 and second point, if you enter the pin to decrypt your data in recovery it never do an automatic wipe i'm a bit confused on what you've really done, but for sure you did something wrong because updating system had never wiped anything
Hitman478™ said:
I think this is impossible.. First the phone didn't return to me the root message before updating like oneplus 5 and second point, if you enter the pin to decrypt your data in recovery it never do an automatic wipe i'm a bit confused on what you've really done, but for sure you did something wrong because updating system had never wiped anything
Click to expand...
Click to collapse
Well this is completely possible, I just had the same thing happened to me. It was exactly as OP described it (except it was OOS 5.1.7, and it did not even ask me to input a pin when I rebooted to recovery). Fortunately I had a backup, so it didn't impact me much but still, it is a very weird thing.
angadsingh said:
Got the (important parts) of my data back. It only wiped the "data" partition - which contained internal app data and sms/calls, etc. It did not wipe the "sdcard" partition (also called "internal storage"). Found this out when I was installing TWRP again (before going through the OS welcome process) to create a dd image of my device for possibility of a future recovery. Android file transfer (thanks to TWRP's MTP support) popped up and showed all my files on the sdcard partition. Immediately backed it up.
To all those senior members who're making fun of this, thanks for all the help, really. You guys were really helpful.
Click to expand...
Click to collapse
Thanks for being sarcastic about being helpful. Sorry we can't hold your hand and fix all your problems because your not responsible for your own actions of modding your phone and can't take the consequences when they arise. Maybe you should learn how some more things work and what can happen when you do this before you do it and don't backup your device ever
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
JimZiii said:
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
Click to expand...
Click to collapse
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
Try removing pin/password in settings and see if it still asks for key.
ante0 said:
Try removing pin/password in settings and see if it still asks for key.
Click to expand...
Click to collapse
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
You can Format Data (removes encryption) and edit /vendor/etc/fstab.xxxx and remove the fileencryption line on /data.
I don't have an Honor 8 so I can't check it, but this is how it was done on Mate 9/10 before we got TWRP with decryption on Oreo.
Of course, flashing a new firmware will replace fstab so you'd have to edit it again/restore previously edited one.
Edit: Also, for fun, default password for decryption is "default_password", so you could try that. It most likely will do nothing. This is done automatically when you have no password/pin set.
cypher187 said:
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min ?
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
---
JimZiii said:
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
Click to expand...
Click to collapse
Unfortunately there is no way. Only with HiSuite or sth else. If your device is rooted you can use TitaniumBackup. It can provide a more complete backup of apps, app-data and settings.
Sent from my FRD-L09 using XDA Labs
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Mumtaz77 said:
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Click to expand...
Click to collapse
Install a full package via dload method. Take an 'unbrick' guide from the guides section if you need. You can use a 'FullOTA' package for your region which you can download with FirmwareFinder by TeamMT.
Sent from my FRD-L09 using XDA Labs