Related
(At the request of management). Even with all the unsticking / mod intervention and warnings up the wahzoo, there are still a lot of user problems. It may return in a week , but for now it is PULLED. The moderators have hidden the thread, at least for the short term.
For those of you on TNT Lite 5 / TTx, just keep using it and no worries. Once we know where VS is headed, I will have a plan to either ask you to downlevel or upgrade. Again, depending on what they do.
EDIT: For those of you who had issues, could you please write up the steps you used before it failed? It would help everyone to understand why there are so many problems with this 3991 stock / TNTL 5 / TTx. From the posts and PM's I've seen, the majority have been either:
1- The device was flashed with clockworkmod to 3991/TNTL5/TTx and gets stuck at the birds or
2- The device was being prepped to stock 3588 and recovery was broken, after the 3588 reversion.
But I'm hearing that others might have applied all the proper steps and still had problems. We're trying to gauge just where the problem lies with this 1.2 UAT of Viewsonic's.
From my own device, I know that clockworkmod flat-out does not work. That's because the BCT partition is being touched by standard recovery, which clockworkmod does not replicate (and seems to be required). But as long as I have a clean 3588 stock ROM running on my device, I have not had an issue upgrading to 3991/TNTL5/TTx, it has worked for me 100% of the time.
Stock 3991 / TNT Lite 5.xx / TTx .9x backout instructions:
There are two way I know of to back out of these:
- Flash to stock 3588. This assumes you have NOT added clockworkmod and have standard recovery. I have done this several times and never had a problem. Stock 3588 link: http://forum.xda-developers.com/showthread.php?t=842000
- nvflash using bekit's 1105 image: http://forum.xda-developers.com/showthread.php?t=861950. This is still the best way to back out, as far as I'm concerned. You can do a full erase first, to wipe user data as well, thread is here: http://forum.xda-developers.com/showthread.php?t=974422
NOOOOOOOOO. Hopefully VS will decide what they are going to do by the end of the month. I am enjoying TnT Lite 5.0 with no issues at all. Thank you for all your hard work Roebeet, it is unfortunate that so many have had problems with this.
Damnnn, was about to install it
Really sucks that people have had problems maybe people should read and then re-read instructions instead of jumping into things and just assuming devs and mods can help them out. They have a life and dont think that after putting in all the work in to create something they want to hear from whiny a$$, irresponsible people that probably caused their own problem
Now people, like me, that wanted to install cant. nice.
thank roebeet tho and all the other g tab devs
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
One of the obstacles I've had in the last 2 weeks is that this is a UAT, not a released firmware from Viewsonic - so its validity is in question (and understandably so). If they release it with the same bootloader and upgrade requirements, it's going to shake things up here a bit.
I still think the odds are that they will - from their standpoint, they are only supporting stock users so, as long as they can ensure that a user is on 3588 stock, then the upgrade should work. In our case, many of the issues were either getting from a mod to 3588 stock, or using clockworkmod by mistake. Viewsonic doesn't have to worry about either of those issues.
But, there's still the X-factor -- everything is 3588 stock and the upgrade still fails. That might be what's holding them back.
bkbrod said:
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
Click to expand...
Click to collapse
No, clockworkmod won't work (even the new one) - if you wanted to backout to old stock (3558, for example), you'd have to use Viewsonic's recovery. Clockworkmod will kill your device, trust me on that. nvflashing to bekit's 1105 also works, that's how I've been backing out to old stock.
Hmmm
In the last 24Hrs, my gTab v.9.02 just decided to go totally nuts. Constant FC's, lockups, lost sound. Tried every fix listed on XDA, wiped /data , re-downloaded apps from Market instead of restoring with TiB; wotked for a little bit, then the same FC's. And random loss of sound.
Going back to 3558 and CWM and 4.2.5.
We'll see what VS throws our way.
Keep up the good work Mr.Roe!!!
roebeet said:
The backout, btw, is the same -- run stock 3588 and it will downlevel you back to the old bootloader. BUT, make sure it's standard recovery and not clockworkmod.
Click to expand...
Click to collapse
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
TwoTapsX works great for me so far. Had TNT Lite 5.0.1 but it wouldn't run some apps correctly. Tried all the ROMS and they all had sleep of death problems. TwoTapsX works the best for me without giving any glitches.
TwoTaps .9.2
Thanks Roebeet for all you do here. I am finding this ROM easier to work with than any other. I have noted that periodically it will flash the home screen while I am working. Mostly this has been while in Dolphin Brower HD.
jholmes5 said:
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
Click to expand...
Click to collapse
Good point, since the other thread is hidden.
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
P00r said:
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
Click to expand...
Click to collapse
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It does not... if you install a custom boot animation it stay there... so it's not full even if after the unit doesn't even start (red text) it's not fully wiped...
I have used clockwork with the partition option, this seem to perform a full format with either the nvflash format or bekit recovery but I am not sure why we can't get this done tru the nvflash...
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It's in my first post, as well. Run that nvflash first to erase the device, then the bekit 1105 nvflash to complete the process.
What seems to happen is that the old stock / new stock user data setups are not compatible. When going to new stock, it's not so bad because new stock has a better recovery. But when reverting, old stock has a crappy recovery with no user data wipe options. Even Viewsonic understood the limitations which is why they changed their recovery in this UAT of theirs.
I mentioned to jerdog that I wanted to see if I could port their new recovery to old stock (using an old kernel). If that works, we could conceivably offer a "bekit 1105 enhanced" version that adds it. This is better than clockworkmod in that it's the vendor's own recovery and includes the ability to wipe user data, calibrate the device AND update / downlevel the bootloader. For the purposes of getting users backed out if needed, it might be a critical piece of the puzzle.
EDIT: No go. The recovery functionality is actually IN the kernel, my bad. So it can't be ported over. Oh well.
You guys are GODS at this. Simply amazing what you are all doing with this G Tab. So I guess I'm one, of some lucky few, that ACTUALLY READ the install instructions for 5.0 and 5.0.1.
Glad I did because I love the market on this thing.
Eagerly watching what happens with Viewsonic......Any chance they did this as a step to make a Honeycomb upgrade easier? I doubt it since the original G Tab with OTA updates is still crippled.
First off just want to give my thanks to roebeet and the devs here at XDA. I've been running TnT Lite 5.0 / TwoTapsX ??? since the day I bought my Gtablet on 3/11 with no problems. On Friday the 11th I was itching for a Xoom somehow managed to find out Staples had the Viewpad 10 but not in store and somehow managed to end up finding out that Office Depot had the Gtablet for $379.99 in store. I read roebeet's at the time TnT Lite 5.0 thread several times before walking to my nearest Office Depot and brought home a Gtablet within minutes of reading that thread.
Out of the box from 2967 I went to 3588 through stock recovery and not OTA; and then did the same thing to go to TnTLite 5.0.0
I have successfully backed out of TNT Lite 5 in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
Click to expand...
Click to collapse
My question to roebeet or anyone who has gone from TnTLite / TwoTapsX back to 3588 using stock recovery. I could swear the above quote from roebeet had an additional line about using stock recovery to run the 3588 stock rom and then wiping user data from stock recovery. From TnTLite 5.0.0 can I go back to 3588 using the stock recovery and wipe user data with the stock recovery after running 3588 but before rebooting?
Android system recovery <3e>
Wipe Data/Factory Reset
Wipe Cache Partition
Click to expand...
Click to collapse
If it is possible to wipe user data after flashing back to 3588 do I need to just wipe data or do I need to use the 'wipe cash partition' as well.
edit: never mind my rambling probably better to wait until we know what Viewsonic is going to do and at that point roebeet will let TTx users know how to proceed from TTx to whatever comes down the pipe from VS
I did have a line (I think in the TwoTaps thread) about reversion and wiping data before you reboot into 3588 stock. But, I tried this once myself and it didn't work.
Maybe I should make a special 3588 "mostly stock" with clockworkmod, as a backout solution (so that, if you get into a bootloop situation post downgrade, you already have clockworkmod installed to fix it - that could work). It's the "wipe data" option, btw.
But first, lets see what the vendor does - if they stick with this new bootloader then TNTL5 / TTx users might already be one step ahead of everyone else - you may not want to backout.
Using it since first release with no problems. I always read the entire first post as well as user issues prior to updating. There are probably many users that try before reading which can lead to issues.
I think this is a great ROM.
Sent from my GTablet-TwoTapsX using Tapatalk
I'm one of the ones who ran into troubles getting this to load and I honestly believed I followed all the instructions when doing so. I've tried mostly all of the custom ROMs and was on the Vegan experimental before loading TTx. Not sure what the problem was but nvflashing with or without recovery didn't take. Kept getting stuck in APX mode. I wasn't really worried since I could always get the tablet to take the nvflash so I just kept playing with it until lo and behold, I was able to enter the TTx recovery mode. Been working fine since. I really like this ROM but I definitely feel like the disclaimer is justified - if you're not into tinkering this isn't something you wanna try.
The only problem I've run into so far is that when I recover my Angry Birds file and run the app it FC's. Runs fine if I just install either version, but when I try to restore my saves by using TB, the app refuses to run. Weird. Other than that, no problems. I don't really like the default browser, but understand that it's required at this point. FLash works fine and I haven't had any issues at all with the market. Even found a few apps that were supposedly only available with XOOM builds.
Many thanks Robeet and hopefully we can get a more "idiotproof" upgrade process.
T
roebeet,
Where can we obtain the bekit 1105 file?
I remember seeing the name somewhere but don't remember seeing the D/L source.
Rev
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
I've only had this phone for a few weeks, bought new from Target. It is a US BLN-L24. It originally was running Marshmallow but I updated it to Nougat via the official updater (BLN-L24C567B360).
The first time I got this issue was when I rooted the stock ROM with Magisk. I later installed Apps2SD Pro (for linking apps to 2nd partition on SD card). It mounted this partition, I rebooted, the device then asks for a PIN# which I didnt have and never set. Afterwards I rebooted to @OldDroid's TWRP, it couldnt mount data partition, some error about not being able to find the crypto footer. I then used the dload method to rollback to MM, then updated to Nougat again, and rerooted, this time with systemless SuperSU instead..
Then eventually everything went fine for awhile, but it happened again. So I decided to try a custom Nougat ROM. I went with Resurrection Remix 7.1.2. And then.....it happened again. This time I had rooted with Magisk. I tried yet again, but with SuperSU. And yet again with Phh's Superuser.
I've also tried AOKP, AOSPA, LineageOS, OctN, all Nougat, the issue returns with all of them.
So, no matter what root solution I use, the encryption issue eventually returns. Magisk, SuperSU, and Phh are all supposed to disable data partition encryption. But it seems they aren't.
What I've tried so far:
1. 3 different root solutions, same results
2. Formatting data and wiping all partitions in TWRP immediately before installing a ROM zip, which is supposed to remove the encryption
3. A custom kernel (CycloX)
4. Formatting my MicroSD, as exFAT, every time I check it for errors in Windows 10 corruption is found and repaired, but it always returns. I had initially thought that the encryption might be related to the SD
It has happened numerous times, on different ROMs including stock, and MM/Nougat, and with different root solutions. I know when it happens, I get stuck on the boot logo forever. TWRP reports that data can't be mounted. At one point my phone randomly rebooted into eRecovery and I was shown a message stating that data partition was corrupted. Sometimes it happens as little as 15 mins after booting into a freshly installed ROM, sometimes it takes a few days, but it always comes back no matter what. So far several dozen times.
I'm at a loss as to what is the cause. It could be a hardware defect, a firmware defect/bug, or something I'm doing wrong/missing. So I really have to ask if others are experiencing this too, and what you did to resolve it, I'm sure I'm not the only one. Please provided detailed steps. This is driving me crazy. I bought the 6X to replace my Samsung Note 4 which recently died after 3 years of loyal service. I'm liking this phone alot, it's very powerful, but this is killing me.
If anyone can help then I would greatly appreciate it. If I can't get this resolved then I'll just sell the phone on Craigslist after returning it to stock.
Thanks!
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
AnonVendetta said:
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
Click to expand...
Click to collapse
Actually I think you are the only one with this issue. Flashing Magisk alone will remove auto-encryption. But then you already flashed custom roms.
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
AnonVendetta said:
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
Click to expand...
Click to collapse
Hello, can you help me? I have the same model BLN-L24C567B360. I got this phone today and updated today as well right out of the box. My problem is that I installed TWRP 3.1.1.0 Berlin version for this phone and it doesn't work at all. Now I have my phone working ROM but with no recovery option. Can you give me a link with the files I need? I was thinking on putting back the original recovery.img file back but unfortunately I never thought on doing a backup of it. I read on the top that you have all original stock files. Thanks
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
AnonVendetta said:
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
Click to expand...
Click to collapse
You can stop crying now, I won't be using your "topic" anymore. I just replied to you asking for files that you already have.
And BTW, I don't need them anymore but thanks anyways.
Yoooooo did Huawei do anything yet?
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
AnonVendetta said:
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
Click to expand...
Click to collapse
Sorry to hear you had such a bad experience with them. Pretty crappy that they used a lame excuse like water damage to deny responsibility in fixing the issue.
I agree with you, I will never buy Huawei again. The phone itself is great but the audio is so so bad Im trying to sell mine at a loss as well but no ones calling so Im tinkering with it again. I would be absolutely livid if I spent the money on one of the flagship Huawei phones. Oh well live and learn I guess, at least the 5T comes out sometime next month.
I heard that the latest TWRP version doesn't work to apply updates because of encryption. How can I check which version I'm on, and is it possible to downgrade from within TWRP? To a lower version?
Yes reboot to recovery and you see the version of TWRP.
Yes
I have just done the update using the unofficial TWRP 3.2.3-0 and it worked for me.
NateDev said:
I heard that the latest TWRP version doesn't work to apply updates because of encryption. How can I check which version I'm on, and is it possible to downgrade from within TWRP? To a lower version?
Click to expand...
Click to collapse
Ok let me dispell all the garbage out there. I am on official TWRP 3.2.2.0 and let me tell you that I have never had any issues with encryption or updates or ANYTHING ELSE for that matter.
What I know is going on is people are using custom roms (people who probably do not have enough knowledge of Android to be doing such things in the first place). When they flash the new rom (any rom, even stock rom will do this) they are not wiping the data partition (probably because they don't know how to use "ADB push" and wiping the data partition will erase the zip they want to flash) and the new rom can not read the encrypted data that the previous rom left behind. If people would invest the $10 dollars for an OTG SD card reader and the $25 on a 128 GB SD card (like I did, and yes it is that cheap and Amazon even sent it to my front door so I never got off my lazy back side to get this) they would not have these problems.
Ok now that rant is over, and I apologise if I offended anyone, allow me to tell you that the official TWRP downloaded from the official TWRP website works exactly as stated on their website. I have never had any encryption issues, and I even updated OOS from 5.1.9 to 5.1.11 this morning with no issues at all. Anyone who is having problems can PM me here and I will gladly explain what needs to be done to update or flash new roms so they don't have problems.
tabletalker7 said:
Ok let me dispell all the garbage out there. I am on official TWRP 3.2.2.0 and let me tell you that I have never had any issues with encryption or updates or ANYTHING ELSE for that matter.
What I know is going on is people are using custom roms (people who probably do not have enough knowledge of Android to be doing such things in the first place). When they flash the new rom (any rom, even stock rom will do this) they are not wiping the data partition (probably because they don't know how to use "ADB push" and wiping the data partition will erase the zip they want to flash) and the new rom can not read the encrypted data that the previous rom left behind. If people would invest the $10 dollars for an OTG SD card reader and the $25 on a 128 GB SD card (like I did, and yes it is that cheap and Amazon even sent it to my front door so I never got off my lazy back side to get this) they would not have these problems.
Ok now that rant is over, and I apologise if I offended anyone, allow me to tell you that the official TWRP downloaded from the official TWRP website works exactly as stated on their website. I have never had any encryption issues, and I even updated OOS from 5.1.9 to 5.1.11 this morning with no issues at all. Anyone who is having problems can PM me here and I will gladly explain what needs to be done to update or flash new roms so they don't have problems.
Click to expand...
Click to collapse
Yeah, I used 3.2.2.0 I think and the update applied perfectly, 5.1.9->5.1.11
I know we don't have a complete implementation of recoveries, like twrp/of (I know it's basically the same), yet. But now that we have the kernel source, what is still missing (vendor?)?
Also and kinda of a similar question, what is still missing regarding a "normal" flashing process? Like wipe system, data, dalvik/art, cache, flash rom and not having to have a base stock firmware and needing to format data.
To be honest, I'm a bit confused with this phone. My other phones (admittedly last one's didn't get past Android 9), were so different in that regard.
So I'd really appreciate if someone could take the time to shed some light on this.
Maybe we'll see a stable version of twrp for surya but support for dynamic partitions will not be available soon.
Having to format data everytime you flash a new rom may be solved having the kernel source. I think it has to do with encryption keys. Even if you don't have any password set in the OS, miui still generates keys to encrypt the data and when you wipe only, they get deleted hence, data on the internal nemeory remains encrypted. That's what I think.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Ok, to be honest and judging by the fact that the announcement by Dees_Troy was over a year ago, things look pretty difficult to say the least.
I had my last phone (axon7) for so long that all the new implementations, like dynamic linking and super partition, weren't really on my radar.
Guess I was a little naive in thinking that the kernel source would be of any help in that regard.
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
pnin said:
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
Click to expand...
Click to collapse
How about EU ROM ?
Thanks for your thread.
I'm asking too.
I went from an old device too (redmi note 4 mido), and i'm a bit lost on flashing process.
Is it possible to :
Install orangefox via fastboot.
Wipe all & format data.
Flash recommend firmware for rom.
Flash custom rom.
Flash gapps.
And boot ?
Any problem with that ? What i'm missing ?
Don't have phone now, I'm waiting for shipping, and will wait for unlock bootloader access. I hope it will more clear and simple when I will discover poco x3.
You can do all those things. What you can't do for example is make a backup and restore your current custom rom.
Oh ok.
Sorry, miss understood your op post.
I was confused because on some custom roms thread, I find strange install instructions, like : dont wipe anything, format data AFTER flash custom roms...
Somes roms requires frimware 12.0.3. What about if phone have a more recent ? Can I downgrade just by flash fw+vendor on recovery before flash rom ?
And some people said they have bricked there devices.
Just to be sure to don't make stupid error on fresh new device, that I can't solve with miflash and fastboot.
Thank you for your reply.
I only clean flash roms, never backup, don't have a lot of apps, and majority have import/export options in-app.
But I hope for you it will be fixed soon.
atifnr said:
How about EU ROM ?
Click to expand...
Click to collapse
As @[armitage] pointed, it doesn't enable nandroid backups that I know of.
.