So I am attempting to use the newly discovered Flash exploit and I am running into a problem. When I first put the files on my sdcard and ran it, part1 ran successfully, then I started my browser and refreshed, then I rebooted the phone. I kept running the command to run part2 however when it finally got to the point where the device would respond to adb, it simply said permission denied. Now I am unable to run any of the parts or do anything really. I have done the "Clear Storage" option in the volume down menu on bootup and the Clear Data in the Privacy setting and then tried again to no avail...my phone simply refuses to run the scripts. I've also tried to format my SD card both through my computer and through the phone.
Any ideas?
Regards,
-Taco
I would try to do a factory reset (menu->settings->privacy?->factory reset?... i dunno if this is right but its somewhere in there).
First time it boots up, just skip through all of the starting config stuff, enable USB debugging, set to charge only, and connect to adb, run your 'adb shell' then 'sh /sdcard/part1'
you should probably see two lines pop up, one says to reboot your phone and run again, the other says to open up the internet app and go to the bit.ly/ap0dRn, REBOOT your phone.
Rerun adb and part 1, if its successful and tells you to reboot then reboot using adb reboot.
What I did (and it took me 3 or 4 factory resets to get this to work), was to leave my phone plugged into the PC and when it comes up to the white HTC boot logo, it will may take a few seconds, but as soon you hear the windows sound saying the phone connect (BA DUN) hit enter on your 'adb shell /data/local/part2' command. If it says not found, just keep hitting up, enter till it does. I think it needs to be done while the white boot screen is still up. If it doesn't, then in my experience with it, I had to do a factory wipe and start over.
You should see the output when its done saying you have rw-rw-rw- root blah blah and it would always kick me out of adb. I never got the su's # prompt. But I would go in and do the cat stuff like it says and reboot, flash the PC36IMG.zip file and it would be downgraded for me to do toast's part 2.
I know it was an essay, but hopefully that works for you.
Related
Here is my issue..I have been rooted since I got the phone and actually rooted both of my EVO's. Last week I decided to go back to Fresh Rom 1.0 and inadvertently flashed a new theme at the same time. Did not flash the ROM and then go back in and flash the theme. As a result, the phone went into a continual cycle of rebooting the loading screen ( for Fresh users you know it has the little guys and says FRESSSHHH). Well that happens over and over again.
The only option I have is to take battery out and go into the bootloader mode. MY problem is this:
* Once in bootloader mode, I can't reflash because when I go into the recovery mode, the recovery says " ADB server is out date" and scrolls thru a few lines an disappears. I've tried every thing suggested to me and still have not been able to fix that.
* Cannot access root of SD card because system doesn't recognize the phone is attached.
* Tried to load PC36IMG file on the card manually and that loaded but I can't get to the restart option. It finds the file but does not give me the restart commands.
I'm at wits end right now. I tried the OTA Recovery but since I cannot connect to the computer, it won't run either.
Please help......
Restore a nandroid.
RUU start over.
I tried to do that but the computer - htc sync won't recognize the phone so I can't RUU again. When I get to the end of the process it tells me either the phone isn't connected to the USB or the USB isn't connected to the computer.
You phone says the ADB server is out of date when you boot into recovery?
It sounds like you are not completely rooted.
You should be able to volume down and power on. Then choose recovery. From there you can restore a backup. That should also give you ADB access to the phone (if you are fully rooted)
If you are not fully rooted, and you have to run some bat file on your computer to get the phone into full recovery, you may be skrewed.
No, the computer says that when I go into recovery mode and have the black screen and red triangle on it. I then go to the computer and try and run the recovery file that I've been running as I've flashed 10-12 ROMS already. The CMD screen on the computer comes up as ADB Server is out of date...and another line or two scrolls by and then it disappears, never connecting to the phone and going into the next screen where I can wipe or flash from SD..etc..
Sounds like you did not complete step 2 of the root process. You should be able to enter recovery without the use of a computer.
Reboot your computer and try again, if you still get errors then I am out of tips.
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk
CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.
slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium
try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.
To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.
THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.
Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.
I have had a Kindle Fire since they day they came out. I immediately disliked the stock Rom so I ran the kindle fire utility and installed Fire Fire Fire and TWRP, rooted it, and installed CM7 Rom which has been working great. Transferred files and programs between my PC and Kindle with no issue for months. Now with all the ICS roms available and working I decided to try and upgrade to one of those and thats when everything went wrong. Its in a bootloop and the triangle appears, fades, lights up again and immediately boots to TWRP. I have flashed the entire kindle using TWRP trying to get everything off of it. Upon plugging it into my PC BRIEFLY when the triangle logo pops up I get a "USB device not recognized" on my PC. I have tried using KFUtility to reinstall drivers, tried uninstalling n reinstalling drivers but the same thing happens. I cannot use TWRP to mount at all, nothing happens. Kindle Fire UTility keeps saying adb offline, CMD adb devices also results in 0 devices found. I have tried putting it on normal boot using both ADB and KFUtility and it says "wait for device" and nothing ever happens. Any idea? Not even sure if I have a rom installed on my kindle anymore but my PC wontread it so I cannot push another image to it. Got a plane trip on Saturday and would love to have this working to kill the bordom lol. Any advise would be greatly appreciated.
It sounds like your bootmode is set to recovery. An easy way to fix this is download FFF1.4 to your computer and use the mount function in recovery to place it on your sdcard.
Flash it in recovery as you would a rom except don't wipe anything. When you reboot, hold the power button like you're trying to enter recovery and you'll be given the option to reset the bootmode.
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
anomiefaunus said:
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
Click to expand...
Click to collapse
Generally, the only thing that would prevent adb/kfu from communicating with the device is the drivers. Make sure they're installed properly. You may have to uninstall them (delete if applicable) and reinstall them.
Follow the instructions in this guide to install and verify your drivers.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
anomiefaunus said:
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
Click to expand...
Click to collapse
Get your device drivers working so you can use adb. Follow the instructions in the post below...
http://forum.xda-developers.com/showpost.php?p=26144447
That is excellent advice and I wish it would work but I cannot pull up ADB once in TeamWin. Keeps saying no devices. As i said my PC detects it and ADB will detect it for .5 seconds on the orange triangle. Once the orange triangle disappears and it either boots to blackness or boots to TeamWin ADB stops recognizing my device. But I will play around with your suggestions once I get off work and let you know what i find out. Thanks again for everyones support.
Frozen screen during rooting
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
peredexter said:
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
Click to expand...
Click to collapse
Don't hijack the threads please. If you have a problem or question, post it in the Q&A section.
hey everyone! new to the forum. needed help bad.
i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?
some notes on my rebooting condition.:
phone keeps rebooting even when booted up in safe mode.
-in safe mode i do have more time before it reboots itself
phone does not reboot itself when in bootloader mode or recovery mode
i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.
any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance
lilzed_747 said:
hey everyone! new to the forum. needed help bad.
i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?
some notes on my rebooting condition.:
phone keeps rebooting even when booted up in safe mode.
-in safe mode i do have more time before it reboots itself
phone does not reboot itself when in bootloader mode or recovery mode
i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.
any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance
Click to expand...
Click to collapse
Hate when a rom just goes bad for some reason.. Could you supply the error messages you get when your backup fails? I'm guessing it might have to do with file names having weird symbols. Also you might want to backup different folders of your sdcard at a time to avoid failure; i.e., "adb pull /sdcard/Download <some_directory_on_computer>".
7175 said:
Hate when a rom just goes bad for some reason.. Could you supply the error messages you get when your backup fails? I'm guessing it might have to do with file names having weird symbols. Also you might want to backup different folders of your sdcard at a time to avoid failure; i.e., "adb pull /sdcard/Download <some_directory_on_computer>".
Click to expand...
Click to collapse
thanks for the reply. system backup finishes then it goes to back up data. after while it says that there's an error making backup image of /data
is it possible to just to use command prompt to just pull my pictures? would it just be adb pull /sdcard/dcim <some directory>?
also for some reason i am unable to communicate with my phone using adb prompts. yesterday i typed in adb devices and my phones serial number would come up as connected. today under "list of devices" its just blank....not sure what to do.
UPDATE: i was able to get my pictures off of my phone. i launched CMD through the nexus toolkit and it seemed to detect my phone.
i flashed my phone back to stock using the toolkit. for some reason after everything was said and done my phone wasnt actually set back to stock. my phone still has all my apps etc. it still restarts every few seconds.
i tried a couple force flashes using the toolkit again but still same phone. nothing has changed or been fixed. not really sure what my next plan of attack should be. any guidance is very much appreciated.
lilzed_747 said:
UPDATE: i was able to get my pictures off of my phone. i launched CMD through the nexus toolkit and it seemed to detect my phone.
i flashed my phone back to stock using the toolkit. for some reason after everything was said and done my phone wasnt actually set back to stock. my phone still has all my apps etc. it still restarts every few seconds.
i tried a couple force flashes using the toolkit again but still same phone. nothing has changed or been fixed. not really sure what my next plan of attack should be. any guidance is very much appreciated.
Click to expand...
Click to collapse
Glad to hear you got your pictures off. As far as wiping your phone. If you got everything off your sdcard that you want, you can do a fastboot wipe.
-press volume up + volume down + power to get to fastboot mode
-connect the phone to your computer and enter in the command window "fastboot devices" to see if it's connected
-enter "fastboot -w" to do a full erasure of the phone's /data partition
Then use nexus toolkit, recovery, or fastboot to flash a new rom from there. This has saved me in the past in a similar situation. Definitely make sure you have everything off your sdcard you want to keep before trying this though.
7175 said:
Glad to hear you got your pictures off. As far as wiping your phone. If you got everything off your sdcard that you want, you can do a fastboot wipe.
-press volume up + volume down + power to get to fastboot mode
-connect the phone to your computer and enter in the command window "fastboot devices" to see if it's connected
-enter "fastboot -w" to do a full erasure of the phone's /data partition
Then use nexus toolkit, recovery, or fastboot to flash a new rom from there. This has saved me in the past in a similar situation. Definitely make sure you have everything off your sdcard you want to keep before trying this though.
Click to expand...
Click to collapse
thanks so much for the help so far. unfortunately everything you have told me so far has not worked.lol. i followed the steps like u said but the phone just stays on the "google" screen after i install a stock rom. left for 2.5 hours in hopes of it doing its thing.lol. had to pull battery and start it up. nothing changed, phone still restarts i also tried using toolkit to flash stock + unroot (both in bricked mode and normal mode), flashed zip stock images and installing in recovery mode. i also used CMD to push stock images to my phone and installing but still nothing.
i also followed the instructions extactly on this forum http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
all of the steps successfully completed but after a reboot my phone was left unchanged.
i may have screwed up my description of the problem earlier. the phone restarts after my phone stop responding/freezes. i also find that there almost always is a program that stops working. i find handcent sms is having the most errors. tried to uninstall but phone freezes. tried in fastboot/adb but nothing happens.
thanks again for the help so far.
I just bought a 2013 Nexus 7 today for very cheap, to use in my car as a headunit and learn a bit about flashing different roms, using the timur kernal, etc. It looks like it was used at some sort of healthcare facility though, because it has some "Optum Health" software on it, deeper than just an app it remained after a factory reset. On restart the optum health logo comes up, immediately after the google logo and says loading, well before it actually loads to the home page of the tablet. So it's pretty deep. I was thinking a fresh factory ROM would help me out.
I was following this guide to get twrp on the phone, as wifi wasn't working (most likely because I had tried to remove the optum stuff by disabling apps, and I got a little trigger happy) load via adb:
https://www.xda-developers.com/how-to-install-twrp/
Everything was cool until I went to restart it. I typed "fastboot reboot" into the command prompt, she restarted, and gets infinitely stuck at the "Optum Health" logo, and the word "Loading" pulses underneath.
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
solson1041 said:
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
Click to expand...
Click to collapse
Follow these instructions to resolve the problem and flash up-to-date Android - https://wiki.lineageos.org/devices/flo/install
"With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons." it really works.
Then connect it to a PC and install proper USB driver - https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Once you get ADB & Fastboot installed on your PC or linux , do a command prompt with the device connected.
adb devices
It should list your device in your terminal output. If and when it does..If your a little hinky on the buttons just do a command prompt: adb reboot recovery, adb will reboot your device for you into recovery mode. Then follow the LOS instructions provided for you & you will be amazed at how great your tablet works. Just a little FYI, if you've never done this before, find the "pico" gapps, don't try to install any of the bigger ones, there is not enough room on the sys partition for the full gapps install. After & if you get pico installed you can always add to it with all the room you have left now on the rest of the device. Also when you are installing LOS, make sure you find and install the gapps at the same time you install the OS, before you reboot your device. It will save you a lot of headaches. Just follow the directions and you will be very happy.