I'll try to make this as short as possible.
Basically, I have the I5510M, and flashed it from the stock Froyo rom to a gingerbread rom for the wrong region. Now it won't flash the original rom. Assumingly because of something that was changed in the bootloader or some other thing.
If I try to flash it, the device won't boot.
So I managed to get my hands on another identical device - I'm wondering if its possible to backup literally everything about the phone into some form Odin flashable thing.
I mean -everything-, the radio, the bootloader, the system, etc. A simple nandroid backup won't work, because it doesn't include things such as the radio.
Unfortunately the only CWM recovery rom available for the device only works with gingerbread. I've tried flashing it to the new phone on the froyo rom, and it simply won't work. I had to flash the stock recovery back onto it with odin.
Related
I flashed a new kernel to test and didn't like it, so I reflashed the ROM to get the stock kernel back and all hell broke loose. I lost root access and cant flash anything. I used Odin, re rooted and am on stock rooted 4.2. I've tried both TWRP and CWM to flash a ROM and from 2 different SD cards or restore my backup and it either says bad ROM or MD5 mismatch.
What am I missing here? In the meantime I'm just stock rooted with no mods, only restored user apps through Titanium.
92drls said:
I flashed a new kernel to test and didn't like it, so I reflashed the ROM to get the stock kernel back and all hell broke loose. I lost root access and cant flash anything. I used Odin, re rooted and am on stock rooted 4.2. I've tried both TWRP and CWM to flash a ROM and from 2 different SD cards or restore my backup and it either says bad ROM or MD5 mismatch.
What am I missing here? In the meantime I'm just stock rooted with no mods, only restored user apps through Titanium.
Click to expand...
Click to collapse
Check to make sure your usb cable is good. Many a time it is tthe usb cable which is bad.
Check to make sure the md5 checksum matches between the file you downloaded and the download itself.. From your device, use md5 checker.
From your pc, there is a similar program to do so.
The ROM has the Kernel cooked into it.
Read the ROM op to make sure.
If you dl a new Kernel file, always check the md5, in addition to inquiring if it's compatible with the ROM.
Always have the Kernel that was working saved somewhere so you can reflash it if necessary.
Always have a Nandroid Backup just in case.
When things don't play nice, always try going into Recovery and wiping
Cache & dalvik cache, and reboot.
Your initial is was:
A Kernel that didn't play nice with the ROM
or a corrupt dl
etc.
Your 2nd issue is most likely related to:
Bad usb cable or
Md5 mismatch, which can be because of a bad dl or a bad usb cabl.
re: stock firmware
92drls said:
I flashed a new kernel to test and didn't like it, so I reflashed the ROM to get the stock kernel back and all hell broke loose. I lost root access and cant flash anything. I used Odin, re rooted and am on stock rooted 4.2. I've tried both TWRP and CWM to flash a ROM and from 2 different SD cards or restore my backup and it either says bad ROM or MD5 mismatch.
What am I missing here? In the meantime I'm just stock rooted with no mods, only restored user apps through Titanium.
Click to expand...
Click to collapse
You need to start from scratch, put your phone into DOWLOAD mode and ODIN flash the stock M919 Samsung Galaxy S4 firmware.
(TAR file)
Here is the link to the official stock tmobile m919 firmware for your samsung galaxy s4 phone: http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
Once you do this you can root the phone if you like or leave it stock.
Good luck!
So I odin'd back to stock and rooted, I may leave it this way, the battery life is killer lol
Thanks for the help guys.
Well I got restless and tried flashing again and still no luck. I odin'd back to stock 4.2 and rooted just fine, have setcpu running and supersu installed but still cant flash anything or restore a backup, I'm really confused now.
While in download mode it says write protection enabled, is this normal? It also says this while I try to delete any files via USB. This is screwy.
I recently decided to try out CM11 on my SGN2-L900 (Sprint) and it wasnt everything I expected it to be. I couldn't install the gapps,zip file that i dl'd from downloadandroidrom.com, i tried a venum ice.zip file, and the sph-l900 stock recovery.zip file from downloadandroidrom.com and none of these files are taking effect. I seem to be stuck on the the CM11 with very basic options. I also backed up all of my data on Titanium Backp because I was rooted prior to the Rom change. I can still see I ahve my files when I hook my phone up to my laptop but have not been able to bring them back to my note.
please assist if familiar.
I'd like to get back to my previous phone state, forget about these roms altogether, and recover all of my files.
First, you may want to make sure you used the right rom version. I'm not sure what the SGN2-L900 is, but that's too different to be a typo for the SPH-L900, which is what this forum is on. I tried a quick search, and no phone variant came up. In addition, trying to flash a rom from a different phone variant can be very bad, and can brick a phone. Luckily, since you can still boot the phone and get into recovery, not all lost.
Plus, when you're downloading a custom rom, such as Cyogenmod, you should take note of the GAPPS file to be used. CM11 uses a different GAPPS files than previous versions such as CM10. Plus, usually you want to flash GAPPS after the CM rom. If you forget to flash it, you can do it later; it's just inconvenient
Titanium Backup is purely an app backup. It's not a ROM backup; this is what a nandriod is used for and one of the tools in the custom recovery. Plus, it is not recommend to use TB to restore apps when switching roms. It should be fine if just updating a rom, such a CM nightly.
If you're having no luck, I would suggest finding a stock tar file, and odin the firmware. This will remove root. But if you've had your phone over year, it'll already be out of warranty. Thus, when you go to re-root, it won't make a difference if you trip Knox warranty void. Just make sure you use the correct ROM for you phone. The odin the can be slightly challenging to find, but a doing a google search should be sufficient. I find version 1.85 or 3.07 work well.
I've been running CM11 nightlies for a while now, but recently decided to switch back to the dreaded touchwiz, as some apps weren't operating correctly. I used CWMR to restore the backup I had made previous to installing CWM. Booting up revealed many processes failing during the setup process, as well as the absence of the keyboard. Being a bit noobish, I installed a stock rom/recovery, hoping that would fix the issues. It did not. It stalls at "Just a sec..." before Setup Wizard quits and it loops indefinitely. Problem is I now can't flash a new rom or restore. I've tried installing cwm with no luck since, but take this with a grain of salt as I was admittedly a bit panicky during. Any help is greatly appreciated.
So are you still looking to restore or find any method to have your device boot up again...?
Spark91 said:
So are you still looking to restore or find any method to have your device boot up again...?
Click to expand...
Click to collapse
Yes. I've had no luck the past few days with it. Might give up on it if I can't get it working.
Head to rwilco12's website and under downloads for the Galaxy S II Sprint SPH-D710, Download the Odin OneClick of the stock rooted GB27, You can choose between deodexed or odexed, pick your poison, note that choosing Full Restore wipes internal and No_Data preserves internal storage.
Put device in download mode and restore.
Once you've fully restored, Download AGAT's gb27 source recovery and flash via recovery flasher on device or Odin on PC. Start up into recovery and try restoring your GB27 ROM again. I remember there being a guide when flashing back and forth from cm to tw and there was a specific way you had to restore it, I've lost the thread but still looking for it for you.
But until then, try the Odin one click method and see where it flies there
I am currently running DarthStalker rom and before that was on Hyperdrive. I would like to try out one of the "L" roms but I am still on the 900TUVUBM17 baseband. From what I have read I have to update and be on the N1 or N9 or maybe even Bsomething? So my question is what is the simplest way to do this and is there a way to do it without a PC as mine is down for a bit. Thanks
Yes, you can do it without a PC. Make sure you have the latest TWRP recovery installed.
1. flash the bootloader 0B6 or the latest one for your phone. Don't flash the incorrect one.
2. flash the modem 0B6 or the latest one for your phone. Don't flash the incorrect one.
3. Verify that you have both of the above, if not, do it again. I had to do it twice for it to stick.
4. flash your choice of custom Lollipop ROM. Make sure to follow the ROM's instruction for flashing, have to backup and wipe everything.
5. Wait about 15 mins for the first boot, you are done.
Thank you HappyPlato
Was on 4.4.2 stock NJ2...Odin'ed a custom recovery like TWRP...rebooted.....NO IMEI and BASEBAND. That's about as simple, yet complex it gets. Tried reverting back to stock recovery in Odin, only to find that NO IMEI and BASEBAND still shows up. THE ONLY way I've successfully kept the IMEI/BASEBAND....is by keeping everything stock, from recovery to rom. Why would this be? I've even tried restoring the EFS folder....to no avail!!!! I'M FRUSTRATED!!!! My end goal is to be able to flash a rom, use TWRP/CWM, and KEEP the IMEI/BASEBAND!!!
ANY HELP? ANYONE having the same issue or fix?
THANKS!!!!!!:good:
Possible fix...
Make sure you have not used device encryption on the rom prior to your desired rom...
If you have then a device full wipe script is needed to clean up the phone prior to flashing the new rom...
(don't forget to check your SD card for encryption or data files that may be affected)...
Flash TWRP version 2.8.6.0 and flash your new rom....
Higher TWRP versions have been buggy for me...
Best I've got atm....g
It's because you are using TWRP 3.0.0.1, that one is broken