Database Info

[ODIN] Stock Rooted ED1 (downgrade from ED2) [2011.05.18]

Well here is something that I hope is the start of some hardcore hacking.
This is an ODIN that I created of stock-rooted ED1 for the DROID Charge. In the course of making this, I bricked my charge (first attempt failed in ODIN) and then created a working ODIN that un-bricked it. I then upgraded to ED2 (I confirmed that I lost root as well) so I could test if this will downgrade back to ED1 and it worked and I have root again!
Instructions for ODIN (for those who are unfamiliar with it):
1. Open ODIN.
2. Put the phone into download mode. Do this by powering off your phone, pulling out the battery, and then holding volume down while connecting it to your pc. A giant yellow triangle should be on the phone's screen and it should say 'Downloading...' ODIN should say 'Added!!' and one of the boxes will be yellow and say '0:[COM#]'
3. Click the button labeled 'PDA' and locate the file you are wanting to flash. For emphasis: YOU MUST USE THE PDA BUTTON!
4. Click start. Do not disconnect the phone while it is flashing, it can cause some serious damage.
5. Wait.
6. When finished, unplug the phone, put the battery back in and power up the phone.
Every time I've flashed this, the phone booted straight into recovery. Just select reboot (press home) and it boots up normally. It should probably be recommended to wipe data and cache afterwards, but I didn't and all of my data stayed in tact.
Multiple people have reported that this works. Use at your own risk. I am not responsible for anything that happens to your phone if this doesn't work.
Thanks to imnuts for the HOW-TO thread on creating ODIN builds.
Download here.
Download ODIN here.
to my redbull habit if you feel the need.

I feel dumb for asking, but what are you using to flash this to the phone? I've never used anything other than simple one click root programs, so if you could give a little more detail I'd be happy to try it out.

Download Odin here: http://goo.gl/52aY1
Download Drivers here: http://goo.gl/Tbcca
Download stockrootedED1-20110517.tar.md5 http://goo.gl/kD3Ld
1. Open Odin3 v1.30
2. Remove battery,Hold Vol down. Connect USB to computer and phone then press power. It should take you to a yellow android.
3. Click PDA Button
4. choose stockrootedED1-20110517.tar.md5
5. Click on the Start button
6. Don't Touch and allow the phone to reboot
7. If its taking a while to start DONT PANIC, its perfectly normal

Thanks for the guide, but it doesn't do anything for me, seems like Odin doesn't even know my phone is there. When I plug it in I get the Verizon media manager link to pop up though.

I edited my first post with a link to ODIN and instructions. I guess I'm a little slow with the typing because you beat me to it medjam, but you left out the step of putting the phone into download mode.

Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!

that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.

Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
Once rooted go into your build.prop file and every thing that says ED1 change it to ED2...that should quit the nagging to update. Then restart your phone
Credit goes to Jt3 for that info as he posted it in the Charge forum at android central.

Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
AWESOME!!! So glad to help!

Very nice!
I know that this will kick start the development of this device now that everybody can haz root.

so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance

streetlightman said:
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
Click to expand...
Click to collapse
Should work for everyone. My Charge that I just ran it on was never rooted before.

das7771 said:
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Click to expand...
Click to collapse
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App

jt1134 said:
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
OH OK...Well let me make change my statemet to be more adult like. If i brick my phone I will just go buy another full price so I don't seem like an asshole. I hope this pleases you Sir....

Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?

teddykgb715 said:
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
Click to expand...
Click to collapse
Did you install the drivers that came with the phone?

wynalazca said:
Did you install the drivers that came with the phone?
Click to expand...
Click to collapse
I thought so, I can connect to USB storage, etc. I'll check it out.

Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.

teddykgb715 said:
I thought so, I can connect to USB storage, etc. I'll check it out.
Click to expand...
Click to collapse
I think the issue is that my damn work laptop is locked down pretty tight so it won't let all the drivers install. Unlike many here, I'm actually not an IT professional so I can't circumvent it. I'll just have to try it at home tonight.

das7771 said:
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
Click to expand...
Click to collapse
You're welcome! I'm very glad to help get this development stuff going. Also, there should be a donate button in the OP.

[Q] Need Some Help Please

I flashed user paulburton's ics rom (beta). I played with it, but wanted to go back to stock (rooted). Problem is, that I must have downloaded the unrooted version of them rom and therefore cannot boot into recovery revert to the backup of my rom. Furthermore, the ics beta will not allow me to install CWM nor will it give me su permissions to do anything. Even worse, mass storage (micro sd) is disabled on this beta. Is there some way (via adb commands possibly) to remove/delete the ics beta and go back to stock? Any help is appreciated.

It quite clearly states that you should not try it unless you know how to get back to honeycomb. If you have SBK1 aka your serial number is B60 or lower then use NVFlash to get back to stock. As there is not a "Unrooted" version of the rom i have no idea what you did. Also when you go into recovery "IE hold powerbutton and volume down then up" what does it show?

mrevankyle, you may want to check your facts. there IS a rooted version of the beta, or at least there is on his blog. and I thought I could get back to honeycomb. Anyway, the message I get when I hold down the power button and volume- is the option to cold boot linux or wipe data.

Tha Driver said:
mrevankyle, you may want to check your facts. there IS a rooted version of the beta, or at least there is on his blog. and I thought I could get back to honeycomb. Anyway, the message I get when I hold down the power button and volume- is the option to cold boot linux or wipe data.
Click to expand...
Click to collapse
You have to push the Vol Up button within about 5 secs after seeing the words
at the top left corner. If you wait too long you'll get the cold boot/wipe data options.

Tha Driver said:
mrevankyle, you may want to check your facts. there IS a rooted version of the beta, or at least there is on his blog. and I thought I could get back to honeycomb. Anyway, the message I get when I hold down the power button and volume- is the option to cold boot linux or wipe data.
Click to expand...
Click to collapse
Why would you even try this if you don't even know how to get to recovery? Should have gotten an ipad.

baseballfanz said:
I guess that means no to the iPAd?
J/K LOL.
Click to expand...
Click to collapse
Baseballfanz, first and foremost, thank you for your assistance. I was able to get into recovery and get my backup installed. As for the douchebag (goodintentions), people such as himself (or herself) really make forums like these a drag. Everyone is not as experienced as him/her or it may be their first time with a particular device. Instead of offering something useful, he offers a smart ass comment, which was totally uncalled for. He/she seems to have forgotten that they too were a noob at one point.

Tha Driver said:
Goodintentions, I don't understand "how scary" it could have been for you or "how further south" it could have gone for anyone but me. If I had indeed bricked my tf, you would not have been out of any money or time. It would have been myself that was out of time and or/money. Furhermore, I stick by my original assessment that if you could not/did not want to help, just STFU. The comment about buying an iPad was uncalled for.
Click to expand...
Click to collapse
People here are glad to help you and as you can see by all of our posts and thanks we have all been here a while. You have not. All of this information is in the reference thread
http://forum.xda-developers.com/showthread.php?t=1044424
As for the comment about the ipad that is essentially the XDA version of calling someone a NOOB and is not to be taken so seriously. It is also nearly impossible to completely brick these things. SO you do not have to worry. And sorry if my original directions were not clear
Tha Driver said:
mrevankyle, you may want to check your facts. there IS a rooted version of the beta, or at least there is on his blog. and I thought I could get back to honeycomb. Anyway, the message I get when I hold down the power button and volume- is the option to cold boot linux or wipe data.
Click to expand...
Click to collapse
And yes that is what i said that there was NO UNROOTED version SO YOU MUST HAVE GOTTEN THE ROOTED VERSION. And also the one on his blog is the original unupdated one and not the latest version so please check your facts before blaming other people

I think we've all learned a valuable lesson here. Closing this thread.

With JB installed: CWM Recovery causes a hang when I try to load into it.

Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?

badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.

untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.

I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.

badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?

sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265

krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that

Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.

krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient

Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.

I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim

I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.

jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...

untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.

It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse

[OUDHS] CWM based recovery for AT&T Express

Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.3
for your AT&T Samsung Galaxy Express
Read this whole post before doing anything ​
Enjoy
Odin Flashable - OUDHS CWM-based Recovery 1.0.3.3
Odin 3.04
Drivers
Directions:
1) Download the above files
2) Extract Odin3-3.04.zip and copy the tar that you downloaded into the folder
3) Run Odin as an administrator
4) Power your device off
5) Press and hold volume down and power to enter download mode
6a) Connect your phone to your computer
6b) Wait for drivers to finish installing if they need to be
7) You should see Odin find your device by marking a blue square in the ID COM box
8) Click on PDA and choose the recovery tar you downloaded
9) Click start
-----------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now if you wish to root youll need to follow these instructions
-----------------------------------------------------------------------------------------------------------------
SuperSU+ 1.25
Directions:
1) Download the above file
2) Connect your phone and copy them to your phone
3) Once they are copied power down your device
4) Hold volume up and power to enter Clockworkmod recovery
5) Navigate recovery by using the volume keys and power to select
6) Choose install zip from sdcard, then pick internal or external (where you copied it to)
7) Scroll down to the SuperSU+.zip and select it to install
-----------------------------------------------------------------------------------------------------------------
Congrats you are rooted! this procedure will work on any firmware update you guys get
-----------------------------------------------------------------------------------------------------------------
If you enjoyed getting root/recovery and want to show appreciation you can always buy me a coke​​
Source​
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) For being the best we can for those whom need us
rdawson28 For being an awesome tester
BlindArtisan For providing the stock recovery, thanks man

I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.

Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?

BlindArtisan said:
Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?
Click to expand...
Click to collapse
www.shabbypenguin.com/OUDstuff/Samsung/ATT/Express/Express-OUDHS-CWM.tar

Thank you. An alternate way to install for those who are rooted and don't want to use Odin.
Create a copy of the recovery on your sdcard.
In the android terminal or adb with shell type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
To make the recovery permanent.
Find /system/etc/install-recovery.sh
Rename the file install-recovery.sh.backup
Reboot into recovery and enjoy the glory.
Sent from my rooted SAMSUNG-SGH-I437 using xda app-developers app

JDC2389 said:
I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.
Click to expand...
Click to collapse
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.

Sworder said:
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.
Click to expand...
Click to collapse
You could always uninstall the drivers then install fresh ones from Samsung. Or use the in phone method.
Sent from my rooted SAMSUNG-SGH-I437

I has to uninstall then put the fresh drivers on thats the easiest way
Sent from my SAMSUNG-SGH-I437 using xda app-developers app

Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.

invert_nexus said:
Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.
Click to expand...
Click to collapse
I have the exact same issue with the date.
I don't quite understand what you are saying, but It doesn't try to fix root on boot it tries to fix the recovery.img
Sent from my rooted SAMSUNG-SGH-I437

Thanks blind you came through for me, that way I didn't have to worry about my phone being recognized in download mode. Nice job on the recovery it looks fantastic.
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Someone needs to make a video about this root method to spread the word and upload it to youtube!

Worked flawlessly on a new phone. A 6 month old one, all appears ok, it sees the phone, odin loads the image, phone reboots ok. When I try try to reboot into recovery mode I get the stock recovery, not CWM.
Any ideas?

guys i am so sorry, i had to reinstall linux and thought i lost teh device t ree, anyways i compiled a new version of OUDHS recovery for yall. and finally uploaded source

Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?

invert_nexus said:
Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?
Click to expand...
Click to collapse
source is at the link
and there is a good deal different in the latest version. honestly i suggest everyone upgrades

Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.

invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
Havent updated yet but sounds like the same problem as before ill test tomorrow been really busy also gonna work on the cooked up rom more when I get a chance im sure the recovery issues will be fixed shortly
Sent from my SAMSUNG-SGH-I437 using xda app-developers app

invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
the time will always be off, recovery doesnt talk to the rest of the phone. crap, did that get fixed? or was it always broken?

shabbypenguin said:
the time will always be off, recovery doesnt talk to the rest of the phone.
Click to expand...
Click to collapse
Odd. Is that just an ussue with this phone?
crap, did that get fixed? or was it always broken?
Click to expand...
Click to collapse
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.

invert_nexus said:
Odd. Is that just an ussue with this phone?
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.
Click to expand...
Click to collapse
the time this is android wide afaik. twrp and official cwm have teh same bug :/
and crap that means some of the new features broke stuff for yall :/ ill put the old on back up in the OP i was really hoping to give you guys touch recovery

SM-G955U1. XAA version. Bootloop problem, any help?

MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin

fefin said:
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
Click to expand...
Click to collapse
Have you reached out to Samsung yet?

Mr. Orange 645 said:
Have you reached out to Samsung yet?
Click to expand...
Click to collapse
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin

fefin said:
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
Click to expand...
Click to collapse
I mean have you called or emailed Samsung?

Mr. Orange 645 said:
I mean have you called or emailed Samsung?
Click to expand...
Click to collapse
No I haven't, I will give a try soon through web chat.
I mean, this shouldn't be happening, it's a brand new phone, all over the internet are people with the same problems as me and looks like so far there is no solution.
Maybe it's a faulty phone/hardware? My knowledge is not enough in this matter.
See you!,
Federico.

I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app

allenjthomsen said:
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.

fefin said:
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
Click to expand...
Click to collapse
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.

allenjthomsen said:
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
Click to expand...
Click to collapse
Sadly it didn't work. The phone is still loading till "android is starting" sign and then restarting again.
I will write you so you can help me through pm, could this be a faulty hardware?

I'd like to know the other solution too.

I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app

try installing PartCyborgRom

@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone ??
Sent from my SM-G955W ??

allenjthomsen said:
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your help! Much appreciated.
DR25 said:
try installing PartCyborgRom
Click to expand...
Click to collapse
Thanks for your suggestion, I will look into it.
shaggyskunk said:
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone
Sent from my SM-G955W
Click to expand...
Click to collapse
Thanks for answering!, sorry for my late response.
Well, if you check samsung's official forum there are a few threads with 15+ pages of people complaining about wifi issues (https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/862/page/1 and https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/30601/page/1) about bootloop problems, (https://us.community.samsung.com/t5...id/GS8QA/thread-id/3920/highlight/true/page/1) also there is a post on another webpage talking about bootloops on this model and how to fix them (https://thedroidguy.com/2017/12/sol...p-issue-s8-turns-screen-remains-black-1079013).
I know it's not representative, as you said, millions of phones has been sold, but what I meant when I said "all over the internet" is that you can easily find people with this same problem. This shouldn't be happening, not on any phone even less on such an expensive phone.
I think the phone is officially dead, I took it to a well known local technician and even him couldn't fix it. My nearest official samsung service is 1600km away. On the other hand, my aunty got for herself an S8 and it's working perfect, so it's just bad luck for my mom I guess.
The phone had issues since she bought it (wifi and bluetooth didn't worked at all, but she is not really a tech person so she thought it was fine), the phone was working with some bootloops from time to time and after a while it fell from and got a little crack on the top but it didn't change the behavior of the phone, it was still ****ed up. That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.

fefin said:
That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
Click to expand...
Click to collapse
If you have some 'proof' the problem existed, before the crack, and can prove when the crack occurred, or reasonable determinate approximation, small claims court will vindicate you, and Samsung will have to pay.
Sad to say would take a little time of yours to get them there, but it is an easy process, and with reasonable ability to determine/evidence those two things, a sure win.
But still a PITA.