As the title suggests, I am having trouble with a bootloop after successfully rooting a BOK3 stock GS5 5.0, installing SafeStrap and successfully flashing steps 2, 4 and 8 on this guide.
I can exit the bootloop by pulling the battery, booting into download mode, downgrading to the ni2 kernel using Odin and finally making it back to SafeStrap. From here however, I'd like some input on how to proceed.
I think I'd like to try to revert all changes through whatever means, all data has been backed up so I'm not concerned about that.
Thanks in advance
problem was being caused by /data not mounting properly, I assume it got corrupted somewhere along the way. Full wipe of everything but sd card fixed the problem and allowed flawless running of the deodexed stock BOK3 rom generously provided by jrkruse, thanks to CVertigo1 for the pointers.
T3nmoku said:
problem was being caused by /data not mounting properly, I assume it got corrupted somewhere along the way. Full wipe of everything but sd card fixed the problem and allowed flawless running of the deodexed stock BOK3 rom generously provided by jrkruse, thanks to CVertigo1 for the pointers.
Click to expand...
Click to collapse
For future reference, you should post issues in that specific ROM thread instead of the generic troubleshooting forum. You'll get help much quicker in the appropriate thread.
Related
I currently have the Samsung Galaxy S4 - MF3; v4.2.2; i337. I got the phone unlocked (direct from AT&T); and then
1. followed this method to root my phone - http://forum.xda-developers.com/showthread.php?t=2387577- Worked.
2. Got Safestrap v3.65 - http://blog.hash-of-codes.com/downloads/safestrap/ - Worked.
3. Tried 3-4 different ROMs, none of them have worked.
a. http://forum.xda-developers.com/showthread.php?t=2356276
b. http://forum.xda-developers.com/showthread.php?t=2418522
c. http://forum.xda-developers.com/showthread.php?t=2630085
d. http://forum.xda-developers.com/showthread.php?t=2537495
4. Tried above ROMs with kernels from here - http://forum.xda-developers.com/showthread.php?t=2292341 (v4.2.2 or v4.4 - depending on the ROM) and also the MF3 kernel (can't find the link)
But, irrespective of what I try, I still get stuck while loading the ROM - blank screen, not moving forward. Could you please shed some light on what I should try to do?
Thanks!
Vishoka said:
I currently have the Samsung Galaxy S4 - MF3; v4.2.2; i337. I got the phone unlocked (direct from AT&T); and then
1. followed this method to root my phone - http://forum.xda-developers.com/showthread.php?t=2387577- Worked.
2. Got Safestrap v3.65 - http://blog.hash-of-codes.com/downloads/safestrap/ - Worked.
3. Tried 3-4 different ROMs, none of them have worked.
a. http://forum.xda-developers.com/showthread.php?t=2356276
b. http://forum.xda-developers.com/showthread.php?t=2418522
c. http://forum.xda-developers.com/showthread.php?t=2630085
d. http://forum.xda-developers.com/showthread.php?t=2537495
4. Tried above ROMs with kernels from here - http://forum.xda-developers.com/showthread.php?t=2292341 (v4.2.2 or v4.4 - depending on the ROM) and also the MF3 kernel (can't find the link)
But, irrespective of what I try, I still get stuck while loading the ROM - blank screen, not moving forward. Could you please shed some light on what I should try to do?
Thanks!
Click to expand...
Click to collapse
ROM's C and D didn't work because they're AOSP ROMs, and 4.4. You can't cross versions. Besides that, I'd get the safestrap 3.65 APK from our own safestrap thread to make sure you get the correct JFLTEATT version and the MF3 kernel modules which you need to flash after every ROM. What exactly is your process for flashing, and what slot are you flashing to?
DeadlySin9 said:
ROM's C and D didn't work because they're AOSP ROMs, and 4.4. You can't cross versions. Besides that, I'd get the safestrap 3.65 APK from our own safestrap thread to make sure you get the correct JFLTEATT version and the MF3 kernel modules which you need to flash after every ROM. What exactly is your process for flashing, and what slot are you flashing to?
Click to expand...
Click to collapse
Thanks for the prompt reply! Appreciate it. I did get the exact safestrap 3.65 APK from my JFLTEATT version.
I'm flashing into Slot 1. Size - 1GB, 1GB, 300MB. I'm not entirely sure what you mean by what process, by here goes - Factory Wipe, Flash ROM, Flash MF3/v4.2.2 Kernal, Wipe Dalvik/Cache, attempt to fix permissions (always fails with same message). Restart into slot 1.
Vishoka said:
Thanks for the prompt reply! Appreciate it. I did get the exact safestrap 3.65 APK from my JFLTEATT version.
I'm flashing into Slot 1. Size - 1GB, 1GB, 300MB. I'm not entirely sure what you mean by what process, by here goes - Factory Wipe, Flash ROM, Flash MF3/v4.2.2 Kernal, Wipe Dalvik/Cache, attempt to fix permissions (always fails with same message). Restart into slot 1.
Click to expand...
Click to collapse
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
DeadlySin9 said:
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
Click to expand...
Click to collapse
Thanks again for the prompt reply, I hope you don't mind me taking more of your time. But, I'm having a hard time finding "latest" ROMs for my version, could you point me to one? I've been scouring through Android Original Development, but they're all 4.3 and 4.4, versions you said I couldn't cross-install. Thank in advance!
DeadlySin9 said:
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
Click to expand...
Click to collapse
I tried what you said, and it worked! With ROM (a), I'm now running into System UI ran into an error, problem. Still looking around.
Vishoka said:
I tried what you said, and it worked! With ROM (a), I'm now running into System UI ran into an error, problem. Still looking around.
Click to expand...
Click to collapse
Did you sign in to a google account at the initial setup? I know there's some issues involving that on the Google ROMs.
Hi everyone,
I have a Note 4 Exynos version and recently i decided to make the root procedure. My steps was first update to 5.1.1 then, root by flashing the su zip file, flashing TWRP recovery and then i did a full backup to make sure i can keep my files intact just in case. I tried installing CM 12.1 but i had the " Execute updating binary failed etc..." and after a lot of tries i decided to restore my backup. The problem is that after restoring my phone keeps rebooting in randomly.. Can i unroot without flashing stock firmware, so i can keep my backup as it is?
Any thoughts appreciated.
5.1.1 can't be root just yet.
Flash stock rom & setup your phone to fix it.
You can flash another rom after that
So that is the reason for the random rebooting? To be honest i followed the procedure from a known website that was talking about rooting this particular phone with version 5.1.1 ...
Thanks for the response
I'm expecting my 910c to arrive soon and I'm currently reading for root procedures.
So, if my phone arrives with 5.1.1, I won't be able to root? and if I root can I later flash 5.1.1 without problems?
Also, please direct me to a threat that is safe to follow in order to root.
Of course you can root 5.1.1
Just read the development section and follow the instructions there
sent from somewhere
Antreassy i have followed the procedure from a website i do not wish to quote since it might be against the forum rules. But the result was not the best since my phone keep rebooting. So the only thing that saved it is by flashing the stock 5.1.1 firmware using odin and everything came back to normal.
From my own research i believe that at the moment the most valuable custom firmware is CM 12.1 and that is the reason i tried to flash it at first but without any success.
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Thank ya for this post, it has actually been a while since I have updated my phone. I haven't had any issues with any of the apps thus far. It's been a little over 24 hours since I've updated. Also, I think my phone runs a lot smoother with the update than it use to. Also, I don't have any issues with the play store updating. I'll post issues if any occurs.
dave011182 said:
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Click to expand...
Click to collapse
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
IMBigWillie said:
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
Click to expand...
Click to collapse
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
dave011182 said:
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
Click to expand...
Click to collapse
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
IMBigWillie said:
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
Click to expand...
Click to collapse
You may also want to try using flashfire to create your own stock partitions tar to flash in this process to be sure my file on drive isn't somehow corrupted. If you used it in the first place. Use the flash firmware package option, wait for it to read the file partitions, then the download icon to create your partitions file. Use what's highlighted by default, create your file, and transfer it to your computer. Flash what is selected by default from the tar and reboot into download mode to flash the partitions file just created.
If all you want is stock root and your data works you shouldn't need to flash anything else at that point.
===Solved! Just overwrite your old SafeStrap by installing the SafeStrap.apk included at this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
and be sure to have BusyBox installed prior to overwriting the SafeStrap install, otherwise it will not actually work.
Unsure if related, but if problem persists connect your microSD directly to a PC and look for ".MM_KERNEL_SS-FF_Flashable" folder
===
So I had followed jkruse's locked bootloader guide to use a stock MM ROM with SS support. After using it for a while, I decided to go back to OptimalROM. Unfortunately, every reboot results in stock recovery. I found I can just flash a PB1 kernel through Odin and that fixes it for now- however on the next reboot BAM- back to the same problem.
I assuming this is caused by the current SafeStrap I have installed- which was linked in the MM for locked bootloaders thread.
How can I prevent the kernel from being overwritten every reboot?
On a side note, where can I find the latest stagefreight fix zip for 5.0? I have tried a few but they only seem to work on the 5.1.1 ported ROMs. Tried Stagefreight_Fix_02_Nov.zip and gets stuck at boot. Same situation with Stagefright_Fix_v2_i9505_i337M.zip.
Surely there is a ported fix somewhere for 5.0 roms?
Can you not flash PB1 thru Odin and just root and install OptimalROM via FF that way
Nandr0idC0nsumer said:
Can you not flash PB1 thru Odin and just root and install OptimalROM via FF that way
Click to expand...
Click to collapse
I can always resort to that, but I am trying to figure out what it is that keeps reflashing the MM kernel on reboot. I assume its the MM_Safestrap.apk, but only @jrkruse knows for sure
It appears I was right on the money! After grabbing the SafeStrap.apk from the OK3-V5 root package and installing that version of SS over the MM specific one, I no longer have the issue! I also opened my microSD directly on my computer (not connected through phone USB) and deleted the .MM_KERNEL_SS-FF_Flashable (note the .) folder.
Hope this helps anyone else who downgrades.
Still looking for a solution to the Stagefright Vulns in 5.0 ROMs
Hi there!
I'm flashing ROMs from XDA since 2013 but now is the first time I experience problems. Since I'm new to this forum I cannot ask directly in the according thread, I'm sorry for that.
Just like always (already flashed a tons of phones) I followed the instructions step by step (http://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274), starting at flashing the modem ("Requirements", Step 2). After that I mentioned that my TWRP noticed my about not successfully mounting /dev/block/... (first block device, don't remember the name) to /firmware. After flashing the ROM and GAPPs the phone stucks at booting (the animated CM-Logo). Erasing all partitions, system, ... doesn't help.
Do I (XT1622, EU-variant, no Amazon) have to flash an other modem file instead?
Thanks advance!
I installed that system today and I can't recall seeing the steps that you are following.
Take a look at the instructions again.
I installed from twrp the following order:
Modem
CM
gapps
And I wiped before and after.
Also I had to have the files on the internal storage for it to work. I got error 1 when I did it from the sd-card.
Hope this helps you
Thanks for your reply, benedictusg!
I actually managed to install the CM14.1 MOD by restoring everything (incl. relocking the bootloader) and then giving it another try. And hooray - here we are! :good:
For anyone experiencing the same or similar problems, here's what to do for restoring the original firmware:
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Cheers!
That's great news! I'm happy for you! I'll keep that in mind if I want to downgrade at some time (I doubt it though, because everything seems to work).