Related
Hello.
I'm not completely sure what happened, but my phone ran out of battery last night, and so after charging it this morning I tried to power it up, and was met by the following.
BUZZ PVT SHIP S-ON
HBOOT-1.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.20.10
Dec 2 2010, 17:14:26
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
However, my phone is not responding to any of the buttons, and I can't get past this page.
can anyone help me pass this?
I seems like that there is a chance that you have no rom on your phone anymore. Something similar happened to me and my phone would only boot in hboot because there was no rom to boot into. Can you get it recognized by your computer.
Sent from my HTC One using Tapatalk 4
WildfireDEV said:
I seems like that there is a chance that you have no rom on your phone anymore. Something similar happened to me and my phone would only boot in hboot because there was no rom to boot into. Can you get it recognized by your computer.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
When I connect it to the usb, it says "FASTBOOT USB", and it comes up as a removable drive on the computer, but I can't access it after that.
altharian13 said:
When I connect it to the usb, it says "FASTBOOT USB", and it comes up as a removable drive on the computer, but I can't access it after that.
Click to expand...
Click to collapse
now it isn't doing it at all now as a removable drive.
altharian13 said:
When I connect it to the usb, it says "FASTBOOT USB", and it comes up as a removable drive on the computer, but I can't access it after that.
Click to expand...
Click to collapse
Can you use fastboot on pc to see the device. To do so go to the folder you have adb and fastboot in and open it up in a command prompt then type fastboot devices while your phone is plugged in. If you see a bunch of numbers and letters and it says device then come back and reply to the thread. I probably won't answer for about another 8 hours as I am going to bed now. When I get up I will try and continue to help you.
Good night
Sent from my HTC One using Tapatalk 4
WildfireDEV said:
Can you use fastboot on pc to see the device. To do so go to the folder you have adb and fastboot in and open it up in a command prompt then type fastboot devices while your phone is plugged in. If you see a bunch of numbers and letters and it says device then come back and reply to the thread. I probably won't answer for about another 8 hours as I am going to bed now. When I get up I will try and continue to help you.
Good night
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Thank you loads, I am trying it now and I shall let you know what happens. Thank you so much.
Hey.
I have the programs installed, however have never had to use them before. I have watched several videos on what to do with this program but I keep getting stuck and confused. I have opened the command window and after trying to search I can not find the device on there. One tutorial I have been watching has got me so far, but I am stuck on it after that point. I've included a screenshot of what I've managed to get so far, any help would be greatly appreciated.
So when you type fastboot also type the word devices. Fastboot devices should show your phone if it is connected if so then we can go from there.
Sent from my HTC One using Tapatalk 4
I tried that, and after several attempts and have got it, it says
"HT06FPY06765 fastboot"
I'm sorry if I don't reply, as it's getting late and I need to sleep soon. I'll be so great full for anymore help you can give me on this issue. Thank you =)
altharian13 said:
I'm sorry if I don't reply, as it's getting late and I need to sleep soon. I'll be so great full for anymore help you can give me on this issue. Thank you =)
Click to expand...
Click to collapse
Yeah sure that okay. Well now that it seems that your phone is being recongnized by the computer. Okay now just tell me if your hardware buttons work at all when you are in hboot.
no, my hardware buttons don't work at all, I can't do anything on the phone to change the original screen.
So the power button doesn't work either.
Sent from my HTC One using Tapatalk 4
---------- Post added at 06:22 PM ---------- Previous post was at 06:21 PM ----------
Because It is going become much harder but I will try and help you to the best of my ability.
Sent from my HTC One using Tapatalk 4
WildfireDEV said:
So the power button doesn't work either.
Sent from my HTC One using Tapatalk 4
---------- Post added at 06:22 PM ---------- Previous post was at 06:21 PM ----------
Because It is going become much harder but I will try and help you to the best of my ability.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
no, the power button doesn't work either. Thank you.
Seeing that your fastboot seems to work try relocking your bootloader through fastboot and download the ruu for your phone with the corresponding carrier from androidfiles ruu. Remember to select buzz if this doesn't work please report back.
Sent from my HTC One using Tapatalk 4
WildfireDEV said:
Seeing that your fastboot seems to work try relocking your bootloader through fastboot and download the ruu for your phone with the corresponding carrier from androidfiles ruu. Remember to select buzz if this doesn't work please report back.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm looking at androidfiles ruu, however they do not have one for my phone ( as it's the original HTC "wildfire"). what would you suggest I do for this?
altharian13 said:
I'm looking at androidfiles ruu, however they do not have one for my phone ( as it's the original HTC "wildfire"). what would you suggest I do for this?
Click to expand...
Click to collapse
Look for the name buzz.
Sent from my HTC One using Tapatalk 4
WildfireDEV said:
Look for the name buzz.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I have selected buzz, and have downloaded the file which I think is correct for my phone and I am getting a usb connection error from the ruu program, although it says it's connected on the phone.
altharian13 said:
I have selected buzz, and have downloaded the file which I think is correct for my phone and I am getting a usb connection error from the ruu program, although it says it's connected on the phone.
Click to expand...
Click to collapse
Have you installed all the htc drivers.
Sent from my HTC One using Tapatalk 4
When I installed sdk, I downloaded the "Google USB Driver" along with it, as it said to do
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon
I have updated my old script to root ZVB as well as ZVA. This should solve issues that some people were having.
Just extract the zip file, run the .bat file and follow the instructions. Should be pretty simple. Let me know if you run into any problems.
Note: If you are having issues with the script hanging try unplugging your phone and plugging it back in. That should help.
Prerequisites:
Code:
adb debugging
LG drivers
Diag mode enabled ##diag (makes things easier but you can do without it, eg. manual reboots.)
Reserved
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
wpmetts said:
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
Click to expand...
Click to collapse
Yeah you might need to update your drivers in device manager once in download mode (searching automatically for the best driver should do the trick)
wpmetts said:
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
Click to expand...
Click to collapse
On line 27 in the bat file, change
Code:
adb reboot
to
Code:
adb reboot download
.
That worked for me.
Tried on Windows 10 and Windows 7 machines, After I manually put my phone into download mode (will not go into download mode automatically) the script detects my phone and I get "Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#"
Then the script just stops with nothing else happening, I've let it sit for 30 minutes thinking it was doing something but nothing. Any suggestions on what to do. My phone and sd card are encrypted, could this be causing the issue?
Out2kill said:
Tried on Windows 10 and Windows 7 machines, After I manually put my phone into download mode (will not go into download mode automatically) the script detects my phone and I get "Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#"
Then the script just stops with nothing else happening, I've let it sit for 30 minutes thinking it was doing something but nothing. Any suggestions on what to do. My phone and sd card are encrypted, could this be causing the issue?
Click to expand...
Click to collapse
Yes an encrypted phone/sdcard is probably the issue.
Sorry for the nooby question, but will autorec work after using this to root ZVB? I'm about to get a new device through insurance and world hate to only have root and not custom recovery.
golpeen420 said:
Sorry for the nooby question, but will autorec work after using this to root ZVB? I'm about to get a new device through insurance and world hate to only have root and not custom recovery.
Click to expand...
Click to collapse
no autorec doesn't work.. but you can use twrp manager (free on google play) or flashimg.
l33tlinuxh4x0r said:
no autorec doesn't work.. but you can use twrp manager (free on google play) or flashimg.
Click to expand...
Click to collapse
Oh wow, had no idea twrp manager supported this device now. That makes things so much easier. Cause I just ordered my new device today and it'll probably come stock with ZVB. Thanks for the info, really thought id be doomed to stock for a minute there.
Bought a G3 from someone off Craigslist last night & used this earlier today to gain root & it worked perfectly. Thanks for sharing!
So when I run the bat file, it just says waiting for device, but my device is plugged in and I know the drivers are installed, even installed them again to be sure and still nothing, and advice?
---------- Post added at 10:50 PM ---------- Previous post was at 10:34 PM ----------
nevermind, I got it
This method worked for me, thanks!!! @l33tlinuxh4x0r your the man, thanks for sharing your knowledge with the community and helping others. After trying several other root methods and having none of them work this root method actually worked! I have a LGLS990 LG G3 32GB SPRINT Shine Gold Smartphone. Goodbye Sprint / LG bloatwear and hello new xda gear!
One tip I can give is towards the end you need to unplug the USB cable, power off your phone and manually go into download mode again. The script doesn't prompt you to do that action but I figured it out when I kept getting stuck at around 90%. After I put my phone into download mode manually and reconnected the USB the root completed and SuperSU was installed. I am now running CloudyG3_2.5 and it's working flawlessly, thanks again.
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Jamesredmond82 said:
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Click to expand...
Click to collapse
I am having the same issue after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out... any help will be appreciated.
Duplicate
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Jamesredmond82 said:
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Click to expand...
Click to collapse
You can use this method, i just rooted my LG G3 using mathod B on the link below.
http://forum.xda-developers.com/spri...stock-t3211878
hkhan1 said:
Duplicate
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
You can use this method, i just rooted my LG G3 using mathod B on the link below.
http://forum.xda-developers.com/spri...stock-t3211878
Click to expand...
Click to collapse
your link didnt work
http://forum.xda-developers.com/spr...990-zvb-root-method-zvb-rooted-stock-t3211878
On this forum go to page number 5 for instructions.
Try this link, this should work.
Rooted a brand new LG G3 sold for Boost Mobile with this method. Lollipop v 5.0.1
twelfth said:
Rooted a brand new LG G3 sold for Boost Mobile with this method. Lollipop v 5.0.1
Click to expand...
Click to collapse
how exactly did you go about doing this?
Hey guys i have been using my dell tablet for more than a year. I also rooted it at the same time i bought the tab. Now a week ago when i was using my tab it was completly turned off. I have tried charging it for a day nothing happens. it dosent Show any Boot animation or charging animation nor does it even enter fastboot mode. It doesn't even turn on. It has just become like a paper weight. When i connect it to pc, it shows under the Device Manager CLOVERVIEW PLUS Device. I checked out some other posts and it shows reflashing it through xFTSK, but i searched everywhere but it doesn't have any firmware or software for Dell Venue 7 HSPA+ 3730. Pls Guys Help me out here, really appreciated. Thanks.
can you boot into the fastboot mode?
Huzaifa_Aziz said:
can you boot into the fastboot mode?
Click to expand...
Click to collapse
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
ssjdeepanshu said:
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
Click to expand...
Click to collapse
I'm really sorry for replying late, was stuck in an issue of my own with S6 Edge, okay so, when you put it on charge does it show up "charging" ?? like the Cell with charging animation shows up?
---------- Post added at 04:10 AM ---------- Previous post was at 03:56 AM ----------
ssjdeepanshu said:
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
Click to expand...
Click to collapse
if it is showing up a response in Device Manager then it means your boot is still alive. There is hope brother, so first of all we need to know if it has juice or not?
also please READ some stuff here http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
and download and extract this package http://https://www.androidfilehost.com/?fid=23622183712464837 from @social-design-concepts and please don't flash stuff just right away. I would suggest that you read first what they have to say, then cautiously proceed with the Toolkit.
do also thank @social-design-concepts on his thread by the way.. :good:
---------- Post added at 04:25 AM ---------- Previous post was at 04:10 AM ----------
ssjdeepanshu said:
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
Click to expand...
Click to collapse
and then there is the good old METHOD number 2,
it's easier as far as I know,
make an easy ADB folder.
Just boot in FASTBOOT mode.
extract the ::Venue_7_3G_KK4.4.2v1.33_FLASHPKG.7z:: archive
and take out Venue_7_3G_KK4.4.2v1.33.system.img.gz (place it in same folder as adb.
after that in fastboot mode
write command
fastboot flash system Venue_7_3G_KK4.4.2v1.33.system.img.gz
Click to expand...
Click to collapse
wait for it to finish.
after that fastboot reboot
and profit!
Sorry for replying late, but as i said earlier it doesn't show any charging animation or enters the fastboot mode but when connected to pc it shows CloverView Plus in the device manager. i am just confused is it even alive or not.....
ssjdeepanshu said:
Sorry for replying late, but as i said earlier it doesn't show any charging animation or enters the fastboot mode but when connected to pc it shows CloverView Plus in the device manager. i am just confused is it even alive or not.....
Click to expand...
Click to collapse
It might be possible that the charging IC has been damaged, if after a continuous 2/3 hour connection with PC/charger the tablet does not turn on. Means it isn't getting enough charge to even boot up. It might be a good idea to get it checked by a technician but I am afraid parts/ replacements and finding an expert on Dell devices is quiet rare because of it's less popularity.
yeah even i am thinking it is a hardware problem, if i was a software problem, i might have been able to solve it on my own.
Anyway's thanks for help.
ssjdeepanshu said:
yeah even i am thinking it is a hardware problem, if i was a software problem, i might have been able to solve it on my own.
Anyway's thanks for help.
Click to expand...
Click to collapse
You are welcome!
I wonder what became of your tablet...
Huzaifa_Aziz said:
You are welcome!
I wonder what became of your tablet...
Click to expand...
Click to collapse
It's now just a useless paper weight :crying:
ssjdeepanshu said:
It's now just a useless paper weight :crying:
Click to expand...
Click to collapse
you know I found that tablet to be indestructible. up till now at least. still running even though I corrupted its recovery once.
I downloaded the new leaked pie version of android for the Galaxy s9+ and after realizing it was buggy, lacking some features i needed, i tried going back to oreo and messed up somewhere. I used odin do get oreo and that worked, then while starting back up, it said i had to factory reset it and after turning the phone back off, i keep getting stuck on the ss rdx screen where it asks to back up to sd card or computer and cant get off that no matter what i do. Ive tried backing up to sd card and nothing happens. Any help would be appreciated.
I had this same problem..... I'm on an s9+ on Xfinity service. I could boot the phone back up by pressing and holding a combo of power and volume down I believe but the phone would boot up and be locked up on the sign-on screen (it wouldn't pull up the keypad to let me enter the pin code). I also couldn't shut down the phone or boot it into download mode or into recovery. I ended up hooking it up to my computer via usb and sending an adb command to fastboot into download mode. Luckily that worked and I could then use Odin and reflash stock firmware. I already had developer mode and usb debugging mode enabled prior to the phone locking up on me.
---------- Post added at 01:21 PM ---------- Previous post was at 01:01 PM ----------
I also found this by digging through Google:
https://forum.xda-developers.com/galaxy-s8+/help/samsung-s8-sm-g955uzkatmb-boot-error-t3726832
Hope this helps.
Libdawg said:
I had this same problem..... I'm on an s9+ on Xfinity service. I could boot the phone back up by pressing and holding a combo of power and volume down I believe but the phone would boot up and be locked up on the sign-on screen (it wouldn't pull up the keypad to let me enter the pin code). I also couldn't shut down the phone or boot it into download mode or into recovery. I ended up hooking it up to my computer via usb and sending an adb command to fastboot into download mode. Luckily that worked and I could then use Odin and reflash stock firmware. I already had developer mode and usb debugging mode enabled prior to the phone locking up on me.
---------- Post added at 01:21 PM ---------- Previous post was at 01:01 PM ----------
I also found this by digging through Google:
https://forum.xda-developers.com/galaxy-s8+/help/samsung-s8-sm-g955uzkatmb-boot-error-t3726832
Hope this helps.
Click to expand...
Click to collapse
Samsung phones do not have "fastboot" mode. What you did is issue the adb command
adb reboot bootloader OR download OR recovery OR edl
If adb wasn't already pre-enabled then this would not have worked, however flashing a combination or eng boot would have enabled adb mode.
billa said:
Samsung phones do not have "fastboot" mode. What you did is issue the adb command
adb reboot bootloader OR download OR recovery OR edl
If adb wasn't already pre-enabled then this would not have worked, however flashing a combination or eng boot would have enabled adb mode.
Click to expand...
Click to collapse
Dude... Way to ressurect an old thread..
InsanePostman said:
Dude... Way to ressurect an old thread..
Click to expand...
Click to collapse
I replied to a message dated 10-04-2018 it's not from 1999 lol
thank you
billa said:
I replied to a message dated 10-04-2018 it's not from 1999 lol
Click to expand...
Click to collapse
and your reply is still relevant... even another year later. I'm in the same boat and was confused about the fastboot reference, but appreciate the info from everyone.
*side note*
"Way to ___" posts and comments rarely add any value and usually have the opposite effect intended... instead calling someone else out or pointing out a misconduct you end up looking like a condescending prick. And now I've got dirty hands as well and seem like a know it all for calling out this know it all. The high road is always a better path.
God bless relevant ressurectable threads. Unlike Pet Cemeteries... sometimes dead is NOT better : )
HT
HTidwell said:
and your reply is still relevant... even another year later. I'm in the same boat and was confused about the fastboot reference, but appreciate the info from everyone.
*side note*
"Way to ___" posts and comments rarely add any value and usually have the opposite effect intended... instead calling someone else out or pointing out a misconduct you end up looking like a condescending prick. And now I've got dirty hands as well and seem like a know it all for calling out this know it all. The high road is always a better path.
God bless relevant ressurectable threads. Unlike Pet Cemeteries... sometimes dead is NOT better : )
HT
Click to expand...
Click to collapse
I see, so anyone posting a relevant reply to a thread regardless if it's new or old, is now called a "know it all" by your name calling.
Interestingly I couldn't find in the xda rules anything that prohibits anyone from posting a reply if it's one year or older.
I'll just leave it at that, and let the moderators decide.