Bootloader Unlocked, Lost Recovery - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

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.

Related

I think my system portion is corrupt... Any chance of saving it?

I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good

Koodo I337M S4 Bricked?

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.

s5 fix from bootloop what to do?

So after a week of just bootloop, black screen of death and hard reset my rooted s5 suddenly open again.
Now that its open again what can I do to fix this? Cause im afraid that if i'll restart my phone i will get stuck in the bootlooop.
Suggestions?
Just to give you an update my s5 has been rooted for the past 2 years ...its just now that it got stuck in the bootloop.. im not really sure what caused this cause havent installed any apps that could affect the system...
Any ideas how can I fix it while its working again?
Would help if you gave us the model S5 it is, which firmware it's running, recovery etc?
Its g900f using stock rom... stock recovery
Please see attached file
Thanks in advance.
Download stock ROM using samfirm (or sammobile .com)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Put phone in download mode
Connect to PC USB > add .MD5 ROM to AP section in ODIN 3.10.7
Flash
Boot to recovery > Factory reset
Any other fix without flashing?
Any other fix.. that doesnt require flashing?
kenchii17 said:
Any other fix.. that doesnt require flashing?
Click to expand...
Click to collapse
Why don't you want to reflash? If you're rooted you should have backups.
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
kenchii17 said:
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
Click to expand...
Click to collapse
No it won't, and for a proper backup you need TWRP recovery
If your phone is having problems like it is, you very likely need to flash
Just flash the stock ROM over the top and your apps and data will remain
But backup photos and important files first by connecting the phone to USB and copying to PC
Forget about apps, you can reinstall them if something goes wrong
Ok thanks im starting to understand it now.. i just need to confirm a few things before i start doing it...i have watched a few vids and ok i think i missed installing a custom recovery... ill install it later and go with cwm...
Flashing the stock.. means getting my firmware(which has the size of 1gig+) in sammobile ang flashing it using odin right?
Read my 2nd post
Thanks alot got it! One last question , suppose that im not going to lose my apps but am i going to lose root once i have flashed the stock rom?
Yep, just root again, instructions are all over the forum, easy to find
Because you're getting bootloops, I suggested factory reset too, that will wipe the device, the flash won't, the reset will
I assume here's the steps that i need to take
1. Back up through cwm
2. Flash stock rom through odin
3. Clear dalv cache
4. Factory reset through recovery or from the homescreen setting?(will this removed supersu?)
6. Root device again
5. Restore back backup from cwm recovery?
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
*Detection* said:
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
Click to expand...
Click to collapse
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
jakeh9777 said:
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
Click to expand...
Click to collapse
Verizon lock their bootloaders
*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
It's unlockable nowadays
*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Rakuu said:
It's unlockable nowadays
Click to expand...
Click to collapse
Yep, but without unlocking it, he can't flash anything
jakeh9777 said:
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Unlock your bootloader and try again

SM-910W8 suck on Set Warranty Bit: Kernel / Recovery

Hi all,
Using my Note4 the other day and it suddenly restarted. When it booted back up, its was suck on the "Set Warranty Bit: Kernel" screen.
I read that I could use Odin to recover the OS as I need the data from the phone.
I downloaded the sock FW from sammobile for my device and flashed it with Odin.
During the flash process, it failed on the modem portion.
When it booted back up, it booted to the "Set Warranty Bit: Recovery" screen.
I tried to flash it again, and it passed this time, but same results.
How can I recover my OS to get the data off the phone or is there another way to do this?
Any help is greatly appreciated.
Thanks.
gigabotx said:
Hi all,
Using my Note4 the other day and it suddenly restarted. When it booted back up, its was suck on the "Set Warranty Bit: Kernel" screen.
I read that I could use Odin to recover the OS as I need the data from the phone.
I downloaded the sock FW from sammobile for my device and flashed it with Odin.
During the flash process, it failed on the modem portion.
When it booted back up, it booted to the "Set Warranty Bit: Recovery" screen.
I tried to flash it again, and it passed this time, but same results.
How can I recover my OS to get the data off the phone or is there another way to do this?
Any help is greatly appreciated.
Thanks.
Click to expand...
Click to collapse
You must wipe cache and data factory reset from recovery after flash firmware to avoid bootloops and clean os .i am not sure how you get data off the phone but for rooted users must make backup to microsd card or pc all data+efs+backup rom all the time .cuz things might go wrong at anytime.
Trex888 said:
You must wipe cache and data factory reset from recovery after flash firmware to avoid bootloops and clean os .i am not sure how you get data off the phone but for rooted users must make backup to microsd card or pc all data+efs+backup rom all the time .cuz things might go wrong at anytime.
Click to expand...
Click to collapse
Are there any utilities to back up the data in the state its in now?
gigabotx said:
Are there any utilities to back up the data in the state its in now?
Click to expand...
Click to collapse
1,Flash twrp recovery via odin
2, go to twrp/mount/and mount usb storage
3,connect phone to pc via usb cable
4.wait few seconds and your internal and external memory will show in pc
5,copy whatever important data you want into pc
6,flash stock firmware again in odin
7,after flash go to recovery and wipe cache data factory reset
Hope that helps:good:
Trex888 said:
1,Flash twrp recovery via odin
2, go to twrp/mount/and mount usb storage
3,connect phone to pc via usb cable
4.wait few seconds and your internal and external memory will show in pc
5,copy whatever important data you want into pc
6,flash stock firmware again in odin
7,after flash go to recovery and wipe cache data factory reset
Hope that helps:good:
Click to expand...
Click to collapse
Stupid question, is there a guide on how to flash twrp recovery via oden? (sorry new to this)
Thank you for your help! I feel like not all is lost and I still may use Android!
gigabotx said:
Stupid question, is there a guide on how to flash twrp recovery via oden? (sorry new to this)
Thank you for your help! I feel like not all is lost and I still may use Android!
Click to expand...
Click to collapse
http://androiding.how/how-to-install-twrp-recovery-using-odin/
This link will guide you how to flash twrp via odin
Make sure you download twrp recovery based on your model number.just google it like( twrp for n910f ) and you will find it easily.
Trex888 said:
http://androiding.how/how-to-install-twrp-recovery-using-odin/
This link will guide you how to flash twrp via odin
Make sure you download twrp recovery based on your model number.just google it like( twrp for n910f ) and you will find it easily.
Click to expand...
Click to collapse
update: I followed the above to flash twrp. When i try to enter twrp it says "Recovery is not seandroid enforcing" "set warranty bit: recovery"
When it boots, its just stuck in a boot loop.
what next?
Does anyone else have any suggestions?
One last try, anyone?

HELP! SM -G901F, TWRP can't find storage partition to mount

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

Categories

Resources