Related
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
A couple weeks ago I bought a Nook Color on ebay. The first thing I did was turn it on and let it fully charge overnight. I noticed that it was in normal condition, but didn't bother going past the intro screen since an off the shelf Nook Color was not what I was interested in anyway.
The next day I flashed phiremod 6.2 on it with no problems (I have done this process successfully to two other Nook Color's by the way). I am able to connect to my wifi, setup my google account, and open the market. Life is good so far. Then I notice in ROM Manager that there is a phiremod 6.3 version out. I try to download phiremod 6.3 from ROM Manager for an entire day with no luck. The download just kept stalling on me. No problem I'll just download phiremod 6.3 onto my sdcard and flash it through clockwork recovery as normal (performing a full wipe first of course).
Then boot loop for no reason I can tell. Just a boot loop at "Touch the future of reading" with no way to get into recovery without restarting it with the sdcard.
So I put the sdcard back in and wipe and reflash phiremod 6.3 with the same results. Then I wipe and reflash phiremod 6.2...boot loop again. I repeat this process until my eyes start to bleed.
At this point I'm thinking, "There's no reason this should be happening. I wish I could just go back in time and start over." That's when I find this link: http://forum.xda-developers.com/showthread.php?t=914690
Ok, I'll just restore everything back to stock. No clockwork, no phiremod, just Barnes and Noble software just like the day it was born. So I go down the road of restoring the device to stock and instead of bootlooping at "Touch the future of Reading" it bootloops at the "N" screen. I'm running out of ideas so I perform the 8x method, get the OTA install, and still bootlooping at the "N" screen. Oh yeah, and "power + n" wont take it into recovery of any kind.
Now that it seems that I've failed to restore the device to stock, I try to flash phiremod 6.3 again because this is really my end goal anyway. This time it is a success. I connect to my wifi. The device says I am connected and the wifi signal is strong, but I can't establish a reliable data connection with google, or open the market, or browse the web. I turn the wifi off and on, I tell it to forget my connection and add it again, but nothing seems to work until a day later when it suddenly establishes a connection.
So everything seemed like it might be ok at this point except strange things started happening with the device. Power + n doesn't take it into recovery, and never did at any time it has been in my possession. When I try to go into recovery from ROM Manager after flashing CWR I go into a bootloop. This is even after updating Rom Manager and doing things like rebooting after flashing CWR. Wifi always says it's strong and connected but any app with internet access is often times painfully slow to the point of being unusable or at least impractical. Downloading a single app from the market is like pulling teeth, and I regularly get the "retry or cancel" popup over and over again. Sometimes when I tell it to reboot or shut off, I get the "rebooting" or "shutting off" message and it just grinds away endlessly.
The device is currently in a bootloop after just telling it to reboot (normal reboot not reboot into recovery), and I know how to pop in my sdcard with CWR and get out of it. However, my problem is that this is a gift for my sister, and I just cant seem to get this device into a normal working state that I can give to her.
I know that there are plenty of threads answering all of the little problems I have outlined here, but none have resolved them for me nor have I found a single thread that deals with a whole host of problems like this device seems to have.
Thank you for your patience in reading this.
Try restoring to stock 1.2:
http://forum.xda-developers.com/showthread.php?t=1050520
It can't hurt at this point, and it may get you fixed.
Thanks for the reply.
No dice. I tried both of those files. I made sure to format the system and data before flashing each time, and I'm still stuck at the "n" screen.
Alright so here's what I just did:
1) Format system
2) Format data
3) Flash B&N v1.1 "old" 1GB "/data", 5+GB "/media" partitioning zip from:
http://forum.xda-developers.com/showthread.php?t=1094371
4) Reboot
5) Flash Stock 1.2 update.zip from:
http://forum.xda-developers.com/showthread.php?t=1050520
6) Unmount sdcard
7) Reboot
8)Still stuck at the "n" screen.
The story so far:
I was forgetting to do the 8 reboots after repartitioning and flashing stock apparently.
I performed the 8 reboots, and my Nook did a factory reset and OTA update. Now it boots into stock v1.1.0. I see the pretty lady, there's a video, I get to accept a B&N agreement, I connect to either of my wireless connections, but after I enter my account name and password it always says "Error sorry we're having trouble setting up your Nookcolor. Please shutdown the device and try again...." It gives me a number to call so I do. After a long bewildering conversation with tech support, I'm told that my device was once registered to someone else (which I already suspected having purchased it on ebay). I'm told that in order to fix the problem they are going remove the old account from the device, and that when I restart it in an hour I will be one with the Nookcolor universe. It has been many hours, and I am still getting same error message.
Should I continue down this path with customer service (who are failing to inspire me), take it into the Barnes and Noble store this weekend (I don't have a receipt but it at least it boots into stock now), or just go ahead and load phiremod 6.3 (which is my end goal, but I want to make sure I don't take one step forward and then two steps back now that I've gotten this far)?
"Device Info" only has "back," "power off," and "reset."
I just tried holding the "power + n" for 10 seconds as demonstrated here Nook blocked after downloading latest software - Barnes & Noble Book Clubs. This guys seems very happy that this solution worked for him. I don't know why it wont work for me seeing as I have the exact same problem.
Barnes and Noble tech support came through and reset my device. It appears that I have a stock 1.1 Nook Color and all is well. I am even connected and able to browse the internet. Does this mean I am ready to start flashing new ROMs onto it, or should I do more testing while it is still stock?
So I made a nandroid backup of the stock system with no problem. Then I flashed phiremod v7 test. Everything was going well until I went to ROM manager, flashed CWR, and tried to make a backup. It went into a bootloop so I put in my sdcard with CWR. Immediately it started putting my backup on that card. I rebooted it through CWR, but it still went into a bootloop. I then did a factory reset, full wipe, and flashed phiremod 6.3... still bootlooping away. This is one of the problems I was having before I started this thread. The CWR on my sdcard is ClockworkMod Recovery v3.0.0.6.
Sorry to read that you're having so much trouble. FWIW I'm having one hell of a time using Phiremod on my NC, too. I've found solace with CM7 nightlies and the latest Dalingrin kernel.
CWR 3.0.0.6 is very outdated at this point. I use CWR 3.2.0.8 on my recovery SD. I think it was V3.0.0.6 that had problems formatting the data partition, but I could be wrong.
Hope you get it sorted out.
Thanks for the support. Do you know where I could find the latest versions of Clockwork?
There's a typo in my post above. The current version is 3.2.0.1
I read about it and got the files from androidforums.com, although I'd be surprised if they weren't on this forum, too.
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR, and now it is endlessly scrolling through the CWR menu on its own. The log at the bottom says "ClockworkMod Recovery v3.2.0.0," then "Back menu button enabled," then "Back menu button disabled," then "Back menu button enabled," and seems to be continuing like that without end. After powering off, removing the sdcard, and holding the power + n buttons for about 8 seconds, the screen shows the cyanogenmod logo and says "booting into recovery" but does nothing. I've repeated this entire process several times while holding the power + n buttons for varying times and it still doesn't actually boot into recovery.
Wulfie6 said:
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR
Click to expand...
Click to collapse
This is the problem. The nook color is the encore not the bravo. You have the wrong recovery image. Its a good thing its unusable...you might fubar your device if you were actually able to use that recovery.
Sent from my Phiremod Nook Color using XDA Premium App
I created a new boot disk with CWR 3.02.8 and successfully flashed Phiremod 6.3 and CM7 nightly 107. I was still essentially unable to use the internet on both of these ROMs even though my wifi connection said it was good. I did not try using my phone as a hotspot with these versions.
I'm on CM7 108 at the moment. I'm still getting sporadic internet access even though my wi-fi is pretty good (usually just shy of full bars). I connected to my phones wi-fi hotspot which produces full bars on the Nook with good internet results. This isn't practical though because I can't always have my phone creating a wi-fi hotspot. Doesn't this seem odd that my Nook is only internet reliable when it's connected to an excellent wifi connection, but functionally wont work when it's on a good wifi connection?
Also when I go into ROM Manager and try to flash the current version of CWR, it pulls up the "confirm phone model" (when it is actually connecting to the internet) but as soon I put my finger on the menu to scroll through, it selects the first one I touch. This is one of the problems I was having before on all ROMs.
So I just went into ROM Manager, flashed the latest version, then tried to make a backup through ROM Manager, and now I'm in a boot loop again except this is the kind of bootloop where I can't get it to turn off. It just sits there with the cyanogenmod logo saying "Loading..." When I hold the power down, it turns off and then comes right back on. When I hold power + n, it does the same thing but instead of saying "Loading..." it says "Booting into recovery..." I don't understand why this time it's different. If I take out the card that's in there now and put in my bootable SD card while it's in the boot loop, will it fry my cards?
Wulfie6 said:
S When I hold the power down, it turns off and then comes right back on.
Click to expand...
Click to collapse
sounds like it's plugged in
TheAmazingDave said:
sounds like it's plugged in
Click to expand...
Click to collapse
It's not plugged in.
Return to stock 1.2 - Stuck at n screen fix.
After you flash the 1.2 image with a clockwork recovery sd boot card, and are stuck at the n screen, you will need to restart and have the Nook software reset to default.
1. Hold Power+n for 8 seconds, release n, then power (it may take a couple of tries to get it right).
2. At the "Factory Reset" screen, confirm your intention to reset to defaults (press "home" n).
3. At the "Are you sure?" screen, confirm again (press "home" n).
It will then go to a "Clearing data..." screen and reboot to the stock nook software.
This procedure will reset your device to stock 1.2, just as it was when it shipped.
I second what JoeInternet says. You NEED to be on stock B&N 1.2 to be able to run the latest CM7 builds and ANY .32 Dalingrin kernels or it will not work.
Quick thought... The first thing that should have been done is an ATO 'deregister' to get that nook's ID dis-associated with the original BN account.
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
UPDATE: Problem solved! Subsequent attempts at Odin flashing succeeded. So...Nevermind!
Hello XDA sages!
I'm an avid Android user and I like to mess around, but I have no genuine technical skills or training and it's now bitten me pretty hard. I just got engaged and I was trying to clean out my phone and gift it to my new mother-in-law...with disastrous consequences. So this is my SOS to this incredible community! (Please note, I have searched many other Note 2 bootloop threads but I've seen nothing describing my situation and their solutions have not helped. Though I do apologize if I've missed something!
My current situation:
* Upon restart, the phone (Note 2 GT-N7100, unlocked) is stuck in a terrible bootloop, where the "Samsung Galaxy NoteII GT-N7100" logo appears for 6 seconds, and is then replaced by the Clockwok mod recovery logo (not recovery mode screen, just the hat+geer+orange arrow logo in the center, with "ClockworkMod Recovery v6.0.4.3" in small letters at the bottom). That logo lasts for about 1 second and then it goes black for 1 second, then repeats with the Samsung logo. And so on.
* Many other threads have suggesting entering recovery mode by holding power + home + volume up. This only causes the Samsung logo to refresh every few seconds (i.e. it eliminates the Clockwork mod logo interlude but does nothing else)
* Down+power+home does stop the loop and change to the custom OS download option screen. Pressing volume up then does enter the "Downloading..." screen with the picture of the green Android. (pressing volume up restarts the phone and the loop begins again).
* I've tried loading a stock firmware package onto the device in this mode with Odin v.3.0.9 (obtained via this post) but it doesn't recognize my device. I'm guessing this is because USB debugging was not turned on before the crash.
How I got here:
* I first rooted and flashed a custom rom several months ago using the Cynogen Mod custom installer. I installed the only "stable" release for the N7100 (here.)
* About 1 month ago I used the Rom Manager app and CWM to flash OmniRom, from a zip file on my external SD card. Just before the crash happened last night, I successfully completed an OTA to the latest OmniRom nightly.
* As mentioned, I was preparing the phone to be gifted to my new mother-in-law, and wanted to clean it out. I started by booting into recovery mode (from the Rom Manager app) and then initiating a factory reset.
* Upon rebooting, I noticed that somehow a bunch of my data was still hiding on the phone. Photos and videos and some songs were mysteriously still present, and the storage analysis in settings showed only about 6 gigs were free out of 16. A subsequent Factory Reset did nothing to change this. (All other aspects appeared to be working perfectly, however, as far as returning to a clean install of a fresh copy of OmniRom Android 4.4.2 -- no account data was preset, all my apps were gone and all the stock apps were in the default folders, etc.)
* I booted into Recovery Mode and initiated a "Media Data wipe" (I think that's what it was called) in an attempt to clear out the stubborn media files that weren't being erased.
* I then initiated a "data wipe" (which appeared to just be one level of storage hierarchy above the media data wipe I had just completed).
* I'm pretty sure I also separately initiated a "cache wipe". (But not a "Dalvik Cache" wipe that I have seen referenced on other threads, as I don't believe I saw a reference to that within the recovery mode interface).
* After these wipes I restarted, and all appeared to be fine. The stubborn media data was wiped clean. Finally, after logging back into my Google account to use the App Store to download Rom Manager one last time, (and I honestly can't quite remember why I needed to that) I wanted to complete the process with one more factory reset to eliminate my account data before handing over the phone. This time, I initiated the reset from within the settings menu of the phone in normal operational mode. (This was the first of the various factory wipes I've mentioned that I initiated this way -- all the other factory resets were initiated from within recovery mode).
* I think this is when the current loop started. But to be embarrassingly honest, I had the phone face down and didn't look at it after initiating that final factory restart until I subsequently popped out the battery in order to remove the SIM card. I think the factory reset was complete by that time, but I'm not sure. (In other words, I might have interrupted the factory reset by removing the battery before it was complete).
* After that point this evil loop began.
* To my amateurish eye, the two leading contenders for how I did this are a) the "media wipe" or "data wipe" which I completed before the penultimate restart (although the phone did boot and operate just fine after those were completed, or b) the final factory reset which I may have interrupted by removing the battery.
Three other notes which may or may not be relevant:
* Every time I did a factory reset or data wipe and then went to restart the phone from within the recovery mode, a warning screen came on saying that something might have messed up root access and asked me if I wanted to fix. I always said that I did,
* I had selected TWRP recovery in the Rom Manager app on the advice of the Omnirom site, and I think I saw a reference to TWRP on the recovery mode screen, but I had previously installed ClockWorkMod Recovery and thought maybe that was still active in a way it shouldn't be. (I can't remember what those indications were exactly, but I think it might have just been seeing the logo in the recovery page). But the presence of the ClockWorkMod Recovery logo in my evil boot loop makes me think this may be relevant.
* Before my first factory reset I had made a full backup copy of the current Rom (omnirom) onto my external SD card, which is still in the phone.
I would be eternally grateful for any help, tips, references or suggestions! My fate is in your hands!!
Many thanks,
- Your overeager n00b
Try simple things first. Reinstall kies so you know drivers isnt corupted and then flash stock rom with odin. And also try to switch usb cable and if that doesnt work switch to another pc. Try that and well go on.
Edit: i see you solved it gj.
Do not touch somebody else's phone if they are going to kill you when something goes bad
Next time better think twice
Brandzel said:
UPDATE: Problem solved! Subsequent attempts at Odin flashing succeeded. So...Nevermind!
Click to expand...
Click to collapse
Nice to hear you solved it You flashed stock, i guess?
By the way, I recommend changing the tag to [SOLVED] :good:
Hello
Since this morning my Note 3 has died. I went to turn it on and it did not go beyond the initial Samsung boot screen.
I have already tried almost everything:
- Enter in recovery mode and make wipe dalvik and cache
- Enter in recovery mode and make wipe factory reset
- Install a new ROM for Odin
When Odin finishes, he gives me the PASS in green as all correct. I start the phone, enter the initial configuration screens, let me put the language, wifi, Google account but when the automatic configuration of the applications starts, it restarts and loops in trying to boot, but does not pass the Samsung logo.
I tried to install the ROM again, in case there had been any problems during the installation (despite giving the PASS in green), but it does not work.
The only thing I can think of is to put another type of ROM of those in which the option Re-Partition is marked, which I think is more exhaustive, but I'm not clear what kind of ROMs those are.
I would appreciate any help with the ROMs with Re-Partition, or any other suggestion that you could give me, to see if I can resuscitate it.
Are you performing a factory reset after flashing a stock ROM with Odin and before the phone boots the stock ROM for the first time?
but when the automatic configuration of the applications starts, it restarts
Reads as an app or something is the problem .
Thank you very much for your responses. After searching a lot, I found a ROM of 4 files + PIT. After installing it, the phone works correctly.