Related
ONLY FOR SGH-T999V VERSION OF GALAXY S3
UPDATED 2012-12-29: Resources at the bottom
JELLY BEAN UPDATE FROM VIDEOTRON DECEMBER
If you have made the Jelly bean update from Videotron in december 2012, you can't go trough these step. You need to first restore the stock
firmware. (2012-05-28 12:10:55 - download from my resource folder) and after go with the normal step from the Android ICS 4.0 not from JB. That's what I had to do to return to CM10.
Install ClockworkMod and Root
Requirements:
• Start from ICS not from Jelly Bean (update from Videotron in december 2012), if you have Jelly Bean restore to ICS with the method bellow.
• Handset USB drivers (T-Mobile_T999_GSIII_Samsung_USB_Driver_v1_4_6_0.exe, 23.2 MB) installed on the PC
• Enable USB debugging on your handset. Go to Settings > Developer options > USB Debugging.
• Maintain a phone battery charge of at least 75%
• Download the following to your PC:
o Odin3 v3.04 (Odin3-v3.04.zip, 457 kB) https://www.dropbox.com/s/t7mhx4huexiqu1b/Odin3-v3.04.rar
o ClockworkMod Recovery (clockworkmod.TAR, 6.8 MB) https://www.dropbox.com/s/1iplxgsticl1d4q/clockworkmod.TAR
o CWM-SuperSU-v0.87 https://www.dropbox.com/s/xbe27r6khd54ypd/CWM-SuperSU-v0.87.zip
Instructions:
a. Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard.
1. Extract the Odin ZIP file to a folder on your computer, preferably on your Desktop where you can easily find it.
2. Turn off your phone.
3. Reboot it into Download Mode by holding down the Volume Down, Home, and the Power buttons until you see “Warning!!” displayed on the screen. Press the Volume Up key again to continue to Download Mode. You will know when you are in Download Mode when you see a green Android with “Downloading” text displayed. If you don’t see it, try again.
4. Go to the folder where you extracted Odin and double-click on Odin3 v3.04.exe to run it.
5. Connect your phone to your PC and if drivers will install again, allow installation to finish first.
6. Odin should recognize your phone. You will know if it did when the COM box in the leftmost part of the window turns blue. An “Added!!” message will also be displayed in the message box.
7. In Odin, click the PDA tab and select the clockworkmod.TAR file.
8. Double check that the “Auto Reboot” and “F. Reset Time” options are ticked.
9. Click Start in Odin to flash ClockworkMod Recovery on your phone and wait for the flashing to finish.
10. Once done, your phone will automatically reboot and you will see a message in Odin saying “Pass!”. This indicates that you can now unplug your phone and close Odin.
11. Boot into ClockworkMod Recovery. Turn off your phone and hold down the Volume Up, Home, and the Power buttons together until the screen turns on. Let go of the buttons and your phone should now boot into ClockworkMod Recovery.
12. Click on install zip, zip from sdcard and select your CWM-SuperSu zip file and flash it.
13. You can press Reboot now.
Great! You now have ClockworkMod Recovery installed
Install ClockworkMod Touch
Requirements:
- done the previous step (Install ClockworkMod and Root)
- Download the following to your PC:
o ClockworkMod Touch https://www.dropbox.com/s/1ydtp2jyo5br9ww/recovery-clockwork-touch-5.8.4.7-d2tmo.img
Instructions:
1. Download ClockworkMod Touch from http://www.clockworkmod.com/rommanager for your device (for this tutorial i use the one in download list)
2. Rename the file cwmtr.img to make the task easier
3. Place the file in your root sdcard
4. install an terminal emulator like this one: https://play.google.com/store/apps/...idterm&feature=nav_result#?t=W251bGwsMSwyLDNd
5. Run this commands:
su
dd if=/sdcard/cwmtr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
6. reboot in recovery mod,
Good ! you have the touch clockworkmod !
Install CyanogenMod 9 on T999V
Requirements:
- Done the two previous step (1. Install ClockworkMod and Root and 2. Install ClockworkMod Touch)
- Download the following to your PC:
o CyanogenMod 9 http://www.clockworkmod.com/rommana...tlies&deviceName=Samsung Galaxy S3 (T-Mobile)
o Google Apps http://www.clockworkmod.com/rommana... Apps&deviceName=Samsung Galaxy S3 (T-Mobile)
Instructions:
1. Place the Cyanomodgen 9 zip and google apps zip on your phone on root sdcard.
2. Reboot in recovery mode
3. Once the device boots into the ClockworkMod Recovery, Select backup and restore to create a backup of current installation on the Samsung Galaxy S III.
4. Select the option to Wipe data/factory reset.
5. Then select the option to Wipe cache partition.
6. Select Install zip from sdcard.
7. Select Choose zip from sdcard.
8. Select the CyanogenMod zip and flash it
9. Install the Google Apps by performing steps 6 - 7 again and choosing the Google Apps zip
10. Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option.
It's done ! you boot in CyanogenMod 9 !!!
Install CyanogenMod 10 on T999V
Requirements:
*- Done the two previous step (1. Install ClockworkMod and Root *and 2. Install ClockworkMod Touch)
- Download the following to your PC:
* * * * *o CyanogenMod 10 http://get.cm/?device=d2tmo
* * * * * o * *Google Apps http://goo.im/gapps/gapps-jb-20120726-signed.zip
Instructions:
1. Place the Cyanomodgen 10 zip and google apps zip on your phone on root sdcard.
2. Reboot in recovery mode
3. Once the device boots into the ClockworkMod Recovery, *Select backup and restore to create a backup of current installation on the Samsung Galaxy S III.
4. Select the option to Wipe data/factory reset.
5. Then select the option to Wipe cache partition.
6. Select Install zip from sdcard.
7. Select Choose zip from sdcard.
8. Select the CyanogenMod *zip and flash it
9. Install the Google Apps by performing steps 6 - 7 again and choosing the Google Apps zip
10. Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option.
It's done ! you boot in CyanogenMod 10 !!!
Update between CyanogenMod builds
- Make a full backup of your phone with Titanium backup
- Download the new build from here: http://www.clockworkmod.com/rommana...htlies&deviceName=Samsung Galaxy S3 (T-Mobile)
- Place it on the root of sdcard
- Reboot in recovery mode
- Make a backup of your phone (restore if the new builg is wrong)
- Wipe Cache
- Optionnal: wipe dalvik (by default flashing new rom clear dalvik anyway)
- Install your new build from zip
- Reboot
- If you loose some data or app restore from titanium backup.
Done! you have new your new build!
Download your Stock firmware
- Download http://fus.nanzen.se/download.php?id=12
- In the droplist (choose a firmware) select Android
- In the next droplist select the SGH-T999V
- Select your region, for me it's VTR for Videotron in canada
- Click on "Check firmware" and wait
- After under the result section click on Download.
Done! you have your stock firmware.
Reset Binary counter
- Go to the Play Store and get Triangle Away (https://play.google.com/store/apps/...leaway&feature=nav_result#?t=W251bGwsMSwyLDNd)
- Give the root user rights
- Open triangle away and click on Reset Flash counter
- wait and reopen triangle away and check the status.
Now! you have your binary counter to 0.
Restore the stock firmware in Galaxy S3
- Download Odin (https://www.dropbox.com/s/t7mhx4huexiqu1b/Odin3-v3.04.rar)
- Download your Stock Firmware (see previous step)
- Put your device in restore mode (press and hold home + volume up + power when device shutdown keep pressing only home and volume up until you see samsung logo)
- now wipe cache and wipe data
- Put your device in Download mode (press and hold home + volume down + power when device shutdown keep pressing only home and volume down until you see samsung logo)
- press volume up to go in download mode
- open Odin, now ou see a com port added to odin (it's your phone)
- check if checkbox Auto Reboot and F. reset Time are checked.
- Click on PDA and select your firmware md5 file
- when you are ready, click on start and wait
When your device is restarting you will see your stock firmware running !
RESOURCES ARE HERE NOW:
https://www.dropbox.com/sh/1f8zmsfzgeiuxku/XZ6_NvbcdW
(I'm not sure if I made the shared folder the good way, so don't be shy to inform me if there is a trouble.)
it contains:
-files
-url shortcut for download updated ressources (shortcut from chrome)
Has anybody else tried this yet on their Canadian gs3...???
Rickkins said:
Has anybody else tried this yet on their Canadian gs3...???
Click to expand...
Click to collapse
i don't know but i'm customer of Videotron and i make 1 week research before apply this recipe to flash my phone, and my phone work perfect!
Try it !
fox4305 said:
i don't know but i'm customer of Videotron and i make 1 week research before apply this recipe to flash my phone, and my phone work perfect!
Try it !
Click to expand...
Click to collapse
Thanks, I may just do that.
What part of this procedure actually "roots" the phone...???
Yes, I am indeed that noobular...
Rickkins said:
Thanks, I may just do that.
What part of this procedure actually "roots" the phone...???
Yes, I am indeed that noobular...
Click to expand...
Click to collapse
The first one root the phone.
Sent from my SGH-T999 using xda premium
Rickkins said:
Has anybody else tried this yet on their Canadian gs3...???
Click to expand...
Click to collapse
I just did this on my Videotron (Canadian) GS3 T999V and it works great
simondadiamond said:
I just did this on my Videotron (Canadian) GS3 T999V and it works great
Click to expand...
Click to collapse
cool !
Can someone with a Wind Mobile SGH-T999V comment on their experience with this?
I'm using a wind GS3. It's really a great rom. I've tried the redrum r4, but HSPA+ doesn't work, and a lot of t-mobile apps. Then I tried this rom, found out that every thing works. It won't overwrite the baseband. Mine is still T999VVLLE6. This is a rom that you really need to try.
Sent from my SGH-T999V using xda app-developers app
grey43 said:
I'm using a wind GS3. It's really a great rom. I've tried the redrum r4, but HSPA+ doesn't work, and a lot of t-mobile apps. Then I tried this rom, found out that every thing works. It won't overwrite the baseband. Mine is still T999VVLLE6. This is a rom that you really need to try.
Sent from my SGH-T999V using xda app-developers app
Click to expand...
Click to collapse
Do you know why the HSPA+ doesn't work? I've had phones flashing new ROMs and the data wasn't working because I forgot to add WIND's APN in the mobile network settings
adslee said:
Do you know why the HSPA+ doesn't work? I've had phones flashing new ROMs and the data wasn't working because I forgot to add WIND's APN in the mobile network settings
Click to expand...
Click to collapse
The WIND APN was there by default. 3G does work but HSPA+ not. I have no idea why this happens. Maybe it's just simply Redrum is made from T-mobile stock ROM. Did anybody else try this great ROM?
hi, many thanks for this post.
quick question? I downloaded my stock firmware, do I just throw it in my SDcard's ROOT and flash using Clockwork ?
im awfully new to this sorry
GearshiftJB said:
hi, many thanks for this post.
quick question? I downloaded my stock firmware, do I just throw it in my SDcard's ROOT and flash using Clockwork ?
im awfully new to this sorry
Click to expand...
Click to collapse
check this tutorial and follow this one but with your stock firmware
http://www.androidauthority.com/galaxy-s3-gt-i9300-android-4-0-4-ics-xxalf2-stock-firmware-100309/
that sound great for you ?
Many thanks to the OP!!
I would like to start with saying many thanks to the OP!! Merci mon ami!!
I also have a Videotron phone that is now rooted and flashed thanks to the OP.
I have been messing around quite a bite lately with different roms on this Phone.
So far I have found that CM10 seems to work best for my phone and has the less amount of bugs.
To the new guys finding this thread and wanting to root/flash your phone. I stress the need for a full backup before applying a new rom.
After installing Clockworkmod - follow the OP's instruction to make a full backup of your phone.
And until you are very familiar with the process. Keep a copy on your internal SD for easy flash back to the stock rom.
Lets get a lot of people involved in this thread so we can gain the most knowledge about these phones/mods.
If you guys have any questions please ask away.
Thanks all.
peleberchot said:
I would like to start with saying many thanks to the OP!! Merci mon ami!!
I also have a Videotron phone that is now rooted and flashed thanks to the OP.
I have been messing around quite a bite lately with different roms on this Phone.
So far I have found that CM10 seems to work best for my phone and has the less amount of bugs.
To the new guys finding this thread and wanting to root/flash your phone. I stress the need for a full backup before applying a new rom.
After installing Clockworkmod - follow the OP's instruction to make a full backup of your phone.
And until you are very familiar with the process. Keep a copy on your internal SD for easy flash back to the stock rom.
Lets get a lot of people involved in this thread so we can gain the most knowledge about these phones/mods.
If you guys have any questions please ask away.
Thanks all.
Click to expand...
Click to collapse
How's CM10? Any huge bugs on the ROM or flaws so far?
CM10
adslee said:
How's CM10? Any huge bugs on the ROM or flaws so far?
Click to expand...
Click to collapse
Hi There.
I have been using CM10 for a daily driver for about 1 week now. My current build dates from the 14th.
It is very stable on my phone and have not experienced a crash.
I did wipe clean before installing the rom. Make sure you have backups before doing anything.
You should always have a full backup made with Clockworkmod and easily accessible on your main SD card in case something goes wrong.
But dont be shy to use the latest CyanogenMod 10. You can always revert back if you don't like it.
peleberchot said:
Hi There.
I have been using CM10 for a daily driver for about 1 week now. My current build dates from the 14th.
It is very stable on my phone and have not experienced a crash.
I did wipe clean before installing the rom. Make sure you have backups before doing anything.
You should always have a full backup made with Clockworkmod and easily accessible on your main SD card in case something goes wrong.
But dont be shy to use the latest CyanogenMod 10. You can always revert back if you don't like it.
Click to expand...
Click to collapse
I assume you are using the T-mobile nightly build of CM10 correct?
galaxy s3
Bonjour ,je suis nouveau ici et besoin d'aide merci ,j'ai le galaxy s3 sgh-t999 cloclworkmod recovery v5.8.4.7 je me demande si je peux siuvre la meme instruction en haute
autre question pour quoi je vois pas mon carte ext sdcard dans le mode recovery v5.8.4.7
cette etape: Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard
est-ce que je dois copier dans mon sdcard ou ext sdcard
car quand je reboote mon covery cloclworkmod recovery v5.8.4.7 je vois pas mon ext sdcard
merci j'attend votre repondre
Hello, I am new here and need of help(assistant) thank you, I have the galaxy s3 Sgh-t999 cloclworkmod recovery v5.8.4.7 I wonder if I can follow the same instruction in the other high question for which I see not my card(map) is sdcard in the recovery mode v5.8.4.7 this stage: Copy the CWM-SuperSu-V0.87 zip takes off has to your phone at the root of sdcard I have to copy in my sdcard or ext-sdcard because when I reboote my covery cloclworkmod recovery v5.8.4.7 I see not my and ext-sdcard thank you I wait your to answer
Videotron Galaxy S3
samsung glx3 said:
Bonjour ,je suis nouveau ici et besoin d'aide merci ,j'ai le galaxy s3 sgh-t999 cloclworkmod recovery v5.8.4.7 je me demande si je peux siuvre la meme instruction en haute
autre question pour quoi je vois pas mon carte ext sdcard dans le mode recovery v5.8.4.7
cette etape: Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard
est-ce que je dois copier dans mon sdcard ou ext sdcard
car quand je reboote mon covery cloclworkmod recovery v5.8.4.7 je vois pas mon ext sdcard
merci j'attend votre repondre
Hello, I am new here and need of help(assistant) thank you, I have the galaxy s3 Sgh-t999 cloclworkmod recovery v5.8.4.7 I wonder if I can follow the same instruction in the other high question for which I see not my card(map) is sdcard in the recovery mode v5.8.4.7 this stage: Copy the CWM-SuperSu-V0.87 zip takes off has to your phone at the root of sdcard I have to copy in my sdcard or ext-sdcard because when I reboote my covery cloclworkmod recovery v5.8.4.7 I see not my and ext-sdcard thank you I wait your to answer
Click to expand...
Click to collapse
Hi,
From my experience with the phone. Yes you have to copy all the files to the internal SD and not your external SD card. There must be a setting but I can't find it.
So to keep everything safe just copy all the needed files to the root of your internal SD card.
Cheers!
Marc
---------- Post added at 09:19 PM ---------- Previous post was at 08:53 PM ----------
sluma said:
I assume you are using the T-mobile nightly build of CM10 correct?
Click to expand...
Click to collapse
Yes I am using the CM10 d2tmo releases. Which are for the T-Mobile version of the S3.
I tried to post a link but I guess I cant... look for something called BBQLog and you will find the change logs and the releases.
And here is the thread about it on the main forums. You will find a lot of info from other users and say what kind of issues they are having with the latest builds. So you can decide to flash or not to flash
http://forum.xda-developers.com/showthread.php?t=1778217
You will also find a link in that thread to the BBQLog website.
Cheers!
Marc
---------- Post added at 09:25 PM ---------- Previous post was at 09:19 PM ----------
ok.
Sorry I tried to break up those post into two instead of one post but it did not work. Obviously I have no idea what I am doing on here yet... lol.
And yes just trying to pad a bit my post count. It's a bit silly that you have to have 10 post counts before you can post links or even have a signature!!
But I will survive and be here .. hehe.
It seems like a great community.
Have a great evening all.
Cheers!!
Marc
samsung glx3 said:
Bonjour ,je suis nouveau ici et besoin d'aide merci ,j'ai le galaxy s3 sgh-t999 cloclworkmod recovery v5.8.4.7 je me demande si je peux siuvre la meme instruction en haute
autre question pour quoi je vois pas mon carte ext sdcard dans le mode recovery v5.8.4.7
cette etape: Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard
est-ce que je dois copier dans mon sdcard ou ext sdcard
car quand je reboote mon covery cloclworkmod recovery v5.8.4.7 je vois pas mon ext sdcard
merci j'attend votre repondre
Hello, I am new here and need of help(assistant) thank you, I have the galaxy s3 Sgh-t999 cloclworkmod recovery v5.8.4.7 I wonder if I can follow the same instruction in the other high question for which I see not my card(map) is sdcard in the recovery mode v5.8.4.7 this stage: Copy the CWM-SuperSu-V0.87 zip takes off has to your phone at the root of sdcard I have to copy in my sdcard or ext-sdcard because when I reboote my covery cloclworkmod recovery v5.8.4.7 I see not my and ext-sdcard thank you I wait your to answer
Click to expand...
Click to collapse
oui je confirme car sd interne de votre cellulaire et oui vous pouvez effectué la même manipulation.
Can someone tell me the simplest way to root SM-J737T? I say simple because I just have a phone and no computer to use Odin with.
I not tested
1. Install twrp without PC
2. Reboot tô twrp 3.4.0
3. Flash magisk
4. Wipe sustém data cache
5. Install H vendor
6. Install any ROM
7. Enjoy
Twrp 3.4.0 j730g
OneDrive
onedrive.live.com
ببین عزیز دلم twrp فقط با اودین رایت میشه
twrp only odinfrom computer
have a root,in magisk boot
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
draymond1987 said:
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
Click to expand...
Click to collapse
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
dimelus said:
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
Click to expand...
Click to collapse
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
draymond1987 said:
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
Click to expand...
Click to collapse
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
What I would do, and it's silly but could work. Go back into fastboot and issue the "
fastboot flashing unlock_critical" command, again. I know this happened to me too because I had these errors and I just tried, out of desperation. I dunno if it's because the phone is on the T-mobile software, that it freaks out like that, question mark?
dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Did you not flash 10.0.3HD65AA rom image which is step "I."? If you go out of step and not follow the instructions as they're laid out then of course you're going to have problems.
urbanman2004 said:
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
Click to expand...
Click to collapse
Thanks for your guide lines.. I am a very newby yet 71 years old.. been messing with hardware and software since 1984, always learning. new to Flashing Rom's , I converted two 6T's and 3 7T from TMO to 1+, the third 7T gave me a fit, because I purchased from someone who didn't tell me that someone had tried to convert to dual sim and I had a hard time to solve the issue.. Two things,, for everyone trying to do this.. Branded to Global or Dual Sim, One You have to have the Correct Drivers for Windows for the ADB and Fastboot.. and it has to be setup correctly.. as for some drivers that are signature issue for windows, and you have exclamation mark because of signatures, as for Win10,
restart your windows with Shift key held down and select restart, when it boots into blue screen select "troubleshoot"
from that select " Startup blue secreen. " after that Select Item #7 which is to forces Windows to ignore Signature error reporting. select Start , then go on with your process for Brand to dual sim or Global, etc..
THANK YOU for Your Information and Procedure Steps to Convert from Branded to Dual / Global, etc.. made it very less time consuming...Appreciate You and All those who have given Good Guidance - Thank You
does this method unlock the sim card?
goggolar said:
does this method unlock the sim card?
Click to expand...
Click to collapse
No, you have a completely separate issue. The OnePlus 7T device I purchased already had an unlocked sim card. You need to refer to your phone carrier who provides you service.
It needs the bootloader unlocked?
SBruno said:
It needs the bootloader unlocked?
Click to expand...
Click to collapse
Yep
CaptRicXT912 said:
Gracias por sus lineamientos .. Soy muy nuevo por 71 años .. he estado jugando con hardware y software desde 1984, siempre aprendiendo. nuevo en Flashing Rom's, convertí dos 6T y 3 7T de TMO a 1+, el tercer 7T me encajó, porque le compré a alguien que no me dijo que alguien había intentado convertir a dual sim y tenía un Es difícil resolver el problema. Dos cosas, para todos los que intentan hacer esto. Con la marca Global o Dual Sim, una Debe tener los controladores correctos para Windows para ADB y Fastboot ... y debe estar configurado correctamente ... como para algunos controladores que son un problema de firma para Windows, y tiene un signo de exclamación debido a las firmas, como para Win10,
reinicie sus ventanas con la tecla Shift presionada y seleccione reiniciar, cuando se inicie en la pantalla azul, seleccione "solucionar problemas"
a partir de ahí, seleccione "Pantalla azul de inicio". Después, seleccione el elemento n. ° 7, que obligará a Windows a ignorar el informe de errores de firma. seleccione Inicio, luego continúe con su proceso de Marca a SIM dual o Global, etc.
GRACIAS por su información y procedimiento Los pasos para convertir de marca a dual / global, etc. hicieron que consumiera mucho menos tiempo ... Le agradezco a usted y a todos los que han dado una buena orientación - Gracias
Click to expand...
Click to collapse
seria de mucha ayuda si usted o alguien me ayudara en este problema estoy atascado en la version de android 10 de t-mobile la computadora no reconoce el dispositivo almenos que lo reinicie de fabrica, en modo fastboot no lo reconoce y estoy desesperado soy nuevo en esto
Excellent work, it did the job for mine. Followed your procedure and a couple of interpretations to get through it to the end.
Thank You for the help!
This worked for me, I wasn't even trying to convert my phone.. just restore a soft brick turned semi-hardbrick.
I haven't done android modding since my Zuk Z1! Previously I had modded my Galaxy s3, some LG [it was the one with RGB home button, man I miss that], and Z1. Yesterday I decided I was finally ready to mod my oneplus 7t [hd1907] after 2 years of ownership. Bootloader unlock, Rooted, modded some things, and then Sound wouldn't play in the speakers, wifi dead, hotspot dead, amongst other broken features. Trouble is, I wasn't thinking like I used to and didn't have my img files backed up. All I wanted to do was revert back to the stock firmware.. but I ended up in a softbrick somehow. I can't find tmo op7t firmware anywhere online.. I was going to try flashing it with adb.Well I came across your guide here, and when all hope was lost I thought I might as well give it a try.. and it worked! Now instead I'm on international software! Even better than just recovering stock! Well youtube is throwing a connection error but I am hoping it just means I need to update my gapps.. Thank you very much this helped me recover my phone..
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
I actually had "FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS" on the first flash as well, and it never booted properly either. On the second flash I was getting "Invalid sparse file format at header magic".. However in the end of the process my phone was working.
I'm going to update gapps and update firmware to the latest OTA now, which popped up in the notifications already! Thanks again Urbanman.
Edit: "some LG [it was the one with RGB home button, man I miss that]" I checked my post history it was LG optimus G pro.
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
k.stahanov73 said:
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
Click to expand...
Click to collapse
Superboy58 msmtool will get u global oos10, then ota to 11.0.9.1 or oos12 global
HueyT said:
Superboy58 msmtool получит u global oos10, затем ota на 11.0.9.1 или oos12 global
Click to expand...
Click to collapse
I can not flash through msm .. at the fastboot stage after a reboot I ALWAYS boot into the old system !! always! already made 50 attempts and changed the cords and ports and no use!
Maybe it's because I have Windows 7?
Hello guys,
This is the first method how to work with both sim 1 and sim 2 Imei's if you mistakly made by 'format all' option in sp flash tool.
WARNINGS:
- Possible risk of data loss ! Backup your files and contents !
- NO dongle and NO box is required.
- NEVER try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI.
- Keep your backup files safe and secure ! If you can, encrypt them.
- Never try to share your backups or your security and privacy will be compromised.
- USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
This method was released by HALABTECH and it's working ONLY with custom rom.
Big thanks to VD171 who shared the patched file.
If somebody has an idea how to implement this patch in stock rom it would be great too..
We need Engineering Rom to be installed first to be able to access meta mode.
Download Maui Meta or Modem Meta to write both original Imei's.
Next,flash the latest Miui rom 12.0.7 global and after it is finished with flashing before it goes to reboot press vol- to enter fastboot mode.
In Fastboot mode flash vbmeta and twrp.
In TWRP at first make format data,then reboot to twrp again,then wipe dalvik,data,cache and flash Pixel Experience custom rom and magisk 22,then make format data again,then restart the phone in fastboot again.
After put your phone in Fastboot Mode extract the patched file,(IMPORTANT) rename it to 'md1img' and flash it exactly like this: fastboot flash md1img md1img.img
Next and last step just reboot it by 'fastboot reboot' and very important thing, at first boot when you see the google logo immediately press the power button to restart the phone to be able to work normally.
Check if you have in both sim slots imeis and signals.
ENG ROM: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/
Latest stock rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.7.0.QJOMIXM/
Patched file is in attachment below.
Hi. I've lost ma IMEIs. Hopefully read this guide, but when I've done this steps, the phone goes tho fatboot after restart :/ Please help...
in twrp you must format data,wipe cache,dalvik and data,then close avb2 and disable twrp check in advanced mode.
The patch file is the MD1IMG.img of the ENGINEERING ROM AL2522-Merlin-V039-Q-0513.
Here, you can find this file and other MD1IMG versions for MERLIN:
[BASEBAND][IMG][STOCK][MD1IMG] MODEM Image Partition for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Original Stock MD1IMG.IMG for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G What is it? This image partition contains the MODEM/BASEBAND/RADIO. How to flash it? fastboot flash md1img md1img.img (Engineering)...
forum.xda-developers.com
Please share the custom rom, or do I just have to flash this patch.zip
i just flashed pixel experience cleared cache and data after that wrote imei with maui meta latest version by selecting load db from target and it worked for me. though wifi is still showing nvram error but it can still connect to wifi.
UnexpectedUser said:
i just flashed pixel experience cleared cache and data after that wrote imei with maui meta latest version by selecting load db from target and it worked for me. though wifi is still showing nvram error but it can still connect to wifi.
Click to expand...
Click to collapse
You can write MAC too.
sir you said "In Fastboot mode flash vbmeta and twrp." but i cant find vbmeta file.
Moss je vb said:
sir you said "In Fastboot mode flash vbmeta and twrp." but i cant find vbmeta file.
Click to expand...
Click to collapse
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
after flashing vbmeta and twrp the phone says system has been distroyed. it some how knows i put custom recovery in it. and my boot loader is locked. what can i do ?
Moss je vb said:
after flashing vbmeta and twrp the phone says system has been distroyed. it some how knows i put custom recovery in it. and my boot loader is locked. what can i do ?
Click to expand...
Click to collapse
Flash the miui firmware again and then unlock the bootloader.
nvdata is corupt because i give it imei with eng rom. so when i try to flash stock rom it says nvdata is corupt
VD171 said:
Flash the miui firmware again and then unlock the bootloader.
Click to expand...
Click to collapse
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Moss je vb said:
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Click to expand...
Click to collapse
You need to repair your imei using engineering rom and modem meta tool.
Moss je vb said:
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Click to expand...
Click to collapse
silahkan terjemahkan ke english.
banyak tutorial yang membingungkan.
jika ingin unlockbootloader cukup menulis imei sim 2.
jika bermasalah penulisan imei ambil file preload dan md1img dari rom_eng.
jika ingin eksperimen bermainlah di md1img.
----------
MOD EDIT: English Translation Below
please translate to english.
a lot of confusing tutorials.
if you want to unlock bootloader just write imei sim 2.
if you have problems writing imei take the preload and md1img files from rom_eng.
if you want to experiment play on md1img.
hckbkl said:
silahkan terjemahkan ke english.
banyak tutorial yang membingungkan.
jika ingin unlockbootloader cukup menulis imei sim 2.
jika bermasalah penulisan imei ambil file preload dan md1img dari rom_eng.
jika ingin eksperimen bermainlah di md1img.
Click to expand...
Click to collapse
English only.
VD171 said:
English only.
Click to expand...
Click to collapse
sorry bos i am tired translate to english.
i am indonesian man.
me just help my brother in the world.
cobalah saudaraku memahami juga bahasa kami indonesia.
Moss je vb said:
Ok i mannaged to bypass nvdata and able to flash stock rom. but i cant still unlock the bootloader because when i try to attach to mi account in developer option it fails. because it needs imei to bind.
Click to expand...
Click to collapse
inti dari penulisan imei hanya preload(dari rom_eng) dan md1img.img(bisa pakai md1img.img dari versi lain atau dari rom_eng).
prosesnya
1. flash lebih bagus dengan pilihan "format&download"
2. kita harus backup terlebih dahulu file tambahan bisa dari redmi 9 normal atau kalau mentok ya ponsel kita yang hilang imei.
3. file backup yang saya saranin : nvcfg,nvram,proinfo,protect1,protect2
{file ini kita baca di scatter dari address dan partition, kita ubah NONE menjadi file(contohnya nvcfg.img), false dibawahnya kita ubah menjadi true, ini kita edit melalui note++}
backup ini berguna untuk file tambahan penguat sinyal komunikasi dan data jaringan.
4. boleh flash format total atau hanya file preload dan md1img.img(file rom_eng). setelah flash bagusnya unlockbootloader.
5. format manual menggunakan flashtool nvdata dan nvram (nilai format ada di scatter, address dan partition)
6. buka mauimeta (10.18versi) kita tulis imei 1 dan 2, lalu restart
7. ponsel akan error tapi tenang, kita format lagi dengan flashtool nvdata dan nvram
8. buka lagi mauimeta dan hanya tulis imei sim 2
9. selesai bila kita kembali ke flashtool, kita centang file nvcfg,nvram,proinfo,protect1,protect2,spmw,scp,sspm,tee lalu flash dan restart ponsel
jaringan ponsel akan lebih segar, imei 1 dan 2 terbaca, komunikasi jaringan cepat dan lancar,
catatan :
• perlu dibuat scatter menggunakan note++
• perlu backup file yang diperlukan
• bagikan tutorial ini disitus atau postingan anda untuk membantu saudara kita yang lain.
• jangan mudah percaya situs jaminan terjamin tutorial ampuh
1000% teruji
----------
MOD EDIT: English Translation Below
The essence of writing IMEI is only preload (from rom_eng) and md1img.img (you can use md1img.img from other versions or from rom_eng).
the process
1. flash is better with the "format&download" option
2. We must first backup additional files from the normal redmi 9 or if it's stuck, our cellphone has lost its IMEI.
3. backup files that I recommend: nvcfg,nvram,proinfo,protect1,protect2
{We read this file in the scatter from address and partition, we change NONE to a file (for example nvcfg.img), we change false below it to true, we edit this via note++}
This backup is useful for additional files of communication signal boosters and network data.
4. You can flash the total format or just the preload file and md1img.img(rom_eng file). after flash the good unlockbootloader.
5. manual format using flashtool nvdata and nvram (format values are in scatter, address and partition)
6. open mauimeta (10.18version) we write imei 1 and 2, then restart
7. the phone will error but calm down, we format it again with flashtool nvdata and nvram
8. Open Mauimeta again and write only IMEI SIM 2
9. finished when we return to flashtool, we check the files nvcfg, nvram, proinfo, protect1, protect2, spmw, scp, sspm, tee then flash and restart the phone
mobile network will be fresher, imei 1 and 2 are read, network communication is fast and smooth,
notes :
• need to create scatter using note++
• need to backup necessary files
• share this tutorial on your site or post to help our other brothers and sisters.
• don't easily trust guaranteed guaranteed tutorial sites, powerful tutorials
1000% tested
hckbkl said:
1000% teruji
Click to expand...
Click to collapse
English only.
VD171 said:
English only.
Click to expand...
Click to collapse
just translate brother
Heya guys,
I did get TWRP + LineageOS 18.1 working on this tablet a few months ago, and have been enjoying it (along with Magisk + google apps).
I had to use Odin, since no other method worked - but I had to borrow a laptop for that (since I don't use Windows, and the Linux apps didn't work at all).
Since LineageOS 19.1 was released, I thought I would give the upgrade a try, and also the backup + restore method a try for TWRP (must be tried + tested right? .. Or so I thought).
So, I get a USB drive, exfat formatted, double the size of the internal storage.
I backup all partitions except for "Dtbo", "cache", "EFS" (so all the stuff that might be touched by a potential patching I wanted backed up)..
Data, I also renamed the "media" to "mediabak" and backed that up - so that I wouldn't lose any media files either.
I then "install"ed the LineageOS 19.1 zip file using the TWRP "install" button.... Cleared the cache, aaaaand got the LineageOS boot animation and then just continual reboot...
5 reboots later, I boot into TWRP: "no worries - I shall restore from my backups!" I say to myself.
I restore everything except the "data" partition, thinking "it's OK, it's only data and it'll save me time restoring that"
... NOPE! - reboot and now I just get continual reboots but no boot animation.
"Maybe I need to wipe them before hand?" - so I select to wipe the partitions (vendor, system, cache, ...).. Only data+recovery not being wiped.
Restore
.... NOPE!
"Let's try data - maybe there's something funny in there?"
.... NOPE! - and what's worse, I get a tar extraction error (255) - probably due to the fact the partition isn't encrypted (as a guess) - I found a webpage showing the "data" files in the backups are only tar files, and on my laptop they show as OK except for having some missing "TWRP.security.encrypt" and something about a missing equals sign on the extended metadata (so I think the data is all intact, so I can probably transfer / extract it after I get the tablet back).
"Let's just try to re-install LineageOS 18.1 from the images... Wipe system, grab the image from the net, use TWRP to 'install' the image"
.... NOPE! - still stuck with a boot loop.
Why will TWRP not install the OS properly?
How can I trust TWRP after this, with no ability to restore things?
What am I missing here, since there's no logs or errors for me to check I'm flying blind here and fairly annoyed at the fact that something so simple (essentially extracting files and running a few scripts for a 'normal' upgrade run) is failing so hard.
... Can anyone point me in the right direction?
--
Paul_one
*UPDATE*
So, I've got a semi-update:
I' was able to use Odin again to flash stock ROM, then re-flash vbmeta.tar, then re-flash recovery, then re-flash lineageOS 19.1
19.1 looks AWEFUL on first boot, nowhere near as 'refined' as 18.1 (using a scroll window center aligned makes me thing of old HTML from the late 90s before CSS).
Anyway, so I am able to boot into LineageOS 19.1 .. If I restore the "system_image" and wipe the data partition (clicking the 'wipe data' button) it allows me to also boot into 18.1 .. GREAT ....
...Except...
I still cannot restore the data partition using TWRP.
Still errors with a "extractTarFork()" error, code 255 .
The tars look "fine" on my Linux machine, and extract with only missing extended metadata errors.
I wrote a script to extract the tar files and run it in the TWRP terminal - it errors about file duplicates (no metadata errors).
I see that this is actually due to a character length limit on the filenames.
One sub-directory it tries to extract (sessions) is shortened (to 'session') and all files within it are extracted as the new shortened directory name... Meaning that it tries to delete a file (which it cannot since it's a directory) and write the file (which it cannot since the directory exists with that name)!
How is this possible when ALL android pathnames are disgustingly long. How has this not been seen before and why is this so cr*p?
There's 2 other 'tar' files (sym-links to 'toybox' - which I assume is a busybox clone) which are a different size to the normal one in the PATH... So I'm going to try those, but I'm a little lost as to how effective this will be, and I'm AMAZED that these errors aren't coming up on any google search since it seems it's broken from the foundational commands!
... How this ever backed up 'correctly' in the first place I will never know - but I'll never trust TWRP to 'backup' my data partition again..
--
Paul_one
Further update:
I progressed with the boot of the system to include a user account and put a decryption pattern on.
After rebooting, ensuring the "wiping" method was "rm -fr" in the settings, I was able to restore from the TWRP data backup.
I then have been able to copy the contents of the old /data/media directory into the new one.
... yet again: however....
The boot of the OS now is stuck on "tablet is starting", with no progress, no change, nothing.
I've tried another restore of the system_image but that hasn't changed anything.
I'll leave it going, just incase it's like a "restorecon" and all the files are being 'corrected' (which could understandably take a long time)... But isn't tarused to stop this sort of b**ks from happening?
This is the worst experience of "backup" I have had in over 20 years!!
If I had known the backup + restore mechanism wasn't actually tested I would have performed my own "dd" to stop any of this.
Hopefully this will be a warning for anyone else trying to use TWRP for 'backup' of actual data and people can make a much better choice going forward.
--
Paul_one
Another update:
So, I am attempting to check through various differences between a "clean" /data, and the /data that's restored and doesn't let the UI come up fully.
I thought "logcat" might be able to point me in the right direction (error message about "Unable to find com.android.systemui")... But it's not exactly helping me out with the mass of other minor errors etc.
I was able to get a tiny bit further by renaming the "/data/app" directory, so I'm now prompted for the pattern to decrypt/log in ... But the "tablet is starting" pops up after (as if the setup wizard is completing or something).
Pressing home does nothing. I can pull down the status bar to access things in there - but the "home" isn't coming up properly.
So, now it's just a long journey of trial+error to try and find the problematic files/directories.
--
Paul_one
[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project, with...
forum.xda-developers.com
The difference between 18.1&TWRP and 19.1&TWRP is inability of TWRP to decrypt /data/media were TWRP directory locates. So once installed, 19.1 makes backup/recovery functions of TWRP inoperable since TWRP cannot nor decrypt nor find encrypted /data/media/TWRP. You can make sure of that with the file manager while in TWRP, seeing abracadabra instead of directory names in /data/media, which is an alias path to /storage/emulated/0 (0 stands for user0), where Download, TWRP etc locates.
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
vpn560 said:
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
Click to expand...
Click to collapse
That's unfortunate. I only discovered this now after upgrading from 18.1 to 19.1 four days ago....and then tried doing a backup through TWRP....which threw up a 255 fork error....
Wondering if a fix will be included with the next vewrsion....twrp-installer-3.6.1_9-0-lake.zip....
Is there any other backup/recovery through recovery you can recommend?
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
djimel said:
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
Click to expand...
Click to collapse
- English Plesse
- wrong forum ; this is for Samsung Tab S5e, not Oneplus..