Related
Hello folks, this is my first ever post on XDA forums and I want to share how i bricked my Kenzo and the errors that i came across before unofficially unlocking my device. And also the solutions .
So firstly, some info
1. Kenzo doesnt have a recovery from the start.
2. As I read, Kenzo requires you to be on developer version of rom for unlocking bootloader the official way.
3. Xiaomi Servers are really bad, so say you want to unlock your device and you got your permission granted then its not clear when xiaomi will update that into their servers. I kept getting the 86012 error which as per forums is due to Xiaomi not updating the device info in their servers.
4. The unofficial way is much faster and imo better as it doesnt require you to wait like 10 days or so to get your permission granted with the only demerit that it would go away the moment you install a new MIUI rom. But you can reunlock it using the same method so no worries.
Oh and btw, do the disable driver signature enforcement for your windows before doing anything . https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also, make sure your battery is >80% . Ik its quite common to do this but in my case my battery was 50% and after flashing multiple times it was 0% and i got the red led so i thought i was booting into edl mode but after putting it to charge i realized that it was the low battery indication .
Now , guides and fixes.
1. So to unlock the device officially you need to headover to the site mentioned in your miui, and to get to that firstly enable developer options then go to developer options>mi unlock state and in the bottom is the link and follow the steps. I suggest waiting 24 hrs after getting the permission granted (which usually takes 5 mins) and then trying to add acc using the button in mi unlock state.
2. If you get the 86012 error, you are in the same boat as most of the people so the only way to officially unlock the device now is to wait 2-30 days.
3. If you get the couldnt connect to network error, download the developer version of your rom and follow instructions to install it. And then try.
4. Now, if you got your permission granted and the add acc thing worked then Congrats . Now if you download the Miunlock app and get the "Account doesnt exist" or "Network Error" error then switch the internet connection, in my case ,if i used vodafone mobile data hotspot then i got the error but with airtel no error. And after getting this Miunlock completed successfully your bootloader is unlocked.
5. Now the unofficial way, simple thing . Follow this https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172 .
6. There are 2 types of edl mode on kenzo, first is when you get 900E in device manager, second is when you get 9008 in device manager on your pc. For any flash to work, you need to get 9008 .
7. Now most likely you might run into "Object instance " error or something like that or even "max buffer size 250k" using Miflash app to install a fastboot rom on kenzo. The fix is to firstly install the 2014 version of miflash app and then after running it on your pc and finding your device using it install latest version and run that. The preferred location to install the app is in C:\ instead of C:\Program Files. Also I used the 2016 version downloaded from a website rather than the latest official one .
8. Your device may get bricked and might only boot to edl mode and the 900E mode at that. To get into 9008 mode, either use edl cable or do the test point method .
9. For custom roms you dont need a modified boot.img which I was unable to retrieve for myself anyway. You can create them too.
Thats all i can gather for now, I will add more issues if i discover more and I hope that I get help from the mods and admins on the forums regarding putting reserved messages and all so that everyone who has a fix and reports here can benefit everyone else
I didnt include much links cause there are quite a few of these guides and I only wanted this to be a support thread and not a full guide .
Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?
Hello,
Here is my problem.
2 days ago, I wanted to root my phone to get rid of any Google stuff (at this point I didn't know the existence of ADB commands :crying: ).
I followed a step by step youtube tutorial (youtube.com/watch?v=ZD-5twDm6XI), which works with TWRP, magisk and Odin (factory reset is needed).
Once everything is finished, my phone is finally rooted, and I grant superuser rights to Titanium app to uninstall google, and only SOME apps uninstalled totally (maps, chrome, facebook) BUT google play services won't uninstall. So, I try with System App Removal to uninstall google play stuff, and the same happens.
I reboot my phone, and it seems that everything disappeared... Not so sure... Indeed, the play store reinstall all applications as soon as I connect to the WiFi! and I have a persistent message "google play services stopped" that prevents me from browsing for example.
At this point, I use ADB commands, to remove anything which contains "com.blahblah.google.blahblah" and the play store (com.android.vending) with -k command. And it worked totally fine !!!!! I disconnect my phone, ready to backup my data. Idkw, i wanted to uninstall system app removal. IMPOSSIBLE from the phone, which says : "samsung One UI stopped" (I was in safe boot mode). My phone doesn't answer, so I reboot it.
Once it has booted, the TWRP menu screen appears. Ok, isn't that weird ? I swipe to allow changes, then I go to system to boot "normally" my phone.
A warning says : NO OS INSTALLED !!!! I don't understand, I panic, but finally boots my phone. Black charging screen. Forever.
I started first to flash an "official" Samsung ROM from Sammobile. TWRP indicates it is an invalid .zip, adb too. Odin doesn't manage to boot from the ROM too. I take a deep breathe and cry. Then I download the /e/ ROM which works fine !! but it has become impossible to backup my data from my samsung account....
So, I came to ask you a few things. WHY did it happen ? How can I be sure that there is no trace of TWRP anymore ? However, my phone storage is 64 GB and there is only 53,5 Gb free of internal storage !? Do you think the original firmware could be "hidden" in my files (e ROM is about 800Mos compressed) ?
It is stupid, but after my mistakes, I miss google...
I will do my best to reply asap.
Thank you for your help !
PS: -I'm a newbie in informatic, don't make things too complicated
-sorry for bad English, not my mother language
Google writes and distributes android.
There are many things in android that you cannot remove and still have a viable system.
imho you will have to flash a rom but we need your phones information (found in settings/system/about phone) model, version baseband, etc. etc
Others more knowledgeable can step in and help.
also read:
https://www.androidcentral.com/factory-reset-protection-what-you-need-know
KrisM22 said:
Google writes and distributes android.
There are many things in android that you cannot remove and still have a viable system.
imho you will have to flash a rom but we need your phones information (found in settings/system/about phone) model, version baseband, etc. etc
Others more knowledgeable can step in and help.
also read:
Click to expand...
Click to collapse
Thank you for your reply ! I've read your article about FRP but I'm afraid it's not my problem...
Here are some of my phone specifications :
model : SM-G950F
version baseband : G950FXXS8DTC1
OS : /e/ version 0.9-p-dev-dreamlte (LineageOS API : Ilama 9)
Android 9
I've been digging the web for ROMs but each time I feel unsecure about it (virus, etc...) so I hope maybe you have something trustworthy
[UPDATE]
S8recovery said:
Hello,
Here is my problem.
2 days ago, I wanted to root my phone to get rid of any Google stuff (at this point I didn't know the existence of ADB commands :crying: ).
I followed a step by step youtube tutorial (youtube.com/watch?v=ZD-5twDm6XI), which works with TWRP, magisk and Odin (factory reset is needed).
Once everything is finished, my phone is finally rooted, and I grant superuser rights to Titanium app to uninstall google, and only SOME apps uninstalled totally (maps, chrome, facebook) BUT google play services won't uninstall. So, I try with System App Removal to uninstall google play stuff, and the same happens.
I reboot my phone, and it seems that everything disappeared... Not so sure... Indeed, the play store reinstall all applications as soon as I connect to the WiFi! and I have a persistent message "google play services stopped" that prevents me from browsing for example.
At this point, I use ADB commands, to remove anything which contains "com.blahblah.google.blahblah" and the play store (com.android.vending) with -k command. And it worked totally fine !!!!! I disconnect my phone, ready to backup my data. Idkw, i wanted to uninstall system app removal. IMPOSSIBLE from the phone, which says : "samsung One UI stopped" (I was in safe boot mode). My phone doesn't answer, so I reboot it.
Once it has booted, the TWRP menu screen appears. Ok, isn't that weird ? I swipe to allow changes, then I go to system to boot "normally" my phone.
A warning says : NO OS INSTALLED !!!! I don't understand, I panic, but finally boots my phone. Black charging screen. Forever.
I started first to flash an "official" Samsung ROM from Sammobile. TWRP indicates it is an invalid .zip, adb too. Odin doesn't manage to boot from the ROM too. I take a deep breathe and cry. Then I download the /e/ ROM which works fine !! but it has become impossible to backup my data from my samsung account....
So, I came to ask you a few things. WHY did it happen ? How can I be sure that there is no trace of TWRP anymore ? However, my phone storage is 64 GB and there is only 53,5 Gb free of internal storage !? Do you think the original firmware could be "hidden" in my files (e ROM is about 800Mos compressed) ?
It is stupid, but after my mistakes, I miss google...
I will do my best to reply asap.
Thank you for your help !
PS: -I'm a newbie in informatic, don't make things too complicated
-sorry for bad English, not my mother language
Click to expand...
Click to collapse
I've been browsing through my root files and folders ( / ) ...
So :
/system is occupied with 2.33 GB
/vendor with 577 MB
/mnt with 9.01 GB
/proc with ... 236.9GB but every under-folder is empty... (explanations welcome !)
/storage is empty
If anyone could check on his device (S8 Exynos with android 9.0 Pie and One UI) if the files' sizes approximately matched, it would be great !
The one I just received is G950FXXS8DTC6 / G950FOXM8DTC1 / G950FXXS8DTC1 (after it took the Apr 1 update) so probably identical - a Yateley GU46 6GG UK phone. I am running it on ATT Prepaid(US) , which gave me the Apr 1 update. I don't know its history but it hasn't been modified - knox=0.
What you would need to do is get that zip and flash it with odin, but having no experience flashing the S8 myself, or any idea where to get that zip, I can be of no help to you. (I just came off a moto x4 which I ruined by flashing a couple custom rom's to try to help others on that forum - the blessings of Pie on that device!)(plus, taking the Apr 1 update on that phone requires a factory reset/wipe.) I needed a dependable phone here and in Europe on vacation.
Keep posting and ask someone to help you re-flash it.
EDIT: I wonder what a settings/general management/factory reset would do. But don't do one until someone here much more experienced with the S8 suggests it.
EDIT: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
lockscreen and security / secure startup / require pin
I also see a note to delete your google account before doing this. Don't know if necessary.
EDIT: I believe I have found the rom - see pic This is from the SamFirm exe. 0.3.7 I put VOD for the region.
Remember: don't do anything with this until someone experienced in S8 tells you to!
Hi KrisM22,
I've already flashed with Odin, and I have talked about this on different forums, seen tutos on websites,... I hope this time it will work
I have the ROM required, selected activate pin, followed step by step the recommendations, and if I figured it out I will keep you up to date !
KrisM22 said:
The one I just received is G950FXXS8DTC6 / G950FOXM8DTC1 / G950FXXS8DTC1 (after it took the Apr 1 update) so probably identical - a Yateley GU46 6GG UK phone. I am running it on ATT Prepaid(US) , which gave me the Apr 1 update. I don't know its history but it hasn't been modified - knox=0.
What you would need to do is get that zip and flash it with odin, but having no experience flashing the S8 myself, or any idea where to get that zip, I can be of no help to you. (I just came off a moto x4 which I ruined by flashing a couple custom rom's to try to help others on that forum - the blessings of Pie on that device!)(plus, taking the Apr 1 update on that phone requires a factory reset/wipe.) I needed a dependable phone here and in Europe on vacation.
Keep posting and ask someone to help you re-flash it.
EDIT: I wonder what a settings/general management/factory reset would do. But don't do one until someone here much more experienced with the S8 suggests it.
EDIT: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
lockscreen and security / secure startup / require pin
I also see a note to delete your google account before doing this. Don't know if necessary.
EDIT: I believe I have found the rom - see pic This is from the SamFirm exe. 0.3.7 I put VOD for the region.
Remember: don't do anything with this until someone experienced in S8 tells you to!
Click to expand...
Click to collapse
The flashing WORKED :victory: !!! It frightens me right now to check if TWRP has disappeared... But thank you anyway !z
S8recovery said:
The flashing WORKED :victory: !!! It frightens me right now to check if TWRP has disappeared... But thank you anyway !z
Click to expand...
Click to collapse
Excellent! What ROM did you flash it with?
KrisM22 said:
Excellent! What ROM did you flash it with?
Click to expand...
Click to collapse
I flashed a ROM from https://www.imei.info/download-firmware/samsung/samsung-g950f-galaxy-s8/SM-G950F/ , then I just followed the steps and flashed with Odin. TWRP has disappeared (the classic recovery menu came back). I think I have found my issue with the "no OS installed" bug : it could be because I deleted the essential API com.google.android.packageinstaller, what may have prevented the phone from booting and launching the OS and its apps .
I should have read this excellent post before...
*I ran antivirus analysis with virustotal and Bitdefender, which both declared the extracted files were safe : I didn't notice anything different by my phone compared to the original OS too, so...
Hello everyone. it's been a week that I work on this problem but I can't solve it myself despite having made numerous attempts. the situation is this: installing lineage os when the system restarted the 6t got stuck in the bootlader. I installed qualcom drivers from here
https://androidfilehost.com/?fid=11410963190603879743
and downloaded msm https://androidfilehost.com/?fid=17248734326145733776
I disabled windows secure boot and installed optional qualcomm drivers on windows... the 6t is correctly recognized as Qualcomm 9008 in the device manager in port 9 but I also tried in the 7 and it is always correct.
I tried other divers (after removing the previous ones) and other versions of msm but I always give the same error : param preload... device not match images.
I have read many discussions and tried many things but I can not solve. someone is willing to help me. Thanks guys.
I also tried uninstalling the drivers and reinstalling these:
QUD.WIN.1.1 Installer-10037.3 Setup.zip | by Dark Nightmare for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
using this version of msm:
6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12.rar | Tool by iaTa for OnePlus 6T
[TOOL] 6T MsmDownloadTool v4.0.58 (OOS v9.0.12) https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
androidfilehost.com
the problem is not solved but changed to: (recording dawnload time in red) images do no match with teh phone!
i can't figure out if it's a msm or driver version problem or maybe something else ...
I don't know what the exact problem. If you have installed magisk or modify something to your phone, sometime msm will fail to recognized or flash..
rom
But if your phone can boot into fastboot mode, try to flash fastboot ROM it might help
Fastboot rom.
[ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if...
forum.xda-developers.com
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
sun-k said:
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
Click to expand...
Click to collapse
if you get a warning in MSM tool: 'images do not match the phone', you are flashing the wrong image. That could happen to a branded phone. So, if you have a T-Mobile branded phone, either convert it to Global first (that tool has 'device check' disabled), or use T-Mobile MSM tool.
Your other option is to contact OnePlus support and they can help you remotely. I got into a similar bind with my 6t a year and ½ ago and nothing I was attempting worked. It was very frustrating. Ultimately I contacted OnePlus and they got me back up and running in no time. I was a little upset that I had to resort to relying on the manufacturer but also relieved to have a working device again and also thankful that it was an option, even if I would've preferred to have fixed it myself. Good luck.
PS - something to be aware of, I'm not 100% sure that it was a result of OnePlus' involvement/remotely flashing the device but somehow I ended up with a new/different IMEI. This created a world of difficulty with my cellular carrier (VZW) - I had finagled a OnePlus 8 out of them by citing manufacturers defect (I had coverage through VZW despite purchasing the phone directly from OnePlus) but they said the OnePlus 6t they received had a different IMEI than what they expected to receive, which makes absolutely no sense and this is the only possible explanation I could come up with. It ultimately saved me from having to pay for retail for the OnePlus 8 but not without a lot of headaches in between. Oh and lemme just say that having a VZW OnePlus with a locker bootloader sucks, I can't wait to get away from this thing and back to something I can root (I only pulled this maneuver in order to buy myself some time as I wasn't thrilled with the 1+9)
Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?
Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!