So I rooted my P6010 and installed CWM but now I'm checking for updates in anticipation of ICS (fingers crossed any day now) and I get an update (stability 17.08MB) but it won't apply as there's no stock recovery installed.
Everything it reboots to try to opens CWM obviously about to apply but can't...
No sign of a downloaded update in the obvious places.
Where do the Samsung OTAs download to?
Sent from my GT-P6810 using XDA Premium App
Jompet said:
So I rooted my P6010 and installed CWM but now I'm checking for updates in anticipation of ICS (fingers crossed any day now) and I get an update (stability 17.08MB) but it won't apply as there's no stock recovery installed.
Everything it reboots to try to opens CWM obviously about to apply but can't...
No sign of a downloaded update in the obvious places.
Where do the Samsung OTAs download to?
Sent from my GT-P6810 using XDA Premium App
Click to expand...
Click to collapse
You can flash the stock recovery back. Get your stock rom, extract the recovery.img
Make a uncompressed tar with just recovery.img in it. Then flash this tar with odin (in the pda)
Tip: dont use 7-zip to build the tar, it just wont work. You should use linux or busybox tar in your tab to create it.
This way you can switch between cwm and stock recovery as necessary.
Thanks for your help. I'm aware of this and I realise I could do this but it's a lot of hassle when I'd prefer to investigate the option of just flashing the OTA using CWM. I just need to find out where the damn file is!
Sent from my GT-P6810 using XDA Premium App
When I try
reboot fota
from a terminal as root, I get a log dumped in /cache/fota
It looks like its looking in multiple locations for a directory tmp_sec_fota.
I dont have any updates, so it all fails, but maybe a clue?
I had a good look around but can't seem to be able to find anything. Shame.
I pulled this screenshot from CWM logs and there's a lot of reference to fota but everywhere I look there's no file even approaching 17MB.
Now I have a real problem because the Tab is my only device apart from a Galaxy Nexus so I don't think I can get a copy of stock recovery. I can flash as I've got MobileOdin though. I'm wondering if it's worth the hassle to do all of this for the OTA or if I should just wait for a version I can flash with CWM.
I only really rooted to sort the rw problem out with my 64GB MSD, if Samsung had have been better devastating I wouldn't have had to.
Sent from my GT-P6810 using XDA Premium App
Stupid swiftkey. I obviously meant developers not devastating.
Sent from my GT-P6810 using XDA Premium App
Those partitions in your photo are not correct for a p6810. You must have the wrong cwm installed.
/system is on /dev/block/mmcblk0p8
on my device, and your data and preload are wrong as well.
Where did you get the cwm. Could you be using one for the p6800? It has different partitions.
See the 7.7 development thread for one suited to the p6810.
Be very careful what operations you select if you have wrong cwm!
Also, any backups you have previously made (with the wrong cwm) should probably be discarded, as the data files will be misnamed/incorrect contents.
I got it from the P6010 CWM thread...? Strange.
I've discarded it and moved back to stock, ran the updates and everything works well now. Ran into some minor permissions stuff with modin but sorted it with removal from such app.
I think a lot of people are going to bump into these problems when ICS hits if they're running CWM.
Sent from my GT-P6810 using XDA Premium App
Oh and thanks for all your help!
Sent from my GT-P6810 using XDA Premium App
Related
Hey all.
On the Verizon i815 tab we seem to have a modem and a separate LTE modem. In the OTA files the scripts always do a
write_firmware_image("/tmp/modem.bin")
and the LTE file gets pushed to /dev/block/mmcblk0p8.
Now the question is, WHERE does the write_firmware_image call flash the bin file and how can I extract it from a running and updated device?
Background: We have one user who by some weird coincidence got the ICS OTA update pushed from Verizon. Everyone else's update always fails (whole debacle can be found in different threads). We now managed to have this one user pull a clone copy of all of his partitions via dd if=/dev/block/mmcblk0pxx of=/sdcard/file_xx commands and pushing those into another tablet yields a working ICS with updated LTE modem but the "regular" baseband still shows the old version!!!
I need to know how this one successfully updated user can dump his modem.bin and where we need to flash this dd or using this proprietary write_firmware_image function, so that in the end everything is updated as if the OTA had worked in the first place ...
THANKS
Pershoot is the king with the 10.1 tab variants, maybe he he can shed some light.
Sent from my SCH-I815 using xda premium
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
This may be the first instance where Honeycomb is actually useful (the recovery part LOL)
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Yes of course. It's Verizon
electron73 said:
Yes of course. It's Verizon
Click to expand...
Click to collapse
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Well it seems like it's "half locked" then. The tab allows you to flash any recovery but nothing else. No kernel, no system fs. And they are locking it down further with every update. New ICS recovery won't flash unsigned zips anymore.
What solution do you have? Always interested in learning more about this stuff.
OK. I can probably help then. I'll post more details when I get home in a little bit.
Sent from my SCH-I500 using xda app-developers app
electron73 said:
New ICS recovery won't flash unsigned zips anymore.
Click to expand...
Click to collapse
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
rhester72 said:
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Click to expand...
Click to collapse
It seems you can simply ODIN your CWM back on and then take it from there. As long as they don't close that hole at some point... Right now with the latest ICS version, even with stock recovery installed, this is still possible.
jt1134 said:
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
Click to expand...
Click to collapse
Awesome! Thanks for your help. Now of course I have a few questions and hope you can give me a quick rundown.
how do I unpack this img. I have linux and good knowledge of linux and unix tools. You say it's an initramfs? Is there a tutorial somewhere that explains how to unpack, modify and repack such a thing? And where do I make the changes if I were to do it myself with *our* ICS recovery?
I believe I can't just flash this one as there are big differences between the international versions and our LTE version of the Tab 7.7
The partition table is different etc. I don't want to use this and end up screwing my stuff up. I'd rather take the original one that came with our ROM and modify it myself.
You don't happen to also know how to unlock the bootloader so that we could just flash a rom with ODIN ?
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
I think maybe we could start a donation for Mr JT to get the i815?
If he's interested yeah?
He's done many marvelous things!!
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
jt1134 said:
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
okashira said:
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
Click to expand...
Click to collapse
Well... Bootloaders I have never really looked into.. I am still unable to flash a kernel or a factory fs with ODIN. Odin only lets me flash the recovery. So something is locked there. Maybe not crazy-locked like the motorola razr phones but also not completely open like the AT&T Galaxy Note was... Maybe someone with a little more experience in this stuff can shed some light
jt1134 said:
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
Click to expand...
Click to collapse
Cool! Thanks for the links. Will look at the stuff and see if I can figure it out
Softbricked, only boot in cwm. So i use apx tool and flash the orignal EUU Honeycomb rom to unbrick. And i can boot to the home screen but My internal storage has gone , only 128mb. I want to know how to get it back.
Sent from my GT-N7000 using xda app-developers app
You probably have corrupt data on it.
I don't know how you got yourself into this, or what you were running before. V8 Bootloader and CWM? Which Ruus?
Do you have your original UID? You will need it again.
Here's a link to TD's V4 rollback. You will need your UID. So get it using the USBDview app in the rollback kit before you begin.
http://d-h.st/0x7
MD
Thank you MD and downloading the file. I have used thor JB ROM with HC Bootloader before. I noticed that message showed "removed error /data/misc/bluetooth/xx:xx:xx:xx:xx:xx/config formate /data error" when I wipe data. After that perhaps data corrupted and cant boot into system again. I jave a question I download another tdV4 package perhaps the same as you give me. And donetdetect.exe cannot run under my system（win8 64bit）It showed compatible error. So perhaps your package can run under my system or I have to wait until Monday afternoon after I finish the damn bussiness things and back to my office and get a xp computer.
Sent from my GT-N7000 using xda app-developers app
Thank you very very much. I roll back and look like it used to be. Nice HC green!
Sent from my GT-N7000 using xda app-developers app
I just rooted my Sprint S4 (MF9 FW) using CF-AutoRoot. Everything appeared to work - SU was installed, my file browser had root access, and I was able to turn on free wifi tethering.
However, literally every single application I have installed (sideloaded or through Play) since rooting is force closing. I even tried something really standard - the official Facebook app. No dice.
The only applications that work are those that I installed prior to rooting.
I used Titanium Backup to remove a handful of things - Sprint Zone, Sprint International, TripAdvisor, FlipBoard, and some of the preinstalled games. I haven't touched any system stuff or even any of the Samsung apps.
Help!
Best thing to do is start from scratch. DIAL ##786# and reset everything. After that if you still have problems, download latest firmware and Odin install it.
Sent from my SPH-L720 using xda app-developers app
Nautilusus said:
Best thing to do is start from scratch. DIAL ##786# and reset everything. After that if you still have problems, download latest firmware and Odin install it.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
What should I use for MSL?
shifuimam said:
What should I use for MSL?
Click to expand...
Click to collapse
Before you did the root did everything work okay?
Sent from my SPH-L720 using xda app-developers app
Nautilusus said:
Before you did the root did everything work okay?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Yep. Any app that I installed prior to running CF-AutoRoot loads just fine. The only application that I installed after rooting that DOESN'T force close is Titanium Backup.
First try this, reboot into recovery, twrp or cwm, and wipe just dalvik and cache but not data. This will force your phone to rebuild its app index and cache and should fix your problem. If that doesn't help see below.
Sounds like you may have deleted the wrong file using TB. You may want to download one of the stock rooted roms either odex or deodex (your choice) and dirty flash it. In other words don't wipe anything but cache and dalvik, don't wipe data. This way the install will replace the files you deleted and you should be up and running.
cruise350 said:
First try this, reboot into recovery, twrp or cwm, and wipe just dalvik and cache but not data. This will force your phone to rebuild its app index and cache and should fix your problem. If that doesn't help see below.
Sounds like you may have deleted the wrong file using TB. You may want to download one of the stock rooted roms either odex or deodex (your choice) and dirty flash it. In other words don't wipe anything but cache and dalvik, don't wipe data. This way the install will replace the files you deleted and you should be up and running.
Click to expand...
Click to collapse
Well, crap. I don't have CWM installed yet. Since I just got the phone yesterday, I don't really have anything on it - I'm fine with wiping it completely back to factory defaults.
I made backups of everything I uninstalled in TB. Should I restore all that first?
ETA:
I cleared my davlik cache via ADB. Rebooted, and now EVERYTHING - including system processes, like com.android.phone - is FCing.
You can try restoring, but I bet wiping cache and dalvik might be the problem. If you have the pro version of TB I believe you can do it from TB without installing a custom recovery. Also, make sure you do a reboot since that will often fix force closing apps.
Sent from my SPH-L720 using Tapatalk 4
Odin install the latest firmware.
Sent from my SPH-L720 using xda app-developers app
Nautilusus said:
Odin install the latest firmware.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
That's what I'm doing now. Still trying to find a copy of the official MF9 firmware that will actually download, though.
Try here...
http://www.sammobile.com/firmwares/1/
Sent from my SPH-L720 using xda app-developers app
Nautilusus said:
Try here...
http://www.sammobile.com/firmwares/1/
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I accidentally cancelled my hotfile download, so I couldn't restart it.
Is there a reason why these firmware files aren't on Bittorrent? It seems like a significantly faster and more efficient way to access such large files.
shifuimam said:
Yeah, I accidentally cancelled my hotfile download, so I couldn't restart it.
Is there a reason why these firmware files aren't on Bittorrent? It seems like a significantly faster and more efficient way to access such large files.
Click to expand...
Click to collapse
Just wait 30 minutes..... it should refresh. A torrent download of the firmware may be tampered with, so I would not mess with a firmware from there. It could potentially brick your phone.
Sent from my SPH-L720 using xda app-developers app
Nautilusus said:
Just wait 30 minutes..... it should refresh. A torrent download of the firmware may be tampered with, so I would not mess with a firmware from there. It could potentially brick your phone.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
No moreso than downloading Ubuntu off Bittorrent.
It's pretty easy to verify that a file on BT hasn't been tampered with - verify the hash of the file. If it doesn't match the original file, it's not valid. Hosting on a crappy site like Hotfile with ungodly slow download speeds in no way verifies that the file hasn't been tampered with. Since these firmware files aren't coming from Samsung or the carrier directly, you can never be completely certain that the file is valid and untouched.
I'd much rather see this stuff on BT where downloads don't take two hours. It's no less trustworthy than downloading from a horrible file upload site with ridiculous limitations.
ETA: the root I downloaded from XDA bricked my phone (even though the thread said multiple times that my version of the stock FW wouldn't brick). Can't trust anything on the Internet...
shifuimam said:
No moreso than downloading Ubuntu off Bittorrent.
It's pretty easy to verify that a file on BT hasn't been tampered with - verify the hash of the file. If it doesn't match the original file, it's not valid. Hosting on a crappy site like Hotfile with ungodly slow download speeds in no way verifies that the file hasn't been tampered with. Since these firmware files aren't coming from Samsung or the carrier directly, you can never be completely certain that the file is valid and untouched.
I'd much rather see this stuff on BT where downloads don't take two hours. It's no less trustworthy than downloading from a horrible file upload site with ridiculous limitations.
ETA: the root I downloaded from XDA bricked my phone (even though the thread said multiple times that my version of the stock FW wouldn't brick). Can't trust anything on the Internet...
Click to expand...
Click to collapse
Sorry to here that....... my reasoning for the torrent answer was to provide an explanation, I also would like a faster download speed but we are in, how shall I say, shady areas of the internet and taking a download from a familiar site and wait a while than a questionable download that takes 5 minutes especially when you could possibly permanently brick your phone (or worst..... do something that has you wondering what the hell is going on.)
Sent from my SPH-L720 using xda app-developers app
Nautilusus said:
Sorry to here that....... my reasoning for the torrent answer was to provide an explanation, I also would like a faster download speed but we are in, how shall I say, shady areas of the internet and taking a download from a familiar site and wait a while than a questionable download that takes 5 minutes especially when you could possibly permanently brick your phone (or worst..... do something that has you wondering what the hell is going on.)
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I guess what I'm getting at is that if the community used BT, it wouldn't be a questionable source.
Content on BT is not inherently questionable or risky. Canonical uses Bittorrent as both the official and the preferred method of downloading Ubuntu LiveCDs because it is so much more efficient and low-cost than traditional direct downloads over HTTP.
I get the feeling that the XDA community has developed the misconception that Bittorrent is only used for porn and pirated media, and has no legitimate or safe purpose - that's just not true at all. You also aren't required to use TPB as a tracker for a torrent you create.
Most major torrent clients include file hash checking as part of the standard download process, for the very purpose of preventing people from changing files mid-download or during seeding.
It would make quite a difference in how ROMs are distributed. I can guarantee you that downloading off Hotfile is no more secure than using BT. Just because you've download files off one of these "stock ROM" sites before doesn't mean that all their ROMs are clean and safe, and it doesn't in any way guarantee that the files they're hosting came from a reliable source.
OK, so for anyone with this issue:
You're pretty much SOL on trying to retain the rooted ROM as-is. The only thing I was able to do successfully was use Odin3 to reflash my phone with a stock Sprint ROM. For the record, my phone was running MF9 when I attempted to root it. I was able to reflash it with stock, unrooted MDC, and basic stuff appeared to work (I didn't test much; I was just trying to make sure the phone worked before flashing with a custom ROM).
I originally had no plans to install a custom ROM right away, because I wanted to mess around with the special "features" in the Samsung firmware. After this fiasco I didn't want to risk the same problems rooting stock, so I just flashed CWM in Odin3 and upgraded to the latest CM10 nightly. It's been stable so far.
You could have tried to fix permissions too.
Definitely tried that multiple times. I've noticed in other threads that CF-AutoRoot is unreliable on MF9, too.
Sent from my SPH-L720 using Tapatalk 4
shifuimam said:
Definitely tried that multiple times. I've noticed in other threads that CF-AutoRoot is unreliable on MF9, too.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
So whats the best way to root the s4 on mf9?
Sent from my SPH-L720 using xda app-developers app
Hi, I was hoping to get some help and insight with the situation I've been dealing with. I'll give as much information as possible so that someone might be able to point me in the right direction.
I have an att galaxy s4 that was purchased and rooted before the mf3 ota that made everything so difficult. I've flashed several roms and decided to go with liquidsmooth 2.37 atm and I'm experiencing a few odd issues (stock mss not working) that no one else seems to have, but for the most part it's running very well. Lately I've wanted to go with a rom using the new 4.4 and I've tried a handful no matter what rom I try I have the same issues. so far I've tried CM 11, Omnirom and Gummy. With all of them everything runs very laggy and glitchy and will frequently freeze until it crashes and reboots. Every single time I've used whatever gapps are linked in the op for every rom and followed flashing instructions to the letter (wipe data/factory reset, wipe cache, wipe dalvik, flash rom , flash gapps, flash super su (if needed) and reboot) and I've even tried different recoveries (both cwm recovery 6.0.4.4 and the latest philz cwm recovery) same results every time. This part shouldn't matter, but I tried flashing these roms while on the original mdl modem and after upgrading to mj9. Let me know any other info you need, but I've tried to be thorough. I appreciate the help.
So what firmware are you on right now?
scott14719 said:
So what firmware are you on right now?
Click to expand...
Click to collapse
I'm guessing mdb
sorry thought i mentioned the firmware is mdl
Rockman195 said:
sorry thought i mentioned the firmware is mdl
Click to expand...
Click to collapse
Looks like you're doing everything right. Have you checked md5's of your downloads?
I don't know how to do that or else I would
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
I don't know how to do that or else I would
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
http://onlinemd5.com/
Thanks for the link. I'm looking into md5 checking and I downloaded the hash droid app. My only question is when I calculate the md5 of a file what am I supposed to compare it to?
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Thanks for the link. I'm looking into md5 checking and I downloaded the hash droid app. My only question is when I calculate the md5 of a file what am I supposed to compare it to?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You should compare it to the md5 typically posted where you download the file from
Ok so the dl site like devhost or whatever
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Ok so the dl site like devhost or whatever
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Correct. I usually just compare the last 5 or 6 characters. If they match it's very unlikely the others won't too.
tried going back and looking in all the threads that I downloaded roms from, can't find md5s for any of them with one exception and thats an outdated version of a rom I'm not currently trying to flash, so I don't see the point in downloading it just to compare the md5
Downloaded an omnirom build and checked the md5 and everything was good, plus I would be surprised if the md5s were bad on all the roms I've tried. Any other suggestions? Should I try two recovery instead of coming?
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Downloaded an omnirom build and checked the md5 and everything was good, plus I would be surprised if the md5s were bad on all the roms I've tried. Any other suggestions? Should I try two recovery instead of coming?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm running out of ideas try twrp recovery. Here is a zip you can flash in your current recovery http://forum.xda-developers.com/showthread.php?p=45511518
flashed twrp and that royally screwed up the phone. opened recovery using twrp and made a back up then did a system wipe and went to install the rom and when I went to do that, the list of all teh files you have to choose from was blank. I could go through different folder levels but the part where it shows the contents was always emtpy. Sometimes I could touch the area and see I portion highlight like it was making a selection but it wouldnt do anything and there was no file name there. Went to restore the backup I made and there was nothing in the list of backups to restore from. Rebooted the phone and liquid smooth 2.37 loaded like a clean flash with none of my info, files, apps, etc so I downloaded rom manger from the playstore and put the latest cwm touch on there. When I went in recovery none of my cwm backups where there or anything so i went to reboot and it only shows the samsung boot screen. Downloaded a few different roms and gapps on my sd card from y computer and put them on the phone and flashed the roms and gapps and still can't get past the boot screen. I'm really open to suggestions on this one.
If it was me, at this point I'd Odin the stock mdl firmware and start all over again. Something's not right with your phone. But it scares me a little since things aren't flashing correctly and there could be something wrong with your internal memory. If memory is bad it could make things worse.
I think your right. Do you know where I can find the stock firmware and instructions for flashing it? I haven't used Odin in a while.
Sent from my GT-N8013 using xda app-developers app
Rockman195 said:
I think your right. Do you know where I can find the stock firmware and instructions for flashing it? I haven't used Odin in a while.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
You can get the stock firmware at sammobile.com. it's free but you have to register. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it and use that in Odin, PDA slot. This is a guide that is not for the s4 but the procedure is the same. It has screen shots in it that help. Don't use any files in it though other than odin. Good luck. http://forum.xda-developers.com/showthread.php?p=26056924
I haven't read the whole thread, so hopefully these haven't already been covered.
1) Make sure your recovery supports 4.4. Not all of them do. Stay the heck away from TWRP because it's done nothing but suck for Galaxy S4, while it was absolute king for the S3. The wrong recovery can still flash a ROM but that ROM may not work very well.
2) Ensure you do a COMPLETE wipe. As in wipe /system and /data. Make sure your internal SD card is formatted. 4.4 may not use some things & folders that 4.2 and 4.3 did, which might cause problems.
3) If you have an external SD, then make sure 4.4 is using the right path for it to access any important files you may have on it, like apps2sd & such.
Well since screwing things up with twrp I'm back to having a working phone again. I didn't have to use Odin but I still might just to go back to stock and then try kit kat. I went into cwm recovery and formatted the system then flashed liquidsmooth 2.37 which is what I was running. Everything works fine with that except when I use the rom manager widget to boot into recovery, it goes to the boot screen with booting recovery at the top but doesn't go further. I have to use the 3 button method to get into recovery. The other odd thing is that mms works for me now.
I tried flashing gummy 4.4 again since everything is fine in jb but I still have the same jittery twitchiness. One thing I noticed is that when I go into the performance settings in 4.4 the current cpu reading will jump from 300 mhz to 1200 to 400 to 1800 etc just at idle. Is that normal. My note 10.1 holds steady when it's just sitting there.
To answer your questions, I'm using cwm 6.0.4.4 which is kit kat approved and I formatted and wiped everything before flashing and it didn't change anything. I appreciate your help so far and look forward to more insight.
Sent from my SGH-I337 using xda app-developers app
I downloaded the update for my note 3 but now I am having second thoughts on installing. How can I stop this update from happening. I keep delaying it. Thanks
Sent from my unrooted note 3
What update are you referring to
Sent from One Bad Ass Note 3
The software update kitkat
Sent from my SM-N900V using xda app-developers app
simp dogg said:
The software update kitkat
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Verizon hasn't released kit-kat for the note 3 yet...
Sent from my SM-N900V using Tapatalk
What base do you currently have installed?
Sent from my SM-N900V using Tapatalk
The update was MJ7 to MJE. I wasn't sure what update it was when I downloaded it. I am sorry coming off like newb. What does MJE do as far as rooting? Does it make it harder to root or just an enhancement.
Sent from my SM-N900V using xda app-developers app
simp dogg said:
The update was MJ7 to MJE. I wasn't sure what update it was when I downloaded it. I am sorry coming off like newb. What does MJE do as far as rooting? Does it make it harder to root or just an enhancement.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
MJE is still rootable with kingo, then you can go ahead and install safestrap if you want.
Sent from my SM-N900V using Tapatalk
The download (a .zip file) gets dropped into the /cache folder, along with a recovery command file at
/cache/recovery/command
If you are rooted, you could just go in to the /cache folder and delete them. After that, you could look up the thread in the dev forum which details the .apk files in /system/apps which could be frozen (or "chmod 000"'ed) so that the nagging and download behavior stops. (This too requires root.)
This last bit is 100% reversible in case you later decide to apply the update, and/or you can keep the downloaded files (from /cache) in case you manually wanted to perform the update at a later time.
I don't know of a way to do this without rooting.
bftb0 said:
The download (a .zip file) gets dropped into the /cache folder, along with a recovery command file at
/cache/recovery/command
If you are rooted, you could just go in to the /cache folder and delete them. After that, you could look up the thread in the dev forum which details the .apk files in /system/apps which could be frozen (or "chmod 000"'ed) so that the nagging and download behavior stops. (This too requires root.)
This last bit is 100% reversible in case you later decide to apply the update, and/or you can keep the downloaded files (from /cache) in case you manually wanted to perform the update at a later time.
I don't know of a way to do this without rooting.
Click to expand...
Click to collapse
Well one way is to flash the pit file in Odin, or just flash a factory restore odin tar (full-wipe) but for the end user it might be easier to just root and do as you said.