Related
I used root explorer, made a copy of my original and named it original, then copied over another build.prop from my SGSII to play with MC3 and now the prime wont boot.
Im sure I will have to wait until i get home to use my USB cable but is this something I can fix through ADB?
how can i get the Prime into state that ADB can talk to it since now all i get is a black screen after the Eee pad splash screen?
Can you get into the recovery?
yes but it it shows the little android on his back with a red triangle.
is that because im rooted?
see if you can get adb access, if so push back an original build.prop...
note... never ever push a build.prop from a different device.. its the most stupid thing you can do.
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
nextelbuddy said:
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
Click to expand...
Click to collapse
i hope so to bro, although i did read someone messed up his build.prop before on his prime, dunno how that went afterwards... u might need to search for that
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
thank you very much i will get to work on this when i get home with my cable. i was just about to post where can i get another one but you posted directions on how to pull my copy that i created which i renamed original.build.prop
Also might wanna take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1514088
PM_mobile said:
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
Click to expand...
Click to collapse
i can get the device into APX mode because i installed the APX driver and when i hold VOl UP and Power, my windows 7 computer shows Asus Prime APX under System Devices and it goes away if i unplug it and vice versa plugging it back in however ABD stil shows Blank for connected devices.
not sure what Im doing wrong so im uninstalling my OLD SDK from last year and reinstalling the latest SDK to see if that helps.
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
nextelbuddy said:
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
I think its bricked... because from the research Swift and I did on a battery mod, he tried a mod I don't remember what and it ended up in boot loop. ADB won't work because of the boot loop it doesn't stay long enough in a booted state for ADB to send/receive the commands. If your still in your return period try for exchange.
nextelbuddy said:
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
The file system will be read only by default. You need to remount /system as read/wrire.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
foxmeister said:
The file system will be read only by default. You need to remount /system as read/write.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Unfortunately i can not remount the system. if i try to remount it says either device not found or error it can not.
its like it never listens long enough..
for example if i type ADB Devices, it will say "ADB Server out of date killing server and then it shows Daemon starting and then says Failed"
if i try that 2-3 times then it will eventually say Devices and list my Serial number.
if i try immediately after that to go to ADB SHELL, it starts and then i type:
adb push original.build.prop /system/build.prop
as soon as i hit enter it says Device not found.
even if i try that command 5 times in a row hoping that it takes one of the times, it does not.
Brollie said:
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
Click to expand...
Click to collapse
i cant look at that link, its truncated. can you post the full link please?
i tried downloading the .15 firmware from Asus site and pasting it on a micro SD card and putting it in the Prime and then booting into recovery mode but it always shows the android laying down with a red triangle.
PM_mobile said:
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i cant remount, i can shell but if i do that then it says no devices connected.
wow, i royally screwed things up with this stupid build.prop like an idiot.
For the record, once in adb shell it's not adb push anymore..
That'd be
cp /system/original.build.prop /system/build.prop
I doubt this will do you any good, it seems you just can't stay in adb long enough because it reboots.
You don't gave a working custom recovery do you? (like clockwork mod)
I think I've seen people with custom recoveries on their primes.. that'd allow you to adb properly or flash a zip file with your build.prop..
Also, Did you look at this thread?
http://forum.xda-developers.com/showthread.php?t=1514088
They have a few unbrick solutions and something about getting adb to work from recovery. Recovery wouldn't bootloop while you're trying to adb..
aznmode said:
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Click to expand...
Click to collapse
THIS!!!
i downloaded the latest stock firmware .15 from asus support site. renamed it to
EP201_SDUPDATE.zip and copied to a micdro SD card.
held VOL DOWN + Power and when i saw the white text hit VOL UP twice
and the recovery manager detected the file on the SD card and started flashing.
no more RED triangle android anymore.
im sooo excited this worked and will definitely take more caution in regards to the build.prop file. never realized how much of an integral role it played in the android OS.
thank you very much for all your help and to the others thanks for your help with ADB. even though it didnt work, i played with ADB so much last night and today that i feel much more comfortable with it.
my phone wont go past HTC starting screen.
How can i flash stock att rom ?
I am stuck. suggestions appreciated.
Why won't it? What did you do to get to this state? What did you flash?
The more details you give...the more likely someone will be able to help you!
well i have unlocked bootloader.
i flashed one mod for extended power menu and after that my phone wont go past HTC one screen so i wiped and did factory reset still phone wont boot.
I went in to recovery menu and formated system and now i dont know how to flash stock rom.
varuun said:
well i have unlocked bootloader.
i flashed one mod for extended power menu and after that my phone wont go past HTC one screen so i wiped and did factory reset still phone wont boot.
I went in to recovery menu and formated system and now i dont know how to flash stock rom.
Click to expand...
Click to collapse
Here is all you need to know.
HTC One FAQ
I take it you did not make a NAND backup?? Always advised to make a BU before flashing anything!
What recovery did you install?
shawman said:
Here is all you need to know.
HTC One FAQ
Click to expand...
Click to collapse
Somehow i can not access USB storage so in this case how can i put rom into internal storage?
varuun said:
Somehow i can not access USB storage so in this case how can i put rom into internal storage?
Click to expand...
Click to collapse
ADB Sideload it. Here's the stock Deodexed ROM I used when I had that problem.
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
wmg316 said:
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Click to expand...
Click to collapse
..... Is that..... Mike G.??? You're an Android Guy too!
That's me! Who is this?
wmg316 said:
That's me! Who is this?
Click to expand...
Click to collapse
Josh S. from Landmark
Small world!!
wmg316 said:
Small world!!
Click to expand...
Click to collapse
No kidding.
P.S TrickDroid is a pretty sweet ROM.
Hi
I am doing as you said but i am getting attached screen. its not working for me.
wmg316 said:
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Click to expand...
Click to collapse
Do you have TWRP recovery?
If so, did you boot device to recovery?
If so, did you then select Advanced, ADB Sideload...then swipe to start?
THEN...run the command adb sideload One_1.29.401.13_deodexed.zip
EDIT:
ADB Sideload does not work until you are in recovery, and select and run adb sideload within recovery.
Also, if you get device not recognized...run:
adb kill-server
adb start-server
then try adb sideload again...
i have clockworkmod recovery v6.0.3.1
I booted into recovery then selected install zip from sideload. but its not working as it suppose to. Am i doing something wrong?
varuun said:
i have clockworkmod recovery v6.0.3.1
I booted into recovery then selected install zip from sideload. but its not working as it suppose to. Am i doing something wrong?
Click to expand...
Click to collapse
"Fastboot erase cache"
when i checked log in to recovery its says that"failed to open adb driver control:no such file or directory"
and when i type adb devices it says
"
C:\fastboot>adb devices
List of devices attached
HT348W900356 host
"
Any clue?
I don't use CWM, so don't know anything about it. Try buying a USB-OTG cable, get a USB stick (USB flash drive) and put the ROM on the USB stick, connect USB stick to phone and mount USB-OTG in recovery. Flash from that. That's the only other thing I can think of.
Sent from my HTC One using Tapatalk 2
varuun said:
when i checked log in to recovery its says that"failed to open adb driver control:no such file or directory"
and when i type adb devices it says
"
C:\fastboot>adb devices
List of devices attached
HT348W900356 host
"
Any clue?
Click to expand...
Click to collapse
Do you have HTC Sync Manager installed? Do you have all the HTC Drivers?
Long story short, ended up flashing a bad rom without backing up my current rom due to lack of storage space Just ordered a micro sd card from Amazon. Currently unable to boot phone due to not having a rom. Downloaded Android SDK and have been trying to sideload the .zip in CWM recovery but I get an "adb server is out of date. killing..." followed by "Daemon started successfully..." "device not found" Running Mac OS and I'm stuck on what to do at this point. Help?
I've been using in Terminal:
cd desktop
cd Android (Placed adb into this folder to make it easier to find)
./adb
./adb sideload Synergy.zip
LGeX said:
Long story short, ended up flashing a bad rom without backing up my current rom due to lack of storage space Just ordered a micro sd card from Amazon. Currently unable to boot phone due to not having a rom. Downloaded Android SDK and have been trying to sideload the .zip in CWM recovery but I get an "adb server is out of date. killing..." followed by "Daemon started successfully..." "device not found" Running Mac OS and I'm stuck on what to do at this point. Help?
I've been using in Terminal:
cd desktop
cd Android (Placed adb into this folder to make it easier to find)
./adb
./adb sideload Synergy.zip
Click to expand...
Click to collapse
You might have to do a system restore of the stock image. If you want to do this I can PM you some info.
Need help as well
DarkMenace said:
You might have to do a system restore of the stock image. If you want to do this I can PM you some info.
Click to expand...
Click to collapse
Could I please get some help with this as well. Trying to do a sideload as well, since I formatted the whole system and lost all of the ROMS I would normally install from the system SD.
UPDATE!
Finally got it working. All in one tool kit + adb sideload the rom = win
Hope this helps anyone else in the future that does this!
So I formatted data and have no ROM to flash anymore - I'm trying to mount USB but it keeps saying "E: Unable to oust 'usb-otg' - How can I get this thing to mount so I can flash my ROM back on and use the phone again!
TWRP Recovery is what I'm using if that helps
Edit: Update!
I also ran into a similar predicament a few days ago. I found adb push to be much easier than sideload. Make sure that your drivers and adb is installed on your PC (I assume Windows). In recovery mode, plug phone into USB and your PC should detect the phone but you won't be able to see phone contents; mine made a connection sound.
Then open a command prompt and type: adb push ROM.zip /data/media/ROM.zip
Rom.zip is the rom file that you want to flash, which should be in the same folder as adb. For the path, I used "/data/media" because the custom recovery defaults to that but you may be able to use "/sdcard" as well.
Then flash the rom using recovery
Click to expand...
Click to collapse
Tried to do this as well, moved AR 10.3 rom to adb folder, did the push command and it couldn't find/connect to device.
Would finding a non-aroma rom and flashing it using fastboot work?
Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK，I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2