Database Develop

[Q] stuck in broken recovery mode

Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz

No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.

cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz

Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.

Starting to get worried - bootloop [RESOLVED] :D

I was following the official cyanogen mod wiki guide and everything was fine up until step 6. I couldn't boot into recovery mode, but I could boot normally. So after turning the phone off to try again, I realized I am now stuck in a boot loop. I can boot into download mode perfectly but now ODIN doesn't recognize when the phone is plugged in. Should I be worried? I have no idea what to do..
Thanks in advance, if you need more info feel free to ask!
Original problem (bootloop) was solved by using Heimdall, as was every subsequent problem I encountered in this thread. Many thanks to all!

MrCathal09 said:
I was following the official cyanogen mod wiki guide and everything was fine up until step 6. I couldn't boot into recovery mode, but I could boot normally. So after turning the phone off to try again, I realized I am now stuck in a boot loop. I can boot into download mode perfectly but now ODIN doesn't recognize when the phone is plugged in. Should I be worried? I have no idea what to do..
Thanks in advance, if you need more info feel free to ask!
Click to expand...
Click to collapse
Don't worry, it doesn't sound bad.
Can you enter CWM recovery? If yes, wipe 3 times (data/factory reset - cache - dalvik cache under "advanced") and reboot. It should do it.
If only download mode is accessible, you must flash a stock ROM with PIT file which will do proper re-partition of the /system again, root it and install CWM. After that you can flash again CM10.2. Don't use the CM site, use the thread of developer pawitp, just flash also compatible Gapps version right after the rom while still in recovery.
Best stock ROM as basic for clean flashing of CyanogenMod seems to be Froyo with SpeedMod kernel. Check this thread, all download links are there and working. If it helps you, post in that thread that it worked:
http://forum.xda-developers.com/showthread.php?t=2444308
Good luck

tetakpatak said:
Don't worry, it doesn't sound bad.
Can you enter CWM recovery? If yes, wipe 3 times (data/factory reset - cache - dalvik cache under "advanced") and reboot. It should do it.
If only download mode is accessible, you must flash a stock ROM with PIT file which will do proper re-partition of the /system again, root it and install CWM. After that you can flash again CM10.2. Don't use the CM site, use the thread of developer pawitp, just flash also compatible Gapps version right after the rom while still in recovery.
Best stock ROM as basic for clean flashing of CyanogenMod seems to be Froyo with SpeedMod kernel. Check this thread, all download links are there and working. If it helps you, post in that thread that it worked:
http://forum.xda-developers.com/showthread.php?t=2444308
Update; Have restarted the laptop and tried a total of 4 different cables, to no avail.
Good luck
Click to expand...
Click to collapse
The speedy reply is appreciated, however Odin refuses to acknowledge my phone for some reason. The device is recognized by my PC, the drivers are installed, after all everything worked seamlessly the first time. Any ideas?

MrCathal09 said:
The speedy reply is appreciated, however Odin refuses to acknowledge my phone for some reason. The device is recognized by my PC, the drivers are installed, after all everything worked seamlessly the first time. Any ideas?
Click to expand...
Click to collapse
Is USB debugging enabled?
Otherwise, leave your i9000 turned off, run Odin and prepare all files first and turn the i9000 on into download mode just short before connecting and flashing. The i9000 has kind of "sleep mode" in download mode so if you run it into the download mode and wait few minutes, nothing will happen anymore.

also try a different USB socket on your computer

Samsung kies is killed???

No amount of port/wire changing seemed to work with Odim. However I followed a tut on youtube to flash with Heimdall, and my phone finally booted up with froyo 2.3.3
My original plan was to downgrade from Cyanogen mod, which my older brother put on a few years ago. The phone was beginning to lag and stuff, so yesterday I finally decided to do something about it. The PLAN was, to downgrade to froyo, and then upgrade to Cyanogen mod 10.2, however after getting froyo, my phone went a boot loop (hence this thread).
So I'm asking you all, what is my next step? I'm usually not this helpless, but I can't afford to screw this up again, and I'm honestly a bit scared to try anything without your say. As I said, I am now on froyo2.3.3, and the phone seems okay.
I'm looking through the file manager, and there's loads of cyanogenmod files in the root directory from before. I sorta wanna clean everything out before upgrading. Where should I go from here?

MrCathal09 said:
No amount of port/wire changing seemed to work with Odim. However I followed a tut on youtube to flash with Heimdall, and my phone finally booted up with froyo 2.3.3
My original plan was to downgrade from Cyanogen mod, which my older brother put on a few years ago. The phone was beginning to lag and stuff, so yesterday I finally decided to do something about it. The PLAN was, to downgrade to froyo, and then upgrade to Cyanogen mod 10.2, however after getting froyo, my phone went a boot loop (hence this thread).
So I'm asking you all, what is my next step? I'm usually not this helpless, but I can't afford to screw this up again, and I'm honestly a bit scared to try anything without your say. As I said, I am now on froyo2.3.3, and the phone seems okay.
I'm looking through the file manager, and there's loads of cyanogenmod files in the root directory from before. I sorta wanna clean everything out before upgrading. Where should I go from here?
Click to expand...
Click to collapse
Excellent BTW, 2.3.x is Gingerbread, not Froyo. Upgrading to CM10.2 from Froyo with SpeedMod kernel works very well. Here is a step-by-step guide:
http://forum.xda-developers.com/showthread.php?t=2444308
You are good adviced to read carefully, not just briefly. So you will void problems.
It could be, that your Samsung USB driver hasn't been installed properly. Installing Heimdall drivers has removed Samsung USB driver from my PC some months ago so be sure to have all working before flashing any new build.
If you flash now some Froyo build over your Gingerbread, you don't need PIT file and re-partition. Leave that field empty and don't touch any Odin options (re-partition will remain unchecked). Use compatible Odin version.

tetakpatak said:
*snip*
Click to expand...
Click to collapse
You're a hero! So I am now following that guide, and here are the steps I think I need first;
Root & install CWM recovery: turn off your i9000 and download speedmod-kernel-k13e-500hz.tar
Run Odin as admin, set "speedmod-kernel-k13e-500hz.tar" under PDA. Reboot and reset time checked, re-partition unchecked(!!)
start your i9000 in download mode with 3-button-combo and connect it via USB cable
if <Added!> and ID:COM port number are displayed in Odin, click on "Start"
after only few seconds kernel will be flashed and your i9000 will automatically reboot
Enjoy, now you can install zips of the CM build and compatible gapps for it via CWM recovery, SpeedMod kernel features CWM version 2xxx so after first attempt to install CM.zip it will upgrade just the CWM recovery to version 6xxx, so after that you can really flash the CMbuild.zip
How would I go about doing this process with Heimdall, as Odin is really not an option anymore

you could also try Mobile Odin Pro (google it) then choose the flashing kernel from here http://ndroidplay.blogspot.com/2012/08/mobile-odin-flash-kernels.html?m=1 then just flash the custom rom from Mobile Odin.
EDIT: this is the flashing kernel for i9000 http://dl.xda-developers.com/attach...9/9/8/7/MobileODIN_FlashKernel_I9000-v2.0.zip
---------- Post added at 12:53 PM ---------- Previous post was at 12:31 PM ----------
actually to use Mobile Odin i forgot you need a phone that working and can boot into the OS to install it so may not be an option for you.

After many hours of errors and whatnot, I have finally managed to upgrade my phone to Cyanogen Mod 11-20131207-NIGHTLY-galaxysmtd.
However, there's no play store!
Apparently I'm running android 4.4.1 and CM 11, therefore none of the gapp files are applicable?
I tried installing the latest one, only to get the error: (bad)

Did you use the latest nightly from today (20131208) ???
And the gapps for CM 11 ??? ==> http://wiki.cyanogenmod.org/w/Gapps
MrCathal09 said:
After many hours of errors and whatnot, I have finally managed to upgrade my phone to Cyanogen Mod 11-20131207-NIGHTLY-galaxysmtd.
However, there's no play store!
Apparently I'm running android 4.4.1 and CM 11, therefore none of the gapp files are applicable?
I tried installing the latest one, only to get the error: (bad)
Click to expand...
Click to collapse

freakymod2120 said:
Did you use the latest nightly from today (20131208) ???
And the gapps for CM 11 ??? ==> http://wiki.cyanogenmod.org/w/Gapps
Click to expand...
Click to collapse
Exactly what I needed. Many thanks!
And thanks to everyone else who helped, I really thought my phone was busted for a while there.

MrCathal09 said:
You're a hero! So I am now following that guide, and here are the steps I think I need first;
Root & install CWM recovery: turn off your i9000 and download speedmod-kernel-k13e-500hz.tar
Run Odin as admin, set "speedmod-kernel-k13e-500hz.tar" under PDA. Reboot and reset time checked, re-partition unchecked(!!)
start your i9000 in download mode with 3-button-combo and connect it via USB cable
if <Added!> and ID:COM port number are displayed in Odin, click on "Start"
after only few seconds kernel will be flashed and your i9000 will automatically reboot
Enjoy, now you can install zips of the CM build and compatible gapps for it via CWM recovery, SpeedMod kernel features CWM version 2xxx so after first attempt to install CM.zip it will upgrade just the CWM recovery to version 6xxx, so after that you can really flash the CMbuild.zip
How would I go about doing this process with Heimdall, as Odin is really not an option anymore
Click to expand...
Click to collapse
Cool, congratulations!
Please if it helped, just post it in my thread that it helped:
http://forum.xda-developers.com/showthread.php?t=2444308
...and also please post info/workflow how did you solve it with the Heimdall, so that other forum users who are in need can benefit from your experience.
Have lot of fun with the KitKat

tetakpatak said:
Cool, congratulations!
Please if it helped, just post it in my thread that it helped:
http://forum.xda-developers.com/showthread.php?t=2444308
...and also please post info/workflow how did you solve it with the Heimdall, so that other forum users who are in need can benefit from your experience.
Have lot of fun with the KitKat
Click to expand...
Click to collapse
I might write up a more in-depth tut later on for those as clueless to the scene as I am, however for now the whole process can be summed up in a few major steps;
Down/Upgrade to GingerBread (Android 2.3-2.3.2)
Root
Install ClockWorkMod
Wipe cache/data
Install Cyanogenmod

Perfect, good to hear, that your phone works as "desgined" :good:
MrCathal09 said:
Exactly what I needed. Many thanks!
And thanks to everyone else who helped, I really thought my phone was busted for a while there.
Click to expand...
Click to collapse

[Q] stucked after a fail with odin

Hi everybody,
just got an old yet effective SGS and I wanted root and get rid of touchwizz and all the crap from my carrier
I was unable to boot into DL mode, i tried everything, so I had to do it with adb reboot
I never had to use Odin to do my hacking with android so i'm not used to it but short story : I rename my rom.zip into rom rom.tar, it failed and all I have is this now :
https://www.dropbox.com/s/wk42jbmp33a3ftu/IMG_20140715_152917.jpg
Also I need to unsimlock, flashing a new rom will also do the trick right ?
thanks

What you just did is bricking your phone. It it was a zip file you need to install it from the recovery. Renaming it is not the way it works. I'm not sure if now you can fix it. Sorry, man
Sent from my GT-I9000 using XDA Premium 4 mobile app

Do you know what I can at least try?

If you can get into download mode:
Follow sections 2 and 3 in this guide.
If you can't:
Follow this guide and after that do what I sails to do if you have download mode.

Does 3-button-combo not work to get into the download mode?
(power & home & volume down)
tetakpatalked from Nexus 7 flo

so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys

@Idealith simlock has nothing to do with the firmware.
You need now any root kernel for that firmware, it has to be compatible with the intiframs of your 2.x version and it will give you a custom recovery.
There you can flash first CM10.2 to get the modified partition sizes and KK ready recovery and after that you can flash CM11
IMHO, the new Mackay ICS 2014 rom based on CM9 is a lot faster than any KitKat and works better on the i9000
tetakpatalked from N7100

my question about the rom still applies cause this one is awful
but with what does it have to do then ?
EDIT : my browser didn't render the end of your answer
I'm afraid i'm not following though :/

I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/

Idealith said:
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Click to expand...
Click to collapse
Hey, could you tell me which country you are at? I could then take a few steps to help you
PFFFFFFFFFFFFFFFFTTT, sent from my i9000

I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks

Idealith said:
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Click to expand...
Click to collapse
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo

tetakpatak said:
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works

Idealith said:
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Click to expand...
Click to collapse
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100

tetakpatak said:
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
Click to expand...
Click to collapse
and how do i get that bootloader set up ?

Idealith said:
and how do i get that bootloader set up ?
Click to expand...
Click to collapse
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100

tetakpatak said:
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
Click to expand...
Click to collapse
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?

Idealith said:
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Click to expand...
Click to collapse
Ask your carrier, I assume the phone contract isn't new anymore (or expired) so you'll get unlock code for free. Here in Europe one can obtain the unlock code after 2 years for free.
Otherwise you can ask one of the online unlock services, it costs usually around 15-20$ to get the code
tetakpatalked from N7100

Idealith said:
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
Click to expand...
Click to collapse
I'm glad that the JIG helped you (I know I'm late )

danielbe said:
I'm glad that the JIG helped you (I know I'm late )
Click to expand...
Click to collapse
yeah that worked like a charm
it was a good idea to buy it, i would have use the resistors so much
is there a more xda way to unlock it ? my carrier wants me to send the phone and have it unlock, they won't just provide the code :/

Does flashing stock ROM via Odin wipe data?

Hello,
So my Galaxy S6 is stuck in a boot loop and i've literally tried EVERYTHING already and nothing will solve the problem. Safe mode won't work, clearing the cache partition won't work and USB Debugging was turned off so adb wasn't seeing my device either. I also tried Kies and Smart Switch. I am convinced my phone is soft bricked and I need to recover some very important pictures and files from it. At this point my last hope is to flash the stock ROM via Odin and I saw that some people said that they have successfully done this without losing any of their data. Is this possible? If so how do I go about doing it properly?
Thanks for any help!
Phone is not rooted and 100% stock.
Recovery and Download screens are working.

How did Kies not work for you? I used it about 4 times to restore to like new.

cwhiatt said:
How did Kies not work for you? I used it about 4 times to restore to like new.
Click to expand...
Click to collapse
Because the phone is stuck in a boot loop. Kies won't detect my phone because it never fully boots.

Weird. I completely removed the system on one before reinstalling the system via Kies before sending it back via warranty exchange. I'd suggest trying again. Obviously you will need model and serial #.

cwhiatt said:
Weird. I completely removed the system on one before reinstalling the system via Kies before sending it back via warranty exchange. I'd suggest trying again. Obviously you will need model and serial #.
Click to expand...
Click to collapse
Tried Kies multiple times but it just won't work. Uninstalled and reinstalled drivers, disconnected and reconnected the phone, nothing works. That's why I turned to Odin.

1337Dev said:
Tried Kies multiple times but it just won't work. Uninstalled and reinstalled drivers, disconnected and reconnected the phone, nothing works. That's why I turned to Odin.
Click to expand...
Click to collapse
Since you can get into recovery, if I were you I'd flash Unikernel (latest version is 9.1 I believe) and then flash a custom rom. If you can get it to boot you shouldn't lose data in the sdcard/download.
---------- Post added at 09:48 PM ---------- Previous post was at 09:46 PM ----------
I am running Sick as Hell version X rom and loving it.

cwhiatt said:
Since you can get into recovery, if I were you I'd flash Unikernel (latest version is 9.1 I believe) and then flash a custom rom. If you can get it to boot you shouldn't lose data in the sdcard/download.
---------- Post added at 09:48 PM ---------- Previous post was at 09:46 PM ----------
I am running Sick as Hell version X rom and loving it.
Click to expand...
Click to collapse
Forgot to mention but I am going to have to return this phone to T-mobile for a warranty exchange, that's why I was trying to avoid custom rom's thinking it might become ineligible. Want to be able to recover data and then reset the phone for return

The phone i wiped the system on was returned via warranty with Tmobile (of course I later reinstalled it via Kies). I would install a custom rom to attempt to get the thing up and running. Once you do that then go from there (back to Kies or factory reset...)

cwhiatt said:
The phone i wiped the system on was returned via warranty with Tmobile (of course I later reinstalled it via Kies). I would install a custom rom to attempt to get the thing up and running. Once you do that then go from there (back to Kies or factory reset...)
Click to expand...
Click to collapse
Ok, Thank you! I was worried about the warranty exchange. I will attempt to install a custom rom let's see how it goes.

The purpose of installing the custom rom is to attempt to retrieve your data. If you can boot and then successfully get your data, it would be advisable to remove the custom rom and restore it to factory. Let me know how it goes...

cwhiatt said:
The purpose of installing the custom rom is to attempt to retrieve your data. If you can boot and then successfully get your data, it would be advisable to remove the custom rom and restore it to factory. Let me know how it goes...
Click to expand...
Click to collapse
Hello another User here , I am in a similar situation . I installed some theme [live] from theme store , then it started acting wierdly. Finally a bad combination of Good Lock , System UI and Safe Mode my phone is in a bootloop.
I want to recover my data mostly videos and pictures. What shall I do. I am unrooted , I can access recovery , adb sideload from recovery , I can get into download mode. Will wipe data option save my Pictures?

y2k2r2d2 said:
Hello another User here , I am in a similar situation . I installed some theme [live] from theme store , then it started acting wierdly. Finally a bad combination of Good Lock , System UI and Safe Mode my phone is in a bootloop.
I want to recover my data mostly videos and pictures. What shall I do. I am unrooted , I can access recovery , adb sideload from recovery , I can get into download mode. Will wipe data option save my Pictures?
Click to expand...
Click to collapse
If you've got recovery installed it would be just for that purpose. Restoring your backup (i.e., recovery). I gather you don't have a backup?
What device do you have?

G920F International. The Recovery is not a custom one . It is the default recovery that doesn't have backup mode.

y2k2r2d2 said:
G920F International. The Recovery is not a custom one . It is the default recovery that doesn't have backup mode.
Click to expand...
Click to collapse
Ahh gotcha. Well...if it were me what I'd do is to boot to download mode and flash TWRP custom recovery file using Odin. Once that passes I'd boot into TWRP and do a backup.
You can then reboot into TWRP and try to restore your backup but you'll likely end up in a bootloop again. If that happens...
Then, I'd download a stock recovery (looks like they have your variant here.
I'd then flash the stock recovery using TWRP and then reboot.
If you get stuck in a bootloop again then I would do a factory reset (which doesn't wipe storage which is where your photos etc. are) and then reflash the stock recovery zip file.
I can't say for certain if that'll wipe your photos, etc. or not but I'm not inclined to think it would.

cwhiatt said:
Ahh gotcha. Well...if it were me what I'd do is to boot to download mode and flash TWRP custom recovery file using Odin. Once that passes I'd boot into TWRP and do a backup.
You can then reboot into TWRP and try to restore your backup but you'll likely end up in a bootloop again. If that happens...
Then, I'd download a stock recovery (looks like they have your variant here.
I'd then flash the stock recovery using TWRP and then reboot.
If you get stuck in a bootloop again then I would do a factory reset (which doesn't wipe storage which is where your photos etc. are) and then reflash the stock recovery zip file.
I can't say for certain if that'll wipe your photos, etc. or not but I'm not inclined to think it would.
Click to expand...
Click to collapse
Thanks. It will help in the backup.
Will factory reset/wipedata from stock recovery remove the pictures ?
Can you backup data using OTG/pendrive from TWRP recovery?

y2k2r2d2 said:
Thanks. It will help in the backup.
Will factory reset/wipedata from stock recovery remove the pictures ?
Can you backup data using OTG/pendrive from TWRP recovery?
Click to expand...
Click to collapse
factory reset doesn't erase storage data.
Not sure about otg/pendrive
Sent from my SM-G920T using XDA-Developers mobile app

I didn't flash TWRP as I learned that Samsung Pay will never work not even Stock ROM flash. I instead pulled some vital data files from adb pull on 'the window of around 1 minute' each time it was active during safe mode rebooting and thankfully Google Photos had a backup of my Photos and videos.
I used the wipe data option on stock recovery that wiped everything. The device is like new.

[SOS] - Calling All Devs - G920T - Stuck on 6.0.1 without an unlocked bootloader

Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.

I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.

What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse

I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.

ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751

Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse

Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse

ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.

Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...

If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?

Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse

Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8

The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse

ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things

I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse

http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe

ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.

For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?

You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse

Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse