Related
Yes, while I understand there have been many threads in regards to RSD Lite not recognizing phones, hear me out as none of them have been helpful to me. I recently got into the world of rooting and flashing roms, so like a fool yesterday I flashed Eclipse v.1 over 2.3.3. Ever since I have been experience the wifi connectivity issue, so reasonably I tried to use RSD lite to get the 2.3.4 sbf onto my X2. However, using RSD 4.5.3 I kept getting a status message along the lines of "chipset type 53 is not supported." Trying it again also with the 2.3.3 sbf, I tried using RSD v.4.9 and 5.3.1, however neither would recognize my phone. Now I am beginning to encounter other issues with Eclipse (my own fault) and I would greatly appreciate any input. All drivers are up to date for anyone who was going to throw that out again.
Be sure the machine you are running rsd on has plenty of disk space.
I got wierd errors a while back when i was running next to full on the HD RSD makes a temporary file before it flashes.
mastafunk said:
Be sure the machine you are running rsd on has plenty of disk space.
I got wierd errors a while back when i was running next to full on the HD RSD makes a temporary file before it flashes.
Click to expand...
Click to collapse
I have more than enough HD space. When running 4.5.3 it has the chipset error as the device status when paired with any sbf.
Are you running RSD as administrator? Maybe that could be a problem but i dont know.
If you are rooted and have installed system recovery try and flash the 2.3.4 zip aligned update in recovery and see if that works
Sent from my DROID X2 using XDA App
phillyo2 said:
Are you running RSD as administrator? Maybe that could be a problem but i dont know.
Click to expand...
Click to collapse
Just tried both ways in 4.9, neither were successful
It might be quicker if you enumerated, step-by-step, how you last sbf'ed ... that way, the more experienced amongst us can determine where you went wrong.
Oh, and throw in details on your computer's OS, too ... I hear there have been some problems using RSD Lite with Windows 7.
Pj
Phoenix, AZ
pdinphx said:
It might be quicker if you enumerated, step-by-step, how you last sbf'ed ... that way, the more experienced amongst us can determine where you went wrong.
Oh, and throw in details on your computer's OS, too ... I hear there have been some problems using RSD Lite with Windows 7.
Pj
Phoenix, AZ
Click to expand...
Click to collapse
I attempted to sbf based on the standard method from what I've seen in threads: run RSD (various versions were attempted), select the sbf, start the RSD protocol on my phone THEN plug it into the usb, and so on.
brossma1 said:
If you are rooted and have installed system recovery try and flash the 2.3.4 zip aligned update in recovery and see if that works
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Just tried that, 2.3.3 isn't showing up when booting and 2.3.4 gets aborted due to signature verification failure or something along those lines.
I am curious as to what is meant by flash 2.3.4 zip aligned update?
---------- Post added at 10:32 PM ---------- Previous post was at 10:28 PM ----------
Also have u tried a factory reset from STOCK recovery? Not the bootstrap...STOCK...
Then see if rsd works
Aldo what method are u using to get to rsd protocol mode?
do u hold power and volume up? ((This is how I do it))
U can also find it with power and vol down then scroll down after u see dastboot on top...try both ways
I know I have had a couple timed where it took a few minutes for rsdlite to actually see my phone ...think it was trying to auto install drivers....
U try uninstallin moto drivers and reinstall? Something go wacky?
I use rsdlite 5.4.4 by the way
Astrotard Jones said:
Just tried that, 2.3.3 isn't showing up when booting and 2.3.4 gets aborted due to signature verification failure or something along those lines.
Click to expand...
Click to collapse
Signature verification sounds like the file corrupted. Try redownloading the sbf file through Firefox or chrome and unzip the file with 7zip.
Sent from my DROID X2 using XDA App
ashclepdia said:
I am curious as to what is meant by flash 2.3.4 zip aligned update?
---------- Post added at 10:32 PM ---------- Previous post was at 10:28 PM ----------
Also have u tried a factory reset from STOCK recovery? Not the bootstrap...STOCK...
Then see if rsd works
Aldo what method are u using to get to rsd protocol mode?
do u hold power and volume up? ((This is how I do it))
U can also find it with power and vol down then scroll down after u see dastboot on top...try both ways
I know I have had a couple timed where it took a few minutes for rsdlite to actually see my phone ...think it was trying to auto install drivers....
U try uninstallin moto drivers and reinstall? Something go wacky?
I use rsdlite 5.4.4 by the way
Click to expand...
Click to collapse
I have tried both methods of recovery, bootstrap and stock as well as the power+ vol up method and the method of accessing the RSD protocol through the vol down boot method. I have also tried reinstalling drivers as well. I also don't believe time was an issue with RSDlite as I gave each version a good 20 minutes to try to recognize my phone (excluding 4.5).
EvilTim said:
Signature verification sounds like the file corrupted. Try redownloading the sbf file through Firefox or chrome and unzip the file with 7zip.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
I will try that, I have yet to try 7zip. Also when I try to access the 2.3.3 sbf zip file from recovery it does not show up as an option.
The versions of RSD you are using are older, I've been using 5.5 without any issues. If the phone is not being recognized it could be a driver issue on your windows machine. My older computer cannot recognize my phone i think the USB is 1.0.
Use version 5.x.x and higher...
Sent from my DROID BIONIC using xda premium
Astrotard Jones said:
I have tried both methods of recovery, bootstrap and stock as well as the power+ vol up method and the method of accessing the RSD protocol through the vol down boot method. I have also tried reinstalling drivers as well. I also don't believe time was an issue with RSDlite as I gave each version a good 20 minutes to try to recognize my phone (excluding 4.5).
I will try that, I have yet to try 7zip. Also when I try to access the 2.3.3 sbf zip file from recovery it does not show up as an option.
Click to expand...
Click to collapse
U r not supposed to flash the sbf zip from recovery.
u should have all the files on ye computer
Other things to try if still stuck:
try rsd 5.3.1 its what I always use.
Try plugging in to a port in the back of the computer.
Try run as administrator when you start rsd lite
Read the tutorial in the android dev subforum, its in the sticky post.
Sent from my DROID X2 using XDA App
EvilTim said:
Other things to try if still stuck:
try rsd 5.3.1 its what I always use.
Try plugging in to a port in the back of the computer.
Try run as administrator when you start rsd lite
Read the tutorial in the android dev subforum, its in the sticky post.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Also make sure correct Motorola drivers installed((different ones for 32bit and 64bit computer))
Try uninstall and reinstall drivers.
Kill all internet connection ((saw someone say before this was causing problems somehow...worth a shot..I think it had to do with when installing drivers it was doing something to find other drivers..not to sure but.couldn't hurt to try))
Maybe even just try a different computer all together ..
ashclepdia said:
Maybe even just try a different computer all together ..
Click to expand...
Click to collapse
agreed try another computer
hamburgerman said:
The versions of RSD you are using are older, I've been using 5.5 without any issues. If the phone is not being recognized it could be a driver issue on your windows machine. My older computer cannot recognize my phone i think the USB is 1.0.
Click to expand...
Click to collapse
I just reinstalled the drivers and tried 5.5, it didn't work sadly enough. Also, to every post under the quoted one; please read the thread before you throw out "advice."
Astrotard Jones said:
to every post under the quoted one; please read the thread before you throw out "advice."
Click to expand...
Click to collapse
No one read your whole post because you obviously didn't read the tutorial before you messed with your phone. So next time before you attempt to do something you clearly have no information on, read about it first. And instead of being a tool, thank us for at least TRYING to help you.
Sent from my DROID X2 using XDA App
I am having serious problems rooting. My fastboot does not seem to work with anything. It all started when I flashed the latest firmware through RSD lite. Any advice. Matt's utility does not work - none of the options.
I am in
AP Fastboot Flash Mode (s)
0A:74
Device is Locked. Stauts Code: 0
Battery OK
OK to program
Transfer Mode:
USB Connected
Trying to flash
Filename: VRZ_XT912_6.7.2-180_DHD-16_M4-31_CFC.xml
Creation Date: 06/14/2012 19:11:24
File size: 2137
Sofware Version: 6.7.2-180_DHD-16_M4-31
For Phone Model: SPYDER
But every time I try to flash on step 14 of 21 I get a failure message and now I am stuck in fastboot - it will not power off or restart
andrewrvincent said:
I am having serious problems rooting. My fastboot does not seem to work with anything. It all started when I flashed the latest firmware through RSD lite. Any advice. Matt's utility does not work - none of the options.
Click to expand...
Click to collapse
You're using the xt912?? Matt's utility works flawlessly if the instructions are followed. I hate to say it but you must be doing something wrong. Are you just trying to root or are you trying to flash stock? If you are having problems after a previous RSD flash then i would try and fastboot back completely stock with data wipe using his utility. Are you putting the phone into fastboot mode? Try a different PC if you're sure you have the device in fastboot mode and you extracted the contents of the zip properly. If not, you should try and post screen shots or describe where the failure is occuring.
---------- Post added at 06:02 PM ---------- Previous post was at 05:55 PM ----------
andrewrvincent said:
I am in
AP Fastboot Flash Mode (s)
0A:74
Device is Locked. Stauts Code: 0
Battery OK
OK to program
Transfer Mode:
USB Connected
Trying to flash
Filename: VRZ_XT912_6.7.2-180_DHD-16_M4-31_CFC.xml
Creation Date: 06/14/2012 19:11:24
File size: 2137
Sofware Version: 6.7.2-180_DHD-16_M4-31
For Phone Model: SPYDER
But every time I try to flash on step 14 of 21 I get a failure message and now I am stuck in fastboot - it will not power off or restart
Click to expand...
Click to collapse
I don't have my laptop with me to verify, but im pretty sure you're using an older version of the utility. The filenames you posted are ICS i think. It should be this one. http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
You are my hero day - I forgot to extract the zip files - basic stuff - but I overlooked it. No wonder it keep saying file does not exist.
I was on verizon's site looking for a new phone. You just saved me some serious cash.
Thank you
I spoke too soon - I am still having issues.
It goes through the whole flash process and says the phone will reboot but the phone says "recipe failure" at the top by flash mode.
Is there a way to go back even further with this?
I tried flashing the latest firmware via rsd lite and the flash failed at step 14 of 21.
It seems hopeless right now
Well you don't want to go back. You tried to flash current firmware, the only direction we go from here is forward. What were you on prior to doing update? ICS? JB xmas leak? Which one of Matts utilities are you using? Go to the link at the bottom of my last post. Is that the same utility that you're using? Not DROID RAZR UTILITY 1.82 or 1.90 but DROID RAZR Utility XT912 Jellybean. I've used this utility to fastboot JB from a stock GB Razr without issues. If all of the above has been verified then redownload the utility and retry. If that fails, try a different computer and if that fails..... send it to me.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 08:53 PM ---------- Previous post was at 08:47 PM ----------
It seems that way. Lol but its not. You can't really hard brick a Razr. Give ^^^^^ a try and report back.
Sent from my SCH-I535 using Tapatalk 2
I am on the latest utility - I went to the link you provided and downloaded it again just to be sure but no luck.
Here is where I stand - I was on JB through dual-boot option but then flashed the latest firmware directly using RSD Lite, not Matt's utility. Doing this caused me to lose root and I hate all the boat and ads so I really wanted to get root back. I then tried Matt's utility - but forgot the basic step of extracting, I let RSD extract and flash. I then had some failure issues since it could not locate the files I failed to extract. I then managed to get stuck in AP Fastboot somehow - I can not get out of it. The last time I tried the utility, after extracting it, the top of my phone stated "recipe failure." I also tried to flash the latest firmware through RSD but it stops on stop 14 out of 21 and merely states "failed"
By "go further back" I mean is there some way to flash something other than firmware?
I am not a developer but have been rooting and flashing ever since I got my original droid ages ago. I am not a magician with these devices but I normally manage to make do what I set out to do - but now I am stumped.
Any help would be appreciated - I just reactivated my OG Droid so I have service but that old thing is 3G and the screen is tiny - I like my RAZR an want to get it back up and running. I am going to hold off on trying anything else until I get a clear idea of how to proceed. I remember doing something once with ADB but I am not sure if it was a bricked Atrix I fixed for a co-worker or if it was the RAZR - I tend to do these things late at night in a sleep deprived haze so my memory is not very clear on that.
Thanks
I am trying fresh downloads of everything - start from scratch. If anyone has a better idea please let me know.
Thanks
Try another computer if it still fails.
Sent from my SCH-I535 using Tapatalk 2
I tried another computer with fresh downloads and still getting same failures.
Any ideas?
I need to reflash stock ROM, however I made the dumb mistake of accidentally formatting everything prior to flashing the new ROM. So I have no OS and no way of mounting the sdcard to ADB push the ROM from my computer instead. I've heard CWM (my recovery) has native support for ADB, but I'm pretty inexperienced). Can anybody point me in the right direction? Sorry if this is a repost, none of the threads I've tried have worried for me thus far.
Sane116 said:
I need to reflash stock ROM, however I made the dumb mistake of accidentally formatting everything prior to flashing the new ROM. So I have no OS and no way of mounting the sdcard to ADB push the ROM from my computer instead. I've heard CWM (my recovery) has native support for ADB, but I'm pretty inexperienced). Can anybody point me in the right direction? Sorry if this is a repost, none of the threads I've tried have worried for me thus far.
Click to expand...
Click to collapse
what about installing the first RUU?
i think it can help you
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=s-on
This is actually exactly what I need, however I can't even complete the first step by putting the files on the internal storage, because it cannot be accessed via CWM as I don't currently have an OS.
koby058 said:
what about installing the first RUU?
i think it can help you
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=s-on
Click to expand...
Click to collapse
Sane116 said:
This is actually exactly what I need, however I can't even complete the first step by putting the files on the internal storage, because it cannot be accessed via CWM as I don't currently have an OS.
Click to expand...
Click to collapse
as for my understanding you don't need nothing to run the RUU
i think it is reinstalling all partitions from scratch
You can use adb push from both twrp and cwm... But yeah for the ruu you don't need to put anything on your phone.
Sent from my Droid DNA using Tapatalk Pro
---------- Post added at 04:02 AM ---------- Previous post was at 03:57 AM ----------
Also if you are going to do the ruu, keep in mind that it flashes the radio as well. So if you are on a later radio you will need to flash that one
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
You can use adb push from both twrp and cwm... But yeah for the ruu you don't need to put anything on your phone.
Sent from my Droid DNA using Tapatalk Pro
---------- Post added at 04:02 AM ---------- Previous post was at 03:57 AM ----------
Also if you are going to do the ruu, keep in mind that it flashes the radio as well. So if you are on a later radio you will need to flash that one
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Can't you plus a recovery img in fastboot using
fastboot flash recovery nameoffile.img
Sane116 said:
I need to reflash stock ROM, however I made the dumb mistake of accidentally formatting everything prior to flashing the new ROM. So I have no OS and no way of mounting the sdcard to ADB push the ROM from my computer instead. I've heard CWM (my recovery) has native support for ADB, but I'm pretty inexperienced). Can anybody point me in the right direction? Sorry if this is a repost, none of the threads I've tried have worried for me thus far.
Click to expand...
Click to collapse
First, don't panic.
Download the ROM you want onto your computer, put it in the same directory as your ADB/SDK tools.
Then, on your phone, press and hold power and volume until it reboots into bootloader.
Press volume down to highlight recovery and then press power to boot into recovery.
Once in recovery you can use ADB Sideload to load ROM to phone from computer.
Enjoy...
sdamark said:
First, don't panic.
Download the ROM you want onto your computer, put it in the same directory as your ADB/SDK tools.
Then, on your phone, press and hold power and volume until it reboots into bootloader.
Press volume down to highlight recovery and then press power to boot into recovery.
Once in recovery you can use ADB Sideload to load ROM to phone from computer.
Enjoy...
Click to expand...
Click to collapse
hello sounds like sound advice my relative did the same but i dont know how to get the phone to be recognized by my computer because when i put the commands to see the device it dosent work it say device error because it dosent see it. you have any pointers on how i cant help out in this mess. i tried to use commands in fast boot and in adb and i got nothing system wont mount cant flash ruu nothing. any information would be very appreciative. im at a lost this is a first for me so not sure where to go. searched for hours and cant find what i need.
demon28 said:
hello sounds like sound advice my relative did the same but i dont know how to get the phone to be recognized by my computer because when i put the commands to see the device it dosent work it say device error because it dosent see it. you have any pointers on how i cant help out in this mess. i tried to use commands in fast boot and in adb and i got nothing system wont mount cant flash ruu nothing. any information would be very appreciative. im at a lost this is a first for me so not sure where to go. searched for hours and cant find what i need.
Click to expand...
Click to collapse
Try installing PDAnet on your computer.
You don't really need the tether app part of the install, but it doesn't hurt.
The main thing you are after, is the drivers it will install.
Run the installer and follow the prompts on your monitor.
That should get the device recognized, assuming you have adb/fastboot set up properly.
Your going to laugh but install pdanet and it will reinstall adb. I don't like cwm I'd advise u gonwith twrp unless ur going to use cm 11
Sent from my HTC6435LVW using XDA Premium 4 mobile app
have you fix this problem help me same problem
I accedently format the internal my android device huawei g610 in my computer now it wont open. Plss help mee
Thank You Very Much
sdamark said:
First, don't panic.
Download the ROM you want onto your computer, put it in the same directory as your ADB/SDK tools.
Then, on your phone, press and hold power and volume until it reboots into bootloader.
Press volume down to highlight recovery and then press power to boot into recovery.
Once in recovery you can use ADB Sideload to load ROM to phone from computer.
Enjoy...
Click to expand...
Click to collapse
Hello. A real big thank you for you. You gave me a big hope by the two words "Dont Panic". Your advice was a huge hint on how to get back my HTC One. I researched on ADB Sideload and within One Hour I got back my phone to normal. Thank You. You are God!
I downloaded a custom ROM and did the adb sideload. It worked. If computer doesnt recognise your device in recovery, try plugging it into other usb ports on your computer.
I have literally no clue what I have done to my phone. All I know is what I've done is bad and that I have voided all warranty. I did this knowingly, but this still really sucks.
I have CWM installed but CAN'T boot to it. Apparently I have like super-bricked my phone and when I try to boot into CWM it boots out and boots into the boot logo where it stays.
Someone please help me. The adb and fastboot commands do not detect my device (Windows 8.1) and they also don't work on my Windows 7 netbook.
I have no clue what to do. The RUU also doesn't work.
I have a Droid DNA.
http://forum.xda-developers.com/showthread.php?t=2561044 this may help you. From what I read you have to put it on an ad card and run load it onto your phone. I'm fairly new to all this myself. Good luck!
Sent from my SM-N900V using Tapatalk
Imarik81 said:
http://forum.xda-developers.com/showthread.php?t=2561044 this may help you. From what I read you have to put it on an ad card and run load it onto your phone. I'm fairly new to all this myself. Good luck!
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I would use this but I get a "<waiting for device>" on my computer and the windows 7 doesn't pick it up either so I can't flash. I am seriously so screwed - I'm sick to my stomach at how screwed I am.
edit: anyone...please..I am literally crying. I cannot fix my phone. I cannot afford a new one.
jake6177 said:
Thanks for the reply. I would use this but I get a "<waiting for device>" on my computer and the windows 7 doesn't pick it up either so I can't flash. I am seriously so screwed - I'm sick to my stomach at how screwed I am.
edit: anyone...please..I am literally crying. I cannot fix my phone. I cannot afford a new one.
Click to expand...
Click to collapse
Can you get into hboot/fastboot?
then in fastboot mode, enter :
Code:
fastboot erase cache
If that goes through, try entering Recovery again.
If your computer isn't seeing the device, make sure you have fastboot and adb installed and if it's a driver issue, try installing this if you can without a booting device
It requires some interaction with the phone, but maybe it will see it in hboot or install enough that it can detect it.: LINK
Don't panic man, your phone is going to be fine. I think we've all been there before. As long as you can get to the bootloader it's not bricked. Just do what santod said, also double check to make sure that you have the drivers installed properly, you can get adb and fastboot working on 8.1 if you install the correct drivers: http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/ also make sure you are using fastboot commands in the bootloader and not adb commands. That may sound ridiculous, but those are the type things that are easy to forget when you're stressed because your phone won't boot.
Sent from my Droid DNA using Tapatalk
---------- Post added at 10:52 AM ---------- Previous post was at 10:51 AM ----------
You may want to read this as well. http://forum.xda-developers.com/showthread.php?p=49909454
Sent from my Droid DNA using Tapatalk
Do you even have a rom on your phone or are you stuck in a bootloop?
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
p̶h̶o̶n̶e̶ ̶n̶o̶w̶ ̶s̶t̶u̶c̶k̶ ̶i̶n̶ ̶R̶U̶U̶ ̶m̶o̶d̶e̶ ̶w̶i̶t̶h̶
S̶E̶C̶U̶R̶I̶T̶Y̶ ̶F̶A̶I̶L̶!̶ ̶
R̶U̶U̶ ̶ ̶
h̶a̶v̶n̶t̶ ̶b̶e̶e̶n̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶i̶t̶ ̶y̶e̶t̶ ̶h̶a̶v̶e̶ ̶t̶o̶ ̶w̶a̶i̶t̶ ̶u̶n̶t̶i̶l̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶d̶i̶e̶s̶ ̶(̶t̶h̶a̶n̶k̶s̶)̶ ̶d̶o̶n̶t̶ ̶h̶a̶v̶e̶ ̶s̶c̶r̶e̶w̶d̶r̶i̶v̶e̶r̶ ̶t̶o̶ ̶t̶a̶k̶e̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶o̶u̶t̶,̶ ̶o̶t̶h̶e̶r̶s̶ ̶h̶a̶v̶e̶ ̶s̶a̶i̶d̶ ̶r̶e̶s̶t̶a̶r̶t̶i̶n̶g̶ ̶w̶o̶n̶t̶ ̶f̶i̶x̶ ̶i̶t̶
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do this??
update: can get back into TWRP not sure what i can do from here as i dont have an SD card reader to transfer files just a usb and a phone with no OS
Swaaz said:
long story short
htc desire 610, rooted, bootloader unlocked
needed to bypass safetynet
used magisk 12.4 worked fine, new update came
magisk no longer worked, forced me to update
update bricked my phone, bypassed this by reflashing rom in recovery
researched why new magisk update was being stubborn, one suggested updating my TWRP to latest build
updated TWRP, flashed the img while in recovery, ended up putting recovery into my boot (following a guide and wasnt paying attention)
phone now stuck in bootloop, can only go in recovery
wiped and formatted everything, decided to use adb sideload as its worked wonders for me before to try and put my rom back in
adb sideload wont detect phone, after many troublesome hours i decided to follow yet another guide i found about installing a RUU file into my phone to recover
followed guide step by step, turns out htc phones need bootloader locked, wasnt mentioned in guide
phone now stuck in RUU mode with
SECURITY FAIL!
RUU
havnt been able to restart it yet have to wait until battery dies (thanks) dont have screwdriver to take battery out, others have said restarting wont fix it
please help....
ive read many pages about similar issues, some saying boot into fastboot, some saying "just type in cmd prompt" with an attached line of code... others saying "its easy just unlock your bootloader" but what i dont understand is how i can do any of this when my phone is stuck in RUU mode??
Click to expand...
Click to collapse
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Can't help with the issue but, the waiting on battery to die issue you can press and hold power button for 8 seconds to force it to turn off
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
this worked, i must of given up at exactly 7 seconds lol
dumb question but with all these programs ive downloaded tonight ive just about given up
if i factory reset my phone in android recovery mode (not TWRP, the one with the 4 androids) on a phone that doesnt have an OS installed there isnt some miracle chance it would revert to stock rom would it? the only thing on my phone is TWRP and i was using CM12 before everything spiraled out of control
update - phone can access TWRP so im back to square one, i tried RUU i tried adb sideload and i also tried the folliwing programs
sdkmanager
SP flash tool (cant be used with htc)
windroid toolkit
USDDeview
ODIN
i just want to start over and try again but i cant seem to fix this
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
No, factory reset just reinstalls the OS that was on the device. If you brick the device it doesn't have an OS to reinstall.
Unfortunately, I can't help you very much as I wasn't able to fix my Galaxy S4 that was bricked trying to unroot as my carrier data was slow and I couldnt find the series of files including Bootloader and OS that I used on my Galaxy Discover that fixed it (obviously galaxy s4 series of files) as Odin will flash stock os and with some work around flash custom os.
Sent from my Z988 using Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
The power reset is 6-15 seconds on devices but stock Android has included this feature since Android 4.0 at the earliest that I know of
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
Hope you can figure it out
Sent from my Z988 using Tapatalk
---------- Post added at 06:37 AM ---------- Previous post was at 06:23 AM ----------
Swaaz said:
its all good i feel like theres hope now that i can get back into recovery, tense moments such as these means id prob never of held down that button for more than 7 seconds to begin with and id still be stuck from RUU mode atleast.
just wish i knew how to get adb sideload to work its worked in the past but i cant get it to detect and the guide im reading says i have to use SP flash tool but i cant use scatter files on an htc phone.
Click to expand...
Click to collapse
I don't really know adb very much as I haven't really had much experience with it.
Will probably be picking up a nexus 6 and rooting it since those are 100% stock Android and are easy to root and unbrick etc I will definitely be getting more experience with adb and root
Sent from my Z988 using Tapatalk
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Swaaz said:
guess its too late in the night for anyone else's assistance ill be back tomorrow morning hopefully my boss doesnt get mad at my phone being bricked. not sure if bumping threads is allowed here so i apologize in advance
Click to expand...
Click to collapse
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
Yes its allowed as far as I know
Sent from my Z988 using Tapatalk
---------- Post added at 07:37 AM ---------- Previous post was at 07:37 AM ----------
Did you try to root your only phone, that's a very bad idea
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Swaaz said:
ive rooted before, and since its rooted its easier to recover in circumstances such as these
the magisk update is what started it, old magisk stopped working and it forced me to update and that caused everything to spiral out of control
Click to expand...
Click to collapse
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
gabe.ulrickson said:
My suggestion is don't use magisk
Sent from my Z988 using Tapatalk
Click to expand...
Click to collapse
unfortunately nintendo apps have decided to label anyone with a bootloader unlocked as a filthy hacker and block access to their games
god forbid i upgrade my stock rom
That's why I try to have multiple devices to use
Sent from my Z988 using Tapatalk
bump
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Swaaz said:
disappointed... guess ill go buy an SD card reader and try and transfer the rom that way. people might think thread was solved due to how many replies there was :X
Click to expand...
Click to collapse
I don't think so...
Sent from my Z988 using Tapatalk
back to square one, new magisk update came out today which claims to not brick phones... still bricks mine
i guess thread closed. nobody here and every 2 hours i come into a different problem so ill just keep toying with it
if anyone cares, my current issue is that i cannot flash the current TWRP it always results in a bootloop im currently using an older build and ive been told that i need the newest TWRP for the newest magisk build