I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Hi,
I have now rooted my phone and seemed to have removed the issue I was encountering. (IMS Framework)
However I have a few issues since rooting and am a bit unsure if what to do next
Any help to the following points is greatly appreciated. I am complete noob so only plain English and links to idiots guides please!
1) as a recent post states, I am also suffering from frequent restarts. They are quick restarts, only a few seconds (not like a hard reset etc) however there seems to be no specific reason or app causing it.
Posts suggest removing Knox might help?
I have a few root removal apps installed now so can someone tell me which Knox apps/programs can be safely removed???
2) when I press side button to unlock the phone, the screen sometimes freezes and doesn't respond. I have to press lock button again to lock, again to unlock then it works again
Not a major problem but annoying none the less
Any ideas??
3) I rooted to save battery by deleting the vodafone virus IMS framework however battery is still not as it good as it was before IMS framework. It doesn't drain within a few hours but again it's annoying.
Android system and OS are currently using more battery than the screen
So being a noob I'm. It sure where to go from here....
I've done a backup from nandroid manager app (in a cwm format it seems) and downloaded rom manager however CWM installer hasn't worked (something on the install guide says something about Samsung devices needing to install something but I can't find a guide on it)
(Please also confirm, the back up I did to external sd card has a few files including an md5 file, a few tar files and recovery img file. Is this correct? Is this the folder I would use to restore if I encounter issues later on??)
So I'm thinking I unroot and reinstall factory settings through kies etc (guide how to do this would be useful??!!)
Then root again and install a new rom (a nice clean one without the bloatware etc)
EDIT. IVE READ HOW TO INSTALL CWM FROM ODIN SO WILL TRY THAT.
QUESTION THEN BECOMES : WILL INSTALLING A CUSTOM ROM FIX POINTS 1,2 and 3????
Am I overthinking this or is there a quicker fix to my issues above?
Any help appreciated!!
1. If you have a custom recovery then flash knox removal script. Then you don't have to delete it manually. For example > http://forum.xda-developers.com/galaxy-s4/general/scriptknoxout-complete-brutal-knox-t2807172
2. Could be related to point 1.
Flash the script and it should solve most of your problems.
For your last question. There is no point in unrooting and using Kies if you want a custom rom. A custom rom will fix point 1, 2 and 3.
HELP!
so i install the Knox Zip (through teamwin)
Phone said "updating apps" then stuck on samsung screen.
Rebooted again.
Done multiple reboots through TWRP. Still same - stuck on samsung screen
I wiped data/factory reset but issue is still same.
I can get to the screen by holding down power volume up and home button but reboot not working.
I looked for restore but it is blank (i did a restore on SD but its not showing!!!)
I need help!
rootromnoob said:
so i install the Knox Zip (through teamwin)
Phone said "updating apps" then stuck on samsung screen.
Rebooted again.
Done multiple reboots through TWRP. Still same - stuck on samsung screen
I wiped data/factory reset but issue is still same.
I can get to the screen by holding down power volume up and home button but reboot not working.
I looked for restore but it is blank (i did a restore on SD but its not showing!!!)
I need help!
Click to expand...
Click to collapse
Either reflash the stock rom you are on
or
Flash a custom rom that you want.
Lennyz1988 said:
Either reflash the stock rom you are on
or
Flash a custom rom that you want.
Click to expand...
Click to collapse
Im guessing that has to be via Odin as there is no ROM file on my phone??
(or could i put a ROM on my External SDcard and flash via TWRP?)
rootromnoob said:
Im guessing that has to be via Odin as there is no ROM file on my phone??
(or could i put a ROM on my External SDcard and flash via TWRP?)
Click to expand...
Click to collapse
Stock ROM (download it on your pc) -> Flash it via ODIN
or
Custom ROM having it in your SDCARD -> Install it via TWRP (Custom Recovery)
Took a while messing around with sd card but managed to flash liquid smooth and all working
Annoyingly Odin didn't recognise phone but that's ill sort that out another time
Thanks for help
Hi,
My i9505 Intl (Australian Telstra LTE) SGS4 has been rooted for a year at least now, and recently (a few months) had TWRP recovery and CM13 installed and everything was going great. I loved CM!
Anyway I had done a few nightly patches of CM and all seemed good and then a week ago I installed the most recent nightly (possibly this one cm-13.0-20160819-NIGHTLY-jfltexx-recovery.img ). Well the subsequent reboot put the phone into a boot loop. So I thought no problem just boot to recovery and install my recent Nandroid back up. So did that but in my haste didn't clear cache or data. The nandroid reinstall seemed to go ok but a subsequent boot hung at the CM logo (I think it was a while ago now) and I couldn't boot to recovery, just hung with the blue text.
So I fired up Odin and booted to download and reflashed with TWRP. Boot to recovery still didn't work however I could still boot to download.
Tried different USB ports, different versions of Odin, re installed drivers to no avail. Also tried CWM, TWRP and Philz recovery and once I did get it to boot to recovery with Philz. THIS TIME cleared cache and data and loaded a good copy of CM that I had on my SD card. Again stuck in boot. Couldn't get back to recovery.
Tried loading the orginal samsung firmware and they I was stuck with a Samsung logo boot looping. Ditto recovery just hung at the logo and the blue text "recovery booting".
Rinse and repeat a few times and now the phone has started to become difficult to get into download or recovery. If I leave it with the battery out for a while it seems to come good again.
Odin when flashing a new recovery either hangs half way though or completes and says everything is OK. Full blue bar on the phone.
Rebooting however still leaves me in the boot loop.
There is no mention on Odin of any issues with the partition however I have d/l a PIT file from one of samersh72's posts but am not sure if it is the correct one for my Int phone or indeed if I need to use it as Odin doesn't seem to report any partition errors.
If any one has any suggestions I am very receptive to ideas right now.....
Thanks
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
audit13 said:
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
Click to expand...
Click to collapse
I did a factory wipe and then installed CM from my SD card but that is the only time I have able to get into recovery since the first time when I reloaded my nandroid backup
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
audit13 said:
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
Click to expand...
Click to collapse
Yup tried that, as I realised that the auto boot might be overwriting the custom recovery...........however as a new development I haven't been able to boot to download or even the stuck recovery since yesterday.
I think it has now moved to a full hard brick
Is still turns on? You have a USB jig to try?
audit13 said:
Is still turns on? You have a USB jig to try?
Click to expand...
Click to collapse
No I don't have one but I have all the makings of one so i'll put one together and give it a go. Though I have to say that I am not that hopeful as I can't even get a peep out of it now.
A jig may be the last solution before sending it for repair or replacing the motherboard.
audit13 said:
A jig may be the last solution before sending it for repair or replacing the motherboard.
Click to expand...
Click to collapse
Thanks Audit, Ill let you know how I get on. Just looked at some replacement motherboards and they don't seem too common for the LTE version used here in Australia AND USD60......pretty much get a working phone locally here on ebay for that and I get the rest of the parts too.
Have you tried already flashing a stock rom as a tar file from sammobile?
justgamer01 said:
Have you tried already flashing a stock rom as a tar file from sammobile?
Click to expand...
Click to collapse
Yup did that as well!
Ghostdog1 said:
Yup did that as well!
Click to expand...
Click to collapse
I'm not sure if it will work! But try emergency recovery with Smart Switch!
justgamer01 said:
I'm not sure if it will work! But try emergency recovery with Smart Switch!
Click to expand...
Click to collapse
With Smartswitch I get the same outcome as with Kires
"GT-I9505 does not support initialising. Please contact our service centre."
But on the plus side it is actually responding to button presses today. I will pick up some 100K resistors tomorrow and finish off my USB jig. See how that goes.
Well it appears to have finally died fully. No response to any button or combination of button presses. Made up a USB jig but without some response to a boot that won't work either.
Thanks to Audit and Justgamer for your advice. Think it is time to draw a line under this one and move on. Maybe a new Nexus when they drop?
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
garylawwd said:
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
Click to expand...
Click to collapse
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
4tson said:
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
Click to expand...
Click to collapse
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
Yeah, I may or may not have already tried hehe.
You wouldn't happen to have a rom that's not being hosted on Mega would you? I exceeded my limit when I was 95% done downloading one of them.
I think I found one, whoops.
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Dyeide said:
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Click to expand...
Click to collapse
Yep, I tried that, although I'm not sure the USB drivers I downloaded were correct, since the official page isn't working at least for me. So I downloaded what the websites claimed were the correct drivers, I went into download mode that way, which has some debug info on the top left stating it's in Odin mode, but Odin still didn't recognize it.
I'm pretty sure usb debug options were turned on before this, but I'm not sure if the factory reset could've messed with that, thought I'm assuming it could be part of it.
I'm currently trying to download some custom roms to follow garylawwd's advice, I'll reply once I've got results.
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
4tson said:
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
Click to expand...
Click to collapse
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
garylawwd said:
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
Click to expand...
Click to collapse
Tried this just now, it rebooted twice and on the second reboot it got stuck on the logo once again.
I think I'm done trying to mess around with it, I'll take it to a repair place :/
Thanks for looking out though, definitely appreciate your tips even if they didn't end up working out. :good:
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...nt/recovery-twrp-3-1-2-blue-dogerino-t3768707 Try flashing this recovery it's a newer version.Just download the .img file and install it through twrp as recovery when prompted.
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
DontTouchMaPhone said:
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
Click to expand...
Click to collapse
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
garylawwd said:
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
Click to expand...
Click to collapse
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
DontTouchMaPhone said:
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
Click to expand...
Click to collapse
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
4tson said:
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
Click to expand...
Click to collapse
Are you on stock now?
DontTouchMaPhone said:
Are you on stock now?
Click to expand...
Click to collapse
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
4tson said:
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
Click to expand...
Click to collapse
Wait,so you paid for the repair right?And he flashed you a custom rom?Looks pretty scammy to me..Anyways do you have twrp or stock recovery?