So, I deleted system when I changed ROM for the first time (always had HTCs so that's how it worked). That went well(!) Then my phone repeatedly refused to boot into recovery, just restarted, but I got lucky one time and it did, so I flashed the ROM I had on there as soon as I could. I knew that was buggy but it worked. Completely forgot about the backup I previously made. So after a few days of trying to get into recovery it finally happened today, then I tried to go back to that restore, but it failed. Then I forgot to backup what I had now, so I'm back to nothing, because CM11 won't flash. Then when I tried to restore the update for a second time, the screen got brighter and brighter and became corrupt, so I just unplugged it. There seems to be no damage, and I'm in TWRP again, but upon mounting to my computer it isn't recognised. So, is there a 4.3 100% STOCK ROM for the i9505 that I could flash in Odin (or any ROM that I could flash in Odin) that could get this phone working again? Unless there's a way to downgrade to 4.2, then I'll take that too.
Edit: I'm in the UK (BTU) and found this tar file: I9505XXUEMK8_I9505BTUEMK5_I9505XXUEMK8_HOME.tar. I believe this should work, as I have the i9505 and I'm in the BTU region, so should I just flash that in Odin?
kylepont said:
So, I deleted system when I changed ROM for the first time (always had HTCs so that's how it worked). That went well(!) Then my phone repeatedly refused to boot into recovery, just restarted, but I got lucky one time and it did, so I flashed the ROM I had on there as soon as I could. I knew that was buggy but it worked. Completely forgot about the backup I previously made. So after a few days of trying to get into recovery it finally happened today, then I tried to go back to that restore, but it failed. Then I forgot to backup what I had now, so I'm back to nothing, because CM11 won't flash. Then when I tried to restore the update for a second time, the screen got brighter and brighter and became corrupt, so I just unplugged it. There seems to be no damage, and I'm in TWRP again, but upon mounting to my computer it isn't recognised. So, is there a 4.3 100% STOCK ROM for the i9505 that I could flash in Odin (or any ROM that I could flash in Odin) that could get this phone working again? Unless there's a way to downgrade to 4.2, then I'll take that too.
Edit: I'm in the UK (BTU) and found this tar file: I9505XXUEMK8_I9505BTUEMK5_I9505XXUEMK8_HOME.tar. I believe this should work, as I have the i9505 and I'm in the BTU region, so should I just flash that in Odin?
Click to expand...
Click to collapse
I'd rather suggest putting a new, clean rom on the phone by copying the rom onto your sdcard (via cardreader if it doesnt mount via usb) and installing it through TWRP on the phone itself instead of through odin.
Or is there some point I am missing why you specifically want to go back to a stock rom? Since a restore is out of the question why not go forward?
Can't answer you on that specific file, sorry.
kajing said:
I'd rather suggest putting a new, clean rom on the phone by copying the rom onto your sdcard (via cardreader if it doesnt mount via usb) and installing it through TWRP on the phone itself instead of through odin.
Or is there some point I am missing why you specifically want to go back to a stock rom? Since a restore is out of the question why not go forward?
Can't answer you on that specific file, sorry.
Click to expand...
Click to collapse
The main reason why I wanted to go back to stock was because virtually nothing worked. Scrolling on recovery was broken, getting into recovery itself was a rarity, the charging screen while the phone was switched off but plugged in didn't work, to name but a few problems. I'm just going to stock to fix all of that, by going back to stock, then I'm going to move forward. Go one step backwards to end up two steps forwards.
Anyway, I just did a #YOLO (help pls), flashed it and the phone appears to work perfectly again, to my relief. *breathes heavily*
Solved I see. U flashed the correct one for ur region
Related
Can I get a little help here? I have a rooted, otherwise stock i337 that I just used the TWRP root app. I wanted to make a backup of my phone before I flashed a new rom. It downloaded jflteatt and I verified and installed it to /dev/block/mmcblk0p21. then i tried to make a backup, and i'm stuck at "Downloading.... do not turn off target!!!" In the upper left corner there's a "Could not do normal boot. ODIN Mode.
I found the post "[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3" but am hesitant to use it, as I am not sure that is what I need to do. I also found some other similar posts, but for different devices so I am again hesitant to rely on those.
I tried pressing home, power and volume down, but it just resets back to this screen. Also, I originally posted this request on the TWRP page, but I think it should be here. If so, I will delete it there.
Please help?
@kamikazees
If you could give more detail that would also help other to help u....such as what firmware that u are running before bricked...... well seem to me that u are either MF3 or MK2 firmware and u installed TWRP ...... u can only install safestrap recovery if u are on MF3 or MK2 firmware. ....Follow my thread http://forum.xda-developers.com/showthread.php?t=2621279 it should get u back to MK2 firmware. .....goodluck
Swyped From MK2 Dark Venom SS Edition
Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.
kamikazees said:
Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.
Click to expand...
Click to collapse
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.
DeadlySin9 said:
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.
Click to expand...
Click to collapse
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
The first one is in img format and won't work through ODIN, but you can use those commands from terminal emulator to flash it if you download it. Otherwise, the TAR files do work just fine.
kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
If you are rooted and can actually boot the phone then I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery. I've been using Safestrap and TWRP since I was on MF3. I have also successfully flashed the tar files through Odin to get to MK2 with no problems. If you are rooted then its a really good idea to use Safestrap with TWRP for a recovery. Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable. The stock recovery on this phone is pretty much useless.
megamanDJ said:
...I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery... Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable.
Click to expand...
Click to collapse
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!
kamikazees said:
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!
Click to expand...
Click to collapse
There is actually a way to flash a rom to the stock slot, but I haven't done it. Somewhere in the Safestrap threads explains how to do it. I think you can even get it back to normal if you change your mind.
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
GST_Diandre said:
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
Click to expand...
Click to collapse
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Journyman16 said:
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Click to expand...
Click to collapse
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
GST_Diandre said:
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
Click to expand...
Click to collapse
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Journyman16 said:
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Click to expand...
Click to collapse
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
GST_Diandre said:
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
Click to expand...
Click to collapse
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Journyman16 said:
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Click to expand...
Click to collapse
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
GST_Diandre said:
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
Click to expand...
Click to collapse
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Journyman16 said:
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Click to expand...
Click to collapse
Okay great So where exactly do I get TiBu for pc?
GST_Diandre said:
Okay great So where exactly do I get TiBu for pc?
Click to expand...
Click to collapse
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Journyman16 said:
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Click to expand...
Click to collapse
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
GST_Diandre said:
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
Click to expand...
Click to collapse
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Journyman16 said:
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots
I thought I could flash the China Qualcomm recovery version of TWRP recovery to my phone. After rooting and installing the official TWRP app, I flashed the heroqlte firmware img and rebooted. I then got the screen saying the phone was locked and to call my carrier.
I hard-shutdown the phone and booted back into the phone successfully. I have not yet tried booting into recovery.
Is there a way I can re-flash stock recovery?
MJPByron said:
I thought I could flash the China Qualcomm recovery version of TWRP recovery to my phone. After rooting and installing the official TWRP app, I flashed the heroqlte firmware img and rebooted. I then got the screen saying the phone was locked and to call my carrier.
I hard-shutdown the phone and booted back into the phone successfully. I have not yet tried booting into recovery.
Is there a way I can re-flash stock recovery?
Click to expand...
Click to collapse
It's (Surprisingly) not hard bricked, meaning you should be Able to get into download mode. If you're able to, just flash the stock firmware through Odin like normal.
The only thing is that this is an SM-G930AZ. I can't seem to find the stock firmware anywhere. I was able to at least get Odin to recognize the device, and even Kies can recognize it. It just sat at 0% for installing firmware in Kies.
MJPByron said:
The only thing is that this is an SM-G930AZ. I can't seem to find the stock firmware anywhere. I was able to at least get Odin to recognize the device, and even Kies can recognize it. It just sat at 0% for installing firmware in Kies.
Click to expand...
Click to collapse
My boy, doing a quick Google search brought me here. I don't know which firmware your phone was last on BUT, if it's wrong it will just fail to flash. Try the firmware posted here.
https://forum.xda-developers.com/att-galaxy-s7/how-to/factory-odin-files-sm-g930az-t3569831
Thanks, good stuff. Could I get away with just flashing the BL part if I want to keep the current rom without starting fresh again?
MJPByron said:
Thanks, good stuff. Could I get away with just flashing the BL part if I want to keep the current rom without starting fresh again?
Click to expand...
Click to collapse
Sorry to say but no. It all has to be re-flashed to become a clean OS. Hope it works for ya
Even if all I want is a stock recovery, it has to go back to full stock? Bleh.
Well, at least it's just a question of throwing time at it.
Thanks again!
MJPByron said:
Even if all I want is a stock recovery, it has to go back to full stock? Bleh.
Well, at least it's just a question of throwing time at it.
Thanks again!
Click to expand...
Click to collapse
No problem man. Glad I could help.
My friend got an old phone from his dad, who had an old custom ROM installed on it, and asked me to return it to the original software.
I used ODIN 3.09 and installed the appropriate ROM which I downloaded from Sammobile.
The phone went into a bootloop, so I wiped the cache and when that didn't work, I wiped all data. After that the phone booted into the Welcome screen and my friend started to configure it. In the middle of the process, the phone rebooted, and now it loads into the Welcome screen, but reboots after a few seconds.
After that I've tried reflashing the software and doing multiple resets, to no avail. Any ideas?
Please let me know of any Ideas. I am very ashamed of damaging my friend's phone.
PS: I should say, I put a bootloader into ODIN the first time I flashed the software because some tutorial recommended it and I haven't seen that requierement in any other tutorial since. Might this be the cause? How could I test that?
What model what firmware what bootloader ??
JJEgan said:
What model what firmware what bootloader ??
Click to expand...
Click to collapse
The phone is a Note 3 N900 UB, the firmware I installed was N900UBSEBQB5, and to be honest, I can't quite tell what the bootloader is, the file I downloaded is just called "bootloader".
the file I downloaded is just called "bootloader
My guess is that's the fault as bootloaders are named same as firmwares
Example >>> BL_N9005ZSUGPJ2
Could be a bootloader for anything .because some tutorial recommended
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
larrycn said:
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
Click to expand...
Click to collapse
Thats wrong .
Greetings,
Yesterday I was about to change my current rom as my phone was running on a custom rom that I found here on the forum with a CWM recovery.
So I went into recovery mode to make a nandroid backup for my device just incase of something bad happens.
When I started the backing up process it took a min or 2 to start and transferring the data and afterwards the device turned off and it went to a black screen with the android logo and it says downloading don't turn off target..
the thing is it still on that screen since yesterday and I can do anything about it because it took longer than the usual as the youtube videos showed me.
I tried turning off the device and turning it back on and still no luck.
I went to download mode to bascially flash a TWRP recovery or a root using odin to later on flash the rom that I wanted but I had no luck as every single time I try to flash something in odin it says "There is no PIT partition"
I looked up online and I found few PIT files and I tried again and its the same thing but it says re partition operation failed something like that.
after doing some research I found even If I flashed the stock firmware it won't change anything as the device won't accept it because of the PIT thing.
I really need your help guys, what can I do now ?
Try using different USB cables and USB 2.0 ports to flash a stock ROM with Odin.
audit13 said:
Try using different USB cables and USB 2.0 ports to flash a stock ROM with Odin.
Click to expand...
Click to collapse
I did and I still have the same issue..
I even tried a different computer and nothing really works, keep in mind that I have downloaded the official stock rom and tried to flash that too and I still have no luck.
I really need help guys :/
Find the correct PIT file and flash that or take for service repair .
Alright I'm writing this reply to whoever searches online for a similar problem.
I fixed my phone long time ago and the problem was ... "the phone USB port"
it turns out my port isn't really good as it had issues in the past and it was changed but I didn't know that until recently and I completely forgot about it.
I didn't fix my port though but how did I fix the phone ?
well it turns out even if your port was bad (depends on the ports condition of course) getting an original cable can help you flash something isn't big such as a root or a recovery mode.
in my case I used an original cable a normal micro USB but after using an original USB 3.0 cable I was able to flash a root and a custom recovery, yes I tried flashing a stock firmware but it I didn't work because of how my port is acting I was kinda limited to the things I can flash so I was able to flash small files but not an entire operating system.
So I flashed a root and a TWRP custom recovery in order to be able to flash an entire OS through the phone itself without the need of plugging it to my computer so I uploaded my custom ROM on an SD Card and flashed it through the recovery mode and I was back in business!
I can safely say the case is solved, I don't know if you guys close the solved topics here or something but thanks for everyone's help.
SEE YA LATER
But port is not PIT problem .