I was restoring one of my nandroids (of euroskank's CM 10.2) and it said it appears as if I'm not rooted and if I want to install super SU and I said yes. Then I got stuck on the Samsung splash screen. When I pull the battery it gives me this screen I've never seen before that says (paraphrashing) that installing a "custom OS" is dangerous and push volume up to do so and down reboot. I tried to install the "custom OS" and it just keeps saying "Downloading. Do not turn off target." But it just stays there.
I'm on MDK and TWRP 5.0.2
scott62185 said:
I was restoring one of my nandroids (of euroskank's CM 10.2) and it said it appears as if I'm not rooted and if I want to install super SU and I said yes. Then I got stuck on the Samsung splash screen. When I pull the battery it gives me this screen I've never seen before that says (paraphrashing) that installing a "custom OS" is dangerous and push volume up to do so and down reboot. I tried to install the "custom OS" and it just keeps saying "Downloading. Do not turn off target." But it just stays there.
I'm on MDK and TWRP 5.0.2
Click to expand...
Click to collapse
Thats download mode, its used to flash stock firmwares using odin. Before you restored your nandroid did you wipe system, factory data reset, and wipe both cachea?
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Thats download mode, its used to flash stock firmwares using odin. Before you restored your nandroid did you wipe system, factory data reset, and wipe both cachea?
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Yes, I did all those things prior to restoring my nandroid...
scott62185 said:
Yes, I did all those things prior to restoring my nandroid...
Click to expand...
Click to collapse
This nandroid backup is likely not a good one, as seeing download mode at boot usually indicates a bad flash.
How many times have you tried restoring using the nandroid backup you have?
If you've tried multiple times with the same result (and you're sure you wiped data/cache/dalvik as well), you will probably need to flash a full tar.md5 image from ODIN (like a stock-rooted ROM, etc).
Related
Hi Guys
I am new to playing around with android but not to electronics. I have a Verizon Samsung Galaxy Tab 10.1 16gb (SCH-i905) with current 4g service.
Here is the problem I am having:
It started yesterday, I was browsing the web and the tablet froze and then rebooted. After the reboot programs randomly freeze and crash, if I reboot anything I have downloaded is gone and anything I deleted is back and I can't install or remove apps. I figured I had something corrupted and a factory wipe would fix it. Unfortunately when I perform a factory wipe from the menus or through Android recovery nothing happens. The tablet boots up like nothing was erased. Still has all my accounts, security pin, apps, and so on.
So after that I figured I would flash the tablet, I found the thread here in the development forum with the stock 3.2 image to load through ODIN. I downloaded everything, followed the instructions. ODIN says the flash was successful but when the tablet reboots it still has all my info and is running 4.0.4. I have tried this multiple times. I have tried loading CWM with ODIN but it will not stick.
Any thoughts? If you need more information I will get it, I am just stuck and can't find anything that helps me with this problem!
Thanks for your help!!!
If you want cwm to load after you install it using odin, then you must immediately boot the tablet into recovery without letting it run normally. During the normal boot process, CWM is deleted and the stock recovery is restored. Therefore once Odin finishes installing CWM, hold the volume up button and once you get to the recovery mode you will be running CWM instead of the stock recovery module.
Regards,
Michael
Yes, I did read that in the multiple thread about installing CWM and have gone into recovery directly after ODIN reboots the tablet, however it is still only the stock recovery app.
Any ideas why the factory reset / data wipe won't work?
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Mixinitup4Christ said:
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Click to expand...
Click to collapse
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
pershoot said:
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
Click to expand...
Click to collapse
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Mixinitup4Christ said:
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Click to expand...
Click to collapse
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
rozeins gone
pershoot said:
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
Click to expand...
Click to collapse
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Mixinitup4Christ said:
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Click to expand...
Click to collapse
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
Will Do, ODIN3 1.85?
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Mixinitup4Christ said:
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Click to expand...
Click to collapse
I had to do this on mine. http://techne.alaya.net/?p=8829. I rooted and modified the file described in the steps. Weirdly enough it still booted into stock recovery the first time I installed CWM. I installed CWM one more time and the tablet now boots into CWM.
Hi all,
I'm having a very strange issue with my i9300 today. I left it charging switched off overnight, and when I tried to switch it back on, it hangs on the Samsung bootscreen. I thought it was odd, but solvable. I went into recovery to try and reflash with the backup I have stored on my sdcard, however when it tried to wipe /Data, it rebooted and hung on the bootscreen again.
I initally had CWM 6.0.4.4 recovery installed, however I have tried PhilZ and TWRP to no avail. All three reboot on flashing /Data.
Anyone have any ideas?
For information, I was running 4.4 KitKat Unofficial. If you need any more information (preferably what can be pulled in Recovery/Download), I'll be happy to post it.
I need my phone running back normally ASAP!
Hi just a little confused..When you say all three reboot on flashing data do you mean data from your backup? If so your backup might be corrupt have you tried doing a clean flash with another rom or tried returning to stock?..Also if you don't want to lose data stored on your backup you can try flashing the original rom that you where on when you made the backup then using philz recovery in advanced settings/ restore you can then just restore data from your backup not the whole rom...And try formatting data system and cache but don't forget this will leave you without a rom so have one ready to install on your sd card....Hope all that makes sense
tallman43 said:
Hi just a little confused..When you say all three reboot on flashing data do you mean data from your backup? If so your backup might be corrupt have you tried doing a clean flash with another rom or tried returning to stock?..Also if you don't want to lose data stored on your backup you can try flashing the original rom that you where on when you made the backup then using philz recovery in advanced settings/ restore you can then just restore data from your backup not the whole rom...And try formatting data system and cache but don't forget this will leave you without a rom so have one ready to install on your sd card....Hope all that makes sense
Click to expand...
Click to collapse
Sorry, I should have been clearer. I was trying to Format the /Data partition in recovery in preparation to restore the backup, and every time a Recovery attempts to Format the partition the phone reboots.
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
tallman43 said:
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
Click to expand...
Click to collapse
Bleh. Returning to stock didn't work. It went past the bootscreen to the green android loading bar screen, went part way then rebooted, and stuck on boot again. >.>
Stickied faqs and guides .
But first what does Product Code say in download mode .
Originally Posted by tallman43<br />
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
Click to expand...
Click to collapse
<br />
<br />
Bleh. Returning to stock didn't work. It went past the bootscreen to the green android loading bar screen, went part way then rebooted, and stuck on boot again. >.>
Click to expand...
Click to collapse
You now have to go to recovery and wipe data/factory reset, wipe cache and reboot. It'll most probably work.
Sent from my silky smooth Samsung GALAXY S3
Rayan28 said:
You now have to go to recovery and wipe data/factory reset, wipe cache and reboot. It'll most probably work.
Sent from my silky smooth Samsung GALAXY S3
Click to expand...
Click to collapse
Ah, that would make sense. I'll give that a try now.
Nope. It's still hanging on the Samsung Bootscreen. Sigh.
I think I'm resigned to the fact I'm going to have to replace this. Most likely with a Nexus 5. Oh well. That sets back some of my luxury spending for the month again.
TermyJW said:
I think I'm resigned to the fact I'm going to have to replace this. Most likely with a Nexus 5. Oh well. That sets back some of my luxury spending for the month again.
Click to expand...
Click to collapse
Are you even flashing the correct ROM for your device with the correct model number? If yes, redownload the ROM. It could be a bad download. This time try the latest 4.3 Jelly Bean.
So I was flashing the new Hyperdrive Rom for the Verizon S4 and I made a mistake. After I wiped data/factory reset the device, cleared the dalvik and cleared the cache I accidentally swiped "Reboot" prior to installing a new Rom. Seeing what I did, I pulled the battery and rebooted into recovery. After rebooting into recovery, I re-wiped the data/factory reset, re-wiped the dalvik and re-wiped the cache.
I then installed the new rom RS11 Rom through the Aroma installer and when I click "Reboot", nothing happens. Phone just goes black and the only thing I can do with it is pull the battery and reboot into recovery. I've re-wiped everything multiple times and performed multiple fresh flashes, but this happens every time.
What did I do? Is this thing bricked? I have a nandroid backup made, but unfortunately it is on a separate SD at home and I'm currently at work.
Any help/advice would be tremendously appreciated.
Thanks!
rjbecker26 said:
So I was flashing the new Hyperdrive Rom for the Verizon S4 and I made a mistake. After I wiped data/factory reset the device, cleared the dalvik and cleared the cache I accidentally swiped "Reboot" prior to installing a new Rom. Seeing what I did, I pulled the battery and rebooted into recovery. After rebooting into recovery, I re-wiped the data/factory reset, re-wiped the dalvik and re-wiped the cache.
I then installed the new rom RS11 Rom through the Aroma installer and when I click "Reboot", nothing happens. Phone just goes black and the only thing I can do with it is pull the battery and reboot into recovery. I've re-wiped everything multiple times and performed multiple fresh flashes, but this happens every time.
What did I do? Is this thing bricked? I have a nandroid backup made, but unfortunately it is on a separate SD at home and I'm currently at work.
Any help/advice would be tremendously appreciated.
Thanks!
Click to expand...
Click to collapse
What recovery are you on? Have you tried rebooting through the recovery rather than Aroma?
joshm.1219 said:
What recovery are you on? Have you tried rebooting through the recovery rather than Aroma?
Click to expand...
Click to collapse
I'm on OUDhs CWM Touch Req0very v1.0.3.5.
I'm worried to reboot through the recovery, because it's telling me "ROM may flash stock recovery on boot. Fix?"
^^Will I lose root if I say ok to that?
You can Odin back to stock and start over as worst case scenario.
powered by hashcode safestrap hyperdrive 10.2
decaturbob said:
You can Odin back to stock and start over as worst case scenario.
powered by hashcode safestrap hyperdrive 10.2
Click to expand...
Click to collapse
I've read things in the past about going back to stock and losing the ability to re-root. Is there a way to avoid that?
rjbecker26 said:
I've read things in the past about going back to stock and losing the ability to re-root. Is there a way to avoid that?
Click to expand...
Click to collapse
You are mdk base and using Loki exploit to load custom recovery right?
powered by hashcode safestrap hyperdrive 10.2
rjbecker26 said:
I'm on OUDhs CWM Touch Req0very v1.0.3.5.
I'm worried to reboot through the recovery, because it's telling me "ROM may flash stock recovery on boot. Fix?"
^^Will I lose root if I say ok to that?
Click to expand...
Click to collapse
I don't think you will, I usually say Yes when it asks that and never had a problem. Can't make a guarantee.
joshm.1219 said:
I don't think you will, I usually say Yes when it asks that and never had a problem. Can't make a guarantee.
Click to expand...
Click to collapse
Said yes to it. Same thing happened. Just a black screen and only a battery pull got me back to recovery.
decaturbob said:
You are mdk base and using Loki exploit to load custom recovery right?
powered by hashcode safestrap hyperdrive 10.2
Click to expand...
Click to collapse
Yup, mdk base and using Loki. Are there instructions for how to go back to stock and re-root?
rjbecker26 said:
Said yes to it. Same thing happened. Just a black screen and only a battery pull got me back to recovery.
Yup, mdk base and using Loki. Are there instructions for how to go back to stock and re-root?
Click to expand...
Click to collapse
I am sure there are...not first time some one had to go back to first base. You will need mdk tar file for Odin. Probably a couple out there. I don't have any links.
powered by hashcode safestrap hyperdrive 10.2
SOLVED
Installed my nandroid backup when I got home, the re-wiped and re-flashed hyperdrive rs11. All is good!
Thanks for the help.
Similar problem, can't get the solution! Please help!
I can no longer get my verizon Samsung galaxy s4 into recovery mode with power+home+up button.
I always get to a screen that says
"Downloading.... Do not turn off target!!"
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0 X 0
KNOX WARRANTY VOID: 0 X 0
CSB-CONFIG-LSB: 0 X 30
WRITE PROTECTION: ENABLE
eMMC BURST MODE: ENABLED
This also happens when I tried to do a factory reset and also when I tried to to the OTA update. (They both failed and I got stuck on the same screen)
I can boot the phone by pulling the battery and pressing power+down+home.
Then it says:
Warning!!
A custom OS can cause critical problems in a phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise, press the volume down key to cancel.
I press the volume down key and then I can use my phone, but I can never get into recovery mode or use any different roms.
How can I fix this problem?
Thanks in advance for your knowledge and help!
Verizon Galaxy S4
Android 4.3
Model SCH- I545
Baseband version I545VRUEMJ7
Build number JSS15J.I545VRUEMJ7
Hardware version I545.06
I tried to install a new theme on jasmine rom. I rebooted and phone said updating app, and remained on update app for over 5 minutes.So I rebooted and the phone remained in the jasmine boot screen. I knew I had a problem so i rebooted into recovery, did a complete wipe and installed my backup and rebooted. The phone started to reboot (Lg splash screen) and then stopped. The screen went dark and my red and blue LED lights started blinking. I tried to get back into recovery manually. I was able to get to stock recovery, hit factory reset and instead of going to TWRP, it went back to the black screen and the blinking LED lights. Same results occurred when I hit safe boot.
I also tried to get in DL mode with the volume up button. Instead, the LG splashscreen came on for less than a second, the screen went black and the blinking lights came again. I tried ADB but it won't recognize my phone. Any suggestions, or is this a goner? Thanks for your help.
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
rp201 said:
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
Click to expand...
Click to collapse
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I did the exact same thing early today and stumbled on that same thread. So relieved
jlokos said:
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
Click to expand...
Click to collapse
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
ohlin5 said:
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
Click to expand...
Click to collapse
I have no clue what happened; Verizon sent me a new phone. I don't have a clue whether this was related to the theme, or not. It may have been an unrelated hardware issue.
This started with my trying Online Nandroid Backup from the Play store, which I've used on my previous Android phones. I made a backup with it (I had TWRP v2.8.2.0) while Jasmine 4.0 was up and running, and then I booted to recovery, made a regular backup directly in recovery, then wiped and tried to restore the backup that Online Nandroid created. I saw something in the restore log about uboot partition. It restored the rest of my partitions fine. Then I made a bad choice and I told TWRP to reboot. I thought I should still be able to get into TWRP even if the ROM won't boot, but negative.
The only thing I can get into is the menu to choose Factory Reset, Wipe Cache, Power Off, Continue Boot, and I think there's one other option.
I've tried them all. I've tried leaving the battery out for more than a minute and then trying again. No matter what, after a brief show of the LG logo, the screen goes dark and the notification LED toggles between green and orange repeatedly.
No ROM booting, not even starting, no recovery at all. The computer doesn't see it in this state. I've tried LGMLauncher.exe, LG Flash Tool 2014, and as I expected nothing will see it, which makes sense.
Any ideas? I expect I'm SOL.
Thanks for your time.
looks like you have stock recovery and that's it. Have you tried getting it in to download mode?
BladeRunner said:
looks like you have stock recovery and that's it. Have you tried getting it in to download mode?
Click to expand...
Click to collapse
Hi, thanks for your suggestion.
Maybe you mean something other than "Stock Recovery"? I had TWRP on there previous to restoring the backup, and the backup had TWRP in it too. All options from the menu resulted in the same Green-Orange-Green, etc LED.
I just got home with a replacement. Ugh.
Something like that happened to me.once the whole lg blank screen then the led lights... I just flashed a stock ROM with the flash tools and solved me problem