asus prime201 stay on recovery and do not reboot - Asus Eee Pad Transformer Prime

after downgrade to .15, root , instnall cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.It lets me backup from recovery but when i reboot again it takes me back to recovery.I am totally inexperienced in these things.If someone can make a small program for me to making my asus prime 201 to work again i donate to him $100.

chasosa said:
after downgrade to .15 root install cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.
Click to expand...
Click to collapse
Uh oh lol, kinda sounds like boynamedstacy's issue. Maybe not though, you could try whatever methods he was unsuccessful with and hopefully you're not bricked.

chasosa said:
after downgrade to .15 root install cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.
Click to expand...
Click to collapse
first of all install the naked drivers and search for a workimg adb.
then connect your tablet with you pc and make sure your prime is in recovery.
open up your cmd (make sure you are on win7) and typ: adb shell
now: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 hit enter.
now typ: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 enter.
exit cmd and now reboot via cwm.
if it stuck on the eee pad screen, just typ in the adb: adb push romname \sdcard\ romname again.
now flash the rom and your done.

Related

Prime still reboot to CWM

Hi, i have big problem. My Prime after factory reset from ICS menu still booting to CWM . Tried wipe everything, install new rom, but Prime still booting to CWM. Please help me.
Solved
ADB shell fix this
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]

[Q] HELP. No idea what to do.

Hello,
Basically my prime was running fine, GooManager then told me to update gApps which i then did. And now my device will only boot into Recovery. It totally skips the bootloader screen, and even holding down just goes into recovery.
I did manage to fix it using the following command:
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
But then i accidentally flashed the gApps again (i know, I'm an idiot)
I could just run the command again and fix it, but adb will not run. Just keeps saying device not found. The drivers are installed, and it shows up in Device Manager fine.
Any ideas on what to do?
Scottymeuk said:
Hello,
Basically my prime was running fine, GooManager then told me to update gApps which i then did. And now my device will only boot into Recovery. It totally skips the bootloader screen, and even holding down just goes into recovery.
I did manage to fix it using the following command:
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
But then i accidentally flashed the gApps again (i know, I'm an idiot)
I could just run the command again and fix it, but adb will not run. Just keeps saying device not found. The drivers are installed, and it shows up in Device Manager fine.
Any ideas on what to do?
Click to expand...
Click to collapse
try to uninstall the drivers and install again
leime68 said:
try to uninstall the drivers and install again
Click to expand...
Click to collapse
Thanks for your reply.
I have done many times Doesnt seem to want to work at all. I dont know what to do

I want CWM off and a stock rom on. I feel like I am close but can't get it.

Ok, I have a tablet that has CWM on it. It also has 9.4.2.15 that I can tell but it won't boot.
What I did was did the full formats as some people say in CWM, then I pushed the stock rom to the internal SDcard and installed it. Well the install looked like it went fine in CWM, but it boots back to CWM every time. I also can't seem to get it into fast boot (maybe I don't know how to properly).
Any suggestion on what I might try? I can get in adb.
I would try to push a rom to prime with adb. Obviesly a custom rom for unlocked bootloader. So the stock ron you flashed, was it purely stock? Straight from Asus? Or for unlocked bootloader?
Sent from my Galaxy Nexus
Makrilli said:
I would try to push a rom to prime with adb. Obviesly a custom rom for unlocked bootloader. So the stock ron you flashed, was it purely stock? Straight from Asus? Or for unlocked bootloader?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Straight from ASUS.
What do you suggest that I put on it as there are so many I really don't know what to choose.
Straight from ASUS is a big NO if your bootloader is unlocked. Is 9.4.2.15 ics? Can't remember
Sent from my Galaxy Nexus
Makrilli said:
Straight from ASUS is a big NO if your bootloader is unlocked. Is 9.4.2.15 ics? Can't remember
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Fixed it with
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
Now how do I get back stock? It's running ODJDub HD Prime 1.0.1
As you have unlocked your bootloader, you can't flash stock rom anymore. You have to find a rom as close stock as possible.
Sent from my Galaxy Nexus

[Q] Lokifying error Boot loop CWM otg

Tying to install a rom. keep getting this error on cwm. Im stuck in Cwm recovery loop. LG G2 (D802). Installing from otg as pc will not find phone. using adb to push rom
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
Keep it simple (Noob Friendly)
donation for fix
Thanks hope you can help
FIXED
if anyone is stuck here is the ADB command that fixed my phone.
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
hope it helps
hayjoesam said:
if anyone is stuck here is the ADB command that fixed my phone.
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
hope it helps
Click to expand...
Click to collapse
You know there's a LG G2 section right? And there's also an irc channel for these types of things.
Sent from an Xposed LG-G2/LS-980

FIX: Bootloop with OTA and TWRP (bumped)

If you accidentally take the OTA and have the bumped twrp installed you'll find yourself in a bootloop.... to fix it do this;
If you have ADB access (once booted into twrp), plug in your phone to your computer and do this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
If you DONT have ADB access for whatever reason or you do not have access to a computer or something you can use TWRP's "terminal command" option to do this:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type the above out with the onscreen keepboard so be very very careful to get all the spaces and /'s.... One wrong letter and you could blow up your phone.
After you can reboot and it should boot as normal.

Categories

Resources