I was rooted in 4.3, unrooted and successfully took the 4.4.2 OTA. While browsing the forum I saw other people state they'd successfully downgraded back to rooted 4.3. I attempted to do this first with Serge1223 's instructions on his rooted 4.4.2, and this failed. I then tried the no-wipe and COMPLETE-WIPE methods.
Now all I get from ODIN is the following:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Help? Please? I can boot into both Recovery and Download modes, but cannot get a fix to take.
caniswesley said:
I was rooted in 4.3, unrooted and successfully took the 4.4.2 OTA. While browsing the forum I saw other people state they'd successfully downgraded back to rooted 4.3. I attempted to do this first with Serge1223 's instructions on his rooted 4.4.2, and this failed. I then tried the no-wipe and COMPLETE-WIPE methods.
Now all I get from ODIN is the following:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Help? Please? I can boot into both Recovery and Download modes, but cannot get a fix to take.
Click to expand...
Click to collapse
Once you've updated to 4.4, you can't flash a 4.3 ROM because the kernel has a higher rev level than the kernel in MJ7/MK2.
You've got to use Surge's directions to flash just the base ROM, leaving the 4.4 kernel in place. Then you need to use bypasslkm to install the WiFi module to allow WiFi to work.
This is why I'm trying to discourage people from going to 4.4. You CAN NOT completely return to MK2 - you can get most of the way there, but can't get the MK2 kernel back, so you've got to use bypasslkm.
I'm still on MK2 and will stay there until a lot more of this is figured out. I'd recommend that you either stay with MK2, or assume that once you go to NC5 that you're not going to have to live with it.
k1mu said:
Once you've updated to 4.4, you can't flash a 4.3 ROM because the kernel has a higher rev level than the kernel in MJ7/MK2.
You've got to use Surge's directions to flash just the base ROM, leaving the 4.4 kernel in place. Then you need to use bypasslkm to install the WiFi module to allow WiFi to work.
This is why I'm trying to discourage people from going to 4.4. You CAN NOT completely return to MK2 - you can get most of the way there, but can't get the MK2 kernel back, so you've got to use bypasslkm.
I'm still on MK2 and will stay there until a lot more of this is figured out. I'd recommend that you either stay with MK2, or assume that once you go to NC5 that you're not going to have to live with it.
Click to expand...
Click to collapse
Thanks a lot for your reply @k1mu.
I have had a difficult time understanding Serge1223's instructions on how to flash only the base ROM. I don't quite get how to use bypasslkm. Is it possible you could explain (to someone still seeking a deeper understanding) more detailed instructions?
caniswesley said:
Thanks a lot for your reply @k1mu.
I have had a difficult time understanding Serge1223's instructions on how to flash only the base ROM. I don't quite get how to use bypasslkm. Is it possible you could explain (to someone still seeking a deeper understanding) more detailed instructions?
Click to expand...
Click to collapse
If I don't have Safestrap already installed, am I out of luck? Is my phone just... dead, even though it can boot into Download and Recovery modes?
caniswesley said:
Thanks a lot for your reply @k1mu.
I have had a difficult time understanding Serge1223's instructions on how to flash only the base ROM. I don't quite get how to use bypasslkm. Is it possible you could explain (to someone still seeking a deeper understanding) more detailed instructions?
Click to expand...
Click to collapse
When you update to 4.4.2, there's a new kernel. You can't downgrade that kernel since the bootloader won't allow it.
So, when you downgrade, you install most of the MK2 system, but leave the NC2 or NC5 kernel in place.
Since kernel modules are signed, you can't install a MK2 WiFi driver on the NCx version of the kernel.
What bypasslkm does is to flip the flag that tells the kernel to enforce proper module signatures. This allows the kernel to load the wifi module from the MK2 build without having it be rejected. That's why you need bypasslkm.
That's the explanation of what bypasslkm does. The directions for running it aren't all that hard - push to /data/local/tmp using adb, then run it at boot time. If you can't get that working, then you're probably going to have to stick with Kit Kat until the downgrade process gets better refined.
---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------
caniswesley said:
If I don't have Safestrap already installed, am I out of luck? Is my phone just... dead, even though it can boot into Download and Recovery modes?
Click to expand...
Click to collapse
You can always use ODIN to flash the Kit Kat ROM again once the NB5 kit becomes available.
k1mu said:
When you update to 4.4.2, there's a new kernel. You can't downgrade that kernel since the bootloader won't allow it.
So, when you downgrade, you install most of the MK2 system, but leave the NC2 or NC5 kernel in place.
Since kernel modules are signed, you can't install a MK2 WiFi driver on the NCx version of the kernel.
What bypasslkm does is to flip the flag that tells the kernel to enforce proper module signatures. This allows the kernel to load the wifi module from the MK2 build without having it be rejected. That's why you need bypasslkm.
That's the explanation of what bypasslkm does. The directions for running it aren't all that hard - push to /data/local/tmp using adb, then run it at boot time. If you can't get that working, then you're probably going to have to stick with Kit Kat until the downgrade process gets better refined.
Click to expand...
Click to collapse
I can't get it to boot into anything anymore other Download Mode that now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", but Kies doesn't recognize my phone.
I fear I may have wiped my partitions. How do I repartition or reinstall 4.4.2? I'd be happy to be back on 4.4.2 with no root and a functional phone....
caniswesley said:
I can't get it to boot into anything anymore other Download Mode that now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", but Kies doesn't recognize my phone.
I fear I may have wiped my partitions. How do I repartition or reinstall 4.4.2? I'd be happy to be back on 4.4.2 with no root and a functional phone....
Click to expand...
Click to collapse
In your "encountered an issue", try using volume up or volume down. One of those may get you past the error and allow a boot to succeed.
k1mu said:
In your "encountered an issue", try using volume up or volume down. One of those may get you past the error and allow a boot to succeed.
Click to expand...
Click to collapse
I can do that to get into regular Download Mode, but there is no more recovery mode (I'm assuming I somehow wiped my recovery, or because the partition (or partition list) is gone?
Do I need a PL, BL, AP, CP of 4.4.2?
caniswesley said:
I can do that to get into regular Download Mode, but there is no more recovery mode (I'm assuming I somehow wiped my recovery, or because the partition (or partition list) is gone?
Do I need a PL, BL, AP, CP of 4.4.2?
Click to expand...
Click to collapse
OKAY!!! I went a little crazy and through some crazy witchcraft, have resurrected my phone. Doubt that anyone will need this, but here's what I did to fix things after getting so far lost:
1. ODIN pushed Serge1223's downgrade to MK2 OP's using the PL from Serge1223's total WIPE MK2.... this got me to a boot screen. It froze there and wouldn't go past.
2. Then I used the leak of 4.2.2 as an OP in ODIN.... and my phone is alive again....
Thank you so much for your efforts in answering my questions @k1mu, and thank you so very much to @serge1223 for supplying such invaluable pieces.
caniswesley said:
OKAY!!! I went a little crazy and through some crazy witchcraft, have resurrected my phone. Doubt that anyone will need this, but here's what I did to fix things after getting so far lost:
1. ODIN pushed Serge1223's downgrade to MK2 OP's using the PL from Serge1223's total WIPE MK2.... this got me to a boot screen. It froze there and wouldn't go past.
2. Then I used the leak of 4.2.2 as an OP in ODIN.... and my phone is alive again....
Thank you so much for your efforts in answering my questions @k1mu, and thank you so very much to @serge1223 for supplying such invaluable pieces.
Click to expand...
Click to collapse
I am literally in the same situation you're in! I've been searching for a solution for two days straight. Is it possible to explain what you did to revive your phone a little more? thanks
Aharmlesspear said:
I am literally in the same situation you're in! I've been searching for a solution for two days straight. Is it possible to explain what you did to revive your phone a little more? thanks
Click to expand...
Click to collapse
Sure. Let's see. I realized that one of the things that I saw on ODIN when I tried to flash was the whole thing about having no recognizable partitions (if yours is saying the same thing, then this is what you'll probably want to do).
1. I grabbed the PIT file from @Surge1223's NO-WIPE and COMPLETE WIPE post, grabbed the MK2 downgrade zip file (also courtesy of @Surge1223), as well as the KitKatNC2 Leak and then went Flash-Crazy with ODIN in this sequence:
Boot your phone into Download Mode.
a. I545VRUEMK2_Downgrade.tar.md5 into the AP slot (or PDA if using Odin 3.07), and the PIT file taken from the NO-WIPE post in the PIT file slot. I can't remember if it failed, but I'm pretty sure it did. As Surge1223 said, though "the file should fail at Cache, thats ok".
Reboot your phone again into Download mode.
b. I545VRUEMK2_Downgrade_system.tar.md5 file with the same PIT file (this probably wasn't necessary, but at this point I was a bit paranoid and praying for it to work). This rebooted, but got stuck at the Verizon boot screen.
I then booted into Recovery and tried a Cache Wipe and Factory Reset. These didn't work, but I'm giving the complete sequence of events because I am also a bit superstitious at times about electronics :silly:
c. At this point I flashed the NC2 Leak in the AP slot. It flashed cleanly, and I was able to boot NC2. However, I decided I wanted to be able to root, so I repeated the steps a and b but without the PIT file <--- at this point just say NO to PIT.
I didn't need to do anything to recover sound. My sound was fine. However, the only downside is, my WIFI is now no longer accessible normally at boot. I have to run the little app I mentioned in another blog post... but the link is here
caniswesley said:
Sure. Let's see. I realized that one of the things that I saw on ODIN when I tried to flash was the whole thing about having no recognizable partitions (if yours is saying the same thing, then this is what you'll probably want to do).
1. I grabbed the PIT file from @Surge1223's NO-WIPE and COMPLETE WIPE post, grabbed the MK2 downgrade zip file (also courtesy of @Surge1223), as well as the KitKatNC2 Leak and then went Flash-Crazy with ODIN in this sequence:
Boot your phone into Download Mode.
a. I545VRUEMK2_Downgrade.tar.md5 into the AP slot (or PDA if using Odin 3.07), and the PIT file taken from the NO-WIPE post in the PIT file slot. I can't remember if it failed, but I'm pretty sure it did. As Surge1223 said, though "the file should fail at Cache, thats ok".
Reboot your phone again into Download mode.
b. I545VRUEMK2_Downgrade_system.tar.md5 file with the same PIT file (this probably wasn't necessary, but at this point I was a bit paranoid and praying for it to work). This rebooted, but got stuck at the Verizon boot screen.
I then booted into Recovery and tried a Cache Wipe and Factory Reset. These didn't work, but I'm giving the complete sequence of events because I am also a bit superstitious at times about electronics :silly:
c. At this point I flashed the NC2 Leak in the AP slot. It flashed cleanly, and I was able to boot NC2. However, I decided I wanted to be able to root, so I repeated the steps a and b but without the PIT file <--- at this point just say NO to PIT.
I didn't need to do anything to recover sound. My sound was fine. However, the only downside is, my WIFI is now no longer accessible normally at boot. I have to run the little app I mentioned in another blog post... but the link is here
Click to expand...
Click to collapse
I appreciate the explanation! Thanks! It's going to take a while to download everything but I will try my best to get this current paperweight back up and running again. I'll post back here with the results - hopefully good! haha
caniswesley said:
Sure. Let's see. I realized that one of the things that I saw on ODIN when I tried to flash was the whole thing about having no recognizable partitions (if yours is saying the same thing, then this is what you'll probably want to do).
1. I grabbed the PIT file from @Surge1223's NO-WIPE and COMPLETE WIPE post, grabbed the MK2 downgrade zip file (also courtesy of @Surge1223), as well as the KitKatNC2 Leak and then went Flash-Crazy with ODIN in this sequence:
Boot your phone into Download Mode.
a. I545VRUEMK2_Downgrade.tar.md5 into the AP slot (or PDA if using Odin 3.07), and the PIT file taken from the NO-WIPE post in the PIT file slot. I can't remember if it failed, but I'm pretty sure it did. As Surge1223 said, though "the file should fail at Cache, thats ok".
Reboot your phone again into Download mode.
b. I545VRUEMK2_Downgrade_system.tar.md5 file with the same PIT file (this probably wasn't necessary, but at this point I was a bit paranoid and praying for it to work). This rebooted, but got stuck at the Verizon boot screen.
I then booted into Recovery and tried a Cache Wipe and Factory Reset. These didn't work, but I'm giving the complete sequence of events because I am also a bit superstitious at times about electronics :silly:
c. At this point I flashed the NC2 Leak in the AP slot. It flashed cleanly, and I was able to boot NC2. However, I decided I wanted to be able to root, so I repeated the steps a and b but without the PIT file <--- at this point just say NO to PIT.
I didn't need to do anything to recover sound. My sound was fine. However, the only downside is, my WIFI is now no longer accessible normally at boot. I have to run the little app I mentioned in another blog post... but the link is here
Click to expand...
Click to collapse
Everything happened just like what you said and my phone is officially working! The only problem is that I wanted to root as well and followed step a and b without the PIT file and it wouldn't get past the samsung screen - would constantly reboot. Any idea how to fix that?
Aharmlesspear said:
Everything happened just like what you said and my phone is officially working! The only problem is that I wanted to root as well and followed step a and b without the PIT file and it wouldn't get past the samsung screen - would constantly reboot. Any idea how to fix that?
Click to expand...
Click to collapse
Have you tried booting into Recovery [If you've never booted into recovery --> (from Power Off, hold down Power + Home + Volume Up until you see the boot screen). Should see in the upper left hand corner blue text reading: "Booting into recovery". The little android dude will appear, and then fall on his side with an explanation pt. This is fine, don't panic. Just let it bring you to the menu. Use volume up and volume down to navigate and power button to select.]
In Recovery do a Factory Reset and Cache Wipe. This should fix the loop. Let me know if not....
telsecr must
caniswesley said:
Have you tried booting into Recovery [If you've never booted into recovery --> (from Power Off, hold down Power + Home + Volume Up until you see the boot screen). Should see in the upper left hand corner blue text reading: "Booting into recovery". The little android dude will appear, and then fall on his side with an explanation pt. This is fine, don't panic. Just let it bring you to the menu. Use volume up and volume down to navigate and power button to select.]
In Recovery do a Factory Reset and Cache Wipe. This should fix the loop. Let me know if not....
Click to expand...
Click to collapse
Yeah I did factory reset and cache wipe when I first did it because it kept looping and I didn't know what else to do. It didn't do anything. I flashed the NC2 file without PIT and that got me back to it booting and loading up. What allows you to root when you did those two steps without the PIT file? Does it make it so it goes back to 4.3 or something?
Aharmlesspear said:
Yeah I did factory reset and cache wipe when I first did it because it kept looping and I didn't know what else to do. It didn't do anything. I flashed the NC2 file without PIT and that got me back to it booting and loading up. What allows you to root when you did those two steps without the PIT file? Does it make it so it goes back to 4.3 or something?
Click to expand...
Click to collapse
The whole idea of flashing with A and B are to put you on 4.3 at the end. Downgrading you from NC2 to MK2. The order of things from this flash were going MK2 (which got stuck like yours did) --> NC2 (which for me, cleared up the loop) --> MK2 (which after a factory reset and wiping the cache, booted back up fine.)
I honestly I am not the expert on these things, I just used the PIT file because at the time my phone was registering as having no established Partitions. so I used the only PIT file I could easily find, crossed my fingers, and got lucky. I stopped using PIT as soon as I was able to boot even back into recovery with a stuck normal Verizon boot screen. I didn't saferoot until I had a functional MK2 (non-root) option. I honestly wanted root so that I could re-establish WIFI. Without root, I don't know of a method to easily re-obtain wifi.
Aharmlesspear said:
Yeah I did factory reset and cache wipe when I first did it because it kept looping and I didn't know what else to do. It didn't do anything. I flashed the NC2 file without PIT and that got me back to it booting and loading up. What allows you to root when you did those two steps without the PIT file? Does it make it so it goes back to 4.3 or something?
Click to expand...
Click to collapse
Does it literally go into a boot loop with the Verizon boot screen? Or is it sitting there for a while? I sat there patiently the first time it booted, and it took a while (setup stuff I think) but booted eventually.
caniswesley said:
Does it literally go into a boot loop with the Verizon boot screen? Or is it sitting there for a while? I sat there patiently the first time it booted, and it took a while (setup stuff I think) but booted eventually.
Click to expand...
Click to collapse
It just kept going to the samsung boot logo and turning off and looping. I'll try again right now - just do the factory reset and cache wipe after both files have been flashed right?
Aharmlesspear said:
It just kept going to the samsung boot logo and turning off and looping. I'll try again right now - just do the factory reset and cache wipe after both files have been flashed right?
Click to expand...
Click to collapse
Yes. I'm assuming you're rebooting after the first flash fails, and then flashing the second file....
caniswesley said:
Yes. I'm assuming you're rebooting after the first flash fails, and then flashing the second file....
Click to expand...
Click to collapse
I reflashed and it got to the verizon boot logo. It's been there for 5-10 min and I think it might be stuck there even though the animation is still continuing (light shining over text). Is this where you format and wipe cache?
Related
A question. After attempting to flash a theme... I got a bootloop. So I flashed the provided undo file. Now my phone will not boot past the Galaxy S 2 screen with the warning triangle. Any help? I'm kinda panicking...
dont you make any cwm backup first ?
i believe u can still enter recovery mode ( power + home + volume up ) ,
and do full wipe, and flash any other rom .zip .
p/s: i believe you already have root, and install any rom before
no i didnt... i was rooted. i have both cwm and download mode... but phone wont boot. I live in canada so samsung has not uploaded our stock rom files...
If it is not backup-ed, then you will have an issue.
Now, try wipe phone via CWM, clear cache and clear dalvik.
Finger's crossed it work.
If not, last choice will be install any Custom ROM and it will wipe (hopefully) all the not 'right' files.
nope.... nothing... guess i will take it in for warranty... thank you anyways my friend
I got that as well in the past, although mine was caused by incompletely flashing Cyanogen. Had a major freakout before I figured it out.
The only way I found to fix it is to flash stock firmware using Odin (and you will not be able to restore stock Canadian as it hasnt been released for us yet). I went with the xxKG2 (polish firmware I think).
There may be other ways to fix the problem but this will 99% sure take care of it. Your warranty will of course be void untill the Canadian firmware is released.
Cheers!
Sent from my GT-I9100 using XDA App
An additional note: from what I understand you're also getting the insecure kernel triangle. If the counter in download mode also shows that you flashed non-official firmware/kernel, your warranty could already be void. In that case Samsung may now honour their Limited Warranty Agreement.
Sent from my GT-I9100 using XDA App
right but when i purchased the phone i also purchased an extended warranty that covers software problems
Tried following the directions in this stickied thread?
http://forum.xda-developers.com/showthread.php?t=1108499
Ahh, well in that case, lucky you =D
Sent from my GT-I9100 using XDA App
ohyeahar said:
Tried following the directions in this stickied thread?
http://forum.xda-developers.com/showthread.php?t=1108499
Click to expand...
Click to collapse
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
on a side note, in recovery mode, it appears that /emmc encountered an error in mounting while all others mounted fine... not sure if this has any relevence, but there you go
Braidonh said:
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
on a side note, in recovery mode, it appears that /emmc encountered an error in mounting while all others mounted fine... not sure if this has any relevence, but there you go
Click to expand...
Click to collapse
/emmc is the external sd card, you probably don't have one in the slot so it wasn't able to mount it.
The Yellow Triangle means you had something changed in the kernel partition, so the custom binary counter went up by 1.
As for stock rom, you will have to wait for Bell Canada to release one.
If you are not looking for stock, I'd recommend CyanogenMOD7, however it is still on nightly development, which means it has it fair share of issues.
I prefer CM7 and its problem over the stock which also has a fair share of issues.
if you can use downloading mode , you can flash back stock rom. believe me it will work.
you can study how to flash back stock rom using odin here --> http://forum.xda-developers.com/showthread.php?t=1075278
Braidonh said:
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
Click to expand...
Click to collapse
Are you sure you've "repeatedly" followed those instructions? You claim that flashing a stock ROM isn't possible. But those instructions require you to flash a stock ROM.
You don't have to flash the ROM that is specific to your region/carrier. Just flash ANY stock ROM to get your phone working again. Then you can flash back to whatever ROM you were on previously.
But if you wanted to get back onto whatever ROM your phone initially came with, you're out of luck.
hi all, my phone simply would not boot, it shows a down load error screen whenever i try to power up the phone.
i am not able to get into the reset screen using "up vol + home + power", but i am able to get to the download screen using "down vol + home + power"
I have tried flashing a stock rom using odin, but it just got stuck at
<OSM> CODE_I9100XXKG6_CL425236_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG6_REV_02_CL1044543.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKG6.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
thereafter the screen went crazy flashing and now i am not able to power up the phone.
i a really at a fix as to what i can do. hope i am able to get some advice and thanks in advance~!
<ID:0/007> Set PIT file..
Wow... you repartitioned the phone. Something that was repeatedly told not to do. Now you have a screwed up partition.
Now you will have to find a official stock rom for your phone, and the correct pit file, then repartition it and hope it works.
The first rule of Odin (for 99% of us) : you never flash a PIT file.
I feel like that should be stickied front page. It would save a lot of people a lot of trouble and possibly around 700$.
Sent from my GT-I9100 using XDA App
I need some help I have the same problem but Odin always fails when I try to flash villainrom 1.1 can you please help me? And any other firmware I flash doesnt work
edgeboy47 said:
I need some help I have the same problem but Odin always fails when I try to flash villainrom 1.1 can you please help me? And any other firmware I flash doesnt work
Click to expand...
Click to collapse
Same problem? You mean you repartitioned the phone as well?
Double check the md5 checksum to see if it is the same as posted if it is posted at all. If not, double check the file size to see if they are the same. Most browsers say the file downloaded is complete when it was disconnected somewhere, and the file is incomplete.
I find it hard to take devs seriously, when they don't post filesize or don't post md5 checksum. Either that, or those two information is really hard to find, not on the download page.
http://www.villainrom.co.uk/forum/content.php/319
Ok so what i mean is cant start the phone I just get the logo with a yellow triangle at the bottom of the page so I tried to flash kernels but that doesnt help, but whenever I try to flash bigger files with Odin (I think they are firmwares, i downloaded them from Intratech's post) or Villainrom 1.1 it always fails when it says boot.bin in the message window for the big files and factoryfs.img for villain rom
Hey all. There's a lot knowledgeable folks around here, so I thought I'd see if I can get some help on my problem.
I've got a Galaxy Tab 10.1 Wifi (GT-P7510, non-branded, UEKME), that I rooted about two months ago, using the instructions found on the Android Forums (can't post a link, but ti's the basic easy way to root, using Odin3). Not a superuser, but wanted to be able to back up everything. Seemed easy enough and the rooting went fine.
Haven't done anything else to it, aside from installing a few run of the mill apps. It did auto-update a couple of times.
Was working fine, now it just got stuck on this screen with a message:
Code:
ODIN3 Download Mode
(Protocol v2.1)
Reason: No Kernal
Secure Mode: Secure
Check Signature: Check
Custom Binary Download: No (0 counts)
Custom Binary: Samsung Official
Waitting USB Cable...
Downloading...
Do not turn off target!!
Apparently, it went to this screen while I was away. I didn't see it until I picked it up and there it was. It comes to this screen after the Samsung title screen (not the animation) and a VERY quick screen with some red writing (goes by too fast to see what it says).
I tried to follow the original instructions again. Put the tab in download mode (power + volume down), open Odin3, select the md5, and hit start. Get a FAIL with this message:
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tab updates with this:
Code:
WritePArtition: Error to NvStorMgrFileWrite![err:0x30000]
DownloadPartition_odin: Error to WritePartition![err:0x30000]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0x30000]
That's as far as I've gotten. I noticed the Re-Partition option is not checked in Odin3, and the errors on the tab have to do with partitions... but didn't want to do that if I could eff it up even more.
I'm also wondering if one of the auto-updates didn't muck up the works. Maybe messed with my bootloader? Again, didn't want to go doing dangerous things without some reassurance. Also, I can't get into recovery mode; it just kinda flashes when I hit the button and stays on the option screen for download/recovery.
Any direction on how to proceed?
Any advice would be so great. It's been like this for about a week and I can't find any help. Thanks everyone.
TL;DR: Stuck in Download Mode, get errors on re-root.
This helped me and I've seen it help many others too in similar situations. Since you're stuck in download mode already it might need to be adjusted and followed from somewhere other than the beginning.
Goto http://www.teamovercome.net/p7500/?page_id=5
Towards the bottom of the guide There is a section called Restocking yer system.
Follow that on down.
Make sure you use the files for you device (7500 or 7510).
Make sure you triple check that you follow everything as suggested. The most common one I see missed is the last step of doing a Wipe data/factory reset.
Let us know how it goes, as this keeps us trying to help when we know we're successful.
Sent from my GT-P7510 using XDA Premium HD app
You have an incomplete bootsector the bootloader is broken but ofcourse your recovery is safe. Just flash a stock firmware on top of it, or flash CWM. You don't have to worry about the options being checked as Odin 1.83 onwards fixes this issue.
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Is there any other way to flash my firmware and/or repair my bootsector/bootloader?
Thanks for your help.
stusic said:
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Click to expand...
Click to collapse
If you followed what I posted, and triple checked every step and check box in the guide was exactly what you did, then I'm lost for other suggestions. Misledz is on a different time than here, so you can either try my process again, if that's what you used, making sure you do evrything as said in the restocking yer system guide on down or wait for more help.
Yeah, I was hoping because it was a really well written guide with links to the correct files right there that I'd have some luck. The directions are pretty straightforward, so I don't think I missed anything, but I can certainly try again.
Thanks, I'll update in a bit.
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
stusic said:
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
Click to expand...
Click to collapse
Sorry that sucks.
Hope Misledz or someone comes along for you.
Best of luck.
Edit: Looking at the Odin repartition error makes me think it may be a full hardware failure issue. But there is still hope with the right files or method for it to be fixed.
I can't find it, but there was another thread here with the same "Reason: No Kernal" error and I think it turned out to be a hardware failure.
Sorry well yeah I've been on offset timezone's and I tend to check this section regularly as I hope to learn more about the tablet In hopes I can get some development done on it.
In the sense I'll assure you that you can't really brick the tablet as they are somewhat hard to brick via software, unless you install a firmware that isn't compatible (Like a 7500 on a 7510) or like wipe the bootloader. Put it this way anything done in download mode is safe.
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Misledz said:
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
Click to expand...
Click to collapse
That's reassuring.
Misledz said:
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Click to expand...
Click to collapse
I notice the second file is in a p7500 directory. I'm guessing this is an all-encompassing directory with p7500 and 7510 files?
EDIT: I see that the file is for all versions (75xx). Thanks.
I'm at work now, but I'll try it when I get home and give an update.
Thanks for taking the time to help me out.
*fingers crossed*
Dammit. No luck.
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
brieuwers said:
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
If you check out his screen shot posted above it shows he used a pit file at least in one attempt
He's still having issues so your help with this would be and is highly needed and appreciated.
Sent from my GT-P7510 using XDA Premium HD app
I've used the pit file and tar file from the guide that Benzoman directed me to. I also tried using the updated CWMs that were suggested (although a pit file wasn't included).
I had installed the windows drivers a while back, but just installed the Kies. Interestingly, after that, I tried flashing again and, although it still failed, it took a lot longer (as opposed to almost instantly). Almost thought I had it for a second...
Am I right in thinking that I can use the pit file from the guide and the tar file from CWM together?
Slightly off-topic; what's the purpose of flashing a bootloader? That's one thing I haven't tried yet.
Thank you for your continued help. I would have lost all hope by now if it weren't for you and this forum.
So is it all good? I don't tend to like leaving people who need help Especially when it's also educational for me.
Flashing a bootloader wouldn't be advisable cause it may really brick the tab.
You don't really need to pit file as it is used for repartioning, flashing just the PDA is good enough
Misledz said:
So is it all good?
Click to expand...
Click to collapse
No, it's still stuck. It seems like any pit file I try doesn't work, which was why I was asking about the bootloaders (I know it's dangerous, but for all intents and purposes, it's already bricked).
I don't know what else to do; I was hoping the updated CWM would help, but it runs into the same problem the other pda files have. I'd be more than happy to try any other suggestions you may have.
Thanks again.
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
stusic said:
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
Click to expand...
Click to collapse
Sorry over my head, but hopefully Someone will look at the error and know what's going on.
Sent from my GT-P7510 using XDA Premium HD app
After installing TWRP restore via Goomanager (on the play store) I pressed reboot to restore. the phone rebooted to to download mode. I Pulled the battery for 40+ seconds, and pressed the power button, but whatever I do, the phone keeps booting into download mode.
Is it possible to factory reset my phone via Odin?
Phone:
Samsung galaxy S4 sch-I545
Thanks,
Bill The android
Yeah you can do that but dont try installing a recovery again. Im betting youre on me7, and currently its only rootable. No recovery.
When you said factory reset I thought you meant restore. But no, you cant reset via odin. You can turn your phone off and then use the key combo to boot into odin. Itll ask to confirm or deny booting and if you deny your phone will boot normally. Everytime you restart yoll have to do this so eventually youll have to restore through odin.
Sent from my SCH-I545 using Tapatalk 2
Did you try booting into recovery? If you get into recovery try rebooting back to system. Hopefully the phone will boot up normally. You could also do a factory reset if you do get into recovery.
I am having a similar issue -- I am stuck in download mode after attempting TWRP installation. Odin is not responding to my phone once plugged in (only says "connecting"). I am unable to enter recovery mode and am not sure what I should try next. Any suggestions?
This is a new S4 on verizon -- I545/ME7
hexitnow said:
Yeah you can do that but dont try installing a recovery again. Im betting youre on me7, and currently its only rootable. No recovery.
When you said factory reset I thought you meant restore. But no, you cant reset via odin. You can turn your phone off and then use the key combo to boot into odin. Itll ask to confirm or deny booting and if you deny your phone will boot normally. Everytime you restart yoll have to do this so eventually youll have to restore through odin.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You cant enter recovery because you overwrote the stock one and youre unable to flash/use a custom one because me7 blocked it. There might be a stock recovery posted on the forums but i havent seen one yet. I would try a different usb port, if youre using a pc a few people have had trouble with the front ports. If youre on win 7 try granting admin rights. Try a different pc. Try a different cable are some solutions.
Sent from my SCH-I545 using Tapatalk 2
I see -- I meant Kies was not connecting to the phone in my previous post (not odin). If I am unable to get it to respond, is the best way to restore to a stock phone using Odin?
Wahoogoose said:
I see -- I meant Kies was not connecting to the phone in my previous post (not odin). If I am unable to get it to respond, is the best way to restore to a stock phone using Odin?
Click to expand...
Click to collapse
I have never used kies so cant really say anything about that. But ya odin is best way to restore a phone to stock in my opinion. Like I said There might be an me7 stock recovery posted and that should fix your problem.
Sent from my SCH-I545 using Tapatalk 2
I am having trouble finding the appropriate restore .tar for my phone -- I have been looking at androidfilehost with minimal luck, but I see where other people claim to have found it.
Theyre in the dev section.
Sent from my SCH-I545 using Tapatalk 2
fixed?
has anyone been able to get out the download/ odin mode booting..... i still cant use my phone or enter recovery, if anyone solved this, any help would be appreciated. I am using the galaxy s4 at&t version i337. Please help me i just got the phone 2 days ago lol
Development section.. me7 stock .. Take out Battery start Odon hold volume down plug in usb.. Make sure drivers are installed. . After it says comm. In Pda browse to stock me7.. reinstall battery then start. . You may need a pit file not sure. .when done Reroot.. There is no cwm for me7 yet so your done after rooting don't try cwm or twerp
Can someone point me to the stock ME7?
SO_dank said:
Development section.. me7 stock .. Take out Battery start Odon hold volume down plug in usb.. Make sure drivers are installed. . After it says comm. In Pda browse to stock me7.. reinstall battery then start. . You may need a pit file not sure. .when done Reroot.. There is no cwm for me7 yet so your done after rooting don't try cwm or twerp
Click to expand...
Click to collapse
This is undoubtedly my solution as I did not do enough research before I tried to flash TWRP while running ME7. I'm a complete noob on this forum and when you say dev section, me7 stock; well, I still have no clue how to find it. I would be extremely grateful if someone could take their time and post a link. Thank you guys. Just switched back from iOS and look forward to becoming a part of the android community!
gs4 root
chris17922 said:
has anyone been able to get out the download/ odin mode booting..... i still cant use my phone or enter recovery, if anyone solved this, any help would be appreciated. I am using the galaxy s4 at&t version i337. Please help me i just got the phone 2 days ago lol
Click to expand...
Click to collapse
hold the power button and the down volume key and it should ask you if you want to install a custom os or not and then you just hit cancel and it will boot regularly
WOW
mavratin15 said:
hold the power button and the down volume key and it should ask you if you want to install a custom os or not and then you just hit cancel and it will boot regularly
Click to expand...
Click to collapse
saved my ass.....
how long are you holding down to get that message? mine is just rebooting without asking.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
bettadaze said:
how long are you holding down to get that message? mine is just rebooting without asking.
Click to expand...
Click to collapse
phew..finally got it...hopefully last of my silly s4 mishaps.
bettadaze said:
how long are you holding down to get that message? mine is just rebooting without asking.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
phew..finally got it...hopefully last of my silly s4 mishaps.
Click to expand...
Click to collapse
I can get past download mode when I click volume down I get the yellow triangle. When I try to odin back to stock I get error message Need help.
chris17922 said:
has anyone been able to get out the download/ odin mode booting..... i still cant use my phone or enter recovery, if anyone solved this, any help would be appreciated. I am using the galaxy s4 at&t version i337. Please help me i just got the phone 2 days ago lol
Click to expand...
Click to collapse
I did this exact thing, and this guide got it fixed.
http://forum.xda-developers.com/showthread.php?t=2301259
Kodaxx said:
I did this exact thing, and this guide got it fixed.
http://forum.xda-developers.com/showthread.php?t=2301259
Click to expand...
Click to collapse
If you upgraded to MJ7 that link will not help you. You need to Odin a MJ7 stock. I had to do it last night problem is you will lose root. You cant flash back to anything yet if you were on MJ7.
Here is link to zip I had to use. Post #12
http://forum.xda-developers.com/showthread.php?p=47041854#post47041854
get out of downloading loop
I have read all the different ways to get out of a downloading loop with ME7 and none of them worked for me. however, i did find another way that did work.
if your phone boots to downloading every time you boot. I came up with this method. I can only attest that it worked for me.
1. At the downloading screen, plug your phone into your computer
2. Run Odin (I used Odin3 v3.09)
3. Uncheck auto reboot and F. Reset Time
4. Select PIT and load a .pit fil ( I used a file called "SCH-I545.pit" that I downloaded from these forums)
5. Click Start
It will fail and your Message box will look like this
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
6. Now uplug your phone from the computer and reboot.
The only explanation I can come up with is that the partition file info gets corrupted or lost and doing this either rewrites the partition info file or tells the system where to look for it. I could be wrong but it is the only thing that works for me.
good luck!
THANX!!
FIXED!!! thank you, i registered here just to say thanks for posting this. Ive been looking for hrs. and this was all I had to do the whole time. great solution for being stuck on the downloading screen with errors....thank you!!! I thought I ruined my new phone! =D lol:good:
[Q] [SOLVED] My Samsung galaxy s2 just got bricked, & now its between life and death
Samsung Galaxy S2 LTE
Model name: SHV-E110S
No Custom Binary Download
Current binary is Samsung Official
Jelly bean 4.1.2 (90% sure)
Froze while using it and upon reboot froze at boot screen where the logo of "T" keeps rotating.
Firstly, being myself a complete Noob when it come to stuffs like Custom Roms, firmware, kernel etc got the phone in worse condition.
Upon reading few forums here, tried using Odion3 v 1.85 and tried fixing it following some ideas from these forums:
http://forum.xda-developers.com/showthread.php?t=1457458
http://forum.xda-developers.com/showthread.php?t=2016984
Reckoning that the mobile must have been soft bricked, tried using recovery package which failed as shown below:
http://oi39.tinypic.com/678nls.jpg
Then committed second mistake by using "PIT" file selecting Re Partition. After that on turning on the mobile, instead of BIOS, came "Odion Mode" where additional logo of "Update appears" The failed pic using PIT is shown below:
http://oi40.tinypic.com/14ihn5h.jpg
So, is there any hope for the phone or it's gone? It doesnt gets detected on kies but is detected on odion. I closed the kies in processes in taskmngr too.
So, please tell me what should i download now?
So, please help me everyone. I need all of your guidance.
I wont use that software without any knowledge.
Please tell me the steps to be taken by me now. I badly need that phone. There's no warranty now, so i dont want to go to customer care center.
And is there any way in which none of the files get deleted inside it. It's internal system memory is 2 GB. And USB memory is 12 gb. No SD card inside it.
Thank you!
best of luck
go here
http://forum.xda-developers.com/showpost.php?p=31319717&postcount=495
How?
gohel.vishal said:
go here
http://forum.xda-developers.com/showpost.php?p=31319717&postcount=495
Click to expand...
Click to collapse
I'm so sorry man, but i didnt understand anything from that forum. I mean the forum hasnt provided kernel for the SHV-E110S. I'm a noob. I'm so sorry
sulav_rock said:
Samsung Galaxy S2 LTE
Model name: SHV-E110S
No Custom Binary Download
Current binary is Samsung Official
Jelly bean 4.1.2 (90% sure)
Froze while using it and upon reboot froze at boot screen where the logo of "T" keeps rotating.
Firstly, being myself a complete Noob when it come to stuffs like Custom Roms, firmware, kernel etc got the phone in worse condition.
Upon reading few forums here, tried using Odion3 v 1.85 and tried fixing it following some ideas from these forums:
http://forum.xda-developers.com/showthread.php?t=1457458
http://forum.xda-developers.com/showthread.php?t=2016984
Reckoning that the mobile must have been soft bricked, tried using recovery package which failed as shown below:
http://oi39.tinypic.com/678nls.jpg
Then committed second mistake by using "PIT" file selecting Re Partition. After that on turning on the mobile, instead of BIOS, came "Odion Mode" where additional logo of "Update appears" The failed pic using PIT is shown below:
http://oi40.tinypic.com/14ihn5h.jpg
So, is there any hope for the phone or it's gone? It doesnt gets detected on kies but is detected on odion. I closed the kies in processes in taskmngr too.
So, please tell me what should i download now?
So, please help me everyone. I need all of your guidance.
I wont use that software without any knowledge.
Please tell me the steps to be taken by me now. I badly need that phone. There's no warranty now, so i dont want to go to customer care center.
And is there any way in which none of the files get deleted inside it. It's internal system memory is 2 GB. And USB memory is 12 gb. No SD card inside it.
Thank you!
Click to expand...
Click to collapse
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
if possible to enter in download mode then noworry you have chance to get back your device,
but if not then give try on some USB JIG products... (buy from web)
this product let you open download mode by just connecting usb part to device.
once you get enter in download mode you'll safely flash stock rom again.
but this time I suggest you to use ODIN V3.07 (latest version much safer much easier to use)
No problem with download mode
j.posarekar70 said:
if possible to enter in download mode then noworry you have chance to get back your device,
but if not then give try on some USB JIG products... (buy from web)
this product let you open download mode by just connecting usb part to device.
once you get enter in download mode you'll safely flash stock rom again.
but this time I suggest you to use
When i turn on my mobile, it directly opens Download mode. And it wont even close when i press power button. I've to force shut down by taking out the battery. There's no boot screen showing Samsung logo.
Actually i used odin3 v3.09 on first place. I knew nothing about it. so following a forum on recovering soft brick i switched to old version.
Click to expand...
Click to collapse
sulav_rock said:
j.posarekar70 said:
if possible to enter in download mode then noworry you have chance to get back your device,
but if not then give try on some USB JIG products... (buy from web)
this product let you open download mode by just connecting usb part to device.
once you get enter in download mode you'll safely flash stock rom again.
but this time I suggest you to use
When i turn on my mobile, it directly opens Download mode. And it wont even close when i press power button. I've to force shut down by taking out the battery. There's no boot screen showing Samsung logo.
Actually i used odin3 v3.09 on first place. I knew nothing about it. so following a forum on recovering soft brick i switched to old version.
Click to expand...
Click to collapse
You still have Download mode on the Phone, so your bootloader is still ok. Flash a stock rom image with Odin and you should be ok...post your results.
Click to expand...
Click to collapse
Questions
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
first of all, thank u so much for responding. Ok i'll try downloading the pre rooted ROM.
I'll post the results on the thread in the forum after it completes.
Since u're really talented in these stuffs, i wanted to ask u few questions.
1) Will installing Pre Rooted ROM root my device or not? Or do i have to root separately?
2) Will everything get wiped out? I'm sure wallpapers, messages, and settings configurations will be deleted. What about songs, photos? Will the USB storage get wiped out too? btw there's no sd card.
3) Can i recover anything? If yes. how?
sulav_rock said:
first of all, thank u so much for responding. Ok i'll try downloading the pre rooted ROM.
I'll post the results on the thread in the forum after it completes.
Since u're really talented in these stuffs, i wanted to ask u few questions.
1) Will installing Pre Rooted ROM root my device or not? Or do i have to root separately?
2) Will everything get wiped out? I'm sure wallpapers, messages, and settings configurations will be deleted. What about songs, photos? Will the USB storage get wiped out too? btw there's no sd card.
3) Can i recover anything? If yes. how?
Click to expand...
Click to collapse
1) Pre-rooted means just that, it is already rooted for your convenience.
2) Wiping data/cache can be different on different phones. It always wipe the internal data partition (place where app specific data and such are stored) and sometimes the internal user data storage (place where your pictures and other user files are stored). Whether the user data storage is cleared, I can't say for certain, varies between roms and phone models. (external sd card is never cleared, so that's why you should get yourself one and store your data there or in the 'cloud')
3) Depending on what happens in 2), yes or no. If it's wiped, it's gone, if not, then you're lucky I suppose.
When you manage to resurrect the phone, try to follow these rules...
- sync photos with Google+
- keep other data, songs, documents, etc... on the external sd card as much as possible
- sync contact, agenda/calendar, notes, and other personal management data synced with a cloud service (Google+, Exchange, etc...)
- make regular backups with for example Titanium Backup, Super Backup, etc...
- a Samsung account and Google account will help to automatically backup some settings, call logs, etc... (If you let/allow them)
so you have download mode,
download this pre-rooted stock rom here
then this pit file for e110s here
once the files are downloaded,
head to odin then choose pit for the pit file you downloaded
same goes for the pda file
then it should flash without any errors. after that if your phone is stuck in boot animation.
turn off the phone then Reboot to recovery (volume up+volume down+power)
use the volume rockr keys to navigate and power button to select an item.
choose wipe data/factory reset and cache.
flash the rom again without the pit file, only PDA to make sure everything is fine.
it should fix your soft bricked e110s.
Thank you so much.
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
Bro,
Thank you so much for all the trouble you took to help me. Finally, i was successful in fixing it.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E110SKSJMH2_SLIM_PR20130904.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> userdata.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> recovery.img
<ID:0/004> param.lfs
<ID:0/004> mdm.bin
<ID:0/004> cache.img.ext4
<ID:0/004> boot.img
<ID:0/004> amss.bin
<ID:0/004> aboot.mbn
<ID:0/004> ums.rfs
<ID:0/004> tomb.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
really want u to thank from my heart. Not only that, i've actually learned so many things in this 3 days regarding ROMS, multiple zip file etc.
So thanks again
best one??
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
Hi,
I'm sure you've flashed at least once samsung gs2 shv e1102 with custom ROM. Did it work? Actually currently, if it's safe i want to switch to the latest version that's available for my device. The stock is JB 4.1.2 So, is it bad if i use the latest verson which will trigger the status of Rom i guess. If it's actually good then i want to try it. Coz the phone has just been recover. There's no need to backup. And i've always been bothered by the sms limit of 80 letters. More than that, it becomes mms and will be sending failure. So, do u have any suggestions. And if i have to upgrade, which one will be good for me? And is the procedure same? By using Odin software?
sulav_rock said:
Hi,
I'm sure you've flashed at least once samsung gs2 shv e1102 with custom ROM. Did it work? Actually currently, if it's safe i want to switch to the latest version that's available for my device. The stock is JB 4.1.2 So, is it bad if i use the latest verson which will trigger the status of Rom i guess. If it's actually good then i want to try it. Coz the phone has just been recover. There's no need to backup. And i've always been bothered by the sms limit of 80 letters. More than that, it becomes mms and will be sending failure. So, do u have any suggestions. And if i have to upgrade, which one will be good for me? And is the procedure same? By using Odin software?
Click to expand...
Click to collapse
Go to this post and download the GT-I9210 Based MF1 Stock Root Ready rom. Same method as stock images with Odin. This is a regionalized version for the European S2 LTE variant. It works well on the E110S and will take care of that 80 character sms limit.
If you have warranty on the Phone, then you might be worried about triggering the custom binary counter, otherwise, don't worry.
Root/unroot
dc_power! said:
Go to this post and download the GT-I9210 Based MF1 Stock Root Ready rom. Same method as stock images with Odin. This is a regionalized version for the European S2 LTE variant. It works well on the E110S and will take care of that 80 character sms limit.
If you have warranty on the Phone, then you might be worried about triggering the custom binary counter, otherwise, don't worry.
Click to expand...
Click to collapse
Ok i'll download it. btw i dont have warranty coz the phone was bought in south korea itself. I didnt even find a flip cover case for that phone is my country. now the question Is there any latest version of JB where the sms limit has been removed. I mean any custom Rom having version greater than 4.1.2. If yes, which one should i download?
and the procedure is same isnt it? I've go in download mode(odin mode) and flash ROM using Odion on the PDA section isnt it?
sulav_rock said:
Ok i'll download it. btw i dont have warranty coz the phone was bought in south korea itself. I didnt even find a flip cover case for that phone is my country. now the question Is there any latest version of JB where the sms limit has been removed. I mean any custom Rom having version greater than 4.1.2. If yes, which one should i download?
and the procedure is same isnt it? I've go in download mode(odin mode) and flash ROM using Odion on the PDA section isnt it?
Click to expand...
Click to collapse
MF1 is 4.1.2. It is a stock based rom, but is identified as custom because some work had to be done with the boot kernel.
If you want anything later than 4.1.2, google cyanogenmod based roms for the e110s/celox devices. There's enough out there, but you have to put some effort into researching and finding it.
4.2.2
dc_power! said:
MF1 is 4.1.2. It is a stock based rom, but is identified as custom because some work had to be done with the boot kernel.
If you want anything later than 4.1.2, google cyanogenmod based roms for the e110s/celox devices. There's enough out there, but you have to put some effort into researching and finding it.
Click to expand...
Click to collapse
The link u gave me before also had Jelly bean 4.2.2. So if i download and flash that using Odin, will it also remove the sms limit. I actually want to switch from 4.1.2 to 4.2.2. The procedure is same isnt it? Flashing it on Odin. Or do i have to factory reset before flashing?
When i flashed official roms with Odin i never used PIT files. Just out the rom on PDA section and flash it. Usually wipe data/factory reset will erase your data on internal storage card,but in my case is not happeni g. I am trying custom roms on my s2 (i9100) and when i wpie cache,data and delvik,no data is lost from the internal memory. Still got my obb files,music and stuff. Try to flash your device using an official rom and after that i recommend omni 4.4.2. It is very stable for samsung galaxy s2.
Trimis de pe al meu GT-I9100 folosind Tapatalk
Bricked again after 2 years
davidcsv said:
Based on your description of the problem, you should still have Odin download mode, which is good.
Let's first try and restore the phone back to somewhat stock...
Go to this post and download the MH2 pre-rooted stock firmware image (and unpack the zip file).
Flash using Odin, but don't change any of the default options and settings, just specify the tar.md5 file in the PDA section as you've done before...DO NOT TOUCH PIT option.
If Odin fails again, post the screen dump and show us the message log
if Odin succeeds, it will reboot and take a few minutes to initialize the phone (this MH2 image performs an implicit factory reset), you should eventually get the configuration wizard to setup the phone
Click to expand...
Click to collapse
You wouldn't believe it but my phone "Samsung Galaxy s2 LTE SHV E100s" got bricked today after 2 years. Yes i'm still using the same phone. And thank you for helping me out last time my phone got bricked.
I have a question for you. Hope you'll help me out this time too david.
1) Which ROM would be best for my phone now? Currently i had "pre rooted 4.1.2 JB" the one you gave me link. I'm sure you have tested all sorts of ROM's.
2) DO You have any new ROMS for shv e110s? if yes, is the procedure to flash it via odin same as before? e.g leave settings on default, select .tar file on pda section and flash?
Thank you!
Update 2: Added a Wi-Fi Hot Spot Fix, thanks to @cooperg21
Update 1: I have attached the recovery, EFS and PIT I personally used on my phone to do this fix, as requested by a fellow member
I've seen a few people that accidentally "bricked" their Verizon Note 2 by accidentally installing the N7100 Bootloader. I myself did this, attempted the resistor mentioned by a fellow member and that also would not work for me. So I set out to find an alternative way to do it, and was successful. You don't even have to open the phone to do it.
You will need:
Odin Software
Stock ND3 Odin compatible stock ROM (I used N7100XXUFND3_N7100OXAFND3_XEF)
N7100 TWRP Recovery (Latest Version, Odin Flashable)(attached to this post)
An i605 ROM (I used DN3).
A backup of your own EFS(if you have one), or the backup I provided(attached to this post)
N7100 PIT File, to repartition your Internal Storage to work with the stock N7100 ROM(attached to this post)
1. Use odin to write the N7100 pit file
2. Then, using Odin, load "N7100XXUFND3_N7100OXAFND3_XEF" into the "PDA" section, after that was finished, I booted into the stock recovery and did a factory reset. That allowed the phone to boot up, but baseband was "Unknown" and it had no service.
3. Then, use Odin to flash the latest version of TWRP for the N7100(it MUST be n7100 or it will bootloop/stick on the Samsung/Rom Booting screen)
4. Then you must flash "N7100_ND3_DrKetan_Custom_ROM_V82.zip" using TWRP recovery, it will boot that up just fine, still says "Unknown" for baseband(i'll explain later why I flashed this, and am directing you to also flash this, despite bootloader still not working).
5. Afterwards, flash the EFS file(attached to this post) using ODIN. This will help resolve the lost Baseband/IMEI problem encountered with flashing the stock N7100 ROM in Step 1.
5. After that, flash "DN3_v5.2_VZW.zip", again, using TWRP Recovery. After that my phone booted up it had service and all of my apps worked.
When I skipped Step 4, a few apps wouldn't work correctly. Instagram wouldn't refresh the feed or load anything, Snapchat wouldn't open anything or send anything either. I'm not sure why that happens, but it ONLY happened if I didn't flash the N7100_ND3_DRKetan ROM before flashing the DN3 ROM
I know this device is beginning to get old, but I hope this can help someone in the future.
cooperg21 said:
Solution to the DN3 Wifi Hotspot Issue:
1) Download and install Xposed
2) Open and update xposed framework (This didn't work the first time for me but after a clean install of the n7100 rom, then DN3 rom (with all S5 options selected), it worked.)
3) Restart (Might not be necessary but it doesn't hurt)
4) Install the "X Tether" Module in xposed.
5) Restart (Might not be necessary but it doesn't hurt)
6) Turn on mobile hotspot!
Click to expand...
Click to collapse
Was your phone previously rooted with an unlocked bootloader?
xnatex21 said:
Was your phone previously rooted with an unlocked bootloader?
Click to expand...
Click to collapse
I'm honestly not sure, I got it second hand from someone, went to flash a new ROM to it and accidentally did the wrong bootloader for the ROM prerequisite. But I don't imagine what used to be on the phone will matter, because the bootloader from the N7100 would've written over it, and flashing the stock N7100 Odin files will overwrite anything previously on the phone.
I did this but it was just a white screen. mtvideos fixed it
iiNFAMOUS CHRiS said:
I've seen a few people that accidentally "bricked" their Verizon Note 2 by accidentally installing the N7100 Bootloader. I myself did this, attempted the resistor mentioned by a fellow member and that also would not work for me. So I set out to find an alternative way to do it, and was successful. You don't even have to open the phone to do it.
You will need:
Odin Software
Stock ND3 Odin compatible stock ROM (I used N7100XXUFND3_N7100OXAFND3_XEF)
N7100 TWRP Recovery (Latest Version, Odin Flashable)
An i605 ROM (I used DN3).
First, you have to flash the stock ND3 ROM to your phone, it will not get past the Samsung screen, that is normal. You will have to enter recovery mode (Vol Up, Home & Power) and choose factory reset, after that the phone will boot android fine, but will not have service.
You will now have to flash the N7100 TWRP Recovery, followed by flashing an i605 ROM. Personally, I used DN3 and it worked for me.
After flashing the ROM and rebooting the phone, I had a 100% WORKING Note 2 that was previously bricked. Download mode shows N7100, yet the phone is working completely. Data, Voice, Text, etc.
I know this device is beginning to get old, but I hope this can help someone in the future.
Click to expand...
Click to collapse
I too accidently flashed this N1700 onto my I605
How do you flash the ND3 ROM if you can't get into recovery? With Odin I've tried loading
-N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5
-root66_VZW_stock_system.tar.md5
-I605VRUAND3_I605VZWAND3_I605VRUAND3_HOME.tar
None with no avail.
They all either never get past the PIT file and or unsuccessful, after rebooting both phone and PC and even tried another PC
at this point I am thinking of paying the 50$ for the JTAG fix. However any advice or suggestions would be helpful.
Also I tried this on both 3.07 and 3.09
PRODCUT NAME : GT-N7100
should be i605. The one that messed this up was N7100
N7100_KK_ND3_BL.tar.md5
... after this, it just rebooted and flash the Note 2 screen with GT-N7100 every 2 seconds... I can only put it in download mode. Recoevery mode will not work
djtenox said:
I too accidently flashed this N1700 onto my I605
How do you flash the ND3 ROM if you can't get into recovery? With Odin I've tried loading
-N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5
-root66_VZW_stock_system.tar.md5
-I605VRUAND3_I605VZWAND3_I605VRUAND3_HOME.tar
None with no avail.
They all either never get past the PIT file and or unsuccessful, after rebooting both phone and PC and even tried another PC
at this point I am thinking of paying the 50$ for the JTAG fix. However any advice or suggestions would be helpful.
Also I tried this on both 3.07 and 3.09
PRODCUT NAME : GT-N7100
should be i605. The one that messed this up was N7100
N7100_KK_ND3_BL.tar.md5
... after this, it just rebooted and flash the Note 2 screen with GT-N7100 every 2 seconds... I can only put it in download mode. Recoevery mode will not work
Click to expand...
Click to collapse
1. Use odin to write the N7100 pit file
2. Then, using Odin, load "N7100XXUFND3_N7100OXAFND3_XEF" into the "PDA" section, after that was finished, I booted into the stock recovery and did a factory reset. That allowed the phone to boot up, but baseband was "Unknown" and it had no service.
3. Then, use Odin to flash the latest version of TWRP for the N7100(it MUST be n7100 or it will bootloop/stick on the Samsung/Rom Booting screen)
4. Then you must flash "N7100_ND3_DrKetan_Custom_ROM_V82.zip" using TWRP recovery, it will boot that up just fine, still says "Unknown" for baseband(i'll explain later why I flashed this, and am directing you to also flash this, despite bootloader still not working).
5. After that, flash "DN3_v5.2_VZW.zip", again, using TWRP Recovery. After that my phone booted up it had service and all of my apps worked.
When I skipped Step 4, a few apps wouldn't work correctly. Instagram wouldn't refresh the feed or load anything, Snapchat wouldn't open anything or send anything either. I'm not sure why that happens, but it ONLY happened if I didn't flash the N7100_ND3_DRKetan ROM before flashing the DN3 ROM.
These are the exact steps I followed, after accidentally flashing the N7100 bootloader onto my i605 Note 2. You MIGHT also have to flash the i605 EFS file to restore your baseband. On ocassion, I had to or I would get Unknown Bootloader. It would also help to flash the "I605VRAMC3 Modem.zip" file, to ensure you're on the i605 Modem.
iiNFAMOUS CHRiS said:
1. Use odin to write the N7100 pit file
2. Then, using Odin, load "N7100XXUFND3_N7100OXAFND3_XEF" into the "PDA" section, after that was finished, I booted into the stock recovery and did a factory reset. That allowed the phone to boot up, but baseband was "Unknown" and it had no service.
3. Then, use Odin to flash the latest version of TWRP for the N7100(it MUST be n7100 or it will bootloop/stick on the Samsung/Rom Booting screen)
4. Then you must flash "N7100_ND3_DrKetan_Custom_ROM_V82.zip" using TWRP recovery, it will boot that up just fine, still says "Unknown" for baseband(i'll explain later why I flashed this, and am directing you to also flash this, despite bootloader still not working).
5. After that, flash "DN3_v5.2_VZW.zip", again, using TWRP Recovery. After that my phone booted up it had service and all of my apps worked.
When I skipped Step 4, a few apps wouldn't work correctly. Instagram wouldn't refresh the feed or load anything, Snapchat wouldn't open anything or send anything either. I'm not sure why that happens, but it ONLY happened if I didn't flash the N7100_ND3_DRKetan ROM before flashing the DN3 ROM.
These are the exact steps I followed, after accidentally flashing the N7100 bootloader onto my i605 Note 2. You MIGHT also have to flash the i605 EFS file to restore your baseband. On ocassion, I had to or I would get Unknown Bootloader. It would also help to flash the "I605VRAMC3 Modem.zip" file, to ensure you're on the i605 Modem.
Click to expand...
Click to collapse
Ok I followed it to a T and got it up with DN3 ROM, So now it at least has a ROM.
I need to load i605 EFS, I have both that and the Modem.zip. Question now is I saw many installers via app to install it however they all say N7100 loader only. I am not sure weather to use that method or another one. Would Odin install it ? if so what would be the procedures for this?
ANYWAY THANKS A LOT..
djtenox said:
Ok I followed it to a T and got it up with DN3 ROM, So now it at least has a ROM.
I need to load i605 EFS, I have both that and the Modem.zip. Question now is I saw many installers via app to install it however they all say N7100 loader only. I am not sure weather to use that method or another one. Would Odin install it ? if so what would be the procedures for this?
ANYWAY THANKS A LOT..
Click to expand...
Click to collapse
the EFS would be flashed via Odin, Modem is flashed via TWRP Recovery. I attached the modem and efs that I used to this post.
I'm glad my post could help you
iiNFAMOUS CHRiS said:
the EFS would be flashed via Odin, Modem is flashed via TWRP Recovery. I attached the modem and efs that I used to this post.
I'm glad my post could help you
Click to expand...
Click to collapse
Ok for the EFS , on Odin, which did you select to install it
Bootloader
PDA
PHONE
CSC
also inside that tar ball there are 3 files. I don't want to "brick" my device again. I've searched plenty of places for Odin flashing EFS but no avail with these instructions, again many thanks.
THANK YOU.
I actually did not find direction, however I found many bash programs that did it automatically and looked at their code, they Added the efs via PDA
then it booted and for good measure I went through the TWRP and installed the modem. Rebooted and I GOT 4G back and a working ROM. If you need any designs / music mixing or anything like that I can see what I can do. Life Saver !
Question, from now on will I need to install roms that are for the N7100 ? I will backup/restore the efs/modem just in case for these too correct if this is the case?
Or can I install i605 ROMS ?
Again MUCH KUDOS !:good:
djtenox said:
THANK YOU.
I actually did not find direction, however I found many bash programs that did it automatically and looked at their code, they Added the efs via PDA
then it booted and for good measure I went through the TWRP and installed the modem. Rebooted and I GOT 4G back and a working ROM. If you need any designs / music mixing or anything like that I can see what I can do. Life Saver !
Question, from now on will I need to install roms that are for the N7100 ? I will backup/restore the efs/modem just in case for these too correct if this is the case?
Or can I install i605 ROMS ?
Again MUCH KUDOS !:good:
Click to expand...
Click to collapse
I haven't tried any other ROMs, I do know that some kernels don't do too well, flashing the AGNI kernel caused me to lose my baseband no matter what I flashed afterwards, haven't found out why yet. The ROM that you flashed at the end, that the phone works with, is a i605 ROM right from the Verizon Note 2 section of these forums. And sorry for the delay in reply, had to do some work on my car lol
iiNFAMOUS CHRiS said:
I haven't tried any other ROMs, I do know that some kernels don't do too well, flashing the AGNI kernel caused me to lose my baseband no matter what I flashed afterwards, haven't found out why yet. The ROM that you flashed at the end, that the phone works with, is a i605 ROM right from the Verizon Note 2 section of these forums. And sorry for the delay in reply, had to do some work on my car lol
Click to expand...
Click to collapse
No worries, I needed to do much research .. But ok. Your method worked well and I tested everything so far, only wifi hotspot did not work, but I don't use it as much to comlain. Thanks
djtenox said:
No worries, I needed to do much research .. But ok. Your method worked well and I tested everything so far, only wifi hotspot did not work, but I don't use it as much to comlain. Thanks
Click to expand...
Click to collapse
That's most likely a problem with the ROM itself, but either way you're welcome -- i'm glad I could help you.
I think I have the same issue as you. I wasn't paying attention and I installed a n7100 bootloader on my i605 phone.
Anyway, I did a search for N7100XXUFND3_N7100OXAFND3_XEF and it looks as if that rom is French. Is that going to cause an issue?
http://forum.xda-developers.com/showpost.php?p=46901976&postcount=741
ran in odin
MJ5 bootloader
Now, gt-n7100 is flashing whenever I plug in my phone
I have about 18% battery life left and can't charge because I get the boot loop as soon as I plug in my phone so I unplugged it.
This shows in Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> param.bin
<ID:0/004> tz.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
cooperg21 said:
I think I have the same issue as you. I wasn't paying attention and I installed a n7100 bootloader on my i605 phone.
Anyway, I did a search for N7100XXUFND3_N7100OXAFND3_XEF and it looks as if that rom is French. Is that going to cause an issue?
Click to expand...
Click to collapse
No, there won't be any problems. I'm in the USA and speak english and it worked fine for me.
iiNFAMOUS CHRiS said:
No, there won't be any problems. I'm in the USA and speak english and it worked fine for me.
Click to expand...
Click to collapse
Thank you very much. I was able to get it installed (kindof). It kept on flashing up with errors. I was able to get TWRP installed. However, my PC says that my phone's capacity is only 107MB now.
I'm going to try putting my SD card back in (had to take it out to get the PIT file working).
I couldn't find the ROM "N7100_ND3_DrKetan_Custom_ROM_V82.zip"but found "N7100_ND3_Prerooted_deknoxed_debloatableV3".
Would that work before I install the i605 rom? Thanks again for all of your help!!!!!!
cooperg21 said:
Thank you very much. I was able to get it installed (kindof). It kept on flashing up with errors. I was able to get TWRP installed. However, my PC says that my phone's capacity is only 107MB now.
I'm going to try putting my SD card back in (had to take it out to get the PIT file working).
I couldn't find the ROM "N7100_ND3_DrKetan_Custom_ROM_V82.zip"but found "N7100_ND3_Prerooted_deknoxed_debloatableV3".
Would that work before I install the i605 rom? Thanks again for all of your help!!!!!!
Click to expand...
Click to collapse
Are you sure you flashed the N7100 recovery, rather than the i605 recovery?
Also, here is a link to the DrKetan ROM
http://forum.xda-developers.com/showthread.php?t=2472270
would be sweet to see if this worked for locked bootloaders and allowed us to flash stuff again
Anybody out there wanna test? I'm pretty close to testing it on mine...since i'm about ready to switch to T-Mobile anyways.
Well, I'm taking the plunge now.
I went in to flash Trent's new B8, wiped data and TWRP crashed or something, then it bootlooped at the Note 2 screen. So instead of ODIN'ing back to VZW stock, i'm going to intentionally brick this beast to try this **** out lol
So annoyed at how bad this phone turned out to be once the 4.3 OTA was accidentally accepted by a lesser being in my house ;
---------- Post added at 11:19 AM ---------- Previous post was at 10:35 AM ----------
my phone must be a beast, it fails to flash everything. It's gaurded by an angel!
I can't flash the n7100 bootloader onto it, it asks for pit, i put the pit, nothing. Just sits there saying looking for PIT to partition for bootloader. womp womp.
iiNFAMOUS CHRiS said:
Are you sure you flashed the N7100 recovery, rather than the i605 recovery?
Click to expand...
Click to collapse
I think so. Here is what I installed.
http://www.androidayos.com/2014/04/26/root-n7100xxufnd3-galaxy-note-2-android-4-4-2-kitkat-update/
https://docs.google.com/uc?id=0ByGZ52Krjat1QzdBWVJZTlk0VTg&export=download
Next step is the.... N7100 Dr.Ketan Custom ROM V 8.1
I ran into some issues with the PIT file (tried two different ones that I randomly found) and when I installed the above rom, it froze a couple of times in ODIN, but the third time was the charm. (If there is any way you could upload a link to the PIT file, future viewers with this problem would be really grateful!)
Is this it?
http://forum.xda-developers.com/showthread.php?t=2653311
or this?
http://forum.xda-developers.com/showthread.php?t=1927983
I'm moving everything onto my card via another phone and will update when I have an answer as to whether or not it worked. Thank again!
- My phone is currently stuck on the Samsung Screen. I'm thinking I didn't do the setup options correct on the rom....
- Tried wiping and reflashing rom but now I can't get past the Galaxy Note II GT-N7100 screen.....
- OK, Starting process again..... so I went back and reinstalled the French Recovery for the N7100. (Listed above). I think my original download didn't work so I redownloaded it. It flashed through Odin and booted without any weird errors! I'm going to follow the rest of the steps now.
- Installed TWRP: openrecovery-twrp-2.7.2.1-t03g.img.tar
- Installing the N7100 Dr.Ketan Custom ROM V 8.1 now via TWRP
- TWRP said FAILED after the install but I rebooted and my phone now says "Android is upgrading...",
- SUCCESS! The ROM installed. (just picked default/skip options) Now I'm going to install the DN3 Rom via TWRP
- Got DN3 up and running but no cell reception. Went to install the EFS via Odin 3.09 but it crashed Odin.... Trying with 3.07.... 3.07 got to NAND write start and my phone has a blue bar across the bottom but I think it's stuck... Task Mgr. shows little to no activity.... Time to try again.... I was able to restore an EFS via TWRPfrom a backup I had made but still no cell reception..... :/
- It works!!!!!!!!!!!!!!!! I was just impatient. After about 30 seconds, I have cell reception! CHRiS, you truly are infamous! You are awesome! Thank you, thank you, thank you!!!!!!!
BlakeDC said:
[/COLOR]my phone must be a beast, it fails to flash everything. It's gaurded by an angel!
I can't flash the n7100 bootloader onto it, it asks for pit, i put the pit, nothing. Just sits there saying looking for PIT to partition for bootloader. womp womp.
Click to expand...
Click to collapse
Did you try just running the PIT by itself using Odin 3.7?