I've seen many people experience the same problem I have and it's that I can't install the Lollipop update at all. Tried this on my brothers Mate 2 and it didn't work as well and his is all stock (No root, nothing)
- Mine is rooted
- Stock recovery, switched back from TWRP
- Unlocked bootloader
Took this off of @GadgetStrutter cause I have the same problem's he's having
1. Extracted B309 to formatted SD card and tried to flash (Software install failed!)
2. Updated my rooted B126 to B148 and tried to flash from SD card again (Software install failed!)
3. Unrooted my B148 and tried to flash from SD card again (Software install failed!)
4. Reformatted SD card and redownloaded B309 and extracted it into root folder, and then trying again after (Software install failed!)
5. Rerooted my phone, but in B148 this time. Tried to restart and flash from SD card.. (Software install failed!)
- Got my phone from Wind Mobile, read threads and apparently made it into the stock B148 rom, (MT2-L03V100R001C00B148)
PLEASE, I'm HELLA impatient when it comes to software updates and I'm sure so is the Huawei community
If you need more info, comment below
I don't think wind mobile variants will take stock updates. Same as CC variants.
Moody66 said:
I don't think wind mobile variants will take stock updates. Same as CC variants.
Click to expand...
Click to collapse
The thing is, multiple users who have bought the HAM 2 from Wind have converted it to into the stock version and are able to update to Lollipop.
I read a bunch of posts saying you can turn your HAM 2 CC Variant into the Stock HAM 2 by download the stock 4.3 rom, call me a bull****ter but I'm just stating what the HAM community says.
mousamsh said:
The thing is, multiple users who have bought the HAM 2 from Wind have converted it to into the stock version and are able to update to Lollipop.
I read a bunch of posts saying you can turn your HAM 2 CC Variant into the Stock HAM 2 by download the stock 4.3 rom, call me a bull****ter but I'm just stating what the HAM community says.
Click to expand...
Click to collapse
That's incorrect. While you can flash the stock b148 onto the CC/Wind variant, its not a full convert. Lollipop update will always fail. There is currently no way to fully convert or fool Huawei updater to think it is the OEM version.
I assure you, no one has gotten Lollipop onto the CC/Wind variant yet.
ArkAngel06 said:
That's incorrect. While you can flash the stock b148 onto the CC/Wind variant, its not a full convert. Lollipop update will always fail. There is currently no way to fully convert or fool Huawei updater to think it is the OEM version.
I assure you, no one has gotten Lollipop onto the CC/Wind variant yet.
Click to expand...
Click to collapse
I'm not the one lying, guess the posts are fake.
Do you think there is any way to get lollipop update with a TWRP backup or possibly a release for the CC or Wind Variant (Or is it released by Wind themselves)?
mousamsh said:
I'm not the one lying, guess the posts are fake.
Do you think there is any way to get lollipop update with a TWRP backup or possibly a release for the CC or Wind Variant (Or is it released by Wind themselves)?
Click to expand...
Click to collapse
A TWRP backup won't work like last time. They changed partition sizes of the boot/system...so when TWRP tries to flash the Lollipop backup it runs out of space and fails.
I doubt that Wind/CC will update it.
Everyone is still hoping someone will come up with a way to flash it. Just gonna take some time.
ArkAngel06 said:
A TWRP backup won't work like last time. They changed partition sizes of the boot/system...so when TWRP tries to flash the Lollipop backup it runs out of space and fails.
I doubt that Wind/CC will update it.
Everyone is still hoping someone will come up with a way to flash it. Just gonna take some time.
Click to expand...
Click to collapse
Is there no available method to increse the size of the boot/system partition? I'm sure there has to be a way but someone isn't and wont look for it. Correct me if I'm wrong but can't you create a partition reserved just for that with an additional size adjustment?
mousamsh said:
Is there no available method to increse the size of the boot/system partition? I'm sure there has to be a way but someone isn't and wont look for it. Correct me if I'm wrong but can't you create a partition reserved just for that with an additional size adjustment?
Click to expand...
Click to collapse
I'm sure there is a way, but the developers here don't have the CC/Wind variant, and can't do any testing.
And they say it is risky thing to do.
Huawei should have been more clear but the Lollipop is ONLY for the US HAM2, MT2-L03. No variants are included, yet. That means Wind and Consumer Cellular will not work using the published methods.
I am not calling anyone a liar. If someone with a variant has been able to update to Lollipop then they really need to create a thread and post how they did it.
Perhaps this?
http://forum.xda-developers.com/ascend-mate2/development/post-twrp-recovery-folders-t2923406
Funny because you posted it lol http://forum.xda-developers.com/showpost.php?p=60958082&postcount=2
What is the ultimate way to find out if my phone is a Wind/CC variant? I have B148 on it right now.. it's an MT2 L03.. and I never purchased it; I actually won it online.
GadgetStrutter said:
What is the ultimate way to find out if my phone is a Wind/CC variant? I have B148 on it right now.. it's an MT2 L03.. and I never purchased it; I actually won it online.
Click to expand...
Click to collapse
Look on the back of it and see if it says ConsumerCellular on the back cover? lol
My guess is it's a variant. Whether its Wind/CC, or Walmart.
It says L03 Sample.
GadgetStrutter said:
It says L03 Sample.
Click to expand...
Click to collapse
Well there's something you don't see everyday
Sample is probably wherein your problem lies.
.
I'm on wind as a customer but i bought the phone off of someone, it's unlocked and doesn't say wind anywhere but i get software install failed. I installed the unify TWRP is that what's messing me up?
I opened the back cover too nothing that says wind or customer variant...
a_ahmed said:
I'm on wind as a customer but i bought the phone off of someone, it's unlocked and doesn't say wind anywhere but i get software install failed. I installed the unify TWRP is that what's messing me up?
I opened the back cover too nothing that says wind or customer variant...
Click to expand...
Click to collapse
You could try flashing stock recovery, but I believe the update works without it.
Your final option is to do the OEM conversion just to make sure its fully OEM.
http://forum.xda-developers.com/ascend-mate2/general/guide-cc-variant-to-oem-convertion-t3149767
No disrespect, but your information is either oudated or absolutely wrong about not being able to convert the wind mobile variant. I just did it today following the guide with what other wind owners said and am running b322 now. I'm only writing this because your posts made me stay away from upgrading for a LONG time. If you don't mind annotating what you said, it would really help others.
So, follow the guide. If when you flash twrp it doesn't work seem to work, simply boot it instead then flash the oem zip and then you can flash oem 4.3. After that, following the guide you should have no issues going straight to b322. Don't do any updates through android itself, power off and use the three button method. It's not hard but it did take me close to an hour if not more.
victorhuge said:
No disrespect, but your information is either oudated or absolutely wrong about not being able to convert the wind mobile variant. I just did it today following the guide with what other wind owners said and am running b322 now. I'm only writing this because your posts made me stay away from upgrading for a LONG time. If you don't mind annotating what you said, it would really help others.
So, follow the guide. If when you flash twrp it doesn't work seem to work, simply boot it instead then flash the oem zip and then you can flash oem 4.3. After that, following the guide you should have no issues going straight to b322. Don't do any updates through android itself, power off and use the three button method. It's not hard but it did take me close to an hour if not more.
Click to expand...
Click to collapse
You do see that this is a thread from July. A lot has happened since then. It might be outdated now but was most likely correct at the time it was posted.
Thank you for encouraging others to try the conversion\upgrade, though.
Yep, I know it's from July, but so is the conversion guide hence why it can be confusing, especially coming from a senior member. In any case, I hope this helps Wind users. I really like the new android and I can't say I've noticed any software bugs yet, it's running great!
victorhuge said:
Yep, I know it's from July, but so is the conversion guide hence why it can be confusing, especially coming from a senior member. In any case, I hope this helps Wind users. I really like the new android and I can't say I've noticed any software bugs yet, it's running great!
Click to expand...
Click to collapse
i know this is old but can you explain how you did this? i have a wind and converted and rooted to 148 but i keep getting a error when trying to go to b322 thanks in advance
Related
http://www.htc.com/us/support/htc-desire-610-att/news/
Here is an update I found .it's Still android 4.4.2. All that I know is it says bug fixes on the provided link for download . I flashed the firmware through fastboot just now . Works fine ,I don't notice any difference from the stock firmware other than the software numbers being different. There are two variants for download . One for pre paid and one for post paid. I have a contract so I used post paid.
I just wanted to post this for all to dig into and also because through hitting check for updates on my phone ,this update did not show up .I found it manually online .
I've developed some roms in the past for the atrix 2 . I am quite possibly going to be diving in once again as its been a year since I stopped for the a2 and currently this phone needs some development going on .
Here is an update I found .it's Still android 4.4.2. All that I know is it says bug fixes on the provided link for download . I flashed the firmware through fastboot just now . Works fine ,I don't notice any difference from the stock firmware other than the software numbers being different. There are two variants for download . One for pre paid and one for post paid. I have a contract so I used post paid.
I just wanted to post this for all to dig into and also because through hitting check for updates on my phone ,this update did not show up .I found it manually online .
I've developed some roms in the past for the atrix 2 . I am quite possibly going to be diving in once again as its been a year since I stopped for the a2 and currently this phone needs some development going on .[/QUOTE]
this update just att phone??
I'm waiting for 5.0 from HTC, but I'm curious if the update will fix a problem with the display. 610 needs devs
I'd really appreciate some confirmation on this. I started the ruu tool and saw it will wipe internal data (prior to reading that I didn't think an update would erase data) Not a big deal. I stopped it and made a backup.
But then I stopped to consider if there are any more surprises.
The 2 step guide right in Google search results does not mention needing adb environment.But other places say you need android sdk tools installed. This is an issue because I don't own a pc. I have everything I need on my Mac but of course I cant run exe files.
Do I need an adb environment for this to work? I can borrow a pc but would prefer to not put too much stuff on it because it's not mine. Just running one program one time--not a huge bother.
Also are there any other things I should be aware of before continuing? With other devices I'm not nearly as cautious but this is my main phone. Thanks.
Sorry to keep coming back but I did a clean install of Windows just for this update. The pc I had really needed maintenance. Still not certain it's necessary but I've got the adb environment set up and working. I just have a few questions...
1. Reading older posts, it says the ruu will relock boot loader and bring me to stock, is this true?
--in case it wasn't assumed, I AM rooted with jmz kernel, unlocked and twrp
2. This WILL lock and unroot my phone automatically, correct? I don't have to do it before?
3. If the answer to the above is yes, I will need to unlock it and root again?
4. Once this is done, can I flash my backup with twrp? Of course that assumes it will be wiped.
Sorry again for what's most likely annoying questions. This is my only phone and bricking it would be bad, worse than other devices that are just for entertainment. I VERY tempted tojust plug in my phone and run ruu but I really want to know exactly what will happen.
For all the threads here I'm surprised this isn't being talked about.
KLit75 said:
Sorry to keep coming back but I did a clean install of Windows just for this update. The pc I had really needed maintenance. Still not certain it's necessary but I've got the adb environment set up and working. I just have a few questions...
1. Reading older posts, it says the ruu will relock boot loader and bring me to stock, is this true?
--in case it wasn't assumed, I AM rooted with jmz kernel, unlocked and twrp
2. This WILL lock and unroot my phone automatically, correct? I don't have to do it before?
3. If the answer to the above is yes, I will need to unlock it and root again?
4. Once this is done, can I flash my backup with twrp? Of course that assumes it will be wiped.
Sorry again for what's most likely annoying questions. This is my only phone and bricking it would be bad, worse than other devices that are just for entertainment. I VERY tempted tojust plug in my phone and run ruu but I really want to know exactly what will happen.
For all the threads here I'm surprised this isn't being talked about.
Click to expand...
Click to collapse
***ok. I finally read the return to stock section and it also is done with ruu. And you do need relock boot loader. Of course this means it will wipe my data.
Sorry. I've read that post before but skipped right over that section. I thought there might be a better way.
TWRP must be essential to flash the kernel but otherwise it really complicates the update process. Without it I could just unroot with Supersu or other tool, take the ota then reroot.
I wonder what differences are in the ROM for pre-paid and contract customers?
Naturally this thread is in relation to the AT&T supplied phones for an RUU with 1.53.502.11 / 1.53.502.12 ( 1.53.502.12 for pre-paid devices)
On HTCdev the main version for the WWE phone is currently only 1.31.401.2, with the Australia (Telstra) as 1.31.841.3.
I have the Australian Telstra supplied HTC Desire 610 (Navy Blue) and it is running 1.31.841.3 with Kernel version 3.4.0-g29bee57 [email protected] #1 SMP PREEMPT
Does anyone know of an RUU for the WWE ROM? or know if the AT&T 1.53.502.XX kernel version is 3.4.0 or 3.4.10 or other?
OTA Update
I received an OTA today on my AT&T 610.I'm rooted with boot loader unlocked and on rooted stock.I copied the OTA file if anyone is interested.I'll upload it and make a shared dropbox folder.There isn't any version info that I can see.I'm.not equipped to read the build prop inside the zip at the moment.Any interest just let me know.
---------- Post added at 02:59 PM ---------- Previous post was at 02:39 PM ----------
I'd say it's just a prep update for the lollipop we are supposed to get in March.
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
bob24260 said:
I received an OTA today on my AT&T 610.I'm rooted with boot loader unlocked and on rooted stock.I copied the OTA file if anyone is interested.I'll upload it and make a shared dropbox folder.There isn't any version info that I can see.I'm.not equipped to read the build prop inside the zip at the moment.Any interest just let me know.
---------- Post added at 02:59 PM ---------- Previous post was at 02:39 PM ----------
I'd say it's just a prep update for the lollipop we are supposed to get in March.
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I heard we weren't getting lollipop till next fall...did they bump it up or was my info wrong?
That did seem like a long wait. By that time a new os might be rolling out!
From what I be read we can expect it.in mid March.I will try to hunt my reference points back up so you can have a look too.
bob24260 said:
From what I be read we can expect it.in mid March.I will try to hunt my reference points back up so you can have a look too.
Click to expand...
Click to collapse
And if its not too much trouble would u try to summarize how you got the update? Did you just relock bootloader, factory reset via HTC menu and take a normal ota? Then unlock it and root again?
Ive rooted and flash ROMs on a few devices already but am surprisingly still confused about this. This phone's gotten so little attention there just isn't much out there to learn from.
Not to mention it'll be a bit time consuming since the PC I used to root this has since died so I'll need a new token. That's where the ruu adds another layer of confusion--as far as I know it doesn't automate the unlock so where's the benefit there? Once you're unlocked, running root tool is easy ...and if you have to unlock and unroot anyway--at that point wouldn't just allowing the ota be easier?
You see. I've got lots of questions. Any help would be much appreciated. Running same firmware 6 months now.
More recent Firmware?
Anyone have an RUU for a more recent firmware? I actually flashed an older version than this (the one in the return to stock thread) thinking it was the latest.
I left it on there for I think around 24 hours,waiting for an ota update before rooting but it never happened so I thought it was already the latest version.
help
plz i will need ur help i have a problem with my htc desire phone can u help me?
this is my email shld in case i might not visit this site often [email protected]
Thanks
anyone have a copy of the ruu anywhere?
rdavisct said:
http://www.htc.com/us/support/htc-desire-610-att/news/
Here is an update I found .it's Still android 4.4.2. All that I know is it says bug fixes on the provided link for download . I flashed the firmware through fastboot just now . Works fine ,I don't notice any difference from the stock firmware other than the software numbers being different. There are two variants for download . One for pre paid and one for post paid. I have a contract so I used post paid.
I just wanted to post this for all to dig into and also because through hitting check for updates on my phone ,this update did not show up .I found it manually online .
I've developed some roms in the past for the atrix 2 . I am quite possibly going to be diving in once again as its been a year since I stopped for the a2 and currently this phone needs some development going on .
Click to expand...
Click to collapse
Where can I find a ruu for the a3_ul? Any will do as my phone is constantly rebooting and has errors. Thanks
I picked up a Huawei GR5 when my current phone went belly up. Was going to flash CM13 on it, but I noticed that my (Canadian) phone is model kii-l05, and I can't find any info on whether I can install CM13 on this model. Will be very sad if I'm stuck with the Huawei SW....
Are you on marsmallow?
Demian3112 said:
Are you on marsmallow?
Click to expand...
Click to collapse
Yes, it's running MM. This phone was sold by Rogers locked, and has since been unlocked. From what I can tell the difference between this and a KII-L21 is that the L05 is not listed as dual sim, despite appearing to have the same HW. It must be firmware limited to only use the usim.
jemez said:
Yes, it's running MM. This phone was sold by Rogers locked, and has since been unlocked. From what I can tell the difference between this and a KII-L21 is that the L05 is not listed as dual sim, despite appearing to have the same HW. It must be firmware limited to only use the usim.
Click to expand...
Click to collapse
I've read here that it works. You will need to do some build.prop editing because your device is single-sim.
Check out this fix for single-sim here
JT-on said:
I've read here that it works. You will need to do some build.prop editing because your device is single-sim.
Check out this fix for single-sim here
Click to expand...
Click to collapse
Thanks. This is a bit scary since the only time I've flashed CM onto a device it was a Nexus and was super easy. I think I need to make sure I know how to get back to normal MM if I mess this up before I try.
jemez said:
Thanks. This is a bit scary since the only time I've flashed CM onto a device it was a Nexus and was super easy. I think I need to make sure I know how to get back to normal MM if I mess this up before I try.
Click to expand...
Click to collapse
Yeah, in general it's not recommended to flash firmware that's not specifically supported for your device. Luckily, someone else has already taken the risk for you
JT-on said:
Yeah, in general it's not recommended to flash firmware that's not specifically supported for your device. Luckily, someone else has already taken the risk for you
Click to expand...
Click to collapse
Does it matter that the fix was done for a different device?
jemez said:
Does it matter that the fix was done for a different device?
Click to expand...
Click to collapse
Shouldn't be a problem. I found the information in the Honor 5x CM13 Unofficial thread, here.
JT-on said:
Shouldn't be a problem. I found the information in the Honor 5x CM13 Unofficial thread, here.
Click to expand...
Click to collapse
Well, I decided to try this today on my KII-L05, but started with just the plain CM13 download. Surprised a bit, but it worked fine on my device without me changing anything, calls, LTE, Wifi, Bluetooth, camera all appear to be fully functional. Only thing is my device doesn't know its device model anymore in the settings, which seems of no importance.
jemez said:
Well, I decided to try this today on my KII-L05, but started with just the plain CM13 download. Surprised a bit, but it worked fine on my device without me changing anything, calls, LTE, Wifi, Bluetooth, camera all appear to be fully functional. Only thing is my device doesn't know its device model anymore in the settings, which seems of no importance.
Click to expand...
Click to collapse
Hi Jemez,
I just got the KII-L05 also. How is the phone working for you since you flashed it?
Can you point me to the procedure you used to root?
Thanks
mouf said:
Hi Jemez,
I just got the KII-L05 also. How is the phone working for you since you flashed it?
Can you point me to the procedure you used to root?
Thanks
Click to expand...
Click to collapse
It was ok until today. I tried to do an OTA update, and it hung on the boot screen. From what I'm seeing in the forum, this looks like a known issue with not using CM13 recovery.
I didn't root, I just unlocked the bootloader, installed TWRP, did a full backup onto an external SD card, and then flashed the new ROMs onto it. The backup on the SD made life much easier today when it hung, I was easily able to revert to the original OS, make sure everything was ok, and now I've swapped to Resurrection remix.
I flashed CM13 last night on my KII-L05, boy what a difference. Very snappy!
One hiccup did occur when I installed the latest nightly via TWRP. I received an Error 7 when installing. It stated that the package was for kiwi where my device was "."
Googled around and learned that the update_script in the CM13 install package is validating the device model / variant.
Essentially I had to remove the "assert" lines validating the model in the update_script.
After that, install was successful.
By any chance do you still have your backup? I can't seem to get mine to work.
jemez said:
It was ok until today. I tried to do an OTA update, and it hung on the boot screen. From what I'm seeing in the forum, this looks like a known issue with not using CM13 recovery.
I didn't root, I just unlocked the bootloader, installed TWRP, did a full backup onto an external SD card, and then flashed the new ROMs onto it. The backup on the SD made life much easier today when it hung, I was easily able to revert to the original OS, make sure everything was ok, and now I've swapped to Resurrection remix.
Click to expand...
Click to collapse
For CM and LineageOS there is no need to do an edit of build.prop. Init will detect the variant just fine and set the props by itself. Currently the variant is not supported on CM13, will include it at least tomorrow, just got the necessary info today. After that, updates won't require editing the install script anymore because model will be set as well. Next time please inform us in the thread, we were not aware of that model at all.
i think, lineage 14.1 is now available for canadian version, check out guys..there is an announcement in the thread
thilak devraj said:
i think, lineage 14.1 is now available for canadian version, check out guys..there is an announcement in the thread
Click to expand...
Click to collapse
Yes and if you would read the thread before posting, you would have seen
a) I answered them already
b) This thread is about CM13, not CM/LineageOS 14.1 and i have not yet added support to CM13...
Which specific Lineage 14.1 should I use for KII-L95? is it the honor 5x? does it requires additional steps to do?
---------- Post added at 11:44 PM ---------- Previous post was at 11:41 PM ----------
BadDaemon said:
For CM and LineageOS there is no need to do an edit of build.prop. Init will detect the variant just fine and set the props by itself. Currently the variant is not supported on CM13, will include it at least tomorrow, just got the necessary info today. After that, updates won't require editing the install script anymore because model will be set as well. Next time please inform us in the thread, we were not aware of that model at all.
Click to expand...
Click to collapse
Can I now use Honor 5x Lineage 14.1 for KII-L05? Please advise. Thanks.
It appears LG is going to release the upcoming Google Security Patches to the LG G line and newer models. This apparently includes the G3, but not sure if that includes the Verizon version of the G3. So this will include all the January security fixes from Google.
https://androidcommunity.com/lg-ann...cial-release-to-nexus-pixel-devices-20170102/
iBolski said:
It appears LG is going to release the upcoming Google Security Patches to the LG G line and newer models. This apparently includes the G3, but not sure if that includes the Verizon version of the G3. So this will include all the January security fixes from Google.
https://androidcommunity.com/lg-ann...cial-release-to-nexus-pixel-devices-20170102/
Click to expand...
Click to collapse
It's here Software Version "VS9854AA" Security patch level 2016-12-01.
dmoney98 said:
It's here Software Version "VS9854AA" Security patch level 2016-12-01.
Click to expand...
Click to collapse
That's a strange version. I would have assumed it would be 49B or 50A. Never seen a 4AA before. Weird.
But thanks for the info!
TOT back
For those interested I was on Fulmics 6.7, I toted back to 10B, Kdz to 49A and took the 4AA update. Wanted to see if I could TOT back and yes you can. Toted back to 10B and Back to Fulmics. Just a heads up for any one interested.
VS98549A
VS9854AA
I think I see what they did. It's hexadecimal. In base-16, A follows 9. A equals decimal 10. lol
So my apologies to the previous poster who did give the correct version. Since I don't have a functioning G3 anymore, I had no way to check it. I just haven't had the heart to throw away/dispose of my G3, yet. It sits on my desk. RIP G3. :crying:
iBolski said:
VS98549A
VS9854AA
I think I see what they did. It's hexadecimal. In base-16, A follows 9. A equals decimal 10. lol
So my apologies to the previous poster who did give the correct version. Since I don't have a functioning G3 anymore, I had no way to check it. I just haven't had the heart to throw away/dispose of my G3, yet. It sits on my desk. RIP G3. :crying:
Click to expand...
Click to collapse
Is this version Root-able?
ovais_43 said:
Is this version Root-able?
Click to expand...
Click to collapse
Ever since 48A, I don't believe you can root. You have to downgrade to 47A to at least use Kingroot. Otherwise, for all non-K models, the best option is to TOT flash to 10B and use Stumproot and then flash a custom stock-based ROM. XDEBs is the most popular.
iBolski said:
Ever since 48A, I don't believe you can root. You have to downgrade to 47A to at least use Kingroot. Otherwise, for all non-K models, the best option is to TOT flash to 10B and use Stumproot and then flash a custom stock-based ROM. XDEBs is the most popular.
Click to expand...
Click to collapse
OK,
Well I am currently using Tekcafe v3.5 with Gabriel Kernel for more than 2 months and its working absolutely perfect.
iBolski said:
Ever since 48A, I don't believe you can root. You have to downgrade to 47A to at least use Kingroot. Otherwise, for all non-K models, the best option is to TOT flash to 10B and use Stumproot and then flash a custom stock-based ROM. XDEBs is the most popular.
Click to expand...
Click to collapse
Haven't had to downgrade before, and my wife is running the latest OTA with a boatload of problems. Can you point me in the direction for downgrading so I can get her on a different ROM?
roflhorse said:
Haven't had to downgrade before, and my wife is running the latest OTA with a boatload of problems. Can you point me in the direction for downgrading so I can get her on a different ROM?
Click to expand...
Click to collapse
First, you have to verify what version of phone she has because if she has the K model, you will not be able to flash custom ROMs as you cannot downgrade to 10B. You can only KDZ flash to 47A which is still marshmallow. Have you done a factory reset first?
If so and she still is having problems, open up the back, remove the battery and see what her model number is. If it ends in a K (such as VS985K, or VS985WK), then you are out of luck and cannot downgrade and flash custom ROMs. You can only KDZ flash 47A, 48A or 49A images which does a factory data reset (you'll lose all data). So if you go this route, then backup all her data to your PC first.
If the model number does NOT end in a K, then you can downgrade to 10B via a TOT flash. Again, backup ALL data on her phone as it WILL be lost.
You can find instructions to downgrade to 10B here:
https://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
If she has a model K and you want to flash to 47A or 48A or 49A, then you can follow these instructions:
https://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
You can get the 47/48/49A KDZ images from here:
https://www.androidfilehost.com/?w=files&flid=35484
NOTE: Read, read, read, and then read all the instructions one more time. Make sure you completely understand what is required and how to do it. It's hard to brick it beyond repair, but you can put it into a bulk mode which requires opening up the device, and exposing the motherboard so you can short two pins. It's not completely undoable, but it can be a pain if you put it into bulk mode. That usually happens when someone flashes an incorrect boot image onto the device that is not compatible. So, again, read, read, and read again the instructions and ensure you understand everything before even beginning to attempt to flash.
xdabbeb said:
Get me a kdz and I'll see if I can find the time to do so. No promises, however, as I have a lot going on IRL.
Click to expand...
Click to collapse
Anybody have any idea where to get the newest KDZ for xdabbeb to work with?
Any recommendations for bootable replacement 4 my vs985?
Sent from my VS985 4G using XDA-Developers Legacy app
meatpuppet007 said:
Any recommendations for bootable replacement 4 my vs985?
Sent from my VS985 4G using XDA-Developers Legacy app
Click to expand...
Click to collapse
Rootable
Sent from my VS985 4G using XDA-Developers Legacy app
Thank you thank you! I purchased a used Verizonn G3 recently to use with the BYOP program on Straight Talk. I have to have a CDMA variant where I live. I had recently rooted and installed a custom ROM (and extra goodies) on a D850 (AT&T G3) for someone else, and liked the outcome so much I HAD to have one! So after finding a very good deal on a Verizon model I couldn't wait to get it redone. That was a little over a month ago, and after first doing my diligent research on the exact procedure to use I found in horror that not only had the AA patch already been put on my phone, but that it was causing problems to those who had updated, mainly in that many could no longer hook up to wifi (mine will NOT hook to wifi, and I have found NO remedy). Then I read by someone who had tried flashing back that it had caused his phone to reset the IMEI to all zeros, and rendered it useless.. So I chose to leave well enough alone figuring that someone would figure it out soon. In all likelihood the person who had screwed up his phone flashing back did something wrong, but I didn't want to chance it. Since you found that you can indeed do it I can't wait to get 'er done! Well I will wait another day or two I guess because I will THOROUGHLY research what I need to do and make sure I have all the right things downloaded prior to actually doing it because it is the only phone I have now so I really want it to go smoothly, which I've found it almost always does IF the instructions are followed to the letter and you've read over the entire thread to make sure that your bases are covered concerning any problems that did surface. I suppose many may think I'm overly cautious, but to date I've rooted and customized quite a few devices for people, and to date have not so much as soft bricked one yet.
Again thank you for being the "guinea pig" and testing this!!! You have no idea how much it's appreciated. You just made my whole week better!
Hope this gets things started,
DETAILS
Stock Korean firmware base AQF5
Rooted
Init d
Deodex
Zip aligned
Busybox
Sqlite
Thanks to
Chainfire for supersu
Ashyx for custom twrp and rooting process
Samsung for the base
Take all care back up, beyond that, your responsibility
Link :-
Android file host
https://www.androidfilehost.com/?fid=889764386195921470
Hit thanks or buy me a coffee if you wish
https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
Leave some posts so I know it works OK, I'm new to this
It would be good if someone could post if this rom was ok, as have a T825 rom built with the same method that I cannot test, due to having a T820 myself. So speak up please
Thank you for this. Now I have to ask a couple of newbie questions. I've been exclusively in the Sony Xperia and Nexus worlds before, this being my first Samsung. In trying to figure out if the processes I've become familiar with are applicable to this device, using your ROM.
For instance, my Sony's were pretty easy after the initial root. Kind souls in the community took new releases and created a pre-rooted firmware with TWRP and SuperSU built-in. I could then just dirty flash the ROM from TWRP, sometimes wiping cache/dalvic, and like magic my device is upgraded with no loss of data.
Is this how it works with this AQF5 ROM? I'm starting with a rooted (@ashyx method) T820 with AQBB. Do I just download the rooted ROM to SD card, boot to TWRP, dirty flash and go?
Thanks again!
Hi,
Dirty flash should work, sometimes I try that first and if I get any strange behaviour, do a wipe and re flash then load the rest back with titanium backup. Make sure you have all your backups organised first before starting.
Let me know how it works out. The risk with the first option is something residual being left that may result in force closes or just defeating the purpose.
Just beware if for some reason it doesn't root DM verity will occur and you will be forced to format internal data so back that up to your external card too, before, just in case, shouldn't happen though. I have no idea how many others have used this yet as there have been no replies to say all ok
rorymc928 said:
Just beware if for some reason it doesn't root DM verity will occur and you will be forced to format internal data so back that up to your external card too, before, just in case, shouldn't happen though. I have no idea how many others have used this yet as there have been no replies to say all ok
Click to expand...
Click to collapse
Not sure I can use this ROM in Germany, what kind of modifications are made? Would love to see some development
As long as you have the same model T-820 you can, some local variants have a local customisation but it's likely to be minor with this model. From memory when I set it up on mine all common languages were available, if that's your concern, make sure you have a twrp backup and you can always roll back
The only mods were as listed above, seems slightly quicker, perhaps the zip aligning, but it will allow more mods as they come along
Will flashing this trip the knox counter?
DarkXoa said:
Will flashing this trip the knox counter?
Click to expand...
Click to collapse
Always, Knox is there to tell Samsung if you've done this sort of thing, it's just what you accept with custom roms
rorymc928 said:
Always, Knox is there to tell Samsung if you've done this sort of thing, it's just what you accept with custom roms
Click to expand...
Click to collapse
I bought you a beer, but didn't find time to try it out
vonschau said:
I bought you a beer, but didn't find time to try it out
Click to expand...
Click to collapse
Thank you very much, most appreciated, let me know how it goes
Any development on tab S3 ROMs???
rorymc928 said:
As long as you have the same model T-820 you can, some local variants have a local customisation but it's likely to be minor with this model. From memory when I set it up on mine all common languages were available, if that's your concern, make sure you have a twrp backup and you can always roll back
The only mods were as listed above, seems slightly quicker, perhaps the zip aligning, but it will allow more mods as they come along
Click to expand...
Click to collapse
I have always wondered about that. Flashing a base from another country. Like I live in the US so I always have flashed USA versions. You are
saying that I CAN flash this Korean version on my T-820 phone and have all working ok with English ?
Thank you
Thibor69 said:
I have always wondered about that. Flashing a base from another country. Like I live in the US so I always have flashed USA versions. You are
saying that I CAN flash this Korean version on my T-820 phone and have all working ok with English ?
Thank you
Click to expand...
Click to collapse
For the record, I don't live in the us but bought mine from best buys whilst there, it was rooted within a couple of hours from memory,..... can't help myself ?.
I Flashed a firmware from another country after that,, just because it was a later series, can't remember which.
I use the Tweaked one as my daily driver, people seem to be finding that good. I have found the latest firmware now seems to carry out a full wipe, and I haven't managed to flash a rom over it yet, so reverted back to the Tweaked version I have.
It may require an update to TWRP
If you have any problems restore your backup, if you want to persist flash the firmware that its based on first,AQF5, then flash the ROM over it, with our without wipe.
Link to Tweaked,
https://forum.xda-developers.com/galaxy-tab-s3/development/rom-sm-t820-tweaked-t3659433
rorymc928 said:
For the record, I don't live in the us but bought mine from best buys whilst there, it was rooted within a couple of hours from memory,..... can't help myself [emoji20].
I Flashed a firmware from another country after that,, just because it was a later series, can't remember which.
I use the Tweaked one as my daily driver, people seem to be finding that good. I have found the latest firmware now seems to carry out a full wipe, and I haven't managed to flash a rom over it yet, so reverted back to the Tweaked version I have.
It may require an update to TWRP
If you have any problems restore your backup, if you want to persist flash the firmware that its based on first,AQF5, then flash the ROM over it, with our without wipe.
Link to Tweaked,
https://forum.xda-developers.com/galaxy-tab-s3/development/rom-sm-t820-tweaked-t3659433
Click to expand...
Click to collapse
It will still work in English you just have to find which is your main language in the very beginning
Sent from my [device_name] using XDA-Developers Legacy app
Works great on T820, no issues so far...
kbroh said:
Works great on T820, no issues so far...
Click to expand...
Click to collapse
Thanks,
This rom is not being developed any more,but the tweaked version in this forum, is based off the stock firmware which came after this,it runs stable, has a few enhancements and being a later base it's got a number of Samsung security updates too.
Would this thread be applicable to a Wi-Fi only S3 model "SM-T820NZKAXAR" ?
Zoandroid said:
Would this thread be applicable to a Wi-Fi only S3 model "SM-T820NZKAXAR" ?
Click to expand...
Click to collapse
Sure is. That's what I got.
DarkXoa said:
Will flashing this trip the knox counter?
Click to expand...
Click to collapse
After 10 years of the same answer its still YES...rooting always trips..
I think this thread is needed. I am an HK snapdragon S10 owner and really want root, I tried the method that is available which some claim is only for Exynos but no official word of it that I found but after flashing patched firmware, phone wouldn't go into recovery. Unless I did something wrong it doesn't work for Snap. Flash back OG firmware.
REGARDLESS, this thread I feel is needed to discuss this and methods, etc etc etc. This is mainly for HK Snaps but U.S Snaps can join this thread too but doubt there will be anything for it.
Hmm, I thought of trying on mine too, but I don't have time to do it until May. Good to know you didn't brick your phone. I'll give it a shot when I have time too just in case.
Did anyone else try it?
I thought I read someone tried but he didn't get far. Trying to find his post.
Yeah, I read he got to Odin stalling at verifying his patched file or something. Doesn't mean it doesn't work tho. I want to try for myself when I have time, unless more people try and they all say it doesn't work. Also, maybe we could try with Heimdall on Linux.
Yea I think he did but for me it flashed my file fine, just the next step I couldn't get to work, booting to recovery.
Based on the documentation, I think that pressing the buttons right for booting sounds a bit finicky. Even for accessing download mode on my phone when I unlocked it, the button combination wouldn't work right away. Same for standard recovery, I had to use adb to boot to recovery for the first time, then after that only did doing it via the buttons worked. I'm wondering if it could be something like that that was the problem for you. Like, I wouldn't necessarily assume it doesn't work at the moment, even though I doubt it works with the SD variants. I think it deserves more tries from more people.
I agree, it could just be fails on my part, I may try again but once I flashed back to OG it had to wipe my data and don't want that to happen again unless I know root will work. I wish topjohnwu would state if it works on snap. So many people asked him on twitter but no answer.
jam51dill said:
I agree, it could just be fails on my part, I may try again but once I flashed back to OG it had to wipe my data and don't want that to happen again unless I know root will work. I wish topjohnwu would state if it works on snap. So many people asked him on twitter but no answer.
Click to expand...
Click to collapse
Yeah, I asked him too. And it's why I'm waiting for next month before trying it myself. I don't have time to go through the process right now, but I'm down to try it a couple times in a row once I have time.
I guess I'll join this thread too. Haven't tried the root method but don't want to risk unless I know for a fact it works in HK.
I'm waiting to buy s10e snap for this reason. No root, no buy..
I choose Android because of its freedom vs Apple system. I want to do anything with MY phone.
Root should always be allowed, and each user then takes the conscious risk!
I prefer a waiting Lounge versus the waiting room! Since we will be here awhile...
Not 100 on it but I asked some guy who knows his stuff and has done some root for older HK Samsungs like Note 9 etc. Hes saying I need to compile a kernel with root protections etc removed, patch with Magisk and flash in Odin. Then you'll be rooted. For me specifically, the HK S10 kernel source is not out. Got to request it and wait. All of this could get us root. If someone wants to try this method with the HK S10 Plus or e since those kernel sources are already out, that would be nice to see if it works.
Has any one tried the CROM method by any chance i thought that app was specifically for unlocking the Hong Kong bootloaders
HK S10 checking in
SM-G9730 here, Excited for a soon (hopefully) root.
Crickets chirping
Don't hold your breath. Anyone who bought a US Snapdragon S10 thinking they would get root is fooling themselves.
bassguy60 said:
Don't hold your breath. Anyone who bought a US Snapdragon S10 thinking they would get root is fooling themselves.
Click to expand...
Click to collapse
This thread is for the HK (Hong Kong) variant.
Outbreak444 said:
This thread is for the HK (Hong Kong) variant.
Click to expand...
Click to collapse
OP says, "...U.S Snaps can join this thread...".
bassguy60 said:
OP says, "...U.S Snaps can join this thread...".
Click to expand...
Click to collapse
I stand corrected... Carry on