[Q] Failed rooting of GT-I9195 - Galaxy S 4 Mini Q&A, Help & Troubleshooting

I have been trying to root my Galaxy S4 Mini (GT-I9195). I successfully installed clockworkmod recovery (v6.0.4.6) and that seems fine... but I currently have an expensive brick after attempting to root. I've tried GT-I9195_RootKit_v2.zip and S4Mini_RootKit_v2.zip (I don't know the difference between these, they are very different sizes).
Whichever of the two files I use, the rooting appears successful, warranty is now void... install from sdcard complete... etc... but upon reboot it shows the initial screen (phone name & model, with "set warranty bit: kernel"), then screen goes black, startup noise plays (sometimes it cuts out before finishing) and then nothing. I've tried various cache wipes, data wipes / factory resets but no luck.
I'd appreciate any suggestions you may have.

helenst said:
I have been trying to root my Galaxy S4 Mini (GT-I9195). I successfully installed clockworkmod recovery (v6.0.4.6) and that seems fine... but I currently have an expensive brick after attempting to root. I've tried GT-I9195_RootKit_v2.zip and S4Mini_RootKit_v2.zip (I don't know the difference between these, they are very different sizes).
Whichever of the two files I use, the rooting appears successful, warranty is now void... install from sdcard complete... etc... but upon reboot it shows the initial screen (phone name & model, with "set warranty bit: kernel"), then screen goes black, startup noise plays (sometimes it cuts out before finishing) and then nothing. I've tried various cache wipes, data wipes / factory resets but no luck.
I'd appreciate any suggestions you may have.
Click to expand...
Click to collapse
you can try this,it works like a charm:http://forum.xda-developers.com/showthread.php?t=1980683

helenst said:
I have been trying to root my Galaxy S4 Mini (GT-I9195). I successfully installed clockworkmod recovery (v6.0.4.6) and that seems fine... but I currently have an expensive brick after attempting to root. I've tried GT-I9195_RootKit_v2.zip and S4Mini_RootKit_v2.zip (I don't know the difference between these, they are very different sizes).
Whichever of the two files I use, the rooting appears successful, warranty is now void... install from sdcard complete... etc... but upon reboot it shows the initial screen (phone name & model, with "set warranty bit: kernel"), then screen goes black, startup noise plays (sometimes it cuts out before finishing) and then nothing. I've tried various cache wipes, data wipes / factory resets but no luck.
I'd appreciate any suggestions you may have.
Click to expand...
Click to collapse
Which instructions did you follow to root because it should have been these? The GT-I9195_RootKit_V2 zip is not mentioned and should not be used. It sounds like you have wiped your ROM thus it has nothing to run after initial boot, so try to flash any of the ROM's available - don't ask which one is best, if you read some signatures you can see what some folks are using.

MarkAndroid.UK said:
Which instructions did you follow to root because it should have been these? The GT-I9195_RootKit_V2 zip is not mentioned and should not be used. It sounds like you have wiped your ROM thus it has nothing to run after initial boot, so try to flash any of the ROM's available - don't ask which one is best, if you read some signatures you can see what some folks are using.
Click to expand...
Click to collapse
Thanks... easy now you've told me what's wrong! Was thinking I'd probably stick with the stock ROM but seeing as I've wiped that anyway, have stuck cyanogen on there and all good again.
I think I got the file from the instructions here... it was in one of the rar files. http://dottech.org/147716/how-root-samsung-galaxy-s4-mini-gt-i9190-gt-i9195-and-install-cwm-guide/ - would've saved a bunch of time if I'd found the right instructions in the first place. Oh well, it's nice to have a phone again

helenst said:
Thanks... easy now you've told me what's wrong! Was thinking I'd probably stick with the stock ROM but seeing as I've wiped that anyway, have stuck cyanogen on there and all good again.
I think I got the file from the instructions here... it was in one of the rar files. http://dottech.org/147716/how-root-samsung-galaxy-s4-mini-gt-i9190-gt-i9195-and-install-cwm-guide/ - would've saved a bunch of time if I'd found the right instructions in the first place. Oh well, it's nice to have a phone again
Click to expand...
Click to collapse
Thats good:good:, CM should be slicker and easier on the battery than stock (autobright actually works properly for example). If you need to go back to stock you can always find it on the sammobile site
I've never come across that web site you linked to. Best to use xda in all things Android

I've got the same problem
MarkAndroid.UK said:
Which instructions did you follow to root because it should have been these? The GT-I9195_RootKit_V2 zip is not mentioned and should not be used. It sounds like you have wiped your ROM thus it has nothing to run after initial boot, so try to flash any of the ROM's available - don't ask which one is best, if you read some signatures you can see what some folks are using.
Click to expand...
Click to collapse
Exactly the same problem as helenst' one here. After reading for 3 hours, I am stuck and can not understand what is the solution.
Please, help me! This is my mother's phone and I have to fix it till the next morning.
Thanks!
PS: I thought that the problem was due to using the wrong file in ODIN 3.09, that is I clicked on AP, but browsed the recovery-clockwork-6.0.5.1-serranoltexx.tar , which is .ZIP, instead of the the MD5 file.

Related

[Q] Boot Loop

I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....
Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium
Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

[Q] Recovery bootloop after Odin/Kies/Heimdall STOCK flash, only boots to DL mode

Hi folks, long time reader, first time noob answer seeker.
I'm no stranger to rooting, flashing, hacking about and such - I even spend most of my day as a software engineer, and I've finally given up on this one - so here I am (rock me like a hurricane), please be kind.
SM-900T - It was rocking pretty darn well on Jedi Elite which I had flashed over rooted stock 4.3 MI7 - then (probably after one too many XPosed modules) it just kept rebooting randomly. Thinking it was no biggie, I thought I could just reflash to stock and call it a day. Thirteen or so flashes later, I gave up on 4.3 and figured I'd just take the thing up to 4.4.2 NB4 by upgrading everything to 4.4.2 via Kies.
That's when I first ran into the bootloop issue, read a lot about it, and managed to get it up(ish) on stock, rooted, with Philz 6.X... Couldn't flash a ROM to save myself and wound up with another soft brick.
Flash forward to Friday - decided to start from scratch again - attempted to flash stock 4.4.2 from Kies, from Odin, From Heimdall... Nothing seems to be able to get me out of the current state it's in:
Only boots to download mode. Flashes seem to work fine, but on that first reboot where it tries to go to stock recovery to finish up on the device itself, it never gets there - boot loops trying to load recovery no matter how it wants to get there. If I pull the battery and start up (either straight to system or by cancelling out of download mode), it boot loops trying to load system. Boots fine to download mode, where I attempt to flash again with the same results.
Yes, I've tried Odin 3.0.9, 3.0.7, 1.8.5, Heimdall on Mac, Heimdall on Windows, Kies on Mac, Kies on Windows - repartition via PIT and not. Installed, uninstalled, and reinstalled all software and drivers multiple times, tried multiple cables on multiple USB ports.... Most of the time it looks like it's going to be fine (sometimes the flash fails, usually through Kies), but never surivives that first reboot after the flash.
Every answer I've seen says to do the things I've already done or cannot do (flash stock via Odin, pull the battery and boot to stock recovery and do a factory reset - which I'd LOVE to do, but can't). No problem recognizing the sucker on the PC/Mac
Next step: try flashing a N9005 ROM...
Any other thoughts? I do have another N900T that's working but has a blacklisted IMEI, and I've been tempted to swap the IMEIs a last resort (although either I'm too dumb to make it stick, EFS pro says it succeeds in writing the IMEI after I do a EFS format, but it doesn't stick.... Either I'm missing something, or I need a UART cable) - is there a way of swapping just the radio hardware or just the internal storage? OR, is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Failing any of these options, perhaps I'll wait for an Odin-flashable 4.4.3 if such a thing exists - or, hope to get lucky and swap it out at a store praying they don't see I've tripped Knox.
Looks like you've tried almost everything. Take it in and have them swap it.
Sent from my SM-G900T using Tapatalk
Coming from you...
noobtoob said:
Looks like you've tried almost everything. Take it in and have them swap it.
Click to expand...
Click to collapse
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
bondidave said:
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
Click to expand...
Click to collapse
Well, I do have a few ideas... Got done questions though.
1. Do you have an external SD card?
2. It goes all the way through flash on 4.4 even with heimdall?
3. Is there anything you have left out? Even the smallest detail can help, and by the op you are detail oriented, so I just need to know.
Sent from my SM-G900T using Tapatalk
... is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Click to expand...
Click to collapse
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring.
If that doesn't work then let 'noobtoob' walk you through booting with the removable sdcard. Your second N900T will be needed to write the data to the sdcard. If this works then you can 'dd' write stock partitions to an sd card with #2 then 'dd' write them in #1.
If either of those works then unroot and take it in for warrenty exchange.
Frank
bondidave said:
... then (probably after one too many XPosed modules) it just kept rebooting randomly.
Click to expand...
Click to collapse
This also indicates data corruption, and this is what started it all. Since you have tried various cables and computers that leaves the device, probably the USB port.
Frank
probably the USB port.
Click to expand...
Click to collapse
Swapped the main board with the working phone to rule out the USB port - still no luck.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Thanks again guys
bondidave said:
Swapped the main board with the working phone to rule out the USB port - still no luck.
Click to expand...
Click to collapse
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Click to expand...
Click to collapse
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Click to expand...
Click to collapse
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Click to expand...
Click to collapse
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Frank Westlake said:
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Click to expand...
Click to collapse
This was for hard brick method and no one has verified it works on 4.4 KK yet. There is an image in there though. My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response. Located here you will find the kkunbrick.img. There is still a problem flashing anything through heimdall after updating to the 4.4 bootloader, so there is no way to tell if the phone actually took the recovery. I have had to switch to Odin for everything afterwards, and in personal experience 3.07 works best with my phone.
@bondidave I was thinking skipping the sd-card trick for now, and trying just a few other things first. Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Also if you have an external find the efs fix zip and have handy on an sd-card, do the same steps above except the nandroid restore. Basically if we can get into a recovery we should be ok. I had a similar issue when it was just booting over and over into download mode and this was how I fixed it. I have never used the efs fix zip, but many others swear by it. I was able to recover fortunately enough.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
As far as making a complete system backup of your current phone, I highly recommend against it, unless you just want to extract information from it and not re-write it. This could definitely cause some system corruption on a new device.
If none of these methods work, then try and have them swap it under warranty.
Frank Westlake said:
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values
Click to expand...
Click to collapse
Yessirreeebobbyjimmy, tried several copies from several different places - that and Kies is a moron and redownloads it every time anyways.
noobtoob said:
My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response.
Click to expand...
Click to collapse
I download these things just to have them handy if something fails.
Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Click to expand...
Click to collapse
I don't think he got that far into installing 4.4, but I recommend not using anything that was saved after this problem began. If the problem was caused by corruption then the restore will reinstall the corruption.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
Click to expand...
Click to collapse
If the problem is bad USB or other bad hardware causing corruption during transfer then the SD-card boot will get past that, then transferring the rest of the partitions by SD-card will continue to be corruption-free. He could then trade-in the phone.
But you are right -- he should try everything else before the SD-card boot. Because if something else succeeds then maybe the hardware is fine, and if he went immediately to SD-card boot he wouldn't know that.
Frank
Thanks for the advice guys - I'm going to try the backup from my other phone, then the efs fix, then the sd-card boot... I'll report back, wish me luck.
A nandroid previous failure, or a ROM install from external SD card was all I meant.
Sent from my SM-G900T using Tapatalk
I got some answers I was looking for here. Glad I read this thread.
Lorettaa said:
I got some answers I was looking for here. Glad I read this thread.
Click to expand...
Click to collapse
Glad something good came out of my frustration!
Here's a quick update: I've done everything but the boot from SD card with no luck (and actually thought I had hard(er?) bricked it for a while after trying to copy over a few images from the other phone - turns out it needed to stay with the battery out for at least 20 minutes).
Good news - walked into a TMO brick-and-mortar last night, showed the guy my endless bootloop, and a replacement is on its way to my house for an affordable $20 warranty service fee.
At this point, I'm thinking the internal flash memory is just bad - as a software engineer, I'm ok with chalking this one up to a hardware issue (as much as I was hoping that my first post on XDA would result in some new profound solution to a longstanding issue common to a few folks).
Oh well - new Note 3 on it's way, and a new S5 shortly behind it (didn't hold out much hope on TMO hooking me up, so I ordered an S5)... let the battle of the Samsungs begin!
Thanks again to you guys who helped out - and the whole XDA community in general, I am very grateful.
Finally you made it fix and enjoy the battle between your phones
Well, sucks it couldn't be fixed, but glad you got a replacement on the way. It pretty much sounded like the partitions were well over written before we attempted anything, but always worth a shot.
Sent from my SM-G900T using Tapatalk
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring. :good:

[Q] Kernel Panic Upload mode

My SM-T210 (Galaxy Tab 3 7.0 Wifi) XSP region which was running fine for over a year starting giving me the Kernel Panic Upload Mode errors in the last few days.
It is absolutely stock - still running Android 4.1.2, never rooted, etc.
From previous threads on this error, it seems that doing a factory reset in recovery ought to fix this. However, I can't quite seem to do the factory reset. Doing it from Android settings just seems to go into recovery. And from recovery, after telling it to do the data wipe/reset and rebooting, I'm back into Android with all of my apps and settings still in place.
So I'm a newbie and don't know what to do from here. Any suggestions please?
Ok, I've tried to flash the TWRP recovery by following the instructions at http://forum.xda-developers.com/showthread.php?t=2437219. But even after getting "RES OK", I did the reboot into recovery, and went straight back into the stock recovery. wtf... it seems as though writes to the internal storage are accepted but ignored.
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
webbrowser said:
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
Click to expand...
Click to collapse
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know ?
-DUHA
DUHAsianSKILLZ said:
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know
-DUHA
Click to expand...
Click to collapse
Roger. I've tried to flash the TWRP recovery via ODIN, but the writes did not seem to work despite "RES OK". Flashing recovering is required before I can change the kernel right?
For what it's worth, my symptoms seem to match the "emmc brickbug".
I've found what appears to be instructions on how to fix this after the brickbug has occured here (these are for different devices, but I suppose it oughta work):
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showthread.php?t=1667886
Unfortunately, I can't seem to run the zips from my stock recovery, as signature verification fails. And I don't think I can install a custom recovery at this point now, since all writes seem to fail. So I'm still stumped, and I think I have a brick :crying:

New to flashing/upgrading

Hi folks,
I'm after some information. My Nexus 4 is about kaput now with the battery lasting about 4 hours or so with a full charge so I am looking to move over to my S4 mini for a while before buying an upgrade.
However i don't fancy rolling back to 4.4.2 from 5.1.1 as have got accustomed to it now. so there for I am looking to upgrade/flash it or whatever.
I am quite the novice and have not done this on any phone before so I am looking for a bit of help,
I have looked over xda and read some bits but think someone just telling me would be better, i'm not a tech dunce but I am not 100% confident in this at the moment as there seems to be more than one way of doing this.
What do i need to do first and foremost to make the process go as planned?
I take it I need to "root" the phone first (what does this do ? give me access to the firmware level? is that it?) using a "recovery tool" as they are called (is that right?)
Then after I have done that I can install a fresh ROM onto the phone and basic app's etc.
I have seen these guides:
http://forum.xda-developers.com/showthread.php?t=2364980
and
http://forum.xda-developers.com/gal...i9190-i9195-cyanogenmod-13-0-s4-mini-t3276141
Is it just a matter of following them or are there other things I need to do first, in between or after?
I am not bothered about anything being saved on the s4 mini it can be wiped clean and start a fresh, I don't need any of my data on it backed up
A quick bullet guide or acknowledgement of the two threads above or pointing me towards some better ones would be great and any pointers or descriptions of the acronyms or places in menu's which may have had their names changed or have been moved.
Many thanks Everyone,
Dahools
Hi!, you dont need to worry about anything, the only thing that you need is follow these guides, but make sure if you have the correct variant.
First Install Kies and connect your phone to it( For correct phone drivers). And after phone connect wells, Close kies from task manager.
You Need Odin to install a recovery software in your phone(TWRP, Clock Recovery, Philip). I only used twrp now.
Here is link below with instruction. Download recovery for your variant(i9190,i9192 or i9195 base on your model).
http://forum.xda-developers.com/showthread.php?t=2678420
Suppose if you install TWRP. Boot into recovery, And click Wipe, Do a factory reset , Clear Devil cache, Then go back and install your Firmware(cm12.1 or cm13 for your intended model). And flash Gapps as well. Then reboot. And you are done.
I have tried TWRP for both i9190 and i9192 model. and installed custom roms. Work fine.
Good Luck.
thanks fellas
I went for it with the original links and it worked. (eventually) A bit of user error on my part missing recovery mode on reboot first time and thinking it was done when it wasn't. Only putting the first bit in (root kit v2) then not realising how to flash the next parts. A bit of persistence paid off.
I have a I9195 model and rooting with that clockwork worked then loading the CM13 and then the Gapps. All one after the other in one go finally worked for me! so so far so good, just getting used to Android 6 now I think everything is working though, not put my sim in yet. will do that tomorrow.
If anyone was to follow what I did the big tip I would say is copy everything onto the SD card before you start anything, not as I did at first just putting the first bit on then thinking I can copy the next bit on later . . .

Categories

Resources