I rooted my phone with z4 root. Got Koush's bootstrapper was granted superuser permissions created nandroid backup downloaded liberty 1.5 flashed it without any problems, used it decided I wanted to check out Rubix Focused 1.9 same procedure had no problems flashing it over with bootstrap recovery mode. Decided I wanted to try the Watermarkd theme for it downloaded it transfered to phone no problem followed step by step instructions for this theme and when the phone rebooted BAM stuck at splash screen ( battery is now at about 40% life)
Realized I was going to have to SBF Flash phone downloaded all required tools drivers, the_gift, RSD 4.9 Went to turn phone on it wouldnt turn on. Hook it up to the wall I get the splash screen nothing else. Tried using the home power button search button to factory reset. After doing so same thing even after wiped partition. I can get into the bootloader screen also but it says low batter cannot program. Is the only way to charge my battery enough to SBF Flash it is by using an external charger or cutting the usb and manually charging the battery through the computer? How can I access my nandroid backup? I know there is something that can be done Im just a little to new to know what that is Please Help
Any help is certainly appreciated!
I do believe that there is a way to charge your battery by cutting the USB cord and I'm going to get back to you on that but one thing you really want to watch out for is that from my experiences, the_gift is for system version 2.3.315 (aka bootloader version 30.03) and since you were running liberty 1.5 I'd assume you're on version 2.3.320/2.3.340 (aka bootloader version 30.04). If this is true and you try to flash it you will brick your phone. Make sure you check you're bootloader version and if it is the newer one look for happy_holidays_from_tbh or something similar. Just make sure its for the right bootloader version
He is correct, you need to pay attention to that.
But you could also just charge the battery in a buddys phone and try again. But if you are like me with no friends ( , lol) you could stop by a store somewhere and ask if they could charge your battery for you in a phone for a bit. Usually they are pretty cool about it. Then that way you can try reflash to stock.
If you still had access to CWM, I would have recommended wipe, wipe dalvik, and reflash of liberty. But that is a nogo at this point.
Thanks for the heads up about the SBF file. I will delete the gift since it never registered on my pc when I loaded up rsd 4.9. ( might be the reason why haha)
Charging the battery is where I am at right now, I need to either wait for the external charger i bought off ebay to come in or use my buddys phone. I feel I am going to want to make sure when I do the battery charged I have detailed instructions in order to FLASH my phone. Im hoping when the battery charges I will be okay but as I stated I am new to this rooting thing and am learning everything super fast. Any and all help is truely appreciated.
Related
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
Ill start this saying, yes, im a noob. I rarely post or visit unless i have problems.
But i do have experience rooting this specific phone before. But this time around its giving me a LOT of problems...
Ill start with:
Samsung Epic 4g (D700.0.5)
FM 2.3.6 (GB)
BB EL30
K 2.6.35.7
Now i will attempt to explain all the problems as well as what i have done to try to fix them and i will give as many links to the pages that i used for guidance as i can.
As i said, i have experience rooting this specific phone in the past. I ran a stock rooted ROM and everything was fine other then some glitches that i just learned to live with. But about 3 months ago i got a few more problems that have been driving me crazy so i desired to reroot.
When i power down the device, it will not turn back on just by pressing/holding the power button. Removing the battery, reinserting it, and holding the power also dose not work. I finally figured out that i have to remove the battery, replace the battery, then quickly (before the on-screen battery disappears) insert a charging cable thats connected to a power source. Then when the battery turns green (even with minimal power or full power) i can then power it on, but only when the on screen battery shows green. If i wait too long and it disappears it will not work and i have to start over from the beginning. (Removing Battery...) That was the 1st problem.
Soon after this happened (maybe 1-2 weeks) my phone started doing random shutdowns and not powering back on (i assume because it didnt have a power source connected). This would happen at anytime of the day or night, even when it was connected to a charger and actively charging. Yesterday i finally had the last of it and started researching this problem. I found that apparently some/all of the epics have this problem in time. From what i read the micro(or mini im not sure) USB port dosnt fit 100% snugly. So it causes heat. This heat causes corrosion and eventually leads to this problem. (I have never got this phone wet in the 1.5 years i have had it, i take very good care of my electronics.) Around the time this started my phone also would drain its self in about 2-3 hours, this was due to it constantly thinking i was plugging and unplugging it from a computer and requesting that i choose from the 3 options of mass storage.... Eventually the whole screen turning black with the android and the 3 buttons went away but the pop up on the notification bar continued, and as already said, it will drain the battery quickly.
NOW on to the rooting problems.
I dont remember what rom i was running originally, but following a few videos from QBKing77.
I odin'd back to EC05. This went fine no problems. (Useing odin 1.85)
I then tried to use the e4gtauto.zip file and running the "RUNFIRST.bat"
Used option A (install Root not EL13/newer)
Everything went though like it was suppose to. No errors or problems. Phone rebooted into recovery rather then to the lock screen.
Not remembering how to use recovery, i did some research, apparently the camera button is SUPPOSED to be the select button, but this did not work for me at all. After several manual reboots (pulling battery) this was the only thing i could get to (not even download mode to try to flash back to EC05 again). I did some research and found a post that said the "home" button on the front of the screen was his selector for some strange reason. This worked for me. I selected "reboot now" or something like that (the 1st option) and it rebooted into what i was thinking was a rooted rom, checked and there was no SU, or BusyBox (as said would happen in the e4gtauto).
I downloaded an su.zip and figured i would flash it with CWM (last time i installed CWM it was "purple" or 3.1.0.1)
Well it seems that my CWM is gone... i did the ever famous "3 finger salute" of Vol Down + Camera + Power and nothing except that i had to select "reboot phone" again from what i believe is stock recovery. Which booted me back into EC05.
By this time it was late at nite (2am or so) so i went to bed, over night apparently it updated and is now EL30. Thinking this was a good thing (and deff proving im not rooted) so today i tried rooting it as EL30.
Still do not have CWM seemingly.
Also would like to note, inorder for me to get to download mode, i have to take out my SD card, take out my battery, plug in the phone, and hold 1+power when the green power indicator comes on as stated above. This is the only way i can get into DownloadMode (if that helps at all)
If i could get any information on how to root from EL30 i would appreciate it greatly!!!
I will answer any questions as fast as possible, and i will provide as much information as you request when as soon as possible.
Thank you all in advance.
LATE:
Im not able to post links... so i cant give all the steps ive followed so far, I have attempted to take out all infomration already stated related to a link or video... Sorry.
I can do this for you remotely via teamviewer 7 google it and install it pm me the id and password and ill do it all for you
Oh and you used the epic touch one click root... not ours.. and el30 doesn't work on one click root.
Sent from my SPH-D700 using xda premium
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
YourLordAndMaster said:
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
Click to expand...
Click to collapse
You have the wrong recovery installed... you used the epic touch one click root... ... just go get teamviewer and ill fix it for you.
oh but now your on stock recovery because samsung has a script in the kernel to restore the stock recovery upon boot.
The rooting has been fixed.
I didnt install a CWM file apparently
and i also did a lot of bad things
Big thanks to "Big Goron" for the help he provided
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
marzell88 said:
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
Click to expand...
Click to collapse
are you able to put your phone in bootloader mode ? and witch version you use to flash your phone with RSD use one of those
http://sbf.droid-developers.org/umts_milestone2/list.php
yes i used the retail british 2.4
i am able to flash sbf file but it still wont go past moto logo and stock recovery cant install any roms. not allowed to install or something like that.
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
jakkokko said:
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
Click to expand...
Click to collapse
thank you i will try this. the battery is currently drained, so i need to recharge first. using wall charger (usb unit) but it didnt charge yet. keeps telling me the batt is low. any tips for that? only thing i found on here is to use a wall charger.
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
jakkokko said:
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
Click to expand...
Click to collapse
this worked as far as the batery problem, pita to do thou. now hope i can root the thing, since i did not yet succeed to run the adb drivers..
update: well, i fear the worst. after the last time flashing the sbf it wont turn on anymore. guess i did screw up the wire-DIY. will update if there is any good news. but for now it seems i should start looking for a new phone.,.
Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!
Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!
Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
chip102 said:
hey all,
Saturday morning a wake up to my alarm on my phone (SM-G950U T-Mobile Stock since new) and turn off the alarm and proceed to check email and scroll social medias. A few minuted later phone turns off and starts boot looping. Occasionally it would boot to home screen and i could unlock it but then maybe 30 seconds later it would start boot loping again. Now it either just boot loops or boots straight to recovery . I have tried flashing current firmware in case it was corrupted and i have tried accessing it through ADB. I know for a fact USB debugging is on because I just used abd to pull wifi passwords 2 weeks ago, but when I try to [ abd devices] if comes up as unauthorized and I cannot proceed. I know everyone will suggest a factory reset, but I am hoping someone has a trick for extracting files. I dont care about most on my phone, but I would like to save the pics from my GF and I trip this past august. Apparently I didnt have my photo library set to sync to cloud -_-
thanks
-chip
update: it appears there is a pattern. it boot loops or boots to recovery (after a blue failed system update screen) 99% of the time. the 1% it boot fully and then crashes is only when battery is 0% . it for some reason is only trickle charging and isnt getting enough juice when it does boot fully to stay on . But if i leave it charging a while it will then only boot loop or boot to recovery. Strange...any way I had enough time this past boot to reauthorize usb debug.....wish me luck with adb
....nevermind. still shows up as unauthorized
Click to expand...
Click to collapse
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
TheMadScientist said:
Ive had similar cases happen with older models. May be time for a battery. They will do crazy **** when the battery crashes. When you flashed stock firmware you lost adb authorisation. Need to get the system back first for that.
Click to expand...
Click to collapse
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
chip102 said:
thank you very much. my battery life was greatly suffering and the USB-c port was worn pretty bad. Ill grab a new battery and hope that works.
Click to expand...
Click to collapse
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
TheMadScientist said:
Cheapest fix in my opinion. I saw another thread a guy dropped his. Now detects 9008 how to fix. More than likely a phone wont just not boot. Or lose programming unless a hardware issue. So if it was just running and quit. Not modding stuff really. More likely than not its gonna be some form of software. But hardware.
Click to expand...
Click to collapse
Replaced Daughter board and battery. No improvement :/ bummer
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
chip102 said:
the only time i can get it back into recovery is after a "successful" flash with odin. by successful i mean that it says it worked but it just continues to boot loop or boots to recovery. attached is a picture of the info i get in recovery every time. hope someone can shed some light in the issue. im using my old phone so i dont feel pressured to call the data a loss and try a factory reset just yet....my old phone is a POS though
Click to expand...
Click to collapse
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
TheMadScientist said:
Yea some one tried to root it using the edl safestrap thread. Only wsy to fix it is filled the steps and reflash jrkruses pie rom. One of my mother boards are in the same state. That's the only way dm verity fails. Is his rom method.
There's some easy to flash a cache wipe in Odin but I hadn't found it yet. I have 2 mother boards and one is identical. I flash this stock and lose download or recovery. but the errors you show are only from doing that edl safestrap
Click to expand...
Click to collapse
chip102 said:
Ill be honest..i have no idea what you are talking about. Ive messed with the software with previous devices and never heard of safe strap. This one has been bone stock since I got it from Tmobile and i haven't attempt to flash anything until i had this issue. never tried to root it
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/development/root-t3904613. This thread can help you at least get pie back up and running. I wouldn't mess with no more. I haven't had much luck with mine. But I did get it booting again