Related
So first, the reason why i'm doing this in the first place is no matter what I do my phone freezes after the first few moments of being in android. Right now it won't make it in Activation, I effed it up so bad that I goto the *Phone* *Yellow Explanation Mark* *Computer* screen. From there I flashed CF-Root to VIA PDA through Odin 3. This got me back to where I was.
So now I figured I want to completely erase every go back to factory, so I downloaded VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar, and VzW-PHONE-ODIN-SCH-I515.EK02_LTE.tar. Every single time with out fail it hangs up on RADIO-CDMA.
Any suggestions? Anything else I should try in my predicament besides ODIN? I just now thought that perhaps I should download those two files from a different source , perhaps my download was corrupt.
Any help would be really appreciated.
badgrafix said:
So first, the reason why i'm doing this in the first place is no matter what I do my phone freezes after the first few moments of being in android. Right now it won't make it in Activation, I effed it up so bad that I goto the *Phone* *Yellow Explanation Mark* *Computer* screen. From there I flashed CF-Root to VIA PDA through Odin 3. This got me back to where I was.
So now I figured I want to completely erase every go back to factory, so I downloaded VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar, and VzW-PHONE-ODIN-SCH-I515.EK02_LTE.tar. Every single time with out fail it hangs up on RADIO-CDMA.
Any suggestions? Anything else I should try in my predicament besides ODIN? I just now thought that perhaps I should download those two files from a different source , perhaps my download was corrupt.
Any help would be really appreciated.
Click to expand...
Click to collapse
To tell if your download's corrupt compare the md5 sum given to the one on your computer, if they match it's a safe bet that it's not corrupt. If you're on windows download this to check it and on *nix type md5 path to file in terminal to have the checksum printed out
But if it won't make it to activation, and fails on flashing the radios. There might be a hardware problem it's running into
Lets assume there is a hardware problem. Is there anything I can do to make it appear i havnt screwed with it as much as I had, so i can send it back for warranty? Will flashing all the stock stuff, and relocking be enough for them to accept my phone?
What do you mean it gets stuck at flashing radio-cdma? How long have you waited? I know it took approximately 3-5 minutes to flash my CDMA radio...
I've waited much longer then that. 10-20 minutes several times. Not only that but i've tried several methods of flashing. I've tried to flash through CWM, only to have it freeze. I've tried t Fastboot flash radio-cdma over, no go. I mean i've tried every thing I can Think of.
badgrafix said:
I've waited much longer then that. 10-20 minutes several times. Not only that but i've tried several methods of flashing. I've tried to flash through CWM, only to have it freeze. I've tried t Fastboot flash radio-cdma over, no go. I mean i've tried every thing I can Think of.
Click to expand...
Click to collapse
Did you try loading back a stock image from Google that includes radio's and Rom...
Check out Mskips tool in the dev section to put your phone back to stock using a stock image. The tool makes it real simple to do.
I DOWNLOADED A ODIN IMAGE FROM XDA:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.MD5
AND NOW THE PHONE WONT EVEN TURN ON, RIGHT AFTER ODIN FINISHED. IS THERE A WAY TO FIX THIS?
cnile said:
I DOWNLOADED A ODIN IMAGE FROM XDA:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.MD5
AND NOW THE PHONE WONT EVEN TURN ON, RIGHT AFTER ODIN FINISHED. IS THERE A WAY TO FIX THIS?
Click to expand...
Click to collapse
Difficult to follow your issue because you've started several threads all of which appear related or perhaps linked to the same issue. If it's one issue, it's always tidier to stick to one discussion thread as opening different threads could lead to you getting conflicting steers based on different members' understanding of the problem. Is this the same device you wanted to manually update to 4.3 from 4.1.1 or a different one? If so, I'd be surprised you opted to try the Odin route. Although there shouldn't be any problem with the Odin image you flashed as it was developed by a well respected XDA member, the recovery option would have been a safer way to go. Did you use Odin ver. 3.07 to flash this image as it seems to work well only with this version and did you get the <Pass> message at the end? If so, there may be nothing to worry about. Try pulling out the battery, wait several minutes, replace the battery and, if it doesn't power on normally, see if you can boot to recovery mode and do a hard wipe/reset. If you are unable to boot to recovery mode, then you may have a soft brick which can, thankfully, be recovered from. You will find the definitive guide to unbricking in the first page of the following thread. All the files you need can be found there too ...
http://forum.xda-developers.com/showthread.php?t=2549068
Hi Everyone,
I am a new owner of a soft-bricked SM-T700. I am feeling very down and need some advice. I will be as thorough as I possibly can and I would truly, truly appreciate some help and advice from you kind folks. This is the first time I have had a bricked device out of my many Android devices.
My PLAN:
-Root
-Custom Recovery
-Nandroid Backup
-Backup EFS
-Flash stock western country firmware
What HAPPENED
Today I bought a wifi T700. I bought it in my hometown, which is China. Whenever I buy a new Android device in China my first action is to ensure it doesn't have any hardware/warranty issues. I then go about reflashing a western firmware so I can use Google services.
1) First I rooted using CF-Auto Root. That worked fine. I confirmed that I had root using an app called root checker.
2) I then attempted to flash TWRP recovery by following the instructions here: http://teamw.in/project/twrp2/238
- First I tried flashing the .tar file using Odin. As soon as I hit 'Start' Odin froze and I got the Windows error saying "Odin Downloader Has Stopped Working", asking to close the program. I close the program. I tried this several times then rebooted. It seemed as though the phone booted fine.
- I then tried using their own software, TWRP manager, here: http://jmzsoftware.com/twrp-manager-4. This app just crashed every time I booted it. I submitted an error log.
- I then tried using 'Flashify' as suggested by someone here on XDA. Once I did that it said flashed successfully and would I like to reboot. I said yes. This is when my troubles started.
3) Upon reboot it immediately booted into a sparse looking 'Download Mode' screen, all in English (the normal one on mine has some Chinese too) without the volume button options to reboot or continue. It just went straight into this screen.
After trying to reboot the phone using several power button holds and key combinations, it appears I am stuck in this screen, so I thought I had no chance of doing a NADROID backup as originally planned, so I decided to try my luck and flash the western firmware.
I tried to flash the version of the firmware provided here: http://forum.xda-developers.com/showthread.php?t=2798835
http://www.androidfilehost.com/?fid=23501681358556680
It got all the way through the install until it hit the hidden.img and then failed. I've attached a screen capture.
A few notes;
I have tried using two different USB cables (the one that came with it, and the one that came with my HTC One). I have tried several USB plugs, including the one in the back of my PC. I allowed Odin to do it's MD5 check and it said the file checks out.
I have tried using the Kies emergency Firmware recovery. Pffft! As it that was going to work. Damn Kies.
I sound like I've still got my sense of humor, but actually I am really cut up about this. It is so much money for a tablet and now it is useless unless I can get s firmware that will flash.
I don't have my stock Chinese firmware. That is T700ZCU1ANF4/T700CHN1ANF4/T700ZCU1ANF4/T700ZCU1ANF4 (CHN).
Questions:
Does anyone know where I could find the stock Chinese firmware to try flashing back to that?
Does anyone have the .PIT file and instructions on how to flash that, because I have read in other threads that it solves the hidden.img problem.
Does anyone know why this may have happened and have any alternative suggestions?
Could it have been the TWRP that actually caused this? The thread here indicates others aren't having trouble. Why would it have frozen for me?
I will try anything at this point. I am desperate.
Thanks so much in advance. Please come through XDA! Please come through Galaxy Tab S owners!!!!!!
-------------------------------------------
CLOSURE EDIT: I managed to flash Australian firmware, after reinstalling Kies, uninstalling and reinstalled the device drivers. I also made sure all Kies processes were killed before flashing with Odin.
For people in a similar situation I would urge them to have patience and keep trying to flash stock firmware.
Private Message UpInTheAir and see what he thinks.
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
The program crashing is when you should back off from trying to flash. Reassess what you did and what happened and if it's failing at a point flash the stock back before rebooting.
Continuing blindly was the problem. On something as expensive as a tablet never continue past a point where something goes wrong without reflashing back to stock and starting again.
As eousphoros said Use heimdall and flash a recovery.
Good luck.
eousphoros said:
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
Click to expand...
Click to collapse
Hi All,
Thanks for taking the time to reply.
You are certainly right that it is my fault and I should have stopped at some point and reassessed what was happening.
Can you please give me some more information about the steps you have offered? I am researching heimdall now, but if you could give some steps or advice that would be much appreciated.
It's probably going to be difficult because I assume we are in different timezones. I will persevere and try to get this worked out.
I have downloaded Heimdall and understand that it is an alternative to using Odin.
I currently have three questions about Heimdall.
1. Do I need to do the install drivers step if I have already installed the drivers for my device? Is this some step that actually replaces the current drivers with ones that are required for Heimdall to operate? I ask them because when I list USB devices, my tab is not shown up as Samsung Composite Device. It is actually shown as two separate entries, looking like generic USB entries.
2. Do I need to have a valid PIT file in order to run a custom Heimdall flash?
3. Which partition should I select if/when I run the Heimdall flash?
I'm dying a little inside every time I look at my tablet
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
eousphoros said:
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
Click to expand...
Click to collapse
First of all, let me just say that OH MY F#@$ING GOD I THINK THE NIGHTMARE IS OVER!!!! I managed to flash the Australian Firmware successfully. It has now booted fine, I have factory reset and I am in the process of setting up the device afresh.
Having said that, when I do come to reroot and install a custom recovery, I will definitely take a look at yours. Was this here 12 hours ago? I looked and couldn't find anything about CWM except for a short thread and an unofficial port. I have never tried TWRP before and I will avoid it like the plague in the future. I have NEVER had trouble with CWM.
When (if ever) I get the nerve up to give this another go, I will try your CWM.
Thanks again.
I am so relieved right now.....
And make a Nandroid first this time
Hey,
I had the exact same issue with my Galaxy Note 8, every time I tried to install European or custom Rom.
The only way to get the tab back was to flash with the Chinese firmware. You may find it easily on Baidu.
Since it happened also with a note 2 and note 3, I stopped buying Android device in China... Unless you can make sure that you buy a model coming from HK.
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
ky3bmu4 said:
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
Click to expand...
Click to collapse
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
ky3bmu4 said:
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
Click to expand...
Click to collapse
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
pierrotee said:
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
Click to expand...
Click to collapse
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
ky3bmu4 said:
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
Click to expand...
Click to collapse
Cool! So do you now have root and custom recovery?
pierrotee said:
Cool! So do you now have root and custom recovery?
Click to expand...
Click to collapse
Yeah))
TWRP installs OK via TWRP Manager
I installed TWRP Manager, selected 'klimtwifi' as the device, and it successfully installed TWRP 2.7.1.1 without a hitch.
From TWRP I then immediately performed a nandroid backup of everything but the caches to my microSD card and encountered no problems.
The last step was to enable writing to my microSD card by installing NextApp SDFix.
My SM-T700 is bricked as well and I tried to flash a custom recovery with Heimdall on Mac but it gave me the Error "Claiming Interface failed". Seems like you really need the pit.
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
the9kill said:
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
Click to expand...
Click to collapse
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
P.s If anyone is interested in looking for this phones Stock ROM I found it here:
samsung-updates.com/device/?id=GT-N7100 (Select the one for your country/region)
the9kill said:
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
Click to expand...
Click to collapse
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
the9kill said:
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
Click to expand...
Click to collapse
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi again,
Yes, I can fully appreciate why you would say that, from what I see ODIN is very straight forward and unless you do something totally (silly), like jiggle the cable or do something midway it should not hardbrick. Therefore it makes sense you suggesting the cable is faulty, but it seemed to copy over 32GB of data seemlessly in one go. Although i will change the cable as a precaution as there is a slight cut.
When I say hardbricked, I mean hardbricked as in no recovery and no download mode, and no display whatsoever no matter what you do.
[UPDATE] Okay, the strangest thing happened. After a whole day of charging the phone, sometimes trying it on for luck, hoping something would happen. I went to the doctors and came back, and oddly enough the screen had life!!! Yes, this gets bizarre, I repeat a clearly hardbricked phone resurrected back to life with a screen showing ("A firmware upgrade encountered an error, please retry with kies") or something like that, so overjoyed with this sign of life I carefully put it into download mode and its now waiting.... But before I try Odin again, I think I will take a leaf from Ceomavericks suggestion and get a brand new cable from another samsung phone and use that this time.
By the way Ceomaverick, last time i just tried to flash to stock rom using AP, and kept autorebook and Ftime checked.
This time I am seeing on a thread to do the following, please advise (given that my TWRP doesnt mount anything at all).
It says do this: from: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
Open ODIN, and check Re-Partition, Nand Erase All, Auto Reboot and F. Reset Time. Uncheck all other boxes. Click the PIT button and select the PIT file appropriate for your device (16GB or 32GB). Click the PDA file and choose the Stock Rom you downloaded. Press start and wait.
File Type: rar PIT_t03g_0907_16GB.rar - [Click for QR Code] (899 Bytes, 84 views)
File Type: zip BOOTLOADER_N7100.zip - [Click for QR Code] (1.03 MB, 75 views)
click start.
If everything goes well, the process should succeed and the phone should reboot. Don't wait for the phone to boot into android. Immediatly boot into recovery, factory reset the phone and wipe cache. Reboot to Android.
Now, if everything worked well, your phone should boot into Android. And then sort out the sleep of death issue.
I think I will wait for some feedback before doing this and just enjoy that my phone is mysteriously back in download mode, perhaps a hardware issue......
Another thread reading http://www.theandroidsoul.com/unbrick-restore-samsung-galaxy-note-2-gt-n7100/
Cheers
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
the9kill said:
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
Click to expand...
Click to collapse
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
the9kill said:
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
Click to expand...
Click to collapse
If the firmware from other region fails, then find pit file for 16gb to flash. If that too fails, I think your phone needs hardware repair.
Sent from my GT-N7100 using Tapatalk
I have a Sprint Note 4 that supposedly had a custom ROM installed on but I believe the digitizer is broken. Nothing shows up on the display. I booted into DOWNLOAD MODE using Home Power and volume down and flashedN910PVPU1ANK2_N910PSPT1ANK2_SPR then N910PVPU1ANIE_N910PSPT1ANIE_SPR via ODIN It sounds like its stuck in a boot loop after both flashes, but ODIN says PASSED when it finishes. Since I can't access the screen, how can i get this flashed back to a stock rom? Any help would be greatly appreciated.
I'm confused; why flash two stock tars? Did you let the phone boot after flashing the first stock tar?
I'd suggest a factory reset in recovery, power down, Odin the factory tar of your choice and let it auto boot. You should see the phone boot into into recovery briefly on the auto boot when flashing stock tar in Odin, then fully boot. If not seeing the brief recovery, start over and try again.
I recall a YouTube video on a digitizer issue that may have been resolved. The guy had a dead spot on the digitizer. I think it only suggests a possible fix in a follow-up video the user posted. But maybe the stock tar will fix it.
why flash two stock tars?
After flashing the the first one, it just kept rebooting. That was last night. Today I flashed the older one. I'm trying install ADB on my Windows 7 desktop to enter recovery.
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
samep said:
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
Click to expand...
Click to collapse
I tried without SD card and I didn't check repartition in ODIN. The md5 matched on both.
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
samep said:
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
Click to expand...
Click to collapse
How can I use TWRP without the screen?
thanks
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
samep said:
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
Click to expand...
Click to collapse
I went by feel....and the fact that Odin said COM connected. and PASSED
kevg77 said:
I went by feel....and the fact that Odin said COM connected. and PASSED
Click to expand...
Click to collapse
So you pulled the battery, pressed and held volume down, home and power buttons until it vibrated, waited to make sure it wasn't just booting, when satisfied, you pressed volume up; right?
I'd say that is a sufficient feel.
If the Odin or kies update won't take and screen is dead; with no adb access, who would know what's on the phone unless it's just not playing the right boot tone when it keeps rebooting? Problem?
I think that may be enough to take your phone back to point of sale and ask for replacement without worrying about root voiding warranty?
Did you try the Kies update?
I am familiar with the Note 3, thats how I was able to get it into Download mode by feel. I tried KIES and it said that my device is not supported. Im using the latest version of KIES. I know I'm running into an issue with the usb driver recognizing...Im on Windows 10 technical preview. thinking about trying it on an old Win7 laptop.. thanks for the advice