N7100 stuck on logo screen - Galaxy Note II Q&A, Help & Troubleshooting

Hey Everyone,
I did a lot of reading in last 2 days on different threads in this forum. I find my case to be a little different. Can some experts advise me on what else can I try before concluding this to be a hardware error that cant be fixed.
Here is where I am, in details:
N7100 bought in 2012 and used extensively till 2015-16. I had installed Cyanogen Mod with TWRP 2.7.0.2 custom recovery on it. It was all good till one morning it wont go past the boot logo. This was a phone bought in india and the issue happened in Australia which I was visiting for a couple of weeks. I had left the phone on charging overnight and next morning it wont boot (could this be important, could this have fried the hardware?).
Anyways, I gave up on it in 2016. but last week my mom needed a phone, so I decided to check this phone again. Here is what I can or cannot do with the phone:
1. I can goto recovery mode but it says 0mb for internal storage and external SD card. The error log starts from 'Unable to find partition size for /boot, /recovery, /modem' and goes on into 'unable to mount efs, data, cache,system'
2. I can goto downloading mode and it reads the product name 'GT N7100', Custom Binary Download 'Yes 4 counts', current binary and system status as 'Custom'
3. I went into ODIN and flashed the N7100XXUFND3 PDA downloaded from sam mobile. It failed on first go and then I found a PIT file which I used and it went through fine. It takes 10-15 minutes but I get a BIG GREEN PASS on ODIN. I was very happy. But no good, it continues to be stuck on boot logo along with point 1 and 2. It still says internal storage 0mb. So where is is flashing the ROM.
I have read that if it is emmc failure or SDS, then in downloading mode you wont see the product name.
At this point, i have no idea what else to try. I am able to flash properly so I think I am in clear as far as hardware failure is concerned. What else can I try or do you think anything above is a good indication of a certain issue. Let me know your thoughts. Thanks

Related

[Q] Evo vibrates 5 times and turns blank with flashing green LED

I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
strdrk1 said:
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
Click to expand...
Click to collapse
That's weird. I'm pretty sure the vibrate 5 times and green blinking led indicates that the phone is in diagnostic mode. I'm not sure how to remedy the situation, I would've suggested a PC36IMG back to stock, but you already tried that. I would try taking the battery out for an hour or more (i've read of people being stuck in diagnostic mode, and leaving the battery out for a good length of time fixed it, i think) then try booting up, and seeing if it works. If not, to answer your question, as long as the bootloader shows S-on, you will have no problems taking it back to Sprint. You need to make sure you have no 'evidence of rooting' on your sd card, just to make sure that the sprint tech doesn't see anything on there. Good luck.
I formatted the sdcard, but it seems to be creating these files QXDM_some numbers.dm is this normal or any indication of rooting the phone.
Sorry to be the bearer of bad news but I had the same issue and eventually gave up after 3 solid days of working on it. You name it, I tried it. Had to get it replaced.
Something about unrevoked and my old 002 phone didn't jive together and the root aborted at an unrecoverable stage. No sd card mount, no adb, not even able to connect via usb, so running an ruu or new pc3600img wasn't an option.
As for the 5 buzzes and shut down after a min or so... Your guess is as good as mine. You can put it in diagnistic mode with the arrow up/power button boot, but thats 3 buzzes not 5.
Wish I could offer some actual help :/ Let us know if you find a fix.
Oh, before I took it back in I did a hard reset so it would reboot before they could get past the setup menus and see the superuser permissions app. Not that they'd care, but just in case.
I have just returned my EVO to sprint for this same problem. He told me it was a common problem. I get my new on today. They could have cared less that it was rooted, he told me it did not matter.
derekstory said:
I have just returned my EVO to sprint for this same problem. He told me it was a common problem. I get my new on today. They could have cared less that it was rooted, he told me it did not matter.
Click to expand...
Click to collapse
I ended up exchanging mine also. The lady really could have cared less. i wish i would of known cause i spent some time trying to get it back to normal. My sister also ended up exchanging hers because she got the white one and wanted the black one instead.
thanks for any help and replies.
I too had the same problem. It all happened when I was trying to flash cyanogen 7 RC2, I wiped all data, and all seemed fine. I rebooted and it went right to the bootloader and I noticed I was S-ON. Tried to re-root, and run a RUU. I did actually get it to boot to sense, but it froze and then I got the buzzes, and the green lights. I went to sprint since I have insurance. They checked it out and then an hour later, they gave me another one.
My EVO is currently stuck in the same state. I have spent a huge amount of time working on it, and have some information. I'm just dumping as much as I can remember in to this post, so excuse the lack of organization.
Before I go any further - I have not been able to fix the issue!
My phone was about as stock as possible when I took it to the Sprint store. They ordered me a new one and gave the broken one back. I have taken a few more risks now that my new one is on the way.
The initial problem started after flashing MIUI recently. The phone booted normally, but I noticed that the SD card was inaccessible. I would bet that the phone was refusing to charge over USB at this point as well, as that issue goes hand-in-hand with the sdcard problem.
The sdcard and its contents were fine. I later made a backup of the card and lost nothing.
Symptoms, high level info:
Phone immediately vibrates 5 times and begins flashing a green indicator, screen black at power on
Under unknown circumstances, the phone will display the white EVO boot screen before exhibiting the above behavior
Cannot exit this mode unless phone is unplugged and battery is removed
Bootloader can be accessed by holding volume down and power when starting fresh
SD Card is accessible in bootloader - indicates the problem is not purely hardware related
Fastboot can be used to temporarily (1 boot) gain access to sd card
Phone can be flashed with official PC36IMG
Phone can be set into RUU mode and flashed with official RUU
Official update.zip can be flashed from stock recovery
Qualcomm diagnostic tools can be used
Phone will remain in the installed OS for a very short amount of time
Bootloader shows S-ON, 'fastboot oem boot' shows Super CID and CID=111111111 instead of SPCS_001
Because one of my initial ideas was to flash a stock PC36IMG from the bootloader, I lost access to a custom recovery very early in the process. Other users may have better luck if they do not immediately flash a stock recovery.
Flashing PC36IMG is accomplished as usual. Vol- + Power.
To temporarily enable the sd card, disable Qualcomm Download mode:
Boot into bootloader
Wait for it to scan the SD Card
Select Fastboot (Power to select)
Plug into computer
Open a command prompt and ensure you have the fastboot executable
Command: fastboot oem enableqxdm 0
Exit fastboot
Select Clear Storage and select No to reboot OR
Select Recovery
The phone will boot into the OS. Under unknown circumstances, the phone will reboot. The amount of time can vary quite a bit. Enabling Airplane mode does not help. Using diagnostic tools to put the phone in Offline mode does not help.
If you would like to use Qualcomm diagnostic tools, the phone will have to be in diagnostic mode, rather than Download mode. The above steps will get you most of the way there, with the added annoyance that the phone will not enter proper diagnostic mode if left plugged in the entire time.
To ensure diagnostic mode correctly enables (or rather, that download mode disables):
Perform the fastboot command to disable qxdm
Unplug the phone
Navigate back to the bootloader, select Clear Storage
Select No (Vol-) to reboot
The white EVO boot screen will display
The screen will go black before the Sprint/4G animation plays
Plug the phone as soon as the white screen disappears, before the Sprint/4G animation
The phone will display in QPST Configuration without saying *Download* everywhere. The phone number will be incorrect, but that value is actually stored as a Directory ID in the NAM. In other words, it's okay.
The QPST Service Programming tool looked like a good place to start. If you would like to look at the configuration options for the EVO, you can start an offline connection using the profile "FFA/SURF QSD8650 Rev 2.0".
Note that the phone will always reboot after writing any values to the phone. This means you will have to pull the battery, unplug it, boot into fastboot, disable qxdm, boot into the OS each time.
You will need your MSL code for many of these applications. You can get it by calling Sprint and asking. They will not provide the code through email.
I can confirm that at least some changes in the Service Programming app will stick. I changed the banner, under the Display tab, to "Brick" (from Sprint), and it showed up in the Notification dropdown.
The NV util can read the values from the phone correctly.
QXDM can issue command to the phone.
ADB will not work. This limits the ability of tools like unrEVOked to do whatever they do. Getting ADB to work could be useful. Note that I did re-enable Debugging in the Setting->Applications menu to no avail. I believe this is a general side effect of this problem and perhaps a key symptom.
The bottom line is that I have run out of ideas. I have not found a setting in any of the QPST or QXDM tools that indicate this mode can be turned off. I have a hard time believing that there is some permanent switch in the Qualcomm SOC that says "always boot into this mode forever", but who knows.
Any suggestions would be great.
To summarize, I have installed a stock PC36IMG, update.zip, RUU. I have access to almost any setting in the phone, but cannot write to NV because it's in the S-ON state, which limits certain fastboot wipe options and the ability to push new images to system partitions from fastboot. I can, in theory, use the QPST Download software to move images if I can find one that might work.
When is the last time you tried running a 3.70 PC36IMG RUU?
I ran the 3.70 RUU literally minutes ago.
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Apparently still not taking?
That's the thing - it *is* taking. Whatever is triggering this mode is not being reset by the RUU (or any other full clear/flash technique).
I have a dump of the NV memory, but I want to run through it with a hex editor to make sure it doesn't have anything that would identify my Sprint account or identity before posting it.
SLOSifl said:
That's the thing - it *is* taking. Whatever is triggering this mode is not being reset by the RUU (or any other full clear/flash technique).
I have a dump of the NV memory, but I want to run through it with a hex editor to make sure it doesn't have anything that would identify my Sprint account or identity before posting it.
Click to expand...
Click to collapse
Ah I see, and good precaution.
My ESN is in the qcn file, and I assume my MEID is as well. I will try to zero them out if I can find them all.
If my phone's ESN is 12345678, then it is in the qcn file as 78 56 34 12.
Does anyone else happen to have a known good QCN? Maybe I can compare them side by side to locate the differences. I suspect that there will be a lot of them, but I can eliminate most of them pretty easily.
While I work on the file (and debate whether or not it's safe to post), here is some information from the NV dump:
Code:
File Version: Major 2, Minor 0, Revision 0
File Summary:
Phone Model: 16 [FFA/SURF QSD8650 Rev 2.0], Configuration Name: default, Total NV Item Count: 1650
Phone Model 16 [FFA/SURF QSD8650 Rev 2.0] Configurations:
Configuration Name: default
Mobile Properties:
ESN: 0xMASKED
Phone Model: 16 [FFA/SURF QSD8650 Rev 2.0]
NV Major: 0
NV Minor: 0
SW Version: 8650B-SDCAPLYM-324026
Client Name: QPST Software Download 2.7.0.362
Code:
Feature Mask:
...Removed for brevity....
Total Set Bits: 108 of 432
Without bothering to specify all the set bits (although there are some interesting ones like "Bit 306: F_UI_GOOFY_MENU_BIT"), maybe someone can confirm that 108 or 432 is close to correct.
I loaded up a nv.img from a nandroid backup I took the day this problem happened (before flashing a ROM). I suspected that the nv.img and the qcn I just pulled should both represent the same general memory in the phone.
The image is...definitely an image. Exactly 640kb, tons of empty space and apparent padding. Much different in overall layout than the QCN, and no trace of my ESN. However, I was able to locate the GPS URLs in both files. While not even close to the same offset in the file, that small section of similarity indicates that the same memory was probably accessed.
Unfortunately I know of no way to push the nv.img to the phone in its current state. If I were able to get the nandroid backup's nv.img onto the phone I could at least eliminate the entire NV memory as a variable. If it fixes it, then awesome, and if it doesn't, then I can ignore the file entirely.
Here is the QCN file with my ESN removed. There may be other private information in the file, but at this point, Sprint is ordering me a new phone, and gave me this one back, so I don't know if they can really do anything about this.
http://rapidshare.com/files/455015717/public.qcn
My enthusiasm toward poking around this file is dropping off pretty quickly since I no longer believe this is where the problem lies.
I had the same thing happen to my EVO last week. Pretty much the exact same symptoms as you. I was able to get the RUU to run, and return my phone back to stock thinking this would fix the problem. I can boot into Sense, but the phone will shut off and do the 5 vibrate thing within a couple of minutes.
I took it into the Sprint store, and the rep told me there is nothing they would do and they would not replace my phone. He assumed it had been rooted (which it had, but I returned it 100% to stock before taking it in), but I have also read of this same thing happening on unrooted phones. I plan on calling Sprint and/or HTC directly to try and get the phone replaced.
From what I've read, it kind of sounds like this is a hardware failure. Possibly something in the internal memory or RAM. Of course, this is just mostly a guess I have. It seems this happens to unrooted phones, but is more common on rooted phones, possibly because of all the flashing we do.
Like I said, it's just a guess of mine, but it kind of makes sense. I wish I could be more help, and I'll definitely be following this thread because this seems to be a fairly common problem with EVOs and Incredibles that nobody has seemed to figure out yet.
hello,
the problem is heat.try to use your evo on the AC vent in your car with ac on you will not get reboot or eny shut down than try to use with out ac...
whenever internal temp goes more than 38C the evo goes off 5 vib. and flashig..
i spent long time testing this so i almost 100% sure that heat is the problem with my evo...
i dont know if there is a way to change the seting on shut down due to heat but it mey be...
adasio said:
hello,
the problem is heat.try to use your evo on the AC vent in your car with ac on you will not get reboot or eny shut down than try to use with out ac...
whenever internal temp goes more than 38C the evo goes off 5 vib. and flashig..
i spent long time testing this so i almost 100% sure that heat is the problem with my evo...
i dont know if there is a way to change the seting on shut down due to heat but it mey be...
Click to expand...
Click to collapse
I was never able to fix mine, but before getting it exchanged i let it sit all night with the battery out and would have the same results. So i know mine wasn't overheating.
strdrk1 said:
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
Click to expand...
Click to collapse
It's bricked. Happened to me when I tried to fix a problem with my phone not mounting the microSD card to any computer (got error message back on a Windows computer saying that the device wasn't recognized). You could probably try to flash the PC36IMG.zip file again from the bootloader, this time without all the addenda at the beginning (if you did that already, the nevermind).
My guess: pray that Sprint doesn't see any evidence of root. If you RUUed back already, they may not see it. You're probably in better position than I am, since the brick happened before I could RUU back with a PC36IMG file (and thus Sprint could see the root. At least Asurion doesn't seem to care about root, as long as I say nothing about it).

[Q] Tried to update, now unuseable

So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.

Cache problem on a Asus Zenfone 2 (ZE551ML)

Hello everybody,
First, sorry for my english. I am actually an exchange student in Canada (Montréal) and i come from France so my english is not that good.
Secund, i have a big issue with my Asus Zenfone 2. I explain, today i was hoping to install the update wich bring Marshmallow on my smartphone, it did not come by the update system so i download it. I was also hoping that this update can correct some problem that i experience since a little fall of the phone.
(There was two problem, the time to fulfill the battery increased, it's more than 8 hours now, before in 4 hour it was done and the sim card isn t recognized anymore so it is really boring even if i don t take a canadian number yet and the computer seems to do not recognize my phone anymore (before the cache problem.)
So i downloaded the update and try to install it in the recovery but at this moment i had my first real problem, i have an error before the recovery menu. I read that i need to push alternatively the sound button and the power buton to resolve that issue (i also read that it comes from a cache problem) and indeed i arrived in the recovery. And i did here one big mistake i think. In order to don t have this error anymore, i choose to reinitiate the cache, so it begun but it was really slow and i thought that a bug occure so i pressed the power button until it stop.
Since i have an error and i can t go in the recovery anymore even if i press both of the buttons like before, i just have this error : e:/ can't mount cache/recovery/last_locale and an alternative dark screen and error image.
Thank you so much by advance,
Elanakin

Bootloop - Errors in Recoverymode i9190

Hello guys,
I have an s4mini i9190 that somehow got bricked (no idea what the reason was). I was using a MM ResurrectionRemix Rom and one night shut down and never could make it work again.
I can access Download Mode (Odin apparently doesn't install things, it says it does, with no errors and yet the phone still has the bootloop of the RR animation).
I can access recovery but a bunch of errors come up, I share them with you in the attachments if you have any clue what it might be that's failing inside my phone. I have a beacon of hope that it might be something software-related and not hardware so I can just fix it easily :crying:. Through recovery I tried flashing cm13 but the huge red list appears.
The list goes like this:
Error opening data/lost+found
error opening data/data/com.google.android-gms/cache/sdsc
error opening data/[...]
over 100 red lines of errors X_X
I can certainly tell that the phone is not being able to mount /data which doesn't let me do anything to make it work apparently.
I think the Emmc are defect.
Any solution my friend?

Help with Note 4 please

I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
RootieTootie said:
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
Click to expand...
Click to collapse
sorry we missed your call gratz on the working phone . you know what they say "give a man a fish he ****s up his phone .....

Categories

Resources