Hey anyone connected their device via UART?
If possible can someone DD system, boot, bootloader, dtb, etc and send me the files?
Why cant i grab a mibox update and unpack?
Its heavily encrypted, the chances of us gaining Xiaomi's decryption keys are slim to null.
And for what i need to do, i must have a decrypted file system to work with.
I thought you were getting a mi box to work with?
oOflyeyesOo said:
I thought you were getting a mi box to work with?
Click to expand...
Click to collapse
i did, its a complete brick with absoluely nothing on the eMMC and to write directly to it(if possible) i need the decrypted partitions for the device
Ricky Divjakovski said:
Hey anyone connected their device via UART?
If possible can someone DD system, boot, bootloader, dtb, etc and send me the files?
Why cant i grab a mibox update and unpack?
Its heavily encrypted, the chances of us gaining Xiaomi's decryption keys are slim to null.
And for what i need to do, i must have a decrypted file system to work with.
Click to expand...
Click to collapse
There are at least 6 different boxes that may be referred to as MiBox.
Please, to avoid confusion rampant on this subject, use the exact model number as in MDZ-XX-YY.
That would be a good start...
bigtalker said:
There are at least 6 different boxes that may be referred to as MiBox.
Please, to avoid confusion rampant on this subject, use the exact model number as in MDZ-XX-YY.
That would be a good start...
Click to expand...
Click to collapse
Either will do
Mdz-16-ab would be best
bigtalker said:
There are at least 6 different boxes that may be referred to as MiBox.
Please, to avoid confusion rampant on this subject, use the exact model number as in MDZ-XX-YY.
That would be a good start...
Click to expand...
Click to collapse
It seems like the software between models is basically the same, so it shouldn't matter.
oOflyeyesOo said:
It seems like the software between models is basically the same, so it shouldn't matter.
Click to expand...
Click to collapse
Pretty much is apart from little dtb/bootloader changes i am guessing
Ricky Divjakovski said:
Hey anyone connected their device via UART?
If possible can someone DD system, boot, bootloader, dtb, etc and send me the files?
Why cant i grab a mibox update and unpack?
Its heavily encrypted, the chances of us gaining Xiaomi's decryption keys are slim to null.
And for what i need to do, i must have a decrypted file system to work with.
Click to expand...
Click to collapse
Someone did what you want for model 16 ab. but I did not see the dtb file.
https://mega.nz/#F!9912FQJQ!Z9HyWJOJRflrGGEUPTI3Ag
oOflyeyesOo said:
It seems like the software between models is basically the same, so it shouldn't matter.
Click to expand...
Click to collapse
You just lost any scintilla of credibility on this subject.
---------- Post added at 02:12 AM ---------- Previous post was at 01:56 AM ----------
Ricky Divjakovski said:
Pretty much is apart from little dtb/bootloader changes i am guessing
Click to expand...
Click to collapse
You are way off track. Perhaps you should peruse a salient thread that has been here for over 14 months that may shed some insight on this subject,,,,,,,
https://forum.xda-developers.com/an...05x-help-mi-box-android-tv-mdz-16-ab-t3477286
bigtalker said:
You just lost any scintilla of credibility on this subject.
---------- Post added at 02:12 AM ---------- Previous post was at 01:56 AM ----------
You are way off track. Perhaps you should peruse a salient thread that has been here for over 14 months that may shed some insight on this subject,,,,,,,
https://forum.xda-developers.com/an...05x-help-mi-box-android-tv-mdz-16-ab-t3477286
Click to expand...
Click to collapse
Hmm not sure about that, my research is very different compared to others, when i find something i consider it a possibillity and leave it to myself to decide, sometimes information you see online isnt always true
oOflyeyesOo said:
It seems like the software between models is basically the same, so it shouldn't matter.
Click to expand...
Click to collapse
it absolutely matters lol..international variant has google tv os, locoed bl and encrypted to where u cant even use amlogic burning tool whereas the AA variant you can do all that and doesnt have google tv os to my understanding..
i suppose from his bricked standpoint it kight not matter but typically it doeslol
Related
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.
So i hard bricked my sprint g5. lol No big deal.
We wont get into how, I know how i did it,
now i have a a zva dump from from lgup. I have a zv8 kdz. which I have extracted into many a images and bins. and a zv6 .tot which i found out passes for downgrade check in lgup just errors out somewhere else flash back and forth plenty of times zv6 and 8 straight in download mode no reboots.. i didnt think to reflash zv8 before rebooting and no crap hard brick. Like it set in as soon as i pulled the battery out for a reboot i was like oh ****
How can I make one of the debrick.img to try to see if she will boot of sd card to download mode?
TheMadScientist420 said:
So i hard bricked my sprint g5. lol No big deal.
We wont get into how, I know how i did it,
now i have a a zva dump from from lgup. I have a zv8 kdz. which I have extracted into many a images and bins. and a zv6 .tot which i found out passes for downgrade check in lgup just errors out somewhere else flash back and forth plenty of times zv6 and 8 straight in download mode no reboots.. i didnt think to reflash zv8 before rebooting and no crap hard brick. Like it set in as soon as i pulled the battery out for a reboot i was like oh ****
How can I make one of the debrick.img to try to see if she will boot of sd card to download mode?
Click to expand...
Click to collapse
Bump
Sent from my LG-H830 using XDA Labs
Nick216ohio said:
Bump
Sent from my LG-H830 using XDA Labs
Click to expand...
Click to collapse
Did you brick yours?
so im gonna try a few things tonight
first u have to have a sd card bigger than 32 gb as 32 gb cards formatted are 29.9 gb. NOT ENOUGH.
I got a 128 and also has to be a class 10 card. im working on downloading another models debrick image so i can see how its constructed.
and i will try to piece one together from the kdzs tots and my zva dump
TheMadScientist420 said:
Did you brick yours?
so im gonna try a few things tonight
first u have to have a sd card bigger than 32 gb as 32 gb cards formatted are 29.9 gb. NOT ENOUGH.
I got a 128 and also has to be a class 10 card. im working on downloading another models debrick image so i can see how its constructed.
and i will try to piece one together from the kdzs tots and my zva dump
Click to expand...
Click to collapse
I really hope you succeed. I have a bricked V20 and zero chance of figuring this out myself.
askermk2000 said:
I really hope you succeed. I have a bricked V20 and zero chance of figuring this out myself.
Click to expand...
Click to collapse
Yea i hope i do too
Ls992 hardbrick
gratefuldeaddougie said:
Ls992 hardbrick
Click to expand...
Click to collapse
What was the reasoning behind this post?
Do you have one hardbricked also?
TheMadScientist said:
What was the reasoning behind this post?
Do you have one hardbricked also?
Click to expand...
Click to collapse
I do have a LS 992 in my possession. It is not hard bricked. To day I will force a hard brick by downgrading improperly as an experiment to see if my theory holds true, universally across LG's G series. I have subscribed to a few services that provide the Quallcomm firehose, raw, and patch files that (in my opinion) Qualcomm should provide for free to the registered users of their products... What's needed is a Qualcomm recovery image for the LS992. Now there is a technique to build these files from scratch with nothing but traditional LG tools that most LG enthusiasts, I'm assuming, are already familiar with or should be. BoardDiag2.99 for .tot's and WindowsLGFirmwareExtract for .kdz's. For starters we need to know what FW version we bricked on. Take careful consideration that many devices on a global scale have been completely reformatted, partitioned, and flashed with FW different than what is embossed on the Logic Board. For example: I have probably purchased at least a dozen G4's advertised as H811 and retain the H811 stamp on the back bezel; but retain the gold embossed marking of H810 on the main board. I imagine this is done to mark up the price. As we know the H811 became more desirable than the H810 because of the difference of T-MO's and AT&T's corporate positions concerning bootloader unlocking. So before doing any "cliff diving triple lindey twist" down the deep flash rabbit whole we have to absolutely be positive of our main board variant and if it matches the FW variant we bricked on. Once that is established it is safe to assume our time and efforts will not be a waste of time. Is yourr main board Printed with LS9922?
---------- Post added at 07:54 PM ---------- Previous post was at 07:40 PM ----------
askermk2000 said:
I really hope you succeed. I have a bricked V20 and zero chance of figuring this out myself.
Click to expand...
Click to collapse
Follow this thread. I am going to try and help. Although this thread is for the LS992, I belive the concept is universal across Qualcomm platforms, specifically LG's. There is a post on the VS996 available to prepare your mind. If of course if you're looking for the mindless route there are many services in which to mail your device to. Most legit services charge about 50 bucks.
---------- Post added at 08:40 PM ---------- Previous post was at 07:54 PM ----------
I have not done any work on the G5 as of yet. I have acquired this device in hopes of safely and successfully rooting it. If the Sprint could be rooted. then the rest should just fall into place. As a matter of fact (I think) the board must be connected to the pc using the test points. The reason being is that even if when connected, device manager recognizes phone as "QHUSB_BULK" or "QDLoader_9008" the modem does not connect. Carefully exame the Windows Device Manager to be certain we are connected as QHUSB AND MODEM. If no QC modem Is avail. then the test points need to be accessed. With the skilled precision of a nuclear physicist, remove the board. Do not attempt this without a heat gun or hair dryer. You will break, if not, at least bend the chassis. Besides not to mention the LCD and Digitizer are at high risk if not reserving the highest level of attention and patience. Stopping often to evaluate our progress during disassembly is a good and advised practice, when concerning doing something we have never done before. Welcome to the world of the unknown. I personally shall feel no remorse if you yourself break your own device. I've have not taken apart this device my self. MadScientist? Can you find us a TUT on doing this? As this is your thread. I will be looking into building a recovery image prior to bricking my LS992. So that we will be able to revive our devices together.
gratefuldeaddougie said:
So before doing any "cliff diving triple lindey twist" down the deep flash rabbit whole we have to absolutely be positive of our main board variant and if it matches the FW variant we bricked on. Once that is established it is safe to assume our time and efforts will not be a waste of time.
Click to expand...
Click to collapse
Interesting. Why is it important to know which firmware we bricked on?
In the case of V20, it seems most boards are marked with *VS995* (the Verizon variant), including mine (H918 T-Mobile).
But I know for certain my model is H918 since the unique TMO bootloader key is in the QFPROM. That's the reason I bricked, I flashed H910PR firmware.
I had never owned a LG phone before, nor any American variant. So I walked into a trap there Could not see any warnings on the V20 forum either. Though I have put up some now
tech mine is on no firmware i wiped all partitions on mine. but zv8 was what i was on
gratefuldeaddougie said:
I do have a LS 992 in my possession. It is not hard bricked. To day I will force a hard brick by downgrading improperly as an experiment to see if my theory holds true, universally across LG's G series. I have subscribed to a few services that provide the Quallcomm firehose, raw, and patch files that (in my opinion) Qualcomm should provide for free to the registered users of their products... What's needed is a Qualcomm recovery image for the LS992. Now there is a technique to build these files from scratch with nothing but traditional LG tools that most LG enthusiasts, I'm assuming, are already familiar with or should be. BoardDiag2.99 for .tot's and WindowsLGFirmwareExtract for .kdz's. For starters we need to know what FW version we bricked on. Take careful consideration that many devices on a global scale have been completely reformatted, partitioned, and flashed with FW different than what is embossed on the Logic Board. For example: I have probably purchased at least a dozen G4's advertised as H811 and retain the H811 stamp on the back bezel; but retain the gold embossed marking of H810 on the main board. I imagine this is done to mark up the price. As we know the H811 became more desirable than the H810 because of the difference of T-MO's and AT&T's corporate positions concerning bootloader unlocking. So before doing any "cliff diving triple lindey twist" down the deep flash rabbit whole we have to absolutely be positive of our main board variant and if it matches the FW variant we bricked on. Once that is established it is safe to assume our time and efforts will not be a waste of time. Is yourr main board Printed with LS9922?
---------- Post added at 07:54 PM ---------- Previous post was at 07:40 PM ----------
Follow this thread. I am going to try and help. Although this thread is for the LS992, I belive the concept is universal across Qualcomm platforms, specifically LG's. There is a post on the VS996 available to prepare your mind. If of course if you're looking for the mindless route there are many services in which to mail your device to. Most legit services charge about 50 bucks.
---------- Post added at 08:40 PM ---------- Previous post was at 07:54 PM ----------
I have not done any work on the G5 as of yet. I have acquired this device in hopes of safely and successfully rooting it. If the Sprint could be rooted. then the rest should just fall into place. As a matter of fact (I think) the board must be connected to the pc using the test points. The reason being is that even if when connected, device manager recognizes phone as "QHUSB_BULK" or "QDLoader_9008" the modem does not connect. Carefully exame the Windows Device Manager to be certain we are connected as QHUSB AND MODEM. If no QC modem Is avail. then the test points need to be accessed. With the skilled precision of a nuclear physicist, remove the board. Do not attempt this without a heat gun or hair dryer. You will break, if not, at least bend the chassis. Besides not to mention the LCD and Digitizer are at high risk if not reserving the highest level of attention and patience. Stopping often to evaluate our progress during disassembly is a good and advised practice, when concerning doing something we have never done before. Welcome to the world of the unknown. I personally shall feel no remorse if you yourself break your own device. I've have not taken apart this device my self. MadScientist? Can you find us a TUT on doing this? As this is your thread. I will be looking into building a recovery image prior to bricking my LS992. So that we will be able to revive our devices together.
Click to expand...
Click to collapse
The device is easy to tear apart take 2 screws out. And pry apart. I have firmwares extracted. The elf files i hqve a load of files but board diag do3s not load tye elf needed for repair
TheMadScientist said:
The device is easy to tear apart take 2 screws out. And pry apart. I have firmwares extracted. The elf files i hqve a load of files but board diag do3s not load tye elf needed for repair
Click to expand...
Click to collapse
What versions of FW files? I'd like to have a look for myself.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
gratefuldeaddougie said:
What versions of FW files? I'd like to have a look for myself.
Click to expand...
Click to collapse
For me. I can only speak for myself. I like to start with the latest version that is known to be downgradable.
---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------
gratefuldeaddougie said:
What versions of FW files? I'd like to have a look for myself.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
For me. I can only speak for myself. I like to start with the latest version that is known to be downgradable.
Click to expand...
Click to collapse
You could probably save us some time if you already know what that is.
gratefuldeaddougie said:
What versions of FW files? I'd like to have a look for myself.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
For me. I can only speak for myself. I like to start with the latest version that is known to be downgradable.
---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------
You could probably save us some time if you already know what that is.
Click to expand...
Click to collapse
I was able to successfully downgrade to zv8 from zva
I have reason to believe i could make it to zv6 as lg flashtool was passing antirollback checks with zv6 but encounters other errors but successfully zv8 kdz
mine isa already in qloader 9008
which like alectel 9008 is fastboot i wish i could flash it that way
gratefuldeaddougie said:
What versions of FW files? I'd like to have a look for myself.
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
For me. I can only speak for myself. I like to start with the latest version that is known to be downgradable.
---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------
You could probably save us some time if you already know what that is.
Click to expand...
Click to collapse
One thing is for sure. The version of Android in which said device is Bricked operating in. Has to match the version of the FW that we would prefer to extract. Any questions so far? I'm just gonna wait for your Q. As As I'm working on another device here as well. My question to you is, What tot did you brick on? & What is the latest "latest downgradable" version?
---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------
TheMadScientist said:
I was able to successfully downgrade to zv8 from zva
I have reason to believe i could make it to zv6 as lg flashtool was passing antirollback checks with zv6 but encounters other errors but successfully zv8 kdz
mine isa already in qloader 9008
which like alectel 9008 is fastboot i wish i could flash it that way
Click to expand...
Click to collapse
Notice how I take special care in saying "universally across LGs" not universally across Qualcomms.
gratefuldeaddougie said:
One thing is for sure. The version of Android in which said device is Bricked operating in. Has to match the version of the FW that we would prefer to extract. Any questions so far? I'm just gonna wait for your Q. As As I'm working on another device here as well. My question to you is, What tot did you brick on? & What is the latest "latest downgradable" version?
Click to expand...
Click to collapse
Zv8 is the one i bricked on and the last confirmed down gradable version.
gratefuldeaddougie said:
One thing is for sure. The version of Android in which said device is Bricked operating in. Has to match the version of the FW that we would prefer to extract. Any questions so far? I'm just gonna wait for your Q. As As I'm working on another device here as well. My question to you is, What tot did you brick on? & What is the latest "latest downgradable" version?
---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------
Notice how I take special care in saying "universally across LGs" not universally across Qualcomms.
Click to expand...
Click to collapse
yes as lgs harbricks are diffrent i have dealt with g 2 g3 and g4 hardbricks before all sprint varients
let me see if mine shows as a modem also
nope only qusb under ports
heres the zv8 kdz
https://drive.google.com/file/d/0BxacnHqAaZbKTWtNd0U2eDJVRDg/view?usp=sharing
O.K. ZV8 it is. That is more unlikely than probable. And is in our favor. And I think I just figured out how to use this app. That is also in our favor. We are on a roll.
---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------
Alright. How are you extracting it. What tool.
N9500 ONLY. DOESNT WORK WITH US MODELS. STOP THINKING ITS THE SAME JUST CUZ BOTH ARE SNAPDRAGON.
EDIT: YOU want to try, you try, else DO not flood the thread with useless comments about how safe is this or what not. If you are afraid the chinese will take your close to useless info and kidnap you, can't help you with that.
I unlocked my BL with this file. Currently waiting for people to make 3rd party roms for it.
Attached link to my gdrive.
https://drive.google.com/open?id=0B-Wqzmcwpi_9c1BpUUJPenI1Y00
Download and install. It will prompt you if you wish to unlock BL. It will not wipe ur internal. You can proceed with ODIN to flash TWRP.
TWRP is available too.
TWRP link : https://drive.google.com/open?id=0B-Wqzmcwpi_9WGJIN0R2NVBtNUk
PLEASE have firmware files available in case of any errors.
AndroidPay works. Magisk is fine
NOT RESPONSIBLE FOR ANY DAMAGES.
Has anyone tried this? The file is called 835crom....... 835 snapdragon I'm assuming. I downloaded it just in case, but won't install just yet. Though, if it were true, I'd unlock my bootloader in a heartbeat.
Permissions are kinda insane but unlocking bootloader is basically changing everything. I still don't trust enough to install.
mas5acre said:
Permissions are kinda insane but unlocking bootloader is basically changing everything. I still don't trust enough to install.
Click to expand...
Click to collapse
You can try it. I have done it. Permissions might be alot as it sends the info it needs to the chinese server for unlocking. Anyway CROM service is used inthe Chinese market due to regulations. Can be downloaded off Samsung Galaxy Apps if you are wary.
Great now we are unlocking access via a Chinese server. 'Cause that seems safe. Not saying anything against China but, a majority of hacks are produced there.
---------- Post added at 02:27 AM ---------- Previous post was at 02:17 AM ----------
Who's brave enough? I also don't see the point of most of these permission requirments....Even if it needs to access servers. Why does it need to access my calendar?
dazemc said:
Great now we are unlocking access via a Chinese server. 'Cause that seems safe. Not saying anything against China but, a majority of hacks are produced there.
---------- Post added at 02:27 AM ---------- Previous post was at 02:17 AM ----------
Who's brave enough? I also don't see the point of most of these permission requirments....Even if it needs to access servers. Why does it need to access my calendar?
Click to expand...
Click to collapse
Lol. That's how it's done there. If you are against it, no one's forcing you to do it. If you actually did some research about it, xda has posts about CROM. Besides, its distributed itself by Samsung inthe Galaxy Apps.
I would not trust this and good luck to whoever does.
dazemc said:
I would not trust this and good luck to whoever does.
Click to expand...
Click to collapse
Sure. If you don't trust Samsung then you shouldn't be using the phone. Please kindly leave and do not flood the thread with non constructive comments. Thanks!
I'm not finding it in galaxy apps. I might install eventally if someone volunteers to test as well. To the OP, if this works, thanks for pointing it out.
Not saying I don't believe you or anything. I hope this isn't offensive, I apologize if so. You can understand why most people would be weary.
Just curious based on your screenshot, it just says successful and doesn't go through the process of wiping your internal data? Which usually is kinda part of the process when unlocking the BL...
1
wigglitz said:
Not saying I don't believe you or anything. I hope this isn't offensive, I apologize if so. You can understand why most people would be weary.
Just curious based on your screenshot, it just says successful and doesn't go through the process of wiping your internal data? Which usually is kinda part of the process when unlocking the BL...
Click to expand...
Click to collapse
Entirely up to u to try. If u are afraid of risks, then so be it. There surely will be people who try. And no, it does not wipe. You can go and visit S8 thread where there is CROM service threads about it. Downloading Apps may requires a Chinese Samsung account.
BlueEffect said:
Besides, its distributed itself by Samsung inthe Galaxy Apps.
Click to expand...
Click to collapse
I dont see it in the samsung galaxy apps app...screenie please
THIS IS NOT FOR USA MODELS! CHINESE MODELS ONLY! Thats why its not in galaxy apps for usa region.
me2151 said:
THIS IS NOT FOR USA MODELS! CHINESE MODELS ONLY! Thats why its not in galaxy apps for usa region.
Click to expand...
Click to collapse
If you look a couple posts back:
BlueEffect said:
Downloading apps may requires a Chinese Samsung account.
Click to expand...
Click to collapse
Doesn't necessarily mean that it only works on Chinese models...
wigglitz said:
If you look a couple posts back:
Doesn't necessarily mean that it only works on Chinese models...
Click to expand...
Click to collapse
I 100% guarantee its chinese models only. They may be snapdragon but their bootloader is setup differently. USA models CANNOT UNLOCK via their method.
It's for model 950chn
Tried it and all it does is crash.
Its super worthless for USA Models
Mehi7 said:
Tried it and all it does is crash.
Its super worthless for USA Models
Click to expand...
Click to collapse
Didnt u read. For N9500 only.
dazemc said:
Great now we are unlocking access via a Chinese server. 'Cause that seems safe. Not saying anything against China but, a majority of hacks are produced there.
---------- Post added at 02:27 AM ---------- Previous post was at 02:17 AM ----------
Who's brave enough? I also don't see the point of most of these permission requirments....Even if it needs to access servers. Why does it need to access my calendar?
Click to expand...
Click to collapse
Dude it's a chinese phone only sold in china, don't tell me you expected anything else lol
Complaints about sending data to China; NO ONE complains about the data they give to Google.
Is anyone already working on porting TWRP to our u11 life? If not, I might try building for us all. Let me know so I don't waste my time.
Thanks!
dpryor88 said:
Is anyone already working on porting TWRP to our u11 life? If not, I might try building for us all. Let me know so I don't waste my time.
Thanks!
Click to expand...
Click to collapse
Dont think it would be considered wasting your time.
I'm here if you need anything I can offer to assist in this.
twinnfamous said:
Dont think it would be considered wasting your time.
I'm here if you need anything I can offer to assist in this.
Click to expand...
Click to collapse
Thanks dude!
I'll start tomorrow maybe after I get off work if I'm not too tired. No promises
I just want this to be like my old m8. An active community though I realize we aren't dealing with a flagship here, I'm still going to try to contribute somehow.
dpryor88 said:
Thanks dude!
I'll start tomorrow maybe after I get off work if I'm not too tired. No promises
I just want this to be like my old m8. An active community though I realize we aren't dealing with a flagship here, I'm still going to try to contribute somehow.
Click to expand...
Click to collapse
Nice to see some development interest for this phone!
Maybe it's too early to know but recovery for T Mobile variant will be the same as Android One?
Sent from my Huawei P9 powered by BlueWei [emoji41]
If I had the device I'd take a gander at making a recovery. I'd even make a CWM just for the fun of it if possible. Keep in mind I've never ported a recovery but I don't imagine the process is that difficult.
Marsou77 said:
Nice to see some development interest for this phone!
Maybe it's too early to know but recovery for T Mobile variant will be the same as Android One?
Click to expand...
Click to collapse
My guess is that the Android One variant will have A/B partitions for seamless updates, so there's going to be a different recovery and install method. All devices endorsed by Google since the launch of the Pixel use the new partition table and this results in difficulty in 3rd party development. Pixel doesn't have an official LOS ROM yet and just got official Magisk last month. It's going to be a rough start, but the community will grow.
Sent from my Mi A1 using XDA Labs
We are able to unlock the bootloader, Which means we can go Super CID. With Super CID we can flash (in DL mode) a magisk patched boot.img , and achieving root access. So next will be porting a recovery........ Get to work.
cbrown245 said:
We are able to unlock the bootloader, Which means we can go Super CID. With Super CID we can flash (in DL mode) a magisk patched boot.img , and achieving root access. So next will be porting a recovery........ Get to work.
Click to expand...
Click to collapse
You don't need SuperCID to flash a boot.img. That's simply incorrect.
Also, there was a link posted in the U11 TWRP thread to a test TWRP build for the U11 Life. Not sure if anyone tried it, but there were also device files uploaded, so it's probably a good place to start.
@sabpprook
Captain_Throwback said:
You don't need SuperCID to flash a boot.img. That's simply incorrect.
Also, there was a link posted in the U11 TWRP thread to a test TWRP build for the U11 Life. Not sure if anyone tried it, but there were also device files uploaded, so it's probably a good place to start.
@sabpprook
Click to expand...
Click to collapse
Technically yes and no , there arent any Tmobile boot img's floating around, so it has to be another GSM boot img. To ensure there are no hiccups being SuperCID wouldn't hurt.
cbrown245 said:
Technically yes and no , there arent any Tmobile boot img's floating around, so it has to be another GSM boot img. To ensure there are no hiccups being SuperCID wouldn't hurt.
Click to expand...
Click to collapse
I repeat: SuperCID has nothing to do with flashing a boot.img. You can literally flash any boot.img that fits on your device (with a proper header & dtb) if the bootloader is unlocked. CID isn't involved. In fact, SuperCID leads to issues with Carrier customization on newer devices, and RUUs will only flash on devices with the correct CID, not SuperCID. I think that happened around the time of the M9 Marshmallow or Nougat update.
In fact, you don't even have to flash the boot.img. You can simply fastboot boot it, and you should still be able to achieve root. And then you can back up the stock boot.img so there IS a T-Mobile boot.img "floating around." If someone just downloads one of the RUUs from Easy Firmware, uses the Decrypt Tool to extract it, and then Magisk to patch it, it should be possible to dump all of the stock T-Mobile device partitions.
Haven't seen you around since the Evo LTE. But I may be getting the U11 Life pretty soon, so I should be able to contribute in some way or form to the development of the device.
Anyone try that test TWRP build in the u11 thread yet? I'm thinking about it..
dpryor88 said:
Anyone try that test TWRP build in the u11 thread yet? I'm thinking about it..
Click to expand...
Click to collapse
u know the risks I looked through the source it has sd660 not 630. So I'm not sure what would happen but we won't know till someone finds out. Also I'm not sure if all the partition info would be the same.
twinnfamous said:
u know the risks I looked through the source it has sd660 not 630. So I'm not sure what would happen but we won't know till someone finds out. Also I'm not sure if all the partition info would be the same.
Click to expand...
Click to collapse
Yeah I'm not gonna chance it haha.
dpryor88 said:
Yeah I'm not gonna chance it haha.
Click to expand...
Click to collapse
Let me know how it goes
twinnfamous said:
Let me know how it goes
Click to expand...
Click to collapse
No I said I'm not going to haha. I'll wait
dpryor88 said:
No I said I'm not going to haha. I'll wait
Click to expand...
Click to collapse
OK my fault got excited and didn't read it rite
---------- Post added at 04:39 AM ---------- Previous post was at 04:18 AM ----------
dpryor88 said:
No I said I'm not going to haha. I'll wait
Click to expand...
Click to collapse
I paid the 15 dollars from easy firmware hopefully it's not a scam website and real files. I'm down loading one now. I'll keep you posted
dpryor88 said:
Yeah I'm not gonna chance it haha.
Click to expand...
Click to collapse
You don't even have to flash it. Just fastboot boot it from the bootloader and see if it works. That makes literally zero changes to your device. Nothing to risk at all.
Also, if you're not willing to soft brick your device for the purpose of testing, then there's no way you'll ever have a working TWRP.
twinnfamous said:
OK my fault got excited and didn't read it rite
---------- Post added at 04:39 AM ---------- Previous post was at 04:18 AM ----------
I paid the 15 dollars from easy firmware hopefully it's not a scam website and real files. I'm down loading one now. I'll keep you posted
Click to expand...
Click to collapse
It's a real website, and the files are all real. If you grab the combined signed RUU for the 617 region, you should be able to patch the extracted boot.img with Magisk for root.
Captain_Throwback said:
You don't even have to flash it. Just fastboot boot it from the bootloader and see if it works. That makes literally zero changes to your device. Nothing to risk at all.
Click to expand...
Click to collapse
Good call haha. Not sure what I was thinking. I'll give it a shot tomorrow.
Captain_Throwback said:
You don't even have to flash it. Just fastboot boot it from the bootloader and see if it works. That makes literally zero changes to your device. Nothing to risk at all.
Also, if you're not willing to soft brick your device for the purpose of testing, then there's no way you'll ever have a working TWRP.
It's a real website, and the files are all real. If you grab the combined signed RUU for the 617 region, you should be able to patch the extracted boot.img with Magisk for root.
Click to expand...
Click to collapse
Thanks and I'm willing to do anything it takes. I know the brick won't be forever I've been getting HTC since the evo days. I really do appreciate all your help.
Anybody have a working copy? I downloaded one from here https://androidfilehost.com/?fid=6006931924117934353 but it seems to be corrupted. Failed md5 invalid binary. Downloaded twice with same result. Anybody have another link would be appreciated.
BTW renaming without the md5 doesn't work. Odin doesn't even seem to recognize it.
Edit - Found. @Mentalmuso was nice enough to get this. If you're here then this saved your life, so don't forget to shoot him a beer.
https://mega.nz/#!j18VnAbC!qBMrOtDRY6H2qtahWcF5gJiYuf6m4QyfKxzEJ4g09rg
I downloaded the combination ROM from the link above, but have never used one (or even heard of them before this post), so I have a few questions:
(1) From what I've read, combo ROMs are 'service' ROMs with capabilities that are mostly useful on phones, but also seems to give the user more freedom over the device, in general. Is this correct?
(2) What advantages on an aleady rooted tablet?
(3) Wanna share any user experience(s)?
Thanks
TiTiB said:
I downloaded the combination ROM from the link above, but have never used one (or even heard of them before this post), so I have a few questions:
(1) From what I've read, combo ROMs are 'service' ROMs with capabilities that are mostly useful on phones, but also seems to give the user more freedom over the device, in general. Is this correct?
(2) What advantages on an aleady rooted tablet?
(3) Wanna share any user experience(s)?
Thanks
Click to expand...
Click to collapse
Service rom. Can help you out of bricks. Nothing when you don't need it. But everything when you do.
do you still have that combination file? I am trying mega link but it doesnt work anymore
mp052052 said:
do you still have that combination file? I am trying mega link but it doesnt work anymore
Click to expand...
Click to collapse
I guess it was removed. Here's another one. A bit older but same bootloader rev number which i believe is all that matters.
https://androidfilehost.com/?fid=6006931924117944557
Unfortunately you won't be able to flash combination files due to some new Samsung security feature with 2019 devices. I've been trying various ways unsuccessfully so far.
Maybe @ashyx can help.
Is there any other way to do FRP bypass? My tablet doesnt have Sim so sim method wont work
mp052052 said:
Is there any other way to do FRP bypass? My tablet doesnt have Sim so sim method wont work
Click to expand...
Click to collapse
I'm in the same boat. Got mine off ebay frp locked. If you find out anything lmk and I'll do the same.
will do
mp052052 said:
will do
Click to expand...
Click to collapse
here's a no sim method. I couldnt get smartswitch to connect after the reboot but maybe you'll have better luck. https://www.youtube.com/watch?v=1ydqy3Nur3w&t=329s
This smartswitch wont work. I have Nov security update so after restart it wont start smartswitch. My firmware is T860CXXs1xxxx so combination T860CXXU1ASG8 wont work cause it has U1 not S1 build. It wont let me flash it. Numbers should match so you are able to flash combination. I believe we will have to wait when S1 or S2 or S3 combination firmware will come out. Better not to flash newer firmware. I guess we have exactly the same situation. If I FRP my tab I will message you
---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------
I tired all previous methods but could not find solution. Usually its a couple of months after security update. So we are very close to crack FRP
Anyone have any luck with bypassing FRP on the Tab S6 yet? I'm in the same boat. Can't flash combination file.
andorraa said:
Anyone have any luck with bypassing FRP on the Tab S6 yet? I'm in the same boat. Can't flash combination file.
Click to expand...
Click to collapse
Pm sent
Also need help please
Airtioteclint said:
Pm sent
Click to expand...
Click to collapse
please can you help me, need to remove frp, i have combo and stock, cant flash combo
Help plz
Airtioteclint said:
Pm sent
Click to expand...
Click to collapse
Same problem(
andorraa said:
Anyone have any luck with bypassing FRP on the Tab S6 yet? I'm in the same boat. Can't flash combination file.
Click to expand...
Click to collapse
I'm in the same boat. FRP locked.
I would REALLY appreciate some assistance and of course I would be eternally gratefull!!
THANKS!!
Problem solved!!
I just figured out how to get passed FRP lock without flashing firmware or using a computer.
Fully updated tab S6. Fairly simple to do. I will be posting a how to as soon as I can. At work now and simply can't. Tropical storm and all....
If you would like to ask a question, feel free.
Woo hoo!!!
Sent from my SM-T860 using Tapatalk
ovalman123 said:
Problem solved!!
I just figured out how to get passed FRP lock without flashing firmware or using a computer.
Fully updated tab S6. Fairly simple to do. I will be posting a how to as soon as I can. At work now and simply can't. Tropical storm and all....
If you would like to ask a question, feel free.
Woo hoo!!!
Sent from my SM-T860 using Tapatalk
Click to expand...
Click to collapse
What question ? Simply explain process and solution (if any) to others and that's all.
If solution is simple, so procedure explanation will be short as well and benefit to those who were stuck in FRP.
Personally, I doubt it is possible without usage of re-flashing or computer.
Since last post at August 4th untill now, it seems a very long 20 days tropical storm indeed.
I don't think I like your attitude.
I have not been on much and I forgot to explain the process I used.
It is possible as I have done it. Don't really care if you doubt it.
For anyone else that would like to know what I did, I will post tomorrow. I am working today and can't.
Sent from my SM-G988U1 using Tapatalk
ovalman123 said:
I don't think I like your attitude.
I have not been on much and I forgot to explain the process I used.
It is possible as I have done it. Don't really care if you doubt it.
For anyone else that would like to know what I did, I will post tomorrow. I am working today and can't.
Click to expand...
Click to collapse
We shall see...