I have a SGH-I337M S4 via Koodo in Canada. I've spent 15 hours on this so far and am now really confused.
History: I installed Cyanogenmod a couple years ago. Recently wanted to change from that so I decided to install stock first via SamMobile for SGH-I337M Koodo. I downloaded 5.0.1 from here sammobile
I had it installed fine and then went to root, so I used Odin, enabled USB debugging - and installed CF Auto Root. That worked.
Then I went to install Clockwork Recovery mod and it errored out and I don't recall exactly what happened but now I'm stuck with the yellow exclamation point saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
In the TOP LEFT of screen is says:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL: LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled
1) I tried to do emergency recovery through KIES but my phone isn't being recognized in Kies.
2) I uninstalled Samsung USB drivers and tried just KIES alone
3) I tried just USB drivers with flashing stock firmware via Odin in download mode - it errors out and says no partition found or says FAIL in red.
I've read a lot but i'm not that technical when it comes to this.. not sure what to do at this point. I can get into download mode but I can't get anything to work.
Is the phone ruined??
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
audit13 said:
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
Click to expand...
Click to collapse
Hi Audit,
Thank you for the reply. I was able to try the original USB cable now and loaded the stock Koodo firmware through Odin and it worked flawlessly. Once loaded and rebooted, it went right to the homescreen and skipped past all the normal setup stages, so I assume something on the phone was there already but just corrupted on a bad upgrade.
Never again using an older USB cable.
Whew, that was a learning lesson. Now I'd like to:
1) re-root again
2) Install custom recovery (clockwork?)
3) Install the marshmallow OS via Broken I believe.
I will keep the thread posted for others who need help and for my own reference.
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
audit13 said:
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
Click to expand...
Click to collapse
I did not know that. I thought I required root first and then had to install a custom ROM. Interesting.
Ok, so the plan then is to find twrp for my phone model and install that first... I'll search and try to do that now.
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
audit13 said:
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
Click to expand...
Click to collapse
Done. I used the latest one for the tar and I have v2.8.4.0 right now. I held volume up and power and it went to Teamwin with a bunch of options. Install/wipe/backup/restore/mount/settings/advacned/reboot
On the TWRP website it says: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
1) I'm not sure what it means by typing that. I'd like to keep TWRP as I install my custom rom. I have the custom rom on an external SD card along with GApps. Should I insert the sd card and then boot to recovery, wipe all data and install from zip on sd card? Is that correct?
2) How do I keep TWRP from not getting overwritten?
Thanks so much for the help. Really appreciate it after a weekend of terror.
I backed up the EFS portion and it wrote it to the internal storage of the phone I believe... data/TWRP something. I did not have my external card in when I did that. Is that the correct way and how would I access that backup if I needed to?
Sorry for the questions. Trying to learn without running in circles.
After I backed up the EFS it also asked me to install SuperSU and I did that - then it rebooted automatically.
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
audit13 said:
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
Click to expand...
Click to collapse
I'm not sure if I can post links due to the new account, but the latest files for me are found on dl.twrp.me/jfltecan/ and the only tar image is twrp-2.8.4.0-jfltecan.tar
I will have to go over your other comments on my own to see the functionality. As of now, this is what I have:
1) Stock firmware
2) TWRP installed
3) TWRP asked if I wanted to root (I said yes, figuring that's what you meant)
4) TWRP installed SuperSu and rebooted
5) I downloaded Root Checker and it verified root.
I did just test it by powering off phone and then booting into recovery. Teamwin came up - so I assume that it's all working correctly and the stock ROM did not overwrite anything?
Questions:
1) Now I can boot into recovery mode and install the custom ROM via a zip file on sdcard?
2) Do I install GApps via recovery mode after I install a custom ROM?
3) Should I wipe/format before installing and if so, which one - "Advanced" or "Format" buttons?
I did a factory reset via TWRP then installed the custom ROM. Seems to be working quite well. Maybe I will try it a couple times in order to get the hang of it.
In order to determine that TWRP is the default recovery - it should load when I go into recovery mode correct?
If the phone boots to twrp once, it should not revert to stock recovery in the future.
Is there a stable ROM for a S4 i337m that is newer? I'm having some trouble finding a solid list that is known to work. I don't want to install a wrong version and mess up. I did try the "broken" ROM but 50% of time when someone phones me, they can't hear me speaking so I'm going to have to go back to stock firmware for now.
You could try ROMs made for the 9505 and i337.
Related
Hello,
Longtime flasher here, but not as familiar with gs4.
My girl has a sgh-i337 that has been boot loader unlocked since day one. It's been on TWRP and slim rom the whole time too.
I was wiping Cache, Dalvik Cache, and System (so no more rom to boot to) prior to doing a rom update and TWRP glitched out while updating partition after the final wipe operation. Screen went black and unresponsive.
Now, the phone boots to download mode only.Will not boot rom (as system was wiped) but shows the samsung custom unlocked logo. When in download (odin) mode, I see product name: sgh-1337, Current Binary: Samsung Official, System Status: Custom CSB_OEM_LSB: 0x30 Write Protection: enable
Universal android toolkit will not show device connected so Installation of custom recovery through toolkit fails.
oddly, ADB will not show device connected so cannot flash rom or recovery via adb though all drivers were updated.
ODIN will show device connected, though (blue Com 4 appears in ODIN when connected).
To recover with odin, can I flash the I337UCUAMDL from sammobile and retain unlocked bootloader?
Thanks for any and all help.
shiftystylee said:
Hello,
Longtime flasher here, but not as familiar with gs4.
My girl has a sgh-i337 that has been boot loader unlocked since day one. It's been on TWRP and slim rom the whole time too.
I was wiping Cache, Dalvik Cache, and System (so no more rom to boot to) prior to doing a rom update and TWRP glitched out while updating partition after the final wipe operation. Screen went black and unresponsive.
Now, the phone boots to download mode only.Will not boot rom (as system was wiped) but shows the samsung custom unlocked logo. When in download (odin) mode, I see product name: sgh-1337, Current Binary: Samsung Official, System Status: Custom CSB_OEM_LSB: 0x30 Write Protection: enable
Universal android toolkit will not show device connected so Installation of custom recovery through toolkit fails.
oddly, ADB will not show device connected so cannot flash rom or recovery via adb though all drivers were updated.
ODIN will show device connected, though (blue Com 4 appears in ODIN when connected).
To recover with odin, can I flash the I337UCUAMDL from sammobile and retain unlocked bootloader?
Thanks for any and all help.
Click to expand...
Click to collapse
Yes. After you flash MDL firmware using Odin, you can still root and flash custom recovery.
Welp, installed that .tar through odin seemingly successfully. I still see the Samsung/custom/unlock boot screen but it hangs at the ATT boot screen (I let it sit for 20 mins). Any thoughts?
shiftystylee said:
Welp, installed that .tar through odin seemingly successfully. I still see the Samsung/custom/unlock boot screen but it hangs at the ATT boot screen (I let it sit for 20 mins). Any thoughts?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset. It'll get you past the bootloop
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Boot into the stock recovery and do a factory reset. It'll get you past the bootloop
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ah, gotcha. That will not wipe SD Card will it? i.e. /data is different than /sd, correct? ...There are vacation pictures on there I haven't backed up yet.
Many thanks again.
If you boot it into MDL stock, you may want to be careful that it doesn't get an OTA update to NB4 and in the process locking the bootloader.
You might be best off flashing the latest TWRP and rom of your choice. Or your girlfriend's choice!
Marc
shiftystylee said:
Ah, gotcha. That will not wipe SD Card will it? i.e. /data is different than /sd, correct? ...There are vacation pictures on there I haven't backed up yet.
Many thanks again.
Click to expand...
Click to collapse
It won't wipe your external sdcard. It will wipe the internal but if you just odin'd the internal is gone already
Sent from my Nexus 5 using XDA Free mobile app
Thanks Marc,
I'm keeping an eye on it waiting for it to boot so I can turn off wireless and data and root/flash recovery/etc. asap but its not booting. (will factory reset/wipe Data if I can confirm that it won't wipe SD Card)
I tried to make a flashable .tar file from the twrp recovery image and flash with oidin, but it fails.
ADB doesn't seem functional without root (?) so I can't push, pull or flash anything with ADB. Any suggestions on how to flash recovery and rom from this state?
shiftystylee said:
Thanks Marc,
I'm keeping an eye on it waiting for it to boot so I can turn off wireless and data and root/flash recovery/etc. asap but its not booting. (will factory reset/wipe Data if I can confirm that it won't wipe SD Card)
I tried to make a flashable .tar file from the twrp recovery image and flash with oidin, but it fails.
ADB doesn't seem functional without root (?) so I can't push, pull or flash anything with ADB. Any suggestions on how to flash recovery and rom from this state?
Click to expand...
Click to collapse
The twrp Odin fails because the bootloader is locked. Use motochopper
Edit, I haven't tried it but it's possible you can use towelroot to root and then flash the twrp image in flashify from the play store
Sent from my Nexus 5 using XDA Free mobile app
Ok. factory reset. Got it to boot. You were right, though. Odin formatted internal SD card. Once in a lifetime photos gone. Live and learn i guess, but I don't recall Odin formatting the SD card on my captivate when I was flashing that thing. ROM Chefs must have written custom scripts.
Time to look into motochopper loki root and the rest.
Thanks for your help guys.
btw, I have recovered deleted tiles from my PC with a utility that makes use of the fact that, in windows, deleted files are not written over, merely marked that those segments on the drive are available to write over. Do you think the flash memory on the phone would work this way?
Edit: pretty sure root/flashify is how I did it the first time. Will attempt that again.
I have searched and can not seem to find a solution
Here is where I am at:
Odin back to stock 4.4.2
Root with Towel Root
Install SuperSU, Update, and Disable KNOX
Install busy box
Install SafeStrap
Install Recovery
Boot into SafeStrap Recovery
Create Backup, Create a Partition and active Rom Slot 1
Wipe System, Cache, Data
Install Zip via External Card
Install goes perfect every time
Reboot
Phone gets stuck on the "Samsung Galaxy S5" screen
I can get into the stock recovery (not safestrap) and Download Mode
I then Odin back to stock and try again
I have tried 4 times and 4 different Roms. Has to be something I am missing
would using Flashfire possibly fix this?
EDIT:
Current set up
Android 4.4.2
Kernal 3.4.0
Build KOT49H.G900VRU1ANCG
update: Same problem with flashfire....
update 2: Could have been bad/wrong kernel. Going to odin to 5.0 and see what happens
67speeda said:
I have searched and can not seem to find a solution
Here is where I am at:
Odin back to stock 4.4.2
Root with Towel Root
Install SuperSU, Update, and Disable KNOX
Install busy box
Install SafeStrap
Install Recovery
Boot into SafeStrap Recovery
Create Backup, Create a Partition and active Rom Slot 1
Wipe System, Cache, Data
Install Zip via External Card
Install goes perfect every time
Reboot
Phone gets stuck on the "Samsung Galaxy S5" screen
I can get into the stock recovery (not safestrap) and Download Mode
I then Odin back to stock and try again
I have tried 4 times and 4 different Roms. Has to be something I am missing
would using Flashfire possibly fix this?
EDIT:
Current set up
Android 4.4.2
Kernal 3.4.0
Build KOT49H.G900VRU1ANCG
Click to expand...
Click to collapse
I think the problem may be you are trying to use the ROM slot. I thought I read that you are supposed to flash ROMs in the stock slot with safestrap.
Thank you for the help
I fixed it but not really sure how.
I THINK it was messed up because I had the wrong Kernel
Here is what I did:
Flashed latest Lollipop with Odin (on parrells on a Mac, worked really well)
Followed the KingRoot Guide to root phone
After a few attempts got root back
Installed the Rom suggested in the the Kingroot Thread
Found some script on XDA to debloat
I really wanted to try the toxic rom but going to play it safe for now...
ROM slot 1 is your problem, as it isn't supported on our devices.
Flash to stock slot only. Ignore the ROM slots.
If you did indeed have the wrong kernel flashed, you would never successfully boot.
Sometimes you also have to wipe cache and dalvik cache again after installing a ROM.
EDIT:
Please delete thread. There is an issue with my SD card resulting in files being corrupted. Massive losses. I was able to successfully install ROM by uploading files to Internal Storage
Hello,
I have been attempting to flash AryaMod : http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-3-tw-lollipop-5-1-1-t3326976/post67619860#post67619860
on my SM-N900W8. From the stock rom, I rooted it using CF-Auto-Root, then installed TWRP.
After downloading and putting all the necessary files on my SD Card, I attempted to install this but TWRP kept giving me file errors "Error: Secure Check Fail : aboot" when attempting to install anything, the kernel, the rom, the bootloader and modem, etc. Nothing was working.
I read that TWRP isn't very good with Aroma stuff and I should be using CWM, so I attempted to install that. Everytime I installed CWM, it would say it is going into recovery, then restart the phone, over and over..
Figured that I needed to just do a fresh install. I get a new Stock Lollipop 5.0 DOH1 from Kies, reroot with CF-Auto-Root, then install CWM from ROM Manager. Same thing, recovery bootloops.
Is there a way to fix either CWM or to get Aryamod to work with TWRP? Is the CF-Auto-Root breaking the recovery install since it installs through recovery as well?
At this point I've spent an entire day trying to get Aryamod with no luck. What the heck am I doing wrong?
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again
I ve done a nadroid of all the system on my oneplus 6t and wiped the system and internal storage and i forgot that the nandroid exists on the internal storage as im used to my old phone... currently i m stuck on TWRP any help ? i m panicking
I have mounted the storage MTP but all i see is this:
https://imgur.com/a/14rbdo9
https://imgur.com/ZVBwTRj
I m not sure i can copy anything into it.
Shady282 said:
I ve done a nadroid of all the system on my oneplus 6t and wiped the system and internal storage and i forgot that the nandroid exists on the internal storage as im used to my old phone... currently i m stuck on TWRP any help ? i m panicking
I have mounted the storage MTP but all i see is this:
https://imgur.com/a/14rbdo9
https://imgur.com/ZVBwTRj
I m not sure i can copy anything into it.
Click to expand...
Click to collapse
Adb sideload full ROM in TWRP with adb push *file* /sdcard
Wipe everything again and reinstall a full OOS zip found here in the forums. Make sure you install it to both slots, once you flash the full rom zip, flash TWRP again, reboot twrp and then reboot to system. You'll have to set everything up again unfortunately. My advice would be after you make a nandroid, copy it to a PC so that when you go to wipe everything, you can copy everything back and go from there or do what I do and buy a USB Type-C flash drive and when you go to make a backup, just backup to the flash drive. Or worst case use the MSM Download Tool to start fresh. Just make sure if you have the T-Mobile 6T to use the MSM specifically for the T-Mobile version.
I keep all of my important files like ROM's, recovery, Kernels, and backups on a 128gb SanDisk Ultra Fit 3.1 and use a Samsung OTG adapter. They can be had on eBay or Amazon for about $25. 32gb for $10, 64gb for $15-20, and 128gb for $20-25.
Do as Mikex8593 said or just flash the system partition of a fastboot rom
fastboot flash system system.img
oskarvlc said:
Do as Mikex8593 said or just flash the system partition of a fastboot rom
fastboot flash system system.img
Click to expand...
Click to collapse
I tried to sideload through TWRP and it failed every time I tried "total xfr: 1.00x.
I was thinking that maybe I should flash stock recovery and from stock recovery to flash the whole OOS Rom as i downloaded from OnePlus website?
Also i was looking at this thread " https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516"
and was wondering about the Fastboot roms, can I just flash it through fastboot and get the phone back working, since TWRP not working.
I m a bit newbie in this and learning my way through.
Thank you for your patience
TheKnux said:
Wipe everything again and reinstall a full OOS zip found here in the forums. Make sure you install it to both slots, once you flash the full rom zip, flash TWRP again, reboot twrp and then reboot to system. You'll have to set everything up again unfortunately. My advice would be after you make a nandroid, copy it to a PC so that when you go to wipe everything, you can copy everything back and go from there or do what I do and buy a USB Type-C flash drive and when you go to make a backup, just backup to the flash drive. Or worst case use the MSM Download Tool to start fresh. Just make sure if you have the T-Mobile 6T to use the MSM specifically for the T-Mobile version.
I keep all of my important files like ROM's, recovery, Kernels, and backups on a 128gb SanDisk Ultra Fit 3.1 and use a Samsung OTG adapter. They can be had on eBay or Amazon for about $25. 32gb for $10, 64gb for $15-20, and 128gb for $20-25.
Click to expand...
Click to collapse
Can you please explain what do you mean by installing it on both slots?
Edit: i Have just discovered the slots on TWRP which is something new to me and googling/trying to understand it.
isn't it possible to flash everything back using fastboot or stock recovery?
TWRP have failed in side-loading the stock rom zip I installed from oneplus website.
Yes, i was thinking of the same, I should get a USB type-C it is a must.
Thank you a lot for your help.
Shady282 said:
Can you please explain what do you mean by installing it on both slots?
isn't it possible to flash everything back using fastboot or stock recovery?
TWRP have failed in side-loading the stock rom zip I installed from oneplus website.
Yes, i was thinking of the same, I should get a USB type-C it is a must.
Thank you a lot for your help.
Click to expand...
Click to collapse
While you're booted into TWRP, if it boots to Slot A, install OOS to A, then change to Slot B and flash OOS to B. PM me if you need help. I'll try and help as best as I can.
TheKnux said:
While you're booted into TWRP, if it boots to Slot A, install OOS to A, then change to Slot B and flash OOS to B. PM me if you need help. I'll try and help as best as I can.
Click to expand...
Click to collapse
I have just decided to go to sleep, and in twrp i tried to click power off. The phone ended up in bootloop... then i tried to boot into bootloader. and then few more minutes the phone just booted in OOS Rom and started the setup process as new Rom.
Which is weird, I don't know what happened.
Also i have lost the TWRP recovery
I m not sure if it is related, to me clicking on slots A - B or so.
Shady282 said:
I have just decided to go to sleep, and in twrp i tried to click power off. The phone ended up in bootloop... then i tried to boot into bootloader. and then few more minutes the phone just booted in OOS Rom and started the setup process as new Rom.
Which is weird, I don't know what happened.
Also i have lost the TWRP recovery
I m not sure if it is related, to me clicking on slots A - B or so.
Click to expand...
Click to collapse
That's the point of slots, if your ROM is screwed in active slot and can't boot, at next boot the other slot will be set and tried. If there's a working ROM on it it's good. And if in the other slot no custom recovery is present you lose it
That's why I don't understand why people recommend to flash the same ROM on both slots, it goes on the contrary of the slot philosophy. The only understandable case is when you need to have up to date vendor official partitions before flashing a custom ROM: there the ROM Dev can recommend to flash official OOS twice. But it's not the case till now in the few custom ROM I've seen around
Sounds like you might have been making it too complicated. You can sideload the ROM, or just transfer the ROM to the phone and load it. The phone will be seen by the OS as a MTP device when TWRP is up and running.
When you are in slot A and you install the factory ROM it is automatically installed to slot B and vice versa. You need to immediately install the TWRP recovery to keep TWRP as the ROM will overwrite your recovery with the stock recovery. Then you need to reboot to recovery again, this would put to the opposite slot where your "new" ROM is installed, and let you install Magisk. If you want to update this the original slot just install the ROM and TWRP again. Reboot to recovery again. No need to specify slots, unless you didn't want to change something in the other slot for some reason (like a dual boot or something)
At this point just fast boot the TWRP image and re-run the TWRP installer to get TWRP back and it sounds like you're all set.
OhioYJ said:
Sounds like you might have been making it too complicated. You can sideload the ROM, or just transfer the ROM to the phone and load it. The phone will be seen by the OS as a MTP device when TWRP is up and running.
When you are in slot A and you install the factory ROM it is automatically installed to slot B and vice versa. You need to immediately install the TWRP recovery to keep TWRP as the ROM will overwrite your recovery with the stock recovery. Then you need to reboot to recovery again, this would put to the opposite slot where your "new" ROM is installed, and let you install Magisk. If you want to update this the original slot just install the ROM and TWRP again. Reboot to recovery again. No need to specify slots, unless you didn't want to change something in the other slot for some reason (like a dual boot or something)
At this point just fast boot the TWRP image and re-run the TWRP installer to get TWRP back and it sounds like you're all set.
Click to expand...
Click to collapse
Hi, I tried to copy the zip file through MTP but it didn't work, the internal storage on PC looked empty and was not mentioning any size of the storage, and when I try to copy and past a file, the copy process gets stuck on 0% forever.
Sideloading didn't work too. The CMD on PC reached 47% and then gave an error of total xfr:1.00x. when i tried to flash the stock rom zip file from oneplus website.
I had TWRP latest official one, i m not sure if it has issues.
Is there a way to validate that the stock rom files and all are still all working fine? Maybe re-flash the stock rom through stock recovery since TWRP is gone?
Also regarding the slot A and Slot B, i have never flashed anything except root through TWRP. So it could be when i wiped it wiped the empty slot. But the system is back at to zero and setup as new.
try this
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516