Well, I've used the RootZenFone 1.4.5 version apk method and it worked out for me... problem is, by modding the system I am now getting a boot loop on the main splash and have no adb access. Does anyone know how to force a manual sd update using the downloaded firmware packages and a micro sd card?
My Recovery is stock, so is the Droidboot (fastboot) image, though I cannot get anything through the adb and fastboot commands.
The only time I get something is when i get it into recovery and enable the sideload - pushing a file using the adb sideload command results in a status 0 error / signature verification failed
Related
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
jojo665 said:
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
Click to expand...
Click to collapse
First of all try adb push Name_of_Rom.zip /sdcard/
If that does not work try adb push Name_of_Rom.zip /system/media/
If that still does not work then download the correct TWRP blob file from the following link for your bootloader. http://www.teamw.in/project/twrp2/93
The fact that you are on CWM and was using CM 10 makes me believe that you are still on the ICS bootloader but to make 100 percent sure when you first power on the device look at where the "NVIDIA" logo is. If it is bottom center it is ICS, if it is bottom right it is Jellybean. (MAKE SURE YOU GET THE CORRECT TWRP VERSION FOR YOUR BOOTLOADER)
Now rename the blob file you downloaded to twrp.blob. Go into fastboot and type the following.
fastboot -i 0x0b05 flash recovery twrp.blob
This should install TWRP which will allow you to install a rom off an external micro sd.
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
jojo665 said:
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
Click to expand...
Click to collapse
What exactly did you do? I'm trying to extinguish all avenues before I have to RMA my tablet. Thanks for the help!
Hello,
I am hoping someone will be able to help me. My Asus Transformer Infinity TF700T was so slow and laggy it was completely unusable so I am attempting to install cyanogenmod for the device. My problem is, after flashing clockwork mod, the tablet will not start up into recovery or normal mode. It is just stuck on the logo screen. It wont even turn off
These are the steps I followed so far.
1. Unlock tablet using asus unlock tool from Asus Website.
2. Root tablet using kingo root
3. I tried to install clockwork mod from Rom Manager however it did not have my device listed so I tried to do it manually.
4. I downloaded the Android SDK with fastboot and ADB, they worked and recognized my device.
5. Downloaded recovery.img to the same folder with ADB and fastboot and used the command fastboot -i 0xb05 flash recovery your_recovery
6. CMD said "writing 'recover'
7. Restarted the tablet and this happened.
At this point I think ill cut my losses with a slow tablet but I need to get it up and running again. At least able to turn it off. Any help on getting it to start up in either recovery or normal mode would be greatly appreciated.
Thank You
Im trying to learn fastboot and adb sideload and adb overall commands.
I downloaded original rom for Asus z380c form Asus support site and as i read somewhere the difference between fastboot and adb was that fastboot cant do one function as adb can i cant remember which function it was (command, process) but as i understood fastboot was limited. Now im trying to flash Asus z380C through abd sideload but its impossible because z380c is in fastboot by default. Yes i tried atp or what is called asus flash tool. Its ok it flashes but z380 wont fully boot. I did almost everything. It seems that boot logo is stuck because i made it work to first installation windows language etc etc. set up. But i did it by chance plugging in usb and disconnection changing cable, power brick etc. So im not sure why there is a lag or bug delay in set up. I want to use adb or fastboot which ever in command prompt to install original rom from site but cmd or adb wont recognize installation. I tried many commands but it doesnt work. Tnx in advance if anyone can help me. Ah yes fastboot reads only img files but original rom from asus is in zip format and inside its standard view of system files. I need img files all of them like in mtk htc type of roms. so i can install rom from img files on fastboot.
Hello! I have a problem with old tablet it is Prestigio multipad 4 quantum 7.85. It is that this tablet doesn't have OS installed so I tried to install it manually with adb . In recovery I turn on ADB update and ADB with command "adb devices" detects it as "sideload" so I tried command adb sideload update.zip (I put it in ADB folder) which contains original software which I downloaded from internet but installation starts and after completion on tablet i see installation aborted. Tablet doesn't have TWRP and as I said only stock recovery is working is there any way to install software to it and will start working?
PS I'm not native speaker but I hope the text is understable