Hi all,
I think I might haves messed things up, where I would have perform a total wipe again, of my Asus TF300T.
Some of you know, I was instructed to perform a total 'wipe' (different than a factory reset), to determine if that would help my constant lag issue (and not responding messages).
Everything is going OK.
But tonight I was working on getting Titanium Backup Pro working again. For a split second I forgot that I needed to install Busybox to get it to work properly.
I installed Busybox and then launched Titanium Backup, granted the required superuser rights. And I was running.
However, almost immediately I got a message stating that my Android Device was changed.
It explained that it was probably due to a factory reset or wipe.
So far it was correct.
Then it offered me a one time chance to replace this new Android Device ID with the old Device ID.
I was having trouble installing a SVOX voice package, something that never happened before.
I made an assumption that it was because of the device ID.
With that stuck in my head, and before coming here first, I decided to restore the old device ID.
I have not tested anything yet. I cleared the caches and did a reboot.
And I immediately came here to get some help to:
1) Get an explanation on what the Android Device ID are used for? (I do have a basic idea what they are for).
2) Did I do the right thing by restoring the old ID? If not, what kind of things can I expected to go wrong.
3) I never wrote down the numbers of the old and new ID's , of course I have the old one, since that is what it got changed to. But if I need the new ID instead of the old one, would I have to perform a total wipe again, to generate a new Device ID ?
Thanks!
Rob
Its all learning for me, I do appreciate the advice and help.
Sent from my SPH-D710 using Tapatalk 2
Afternoon, y'all. Let me cut to the chase:
My objective: To install the custom ROM located at this link (http://forum.xda-developers.com/showthread.php?t=2591895). I don't want to lose my root functionality/benefits by taking the OTA 4.3 update (Titanium, Greenify, etc), but I want to be able to use apps like DashClock which don't work with 4.1.2.
My phone specs:
Model SCH-i535
Android Version 4.1.2
Baseband Version i535VRBMF1
Kernel Version 3.0.31-1152558 ([email protected] #1)
Build Number JZO54K.i535VRBMF1
Hardware version 1535.10
Phone IS ROOTED, and I used the Casual root tool located here: http://forum.xda-developers.com/showthread.php?t=2332825
[*]Apps I am using during this process (specific to root, backup, etc): Titanium Backup Pro (full backup made, including update.zip), ROM Manager, Root Checker, SuperSU
[*]Although I had a ton of frozen bloatware/system apps (all safe, I checked thoroughly before I did this a few months ago), I have unfrozen everything.
Previous experience: Before this S3, I had an HTC Thunderbolt which I successfully rooted and installed a custom ROM onto. So I have *some* experience, but I am no zen master.
Problems I've run into this time around:
Phone is rooted, but I am pretty sure the bootloader is NOT unlocked. Rootchecker confirms that the phone is rooted, and apps that require root access work just fine.
Related to the above point, when I run Casual (as I did just a few minutes ago), this is the log that appears in the window:
-Waiting for device...
Waiting for ADB device connection. When your OS recognizes the device, we will continue. Don't touch anything.
-Device found.
-Pushing exploit...
4298 KB/s (1283460 bytes in 0.291s)
-Pushing root tools...
2990 KB/s (96260 bytes in 0.031s)
4692 KB/s (1867568 bytes in 0.388s)
5424 KB/s (1872015 bytes in 0.336s)
-Rooting phone...
-This may take a few minutes.
Failure.
-installing superuser to system partition
-once root is confirmed you can flash the Insecure aboot
done
-Script Complete
This "FAILURE" is what catches my eye. I can't tell if the phone is "half-rooted" (no unlocked bootloader), or if it's just that Casual sees that my phone is already rooted so it doesn't bother trying to do it again (which is fine, I can understand that point, if it is true).
ClockworkRecovery Mod fails when trying to backup my current ROM (unlocked TouchWiz, no custom ROM installed yet). When I push "Backup Current ROM" in ROM Manager, it reboots the phone (crashes) and puts it into recovery mode, but there's nothing to recover. So my screen goes to the Yellow Triangle of Death screen and gives me a red error message in the top-left corner saying "secure kernel: fail". I had to reboot the phone using Volume Down+Home+Power, and it goes right back to a normal startup. This is what leads me to believe my bootloader is still locked, and I can't find a way to overcome that. I NEVER see the CWM menu to wipe cache, data, etc.
Titanium Backup failed to backup my SMS messages (everything else went fine). It gives me an XML error right away. I used a different app to back them up, which gave me no problems. Not sure if this is related to the larger problem, but I figured it was worth mentioning.
What I'm asking: I'm wanting to make sure that I've got all my bases covered. I know I've done my backups through Titanium Backup correctly, but I do remember that with my Thunderbolt I had to copy down some ID numbers related to the phone so I could sync it after installing a custom ROM (I haven't read any mention of this with the S3, so I'm a bit worried that I'm missing something).
CWM not working correctly is what's throwing me off- I don't want to get my phone stuck in bootloops like before. I want to backup my current setup, clean the cache/data/etc, install the ROM and then restore my apps and data.
I want to avoid resorting to ODIN and putting my phone back to stock (and risk getting the OTA 4.3 update, which I refuse to do) to be able to load this ROM, but if that's what I need to do, then so be it.
Any help, insights, etc would be immensely appreciated! I've read countless threads over the last few months (and especially in the last week), and the fact that there isn't much documentation regarding MF1 when it comes to installing bootchains and ODIN makes me feel like I'm groping in a dark a bit.
Many thanks!
Wow, long post.
Sounds like you're rooted, so download ez unlock v 1.2 to flash the insecure aboot. Then flash the rom after.
You should be good to go after that.
Edit : additionally, I wouldn't restore any apps or data from tibu in this case, going from 4.1.2 to 4.3 changes quite a bit of file structuring and could cause problems.
Sent from my SCH-I535 using Tapatalk 2
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
DuoDSG said:
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
Click to expand...
Click to collapse
Don't be sorry for the long post, much better to be detailed and explain as much as you can. Shows you did some research before asking. I wish everyone researched that much before posting.
Ez unlock is great to use in this case, it will brick your phone if you're on 4.3.
You can always restore your contacts from googles database, as far as restoring call logs and sms messages you should be OK. But if you encounter any lag or bugs it could have something to do with that.
Sent from my SCH-I535 using Tapatalk 2
All right, so I followed your instructions. I sideloaded EZ Unlock, which did the trick, and then I went into CWM Recovery, wiped the data, cache and dalvik.
Then I went ahead and loaded the ROM zip from the SD card, and VOILA! Without a hitch. The phone is snappier than EVER and it's just a matter of downloading the apps I want to again from the play store. Even the data speeds--whether on WiFi or 4G--are blazing fast, I never encountered speeds like this, even when I first got my phone stock from Verizon.
I was pleasantly surprised that my phone didn't have an identity crisis (as had happened when I rooted and loaded a custom ROM on my HTC Thunderbolt years ago). Right away it knew my phone number, and my Google account sync was flawless.
So far, extremely impressed. And I can breathe a sigh of relief that I OVERprepared for this instead of missing something crucial (so far! fingers crossed). Before, under 4.1.2, I used a combination of Greenify, freezing unwanted bloatware/system apps and Xposed Framework to get my phone to do incredible things, and I look forward to seeing how everything works under 4.3 without Verizon's slimy tentacles all over my phone again.
I will continue to update the thread as I run into issues or curious info that might be useful to anyone considering going through the same process. Surely my experience and effort can allow someone else to have an easier time than I did!
Thank you again for your help- it may have seemed simple, but the direction and reassurance you gave was all the help I needed to make it happen and not blow up my phone
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
When trying to update this message pops "Your device has been modified. Software updates are not available".
I did experiment with android operational system versions, but it was a long time ago, so I could not tell what exactly I did.
Right now it's running 4.1.2 version.
I already did some research, so I tell what I have already tried:
Resetting factory settings;
wiping cache partition;
updating while in safe mode;
unrooting it with several apps, but all of them say the device is not rooted;
there can't be any issues caused by SD card, because I don't own one on this device.
I would really appreciate your help
Baikasas said:
When trying to update this message pops "Your device has been modified. Software updates are not available".
I did experiment with android operational system versions, but it was a long time ago, so I could not tell what exactly I did.
Right now it's running 4.1.2 version.
I already did some research, so I tell what I have already tried:
Resetting factory settings;
wiping cache partition;
updating while in safe mode;
unrooting it with several apps, but all of them say the device is not rooted;
there can't be any issues caused by SD card, because I don't own one on this device.
I would really appreciate your help
Click to expand...
Click to collapse
Well, probably you rooted the device long back and then unrooted it which has modified the device. Anyway, how will you get any update for this device in 2021 ??? All you can now do is install a custom rom of android 6. Or else if you want to remain on android 4.1.2, you'll need to install firmware.
Hi everyone,
I hope some of you are still following up on this device or maybe my query is not too specific after all...
To give you some background: When I rooted my Zenfone 3 Ultra in April 2019 the storage was encrypted such that I had to enter a key each time I powered it up. After ~ 1 year or so I could not access the OS anymore after a reboot because it said the key I entered was wrong. So I went to twrp and did a wipe in order to set everything up again, this time not using device encryption. I noticed that after this wipe the flash light and third party apps using the camera would cause crashes (black screen or immediate reboot). I could live with it so far but recently I thought more and more often that it would be nice to finally use the camera in third party apps. So yesterday I had some time and decided to address the issue by doing a factory reset.
Now the factory reset did not resolve the issue. I remembered that when I had rooted the device (and everything was still working) I had created a nandroid backup in twrp which I then restored. I included everything in the restore which was offerd by twrp, i.e. Boot, Data (excl. storage), System and System Image. Still the same issue. I am not sure anymore if I created the one nandroid backup which I still have before or after rooting but when I boot up the device and install Magisk Manager, Magisk is shown with the version I installed back then.
According to the ZU680KL unlock/root thread unlocking is not possible anymore. However, I would like to keep root / be able to regain it. I assume the latest firmware (UL-ASUS_A001-WW-14.1010.1804.75-user.zip) as well as the corresponding boot.img and recovery.img which @ndi provided in this thread (thanks!) would allow me to go back further. However, I noticed that in my boot menu it says "DEVICE STATE - locked", which already makes me kind of nervous due to the unlocking issue above. I just don't want to try anything else on my own because I am afraid to do something foolish. So maybe you can help me with these two questions:
With everything being as it is, how could I start as clean as possible without loosing root / the ability to root again?
If I was willing to sacrifice root access, how could I proceed to bring everything back to stock?
Or maybe you have some other idea to fix the camera issue. Any help will be appreciated.
Many thanks!
Hello again everyone,
I decided to move on and go back to stock. Eventhough I was not able to maintain/regain root, there is an approach that might be applicable to our device as well. Also, I would like to share what I found out regarding my initial goals (i.e. camera issues and resetting a rooted device).
Camera issues: It seems to me that these appear on (some?) ZU680KL devices running Android 7 (Nougat). They can affect the flashlight or the camera in general, as you can read here. I decided to go back to the latest Android 6 (Marshmallow) realease as suggested in the same thread. The system no longer crashes when I use the flashlight or the camera is used by a third party app. However I sometimes still need to start the camera app in order to make it work in third party apps.
Going back to stock: A guide for the Zenfone 3 siblings can be found here. I went back to stock using TWRP and a MicroSD card (with boot.img, recovery.img and ROM zip file):
I first flashed the boot and recovery (i.e. TWRP) partition with the stock images for the ROM I was planning to flash.
Then I booted into stock recovery and flashed the ROM zip file. The key combination to get into stock recovery was a little weird ('volume -' followed by 'volume +' while keeping 'power' pressed). It had to be entered during the 'no command' notification that was shown after choosing recovery from the fastboot menu.
After successfully flashing the ROM, I wiped cache and data and rebooted. I ran into a "Dm-Verity in EIO mode" error (see attached). This error had already occured after my last try to restore a nandroid backup in TWRP but I could resolve it with the steps described in this youtube video and repeated (2.). When I think about it now I guess I should have started with (3.) right away because of the Dm-Verity issue.
Regaining root: I think this is something yet to be done but it does not seem completely hopeless.
I hope this can be of help if you face any of these issues.