Database Users

JPC Rom install issues - dreaded USB logo - Help Doc

Hi,
Just wanted to share my experience getting JPC Rom installed and rooted.
Prior to upgrade, I had the JP3 Rom, rooted with clockwork and 1-click lag fix.
I had some major issues installing JPC. In fact, I ended up with the dreaded USB logo a few times.
This is not a complete guide, but hopefully it will help avoid the problems I had.
1) Before installing the new rom, I strongly suggest that you Factory Reset the phone.
2) Install the JPC Rom using the other guides on this page. I used Odin and choose Repartition to get a clean install.
3) Here is where the problems started. After the rom installed cleanly and the phone rebooted, it would get stuck on the second Samsung logo and eventually go black. This happened to me twice. The fix I found out, is to go into Rececovery mode (Vol Up, Home, Power) after the install and clear the cache, reformat SD and factory reset. After you do this the phone will boot normally.
4) After that I followed the rooting guide on this forum, but ended up with the dreaded USB logo. If this happens to you, just go back into DOwnload mode and reflash with Odin again (following the guide in this forum)
IMPORTANT: I have TWO galaxy s phones. The strange thing is, one of them is VERY easy to get into Download or recovery mode. The other is almost impossible. For those of you that have a similar model to me that seems like it does not have a 3 button download or recovery mode you probably do.
I thought I was bricked, and tried for over an hour to get my second phone into download mode (take out battery, hold three buttons, put in battery, over and over again). I was about to give up, but found I was able to get the phone into download mode if I ....
1) Take Battery Out. Put it back in.
2) Plug phone into USB on computer (do not turn it on)
3) Now try to do the 3 button Download mode. Press all three buttons at one time and release power about 1 second after seeing Samsung logo.
Again my second phone I can very easily get to download mode 100% of the time. I am really not sure why the two phones would be any different. I hope this helps people that have a stubborn phone like mine.
P.S. I did not install Clockwork on JPC, but I did root the phone and installed 1 click lag fix. Phone is running VERY stable and all features seem to work (including Mobile AP).

I hope this helps others like me who tried to install update.zip as explained in some posts & got the dreaded USB logo on boot & didn't know what to do because I am sharp but no programming & all that. I got mine to go ahead ONLY after I put in my SIM & External SD card. With both OUT, I get the USB logo 100% of the times.
I hope this helps.

Ive installed jpc a few time now and a factory reser after flashing did it for me every time

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

[Q] First boot loop, now wont turn on, 7 vibrations?? HELP!!

Hello, I have the HTC tmobile mytouch 4g and it is acting up. Stock phone, no roms or rooted.
Three days ago, at night, doing some browsing and then everything froze, would not respond. I removed battery, and then it did a boot loop so i kept trying for a while, taking out battery, and turning on but still boot loop, so then left it alone.
The next morning i held the power and home button and it turned on and it worked normally for the whole day! until about the same time two days ago. Doing a little reading and browsing before bed (same website too, but i didn't download anything and the site works fine on a computer) and it froze. Did the same routine except it didnt work in the morning again. I removed sd and sim card too, left everything out for a long time, but whatever i tried it wouldn't work.
Yesterday i tried all day and then I read online I should do a wipe cache partition from the recovery menu. So i did that, but it was still a boot loop. After a few tries, it stopped turning on. Now the screen doesn't even turn on, but the phone vibrates 7 times when power is pressed, then will not respond at all unless i take battery out, then it will do the 7 vibrations and etc.
All htc said is to try a factory reset, but it wont even go to that menu. I can send it to them, but will probably lose everything on my phone ( like messages, contacts, and app data?) BUT I'm convinced there is another way, since it fixed itself the first time.
Just recently, now it has started blinking the charging light when charging (i charged it about 10 hours ago and it didn't blink)
I don't really know much about how these things work, but I have been reading some stuff about pd15??.jzip and putting it on the sd card (i have access to a micro sdcard reader) Also about a stock image or something. I don't know much so please give a simple-ish answer.
IF THE SOLUTION YOU WILL PROPOSE HAS A LOW SUCCESS RATE OR HAS A POSSIBILITY OF FURTHER DAMAGING THE PHONE, PLEASE LET ME KNOW... If it is too difficult/ too much work/ or dangerous, then I don't mind losing whatever i have on the phone

The PD15IMG.zip is the "stock image." It has to be installed in the bootloader, and you WILL lose all of your data. Usually you can get to the bootloader by holding volume down while booting. It will scan for the file there. Can you get into your bootloader?

sigh
cannot turn on no matter what i hold.
I think the blinking last night meant that it isn't charging the battery anymore. wont even vibrate now unless it is plugged in. its not an issue with the battery is it??
if this stock image is going to delete everything anyway, i might as well send it to htc. i just hoped i might be able to save my messages because i have some really hilarious ones, but oh well.
Can you please tell me exactly what ill lose? so,
bookmarks on the browsers
contacts and messages
all apps (they're on my phone) and app data? (like will i lose my progress in temple run 2, lol)

myTouch 4g HELP said:
cannot turn on no matter what i hold.
I think the blinking last night meant that it isn't charging the battery anymore. wont even vibrate now unless it is plugged in. its not an issue with the battery is it??
if this stock image is going to delete everything anyway, i might as well send it to htc. i just hoped i might be able to save my messages because i have some really hilarious ones, but oh well.
Can you please tell me exactly what ill lose? so,
bookmarks on the browsers
contacts and messages
all apps (they're on my phone) and app data? (like will i lose my progress in temple run 2, lol)
Click to expand...
Click to collapse
I don't have this phone with me ATM.but I seem to remember when you press volume UP: and POWER it if i remember correctly would do the blinking light and vibrating a few times .Anyways to get in recovery You Press Volume DOWN and press POWER at same time should bring you to recovery and if running a custom recovery such as CWM or 4EXT you can try the wipe cache and wipe dalvik cache to see if fix issue or try if using a custom ROM you can try installing the ROM again without wiping data and system first.I Read your post and the replies and correct me if I am wrong it sounds like this might work and sounds like you are able to get to recovery from reading your post I think.I would try and confirm that you are or are not able to try these suggestions before you try the boot-loader suggestion with the PD15IMG.zip or whatever it is called ,these are assuming your rooted with a custom recovery such 4EXT if not and I read wrong again I apologize. Good Luck!

alternatively you could use adb if u installed it
1. connect ur phone via usb cable.
2. run cmd from ur android-sdk folder (or whatever you named it). by running in folder I mean, ur path in cmd should be C:/whatever-is-your-sdk-folder path
3. type this in cmd window "adb reboot bootloader" (without ")
it should load your phone in bootloader from where u can get more options like factory reset or install new rom (u can mount ur sd card in recovery & put new rom to flash on sd card)

lg mobile support tool stuck at 49%

i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.

LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00

try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck

tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck

El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00

tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots

El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!

Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...

tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens

El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00

Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app

Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer

i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support

El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef

1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !

Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.

My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!

Other kind of boot loop...

Hi all!
Here is a little problem that i didn't solved.
i have a N910F Note 4 that likes to boot loop . I received it as it is and don't know what caused it(i suppose that was a rooting issue because had the knox value 1)
During the all time, PC and MAC were unable to recognize the Note 4, despite of repeatedly reinstalled drivers(older and newer versions) , Keys and Smart Switch were unable to recognize the device, PC is failing to install the MTP driver for some reason. I changed the USB ports,restarted,updated drivers,updated windows etc. -NO RESULT. BUT : Somehow Keys is able to run recovery and initialization and install it on the device while saying Connecting device... , phone also doesn't appear in device manager or file explorer as external drive.NOTHING! Odin and Jodin says ''added!'' and starts the job with no comments
1. I tried different versions of boot loaders with different versions of ROM (all for my specific model) with no result.
The end of the boot is when Samsung logo ,sound and graphic appears but freezes before actually starting OS, then restarts. IT keeps restarting until battery goes off(even while connected to pc by usb!!! ). Then starts to charge the battery normally.
It boots in recovery and download mode with no problems, it did every time i flashed it…
2. I tried different versions of boot loaders with stock roms , custom kernels etc...and the problem was the same
3. I tried to flash with Odin the stock 4.4.4 without problems but….the problem was the same
4.I tried Device recovery and initialization with Keys and here something interesting happened:
First time when i did it, it went over the samsung logo and booted. I selected language,i skipped wifi network selection and i accepted the user agreement. No matter how fast i was moving, the boot loop didn't went over the user name selection which is after the user agreement. Then freeze and boot again.
Second time when recovered with Keys (tried more stuff in the mean time) it went over the logo and started to update like…''updating applications 2of 17'' the max reach point was ''3 apps of 17'' and then freeze and reboot
I am out of ideas so i suspect that the battery might be dead because it gets empty even if is charging while phone is ''boot looping''. I ordered a battery,should arrive soon.
If that don't work…i am gonna spend some cash and sent it to Samsung for repairs (i bet that it won't be cheap because they will probably tell me that is the motherboard fried so they make you pay for being a bad boy and tried to root). Far as i know is not a brick as long as download mode and recovery works just fine.
Is here someone that has any new ideas for bringing this phone to life? Any help is well received , maybe i skipped something….
Thank you in advance.

Boot into recovery and perform a factory reset, it will wipe the internal storage.

Battlehero said:
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Click to expand...
Click to collapse
That was the first thing i tried , cache wiped also. After every rom when booting failed.

UPPME said:
That was the first thing i tried , cache wiped also. After every rom when booting failed.
Click to expand...
Click to collapse
Uninstall Kies, and install Samsung USB drivers: https://www.androidfilehost.com/?fid=24052804347849220
Take the battery out, leave it for approximately 10 seconds, enter the battery back in.
Hold volume down key + Home key and power on the device.
Then plug the mobile phone into the computer.
Run Odin as Admin: https://www.androidfilehost.com/?fid=24052804347851815
Then flash the firmware in the AP section.
Make sure that the firmware is for your region, you can download it from Sammobile or SamFirm.

i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..

kerbiii said:
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
Click to expand...
Click to collapse
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.

Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English

UPPME said:
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Click to expand...
Click to collapse
if you can stay in recovery mode and download mode for more than 10mins i think its not battery problem, i think i have corrupted system files, i left my note 4 to samsung service center a while ago i will get it tom, i just hope they wont charge me too much for it,
uldyzjan said:
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
Click to expand...
Click to collapse
nah it doesnt work thats the first thing I do, that only work on ordinary bootloop

I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.

guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty

kerbiii said:
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
Click to expand...
Click to collapse
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.

guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
guts100 said:
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
Click to expand...
Click to collapse
yes thats the good thing and its under warranty even though im already rooted, with knox 01 and custom binary haha, i was already expecting to pay a huge amount of money but they said they will cover it, so its a blessing, but i hope the OP fixed his problem.