Hello all and thank you for your time. been doing this for a while and i cannot figure out what im doing wrong. hopefully someone can help me figure out what i missed. I was odin'ing back to try and fix a LTE modem issue. followed the sticky guide like i did originally to root. first wiped everything, then odin MDK (never OTA'd), flash MD2 kernel, ticked appropriate boxes, updated super su and binary, checked root with TBU, odin'ed MDK kernel, then flashed with rom manager CWM. root was granted at the respected times. everything seems right until i boot into recovery and the screen goes to the stock recovery and the android man has a red exclamation mark. the recovery is usable but it does not help me much..
thanks for the time and suggestions.
take care.
electroman789
One.... You're on Verizon...... There's no flashing a custom ROM yet.... Only touch wiz based ones.....no recovery.... Only safestrap.... Especially if you're on the newest bootloader or newest ota, there's no flashing anything besides a touch wiz ROM in a ROM slot on safe strap....
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
electroman987 said:
Hello all and thank you for your time. been doing this for a while and i cannot figure out what im doing wrong. hopefully someone can help me figure out what i missed. I was odin'ing back to try and fix a LTE modem issue. followed the sticky guide like i did originally to root. first wiped everything, then odin MDK (never OTA'd), flash MD2 kernel, ticked appropriate boxes, updated super su and binary, checked root with TBU, odin'ed MDK kernel, then flashed with rom manager CWM. root was granted at the respected times. everything seems right until i boot into recovery and the screen goes to the stock recovery and the android man has a red exclamation mark. the recovery is usable but it does not help me much..
thanks for the time and suggestions.
take care.
electroman789
Click to expand...
Click to collapse
If you have a phone with the MDK bootloader, all you should have to do is to update the modem to the latest release.
Since installing MD2 seems to have worked, your bootloader is MDK so you're OK.
Did you follow the recovery instructions in http://forum.xda-developers.com/showthread.php?t=2292112 to install CWM?
I'd be asking questions there to get help with getting this done.
However, it appears that people have had better success with other custom recoveries, like Philz and TWRP.
I can't say from personal experience, never having had a MDK phone in hand, but you may want to try TWRP.
to pball52998; there is root (not safestrap) for MDK (stock baseband) users (not OTA'd peers). root access is attained by guild linked to by my first post. safestrap started for users that locked their bootloaders by ota. hence twiz.
to k1mu; i have followed all of the instructions per the guide linked in on my question. recovery instillation was done using rom manager, goomanager, and philz using odin (which failed due to authentication error??).
<ID:0/011> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltevzw.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
phone says:
odin mode
product name: sch-i545
current binary: samsung official
system status: custom
csb-oem_config_lsb:0x30
write protection: enabled
start [224,1440]
secure check fail : recovery
i would also like to include that i am restoring from the mdk no wipe tar.md5 via odin 3.07.
im running out of solutions. ill use stock rom but i have grown accustomed to aftermarket roms and would like to continue using them.
any other ideas?
You may have to Odin back and then this time install TWRP. Then use a Philz zip file from within TWRP to get you that recovery. I've actually seen a few people lately having problems with ROM manager. So I'm not sure what's up with that. But that's what I did without issue . TWRP --->Philz
Sent from my SCH-I545 using Tapatalk
Mistertac said:
You may have to Odin back and then this time install TWRP. Then use a Philz zip file from within TWRP to get you that recovery. I've actually seen a few people lately having problems with ROM manager. So I'm not sure what's up with that. But that's what I did without issue . TWRP --->Philz
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you for the suggestion but I tried using twrp by installing via goomanager to no avail. Same result as rom manager. Says it is successfully installed but when I boot into recovery, stock recovery . Ive also noticed that when I boot up, I see a plain samsung logo and a unlocked padlock with the word "custom" under it. This is the first boot screen that I am describing. I dont know what is happening. And that boot screen is not consistent. Some times it will boot normal and then boot up the "custom unlock" boot screen. All the things that should work are not for some reason. Again I have not ota'd, odin'd to fix a modem issue, gaining root but not custom recovery....
thx again for your time
electroman987 said:
Thank you for the suggestion but I tried using twrp by installing via goomanager to no avail. Same result as rom manager. Says it is successfully installed but when I boot into recovery, stock recovery . Ive also noticed that when I boot up, I see a plain samsung logo and a unlocked padlock with the word "custom" under it. This is the first boot screen that I am describing. I dont know what is happening. And that boot screen is not consistent. Some times it will boot normal and then boot up the "custom unlock" boot screen. All the things that should work are not for some reason. Again I have not ota'd, odin'd to fix a modem issue, gaining root but not custom recovery....
thx again for your time
Click to expand...
Click to collapse
Are you booting into recovery from ROM manager or from phone off + vol up + power + home?
Like I said someone else was having this same issue. Maybe try a full wipe in Odin. I'm going to look for that other guys post on here and see what he did I don't recall
Sent from my SCH-I545 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:07 AM ----------
Also don't worry about that custom screen. Mine went away when I switched to Philz recovery. But either way its just an indication your phone is rooted/modified
Sent from my SCH-I545 using Tapatalk
---------- Post added at 08:12 AM ---------- Previous post was at 08:09 AM ----------
I used this mdk Odin file. Worked perfect
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk
---------- Post added at 08:32 AM ---------- Previous post was at 08:12 AM ----------
Also.. A few on here swear by the all in one root + recovery tool that's on here for our phones. Just an idea that's all. I myself used that Odin file I linked you to. Rooted it. Then installed TWRP then Philz. I don't know enough about ROM manager to begin guessing. Another idea is try using an older version of Philz In Odin. Or an older version of TWRP from Odin. Again just throwing out ideas
Sent from my SCH-I545 using Tapatalk
---------- Post added at 08:40 AM ---------- Previous post was at 08:32 AM ----------
http://teamw.in/project/twrp2/181
Go here. Its twrp for our phones with instructions on how to manually install it and at the bottom are others talking about the same issue you're having. Guess its a known issue. Okkkk enough fragmented posts from me. Lol
Sent from my SCH-I545 using Tapatalk
[solved] phone not flashing recovery after odin reset
Thanks to mistertac for finding the link he did for I had not seen it in the research I frantically looked through to find the solution to my problem. :victory:
If anyone has issues with flashing a custom recovery after a full Odin, I have found through experience that it is unnerving and frustrating.
DO NOT FREAK OUT!!!!! Try your usual steps again. If it does not work, try flashify. Find on Google play. I am not responsible for any actions you do to your device but it worked for me the first time. Now I am again on my favorite ROM running as if nothing ever happened. Took 3 days and sweating bullets but it worked.
I hope this experience doesn't have to be repeated so learn from my experience.
Related
I had Crodorom working on my SGS2, downloaded the new Omega rom, flashed it and this is what I got: kernel panic upload mode. It doesn't go into recovery mode, only download, but when I try to flash something via odin, my laptop freezes. I don't know what else to do, tried flashing everything I have and every time freezes.
Please HELP ME!!!!:
Search.
http://forum.xda-developers.com/showthread.php?t=1521482
http://www.google.co.uk/search?clie..._upl=3091l3091l0l5344l1l1l0l0l0l0l63l63l1l1l0
jje
kernel panic upload mode
I was flashing custom ROMS from couple of months and did dozens of times.
But when I was flashing resurrection ROM an updated version, it completed but when I rebooted it was stuck in the kernel panic upload mode after the boot screen(galaxy s2). It was not going to clockworkmod recovery too. Then using the odin I tried to flash the stock ROM as well as custom ones. But it will finish, will stuck in the boot screen. Then flashed recovery using Odin and tried to flash custom roms. Couple of ROMS worked but most of them failed and stuck in the boot screen. I could able to restore the stock version which I saved previously.
But I cant try most of the ROMs now. CM9 didnt work.. But MIUI worked.
Can anyone help me.???
Go to formats and storage and delete cache and data before doing full wipes sometimes there is kinda like data blockage you need to get cwm can you flash it with odin
Sent from my GT-I9100 using xda premium
As far as others experience with the same issue, you should also be able to get download mod and flash a ROM from ODIN, freezing issue must be due to your connection or PC problem, try with another PC,
shashankdombe said:
I was flashing custom ROMS from couple of months and did dozens of times.
But when I was flashing resurrection ROM an updated version, it completed but when I rebooted it was stuck in the kernel panic upload mode after the boot screen(galaxy s2). It was not going to clockworkmod recovery too. Then using the odin I tried to flash the stock ROM as well as custom ones. But it will finish, will stuck in the boot screen. Then flashed recovery using Odin and tried to flash custom roms. Couple of ROMS worked but most of them failed and stuck in the boot screen. I could able to restore the stock version which I saved previously.
But I cant try most of the ROMs now. CM9 didnt work.. But MIUI worked.
Can anyone help me.???
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=24648392&postcount=910
Yes.. but no improvements
djseaneq said:
Go to formats and storage and delete cache and data before doing full wipes sometimes there is kinda like data blockage you need to get cwm can you flash it with odin
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes I can flash using Odin.. It even succed and resets... But when it reboots it just stuck in the boot screen and cant boot in recovery too...
But if I flash just the CMW 4 it flashes and I can just access recovery and flash some ROMS from there..
---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------
078gregory said:
Follow this http://forum.xda-developers.com/showpost.php?p=24648392&postcount=910
Click to expand...
Click to collapse
Tried it with the stock one which I got with mobile ... But it was not ROM.. just stock firmare... I will try with complete ROM.
Hayelp --- STUCK in KERNEL PANIC UPLOAD MODE
OK, so I did a stupid thing. I decided to use ROM Manager to move from CYANOGENMOD 9 (earlyish variant) to MIUI 2.5.11.
(I'm usually fairly comfortable/confident/competent doing this kind of thing - never bricked anything before - PSP, Galaxy S, Experia min pro, etc...)
I told ROM Manager to backup the ROM, and set it off to do its thing.
Next thing I'm aware of is "KERNEL PANIC UPLOAD MODE" and the text [ RST_STAT = 0x20000000 ] in red in the top left hand corner of the screen.
I've searched the Fora and found some others with a similar issue, so I tried a few things.
1stly I tried to get into ClockwordModRecovery mode, but was unable to.
But I got into Odin upload mode, so I dug out Odin, and an XW ROM, tried to download them to the device. No joy, so I tried another Odin XX ROM - also no joy. (Following various guides as to which ROM to try, and how to do it). Currently the ODIN Mode says.
ODIN MODE
PRODUCT NAME: GT-i9100
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
...
I could flash a new ROM over the existing one(it doesn't seem as if I can now...) and am currently on (I believe) Kernel_I9100XWLP7.
OK, so what to do next...
Well I tried to get back into CWM (on, up volume and home) to get into something which looked like CWMRecovery, but only gave 4 (?) options - reboot now, install update from SD, wipe Cache, wipe data - the wipe data came up with a password required, which I don't know so backed out of.
Oh, I downloaded KIES 2.0 to see if that could help - not in this instance it can't...
Now I'm stuck, I will try some other ODIN ROMs as that seems to be the only point of attack left to me.
Can anyone suggest anything else to try?
Please?
Argon0 said:
ODIN MODE
PRODUCT NAME: GT-i9100
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
Click to expand...
Click to collapse
if your status is above while you enter into Download mod, you should be able to flash a stock ROM from the ODIN, provided you have followed the steps correctly.
find any official stock ROM and flash it from ODIN after leraning well how to flash from ODIN.
prefer GB oficial ROM.
Further info:
Removal of Kies leads me to be able to use ODIN again. I have just been able to "flash" with Kernel_I9100XWLA4.tar.md5.
The phone is now stuck on the
"Samsung
GALAXY SII
GT-I9100"
Screen.
Argon0 said:
Further info:
Removal of Kies leads me to be able to use ODIN again. I have just been able to "flash" with Kernel_I9100XWLA4.tar.md5.
The phone is now stuck on the
"Samsung
GALAXY SII
GT-I9100"
Screen.
Click to expand...
Click to collapse
why do you try only the kernel....flash the same XWLA4 complete ROM.
Kies are installed for getting the required drivers installed, better you install Kies and just kill the application, from system tray too..
Firstly ZACQ8 I have tried that, can you recommend a specific ROM? (This is a UK T-mobile SGS2).
I can now get into the "Android System Recovery <3e>" screen.
It has four options:
reboot
apply update from SDCard
wipe data/factory reset
wipe cache partition.
The "command window" shows (in yellow):
-- Copying media files...
Successfully copied meida[sic] files.
# MANUAL MODE #
-- Updating applicaton...
{this bit in red}
E:check_point2: /sdcard/.ngmoco//53297255e6f7dd7073c89e6dea2da0d1 is not directory
{back to yellow}
Successfully update application.
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ODK/system/'.
Successfully applied multi-CSC.
that is the stock recovery, did you try both wipes there and reboot?
OMG - I can't believe I missed the "complete ROM" bit before... OK downloading the latest UK (XEU) version of Stock from:
http://skywanker.net/download/downl...9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.7z
Hope this works... (should have clicked earlier - this is taken a lot longer than the Kernel.. I wonder why!!!).
Thanks ZACQ8 - will click on the Thanks button if this works!
---------- Post added at 02:20 PM ---------- Previous post was at 01:54 PM ----------
OK, having installed that complete ROM. I'm still getting nowhere fast...
Now its stuck at SAMSUNG GALAXY SII GT-I9100 screen... (actually seems to cycle to that screen and go no further).
Now I can't get into the Android Recovery Screen Either...
Output from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> zImage
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Will now try the XXLPS from: http://skywanker.net/download/downl...9100_XEO_I9100XXLPS_I9100OXALPS_I9100XXLPS.7z
---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------
Yes, first one asked for a password (which I don't know), 2nd (cache) seemed to do as expected, but made no difference.
The factory reset password - if you do 3 fails at that it says one more go and then I'll damage the contents of the SDCARD - does this matter?
I'll add that there is nothing I don't have elsewhere on either the internal or external SD cards...
try GB roms...
Recovered from "KERNEL PANIC UPLOAD MODE"
GB ROMS from where? The letter coding is a little tricky to understand...
(I understand that XX and XW refer to UK type ROMS, is there a separate section/letter code for GB Roms?) - is this: http://skywanker.net/download/downl...9100_SEB_I9100XXLPQ_I9100OXXLPD_I9100XXLPQ.7z what you refer to as a GB ROM?
I now have a Galaxy SII booting up, into the stock ROM mentioned above. (well it seems to be booting I got the Android with the vector polyhedron in its tummy, and now the screen is showing a glowing S with Samsung Galaxy SII underneath it - I shall leave it at that for a few minutes before... well what next.. if its stuck here..) I guess another reboot and another ROM, or into recovery....
Got into recovery, did wipe cache and factory reset... booting now.... same as last time, but a little quicker to the glowing S...
Now its installing applications.... (KIES AIR, etc...)..
Connecting to WiFi - done (Working SIM is in other phone atm).
Signing in...
Restoring...
Ready to use !!! Y
<YAY>
what up now? from where are you downloading the ROMs from,
ICS roms are 4.0.3 and GB Roms are 2.3+
you can see the coplete list of ROM released here : http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regiona
EDIT : I think you have not given much time to boot your phone....thanks GOD finaly it worked..
AH... GB = GingerBread - I thought you were referring to Great Britain!!!
Ho Hum.
I now have a working phone at least - ICS with Touchwiz (yuk)...
Now how do I put MIUI on it.. (any links to tutorials?)? Or do I go back to CM9?
(And yes I do need root, I want to use some remote desktop apps - such as Remote Call - so I can control the phone from my PC).
Last sucessful flash was LP7 right?
pick the CF-root for the same from the link CF-root below, download the zip, unzip it to get TAR file flash same like u flashed the ROM put it on PDA.
then you will get your phone rooted and CWM installed, then flash watever rom from CWM
Successful flash was GT-I9100_XEO_I9100XXLPS_I9100OXALPS_I9100XXLPS.tar.md5
Is there a reason why Odin doesn't get used to flash things like MIUI?
It would seem to be a good standard (and fairly safe) way to flash Galaxies...
Again, Thanks ZACQ8.
---------- Post added at 04:02 PM ---------- Previous post was at 03:22 PM ----------
DOH... Read the thread he points you to before typing anything new....
OK so if I have ...LPS I need to use this cf-root CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip right?
---------- Post added at 04:10 PM ---------- Previous post was at 04:02 PM ----------
OK, just to keep this all in the same place, in case its useful for anybody else...
Yup that did seem to be the correct cf-root - I've now got a rooted stock Galaxy S2 - still with the yellow triangle, but that can stay for the moment. I guess the next bit is to put the MiuiAndroid.zip in the root of the sdcard...
Then boot into CWM, then install from sdcard... Lets see....
One other thing which might be useful for others is that I had to restart ODIN every time I wanted to flash, I couldn't flash, then reset reconnect and reflash. This is on Windows 7 Pro. Also I made sure I ran ODIN as administrator.
Edit: Problem Solved!
This problem is caused by an auto-restore script in Canadian ICS notes. When the phone boots up, it restores the recovery image to the stock Android recovery. To fix this problem, follow the link kindly supplied by zaptor99:
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
It worked for me!
Initial Post: So, after my ICS OTA update, I set about reinstalling CWM, then re-rooting the phone.
Steps followed:
Put phone into Download Mode(Power+Down Vol, then Up Vol at warning screen), successful.
Open ODIN, select CWM-i717-120305.tar.md5 (Also done with cwm-touch-i717-120414.tar.md5) as PDA
Plug in phone - Odin detects correctly.
Click Start; ODIN steps through it's business:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Seems successful, no?
Phone reboots, works normally.
Shut down phone, disconnect from PC
Boot into Recovery Mode (Vol Up+Vol Down+Power, as normal)
Aaaaaand, into Android System Recovery (3e).
Other information:
Before doing the Rogers OTA update, I reflashed to stock Rogers firmware using this post: http://forum.xda-developers.com/showthread.php?t=1657262
This process worked perfectly from Gingerbread - I installed CWMTouch, then a rooted kernel via ODIN.
I've no idea why I can't boot into CWM? I figure, either the ODIN write is failing (though it reports success), or it's writing to the wrong place. But without root, I'm not sure how I can check.
I'd be eternally grateful for any help. The phone works fine, now, but I *REALLY* don't want to be forever stuck on stock firmware with no way to make proper nandroid backups.
I am not sure why it is like that but it's exactly same on my i717m.
For me, I just went to CWM mode by pressing those keys before giving Note a full reboot.
I could get into CWM mode without a problem so I installed superuse. And my phone is fully rooted.
darknoon77 said:
I am not sure why it is like that but it's exactly same on my i717m.
For me, I just went to CWM mode by pressing those keys before giving Note a full reboot.
I could get into CWM mode without a problem so I installed superuse. And my phone is fully rooted.
Click to expand...
Click to collapse
I can't get into CWM. It seems to flash fine, but when I try to reboot into CWM, it loads the stock Android Recovery instead, so I have no way to flash superuser.
Edit: To be clear, my problem isn't getting root. It's getting CWM working, so I can move forward in any way. Once I've got CWM running, there's zounds of different ways to get root.
Further Edit: Attempts to flash CWM *are* increasing my flash counter.
Wintersdark said:
I can't get into CWM. It seems to flash fine, but when I try to reboot into CWM, it loads the stock Android Recovery instead, so I have no way to flash superuser.
Edit: To be clear, my problem isn't getting root. It's getting CWM working, so I can move forward in any way. Once I've got CWM running, there's zounds of different ways to get root.
Further Edit: Attempts to flash CWM *are* increasing my flash counter.
Click to expand...
Click to collapse
try TWRP or try to redownload CWM maybe you just got a bad zip
Bradl79 said:
try TWRP or try to redownload CWM maybe you just got a bad zip
Click to expand...
Click to collapse
How can I install TWRP on an unrooted phone without cwm installed? Is there an ODIN friendly tar kicking about? I looked but without success.
My zips are known good, though, used them to install CWM back on Gingerbread.
I just came to the q&a forums to post the same think. I tried flashing CWM 3 times and Im still going into stock recovery. I managed to go into CWM once and was able to flash SU so I have root but when I try to go back to recovery, I end up at stock recovery.
Sent from my SGH-I717M using xda app-developers app
id_mew said:
I just came to the q&a forums to post the same think. I tried flashing CWM 3 times and Im still going into stock recovery. I managed to go into CWM once and was able to flash SU so I have root but when I try to go back to recovery, I end up at stock recovery.
Sent from my SGH-I717M using xda app-developers app
Click to expand...
Click to collapse
You're freshly into ICS as well? did you upgrade OTA or with Kies? Bdfore upgrading, did you flaah the "stock Rogers original firmware" from here on XDA?
Trying to pin down the common thread, as this appears to be happening to several people.
Wintersdark said:
You're freshly into ICS as well? did you upgrade OTA or with Kies? Bdfore upgrading, did you flaah the "stock Rogers original firmware" from here on XDA?
Trying to pin down the common thread, as this appears to be happening to several people.
Click to expand...
Click to collapse
I reverted back to Bell stock firmware and updated ics OTA.
I tried flashing CWM recovery a couple of times and I noticed the only time I can get into CWM is when I flash and press the volume up + down and the power button before my phone full reboots after the flash.
That way It works but right after the phone reboot for the first time after flashing CWM, it will not fo back into it.
Can anybody help us?
How can we try TWRP if we can't get into CWM?
Sent from my SGH-I717M using xda app-developers app
Interesting! If you can get into CWM that way (reflash and squeeze in) try doing that and using cwm to flash SuperUser.
Then, once rooted, install ROM Manager and have it reflash the latest CWM, maybe that will get us a good cwm install.
cwm 5.8.4.8 works flawlessly.
Sent from my SGH-I717M using xda app-developers app
Wintersdark said:
Interesting! If you can get into CWM that way (reflash and squeeze in) try doing that and using cwm to flash SuperUser.
Then, once rooted, install ROM Manager and have it reflash the latest CWM, maybe that will get us a good cwm install.
Click to expand...
Click to collapse
I actually flashed CWM went into it before my phone rebooted and flashed TWRP and same think happened, when my phone rebooted I loose my flashed recovery.
I doubt Rom manager would work.
Sent from my SGH-I717M using xda app-developers app
id_mew said:
I actually flashed CWM went into it before my phone rebooted and flashed TWRP and same think happened, when my phone rebooted I loose my flashed recovery.
I doubt Rom manager would work.
Sent from my SGH-I717M using xda app-developers app
Click to expand...
Click to collapse
It seems like its somehow reverting the restore partition on boot. i suspect it may be a scripted event "on next boot" after ODIN, so flashing another recovery then wouldnt help - the on next boot event happening again when you reboot.
However, ROM Manager would give you a chance to reflash recovery after that happens. Its a xhance, anyways. Seems to have worked for dark? I can't try until after work today.
Plz update me when u give Rom manager a try.
Sent from my SGH-I717M using xda app-developers app
Wintersdark said:
So, after my ICS OTA update, I set about reinstalling CWM, then re-rooting the phone.
Steps followed:
Put phone into Download Mode(Power+Down Vol, then Up Vol at warning screen), successful.
Open ODIN, select CWM-i717-120305.tar.md5 (Also done with cwm-touch-i717-120414.tar.md5) as PDA
Plug in phone - Odin detects correctly.
Click Start; ODIN steps through it's business:
Phone reboots, works normally.
Shut down phone, disconnect from PC
Boot into Recovery Mode (Vol Up+Vol Down+Power, as normal)
Aaaaaand, into Android System Recovery (3e).
Other information:
Before doing the Rogers OTA update, I reflashed to stock Rogers firmware using this post: http://forum.xda-developers.com/showthread.php?t=1657262
This process worked perfectly from Gingerbread - I installed CWMTouch, then a rooted kernel via ODIN.
I've no idea why I can't boot into CWM? I figure, either the ODIN write is failing (though it reports success), or it's writing to the wrong place. But without root, I'm not sure how I can check.
I'd be eternally grateful for any help. The phone works fine, now, but I *REALLY* don't want to be forever stuck on stock firmware with no way to make proper nandroid backups.
Click to expand...
Click to collapse
I did EXACTLY as you did. But I used cwm-i717-120305.tar instead. Does it make a difference if the file is .tar and not .md5? Because CWM recovery stayed on mine and works perfectly.
Agoattamer said:
I did EXACTLY as you did. But I used cwm-i717-120305.tar instead. Does it make a difference if the file is .tar and not .md5? Because CWM recovery stayed on mine and works perfectly.
Click to expand...
Click to collapse
Did you install ICS OTA over pure stock Gingerbread? This doesnt seem to happen to people who had a modded recovery before installing the ICS update.
Wintersdark said:
Did you install ICS OTA over pure stock Gingerbread? This doesnt seem to happen to people who had a modded recovery before installing the ICS update.
Click to expand...
Click to collapse
It was pure stock Gingerbread. I was running an ATT leaked ICS version with CWM installed. But to get the Rogers update I used odin to restore the gingerbread version from here: http://forum.xda-developers.com/showthread.php?t=1657262
I did not install CWM or root before I used Kies to get the ICS update. But I see the difference now. I used Kies to get the update and you used OTA. Maybe if you went back to gingerbread and used Kies this time to get the update, it might fix your issue??
Any luck from Rom Manager?
I'm at at a wedding now so I won't be able to try it.
Sent from my SGH-I717M using xda app-developers app
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
That's fantastic! Thanks so much for the linkage there
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
Thanks Zaptor! it worked.
Finally, this gave me enough trouble.
Hi everyone!
thanks for the fast response,
i tried to upgrade my rom to cyanogen cm9 from 7,
it got stuck in boot loop,
also - i lost cwm,
i can enter download mode, but no matter what kernel\rom (i even used stock)
it gets stuck in boot (in some roms it went to the rom opening screen - and then it gets stuck,
i tried flashing different kernels - nothing.
is there anyway to get clock work back at least? i tried flashing it trough odin 4 times already - says ok,
but doesnt appear when i start the phone.
i promise ill be a good boy, help me out here please
Try flashing cm9 resurrection Odin method and see if it works
Sent from my GT-I9100 using Tapatalk 2
drivenbythemadness said:
hi everyone!
Thanks for the fast response,
i tried to upgrade my rom to cyanogen cm9 from 7,
it got stuck in boot loop,
also - i lost cwm,
i can enter download mode, but no matter what kernel\rom (i even used stock)
it gets stuck in boot (in some roms it went to the rom opening screen - and then it gets stuck,
i tried flashing different kernels - nothing.
Is there anyway to get clock work back at least? I tried flashing it trough odin 4 times already - says ok,
but doesnt appear when i start the phone.
I promise ill be a good boy, help me out here please
Click to expand...
Click to collapse
did tou try to wipe data: Factory reset ?
Can't get there, phone will only enter download mode or boot loop,
i keep messing with it in the meanwhile,
now the drivers for the device are gone, odin won't see the phone,
talk about a string of mistakes :/
Is there anyway you can walk me trough it? its a moment of your time, and at least a few months of work if i have to buy a new one...
drivenbythemadness said:
Can't get there, phone will only enter download mode or boot loop,
i keep messing with it in the meanwhile,
now the drivers for the device are gone, odin won't see the phone,
talk about a string of mistakes :/
Is there anyway you can walk me trough it? its a moment of your time, and at least a few months of work if i have to buy a new one...
Click to expand...
Click to collapse
Re-install Kies
Reboot
Connect phone (in download mode)
Flash Siyah kernel via odin
Boot into recovery
full factory wipe
enable mass storage
transfer then flash rom.
ronhoover88 said:
Try flashing cm9 resurrection Odin method and see if it works
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
well, i gotta figure out how to make odin see the phone now, i messed it up too :/
TheATHEiST said:
Re-install Kies
Reboot
Connect phone (in download mode)
Flash Siyah kernel via odin
Boot into recovery
full factory wipe
enable mass storage
transfer then flash rom.
Click to expand...
Click to collapse
i managed to get the drivers working, Odin fails to flash with siyah :
> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kept trying, No change. can anyone help me out on this one? i really don't think my provider will fix it...
drivenbythemadness said:
i managed to get the drivers working, Odin fails to flash with siyah :
> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kept trying, No change. can anyone help me out on this one? i really don't think my provider will fix it...
Click to expand...
Click to collapse
Well... since odin is working now, why dont u flash the resurrection edition?
Sent from my GT-I9100 using xda app-developers app
can flash anything, i believe its "Kernel corruption" or something like that, i found a guide that helped me, had to flash the bootloader and everything,
thanks alot for the help guys,
for future reference i will post the link to the guide :
http://forum.xda-developers.com/showthread.php?t=1457458
Thanks alot guys, its the best feeling knowing there is someone trying to help even if its a stupid error from my side.
Good to know everything's good and running. Perhaps you can copy and paste the link in the OP and edit the title to [issue solved] for future similar issues.
Sent from my GT-I9100 using xda app-developers app
Hello guys
I have Verizon's 4G LTE Samsung Galaxy Tab 10.1 running stock Samsung firmware (Model SCH-i905).
Recently, I have updated the device to latest ICS update via Software Update.
I am looking for a safe and an eazy to use method for rooting this device.
Any help?
Thank you!
tweetatoo said:
Hello guys
I have Verizon's 4G LTE Samsung Galaxy Tab 10.1 running stock Samsung firmware (Model SCH-i905).
Recently, I have updated the device to latest ICS update via Software Update.
I am looking for a safe and an eazy to use method for rooting this device.
Any help?
Thank you!
Click to expand...
Click to collapse
Hi Tweetatoo. I'm not saying this to be an A-hole but this information can be found with a simple search on this board.
Here's the thread you are looking for, click thanks button if it helps.
http://forum.xda-developers.com/showthread.php?t=1444714
You will only need to start from step 5. Be sure to read and follow the instructions completely.
eejimen said:
You will only need to start from step 5. Be sure to read and follow the instructions completely.
Click to expand...
Click to collapse
Excellent... but this is not working. I can flash recovery, but I can't get into recovery. When I try to flash a stock ROM with Odin it fails on system.img because the partition is too small. Heimdall fails to "to initialise protocol". I only have access to Odin, fastboot and nvflash. No adb and the device is stuck on a boot loop. Am I simply out of luck?
sgeos said:
Excellent... but this is not working. I can flash recovery, but I can't get into recovery. When I try to flash a stock ROM with Odin it fails on system.img because the partition is too small. Heimdall fails to "to initialise protocol". I only have access to Odin, fastboot and nvflash. No adb and the device is stuck on a boot loop. Am I simply out of luck?
Click to expand...
Click to collapse
What image are you trying to flash via Odin? Have you tried to go back to bone stock 3.1 (http://forum.xda-developers.com/showthread.php?t=1342995) ?
How did you get into this situation, flashed an incorrect ROM? Seems odd to have partition size errors.
muzzy996 said:
What image are you trying to flash via Odin? Have you tried to go back to bone stock 3.1 (http://forum.xda-developers.com/showthread.php?t=1342995) ?
How did you get into this situation, flashed an incorrect ROM? Seems odd to have partition size errors.
Click to expand...
Click to collapse
I tried to install CyanogenMod for the SCH-i905, but it failed to install. ROM Manager recommended the wifi ROM. I installed that and it worked without sound. I figured if one wifi ROM works, another one should too, right? Big mistake. I flashed CleanROM and have been in a bootloop ever since.
I can flash with fastboot, nvflash and Odin, but all of them fail to flash system.img. I dumped the system partition and partition information with nvflash, and it appears to be 256M. The system.img is larger than 256M in all of the ROMs I have found that can be flashed with Odin. I'm pretty sure the system.img in EG01 is 312M, but I will download it again and try to reflash after recharging the unit. There is a custom ROM with a system.img that is less than 256M, but it appears that ROM can only be flashed via recovery and I can not get into recovery.
Unless something is totally wonky, it seems like I should be able to reflash *if* I can repartition. I know how big I want the partitions to be, but I do not know how to repartition the device. PIT files are nowhere to be found. (At this point I have backups of all but the user data partition.)
I downloaded EG01 yet again and tried to flash it. The recovery.img file flashes to SOS without issue. The system.img file fails to flash to APP. Odin fails with the following output:
Code:
<ID:0/004> Added!!
<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> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The following is displayed on the device:
Code:
WriteExt4Partition: Fail to OpenCompExt4![err:0xa]
DownloadPartition_odin: Fail to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Fail to DowloadPartition_odin![err:0xa]
A peek inside the tar file indicates the system.img is indeed a little over 312M. I think the flash is failing because the APP partition is only 256M. FWIW, the SOS partition is 5M and recovery.img is ~4.28M so a successful flash makes sense here.
Code:
$ tar -tvf PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar
-rwxr-xr-x 0 0 0 4485120 Jan 1 2009 recovery.img
-rwxr-xr-x 0 0 0 327200196 Jan 1 2009 system.img
-rwxr-xr-x 0 0 0 9376048 May 2 2011 cache.img
-rwxr-xr-x 0 0 0 16 May 2 2011 fusetrigger.bin
-rwxr-xr-x 0 0 0 10747904 Jun 24 2011 lte_modem.bin
-rwxr-xr-x 0 0 0 3962240 Jul 4 2011 modem.bin
-rwxr-xr-x 0 0 0 4051200 Jul 8 2011 boot.img
$
So far as I can tell, there are no tools that I can use to partition my device. I can not find any files to repartition my SCH-i905 with nvflash, Odin or fastboot. Am I simply out of luck? (Anyone who wants to help is free to PM me if that makes sense in this case.)
Had a feeling that the wrong ROM was flashed at some point; ROM manager should not be used for these tabs. As you just found out, the structure of the different variants of the 10.1 is indeed different. I'm not sure how to fix the issue, hopefully someone can chime in who does.
Sent from my SCH-I905 using Tapatalk 2
muzzy996 said:
Had a feeling that the wrong ROM was flashed at some point;
Click to expand...
Click to collapse
Twice, actually. ROM manager recommended CyanogenMod for the wifi tablet. It worked without sound, and I figured if one wifi ROM works they all should, right? Big mistake. I've been in a boot loop ever since flashing CleanROM.
muzzy996 said:
ROM manager should not be used for these tabs. As you just found out, the structure of the different variants of the 10.1 is indeed different.
Click to expand...
Click to collapse
These tablets are confusing at first, but this ordeal has taught me a lot. There should be a sticky post at the top of these forums warning people not to flash anything until they know the version of their device, and the model the ROM will run on. It should also warn about ROM manager and state "when in doubt do not flash anything".
muzzy996 said:
I'm not sure how to fix the issue, hopefully someone can chime in who does.
Click to expand...
Click to collapse
My guess is that I could restore my tablet with nvflash dumps of a working partition table. Maybe parts 2 ~ 4 (BCT, PT, EBT)? I'm not sure what the GP1 partition is. I'm also not sure if partitions like MDM or LTE need to be intact for the tablet to run. I may have wiped something out with fastboot before I figured out how all of this works (this would be after getting stuck in a boot loop.).
If someone with a working SCH-i905 is willing to work with me, I should be able to restore my tablet. If anyone is feeling helpful, please PM me.
The link to the thread is not accurate
eejimen said:
Hi Tweetatoo. I'm not saying this to be an A-hole but this information can be found with a simple search on this board.
Here's the thread you are looking for, click thanks button if it helps.
http://forum.xda-developers.com/showthread.php?t=1444714
You will only need to start from step 5. Be sure to read and follow the instructions completely.
Click to expand...
Click to collapse
Hello - I know you were not trying to be an "A-hole" as i am not either. The link you provided is to a gingerbread root (3.2)... the original post stated ICS (4.04). So though you may not have been trying to be an A-Hole.... i think you may have made yourself look like one I am off to find out how to root my SGT 10.1 LTE (SCH-i905) running ICS 4.04 - If anyone has advice on where to find a How To, please let us know. Thank you -Bryan
See here: http://forum.xda-developers.com/showthread.php?t=1888755.
You DO NOT need to flash the first link in the original post of that thread but you should download superuser using the second link and clockwork mod recovery from droidbasement.com. It is best to disable auto restart in Odin when you flash CWM because the tab will boot into android and erase CWM if you don't catch the proper key presses quickly enough once Odin flashes, so uncheck that option and monitor Odin for a successful flash. Reboot into recovery and install superuser. Get busybox installer via the Play store and install busybox. At this point you can install a root checker from play store to verify root. You will have lost cwm at this first boot into stock ICS but root will have been installed and will remain on subsequent boots from this point on.
I did not try any other kernels to see if I could find one that would allow me to keep cwm so anyone looking to do that is on their own and does so at their own risk.
This is all I remember for stock ICS since once I had it I quickly went into CM9.
Sent from my SCH-I905 using Tapatalk 2
I did something stupid on my MDK S4.
I used the TWRP app to flash the latest version of TWRP recovery, but instead of selecting JFLTEVZW, I selected the recovery for DEB (my nexus 7 lte tablet).
So, nothing will boot on the phone, and I need to use ODIN to flash a factory recovery.
Can anyone point me where to download the ODIN recovery file for MDK ?
Oh my gosh is this phone in trouble.
Trying to ODIN everything back to stock with PDA file I get:
Initialization..
Get PIT for mapping..
There is no PIT partition.
All threads completed.(succeed 0 / failed 1)
Removed!!
Added!!
So, where can I find a partition (PIT) file for the Verizon S4 ?
OK, solved everything.
I had been using an old USB cable which had come with my ancient droid-x phone.
I switched to a nice newer thicker USB cable, and was able to flash the stock mdk recovery using Odin.
Then booted cyanogenmod 12, ran TWRP app to install latest TWRP recovery.
The end