Related
Hello,
I turned on my Xoom to see "Encryption Unsuccessful" tonight. If i boot into stock recovery and try to factory reset, it cannot mount Cache. If I plug the device into my computer, fastboot can find it but ADB cannot. I have the proper drivers installed. I can't get into my tablet to turn on USB debugging. I just bought an OTG cable to try to fix it, but cannot find the update.zip file that I need. If i try to fastboot oem unlock, it fails. I've tried everything I can find, I've done hours worth of playing/trial and error to no avail. Any help would be fantastic. Truly at a stand still. Please ask with any specifics needed to assist me.
Is it possible to flash to CWM recovery without being able to boot/find it in ADB?
Thank you,
Bradon
>.<
Nearly to the point of offering some sort of payment for assisting me. I'd rather not ship it out, but more than glad to work something out paypal or giftcard wise. This tablet is the only thing keeping my wife entertained, and another tablet is not in the budget.
But u can connect with fastboot to device ?
if yes this should help you
http://forum.xda-developers.com/showthread.php?t=1451655&page=7
http://forum.xda-developers.com/showthread.php?t=1049485
Probably you will lose all data on it ... Why u wanted to encrypt u device ...
I did it too but it was missunderstanding specialy when flashing a lot .
Alright so...
I've used fast boot flash user data, system, recovery and boot. Those are all successful, but if I reboot.. Nothing changes.
I've loaded many zips onto a flash drive with an otg cable, boot into the stock recovery and try to update, unable to verify signature.
Adv will not find the device, reinstalled drivers many times
Rsd will not find the device
Factory reset fails, cannot mount cache and about 10 other cache/recovery errors
Fast boot OEM unlock fails, unable to write a certain 3 letter file
I'm at work right now, so I can post specifics/pics later.
I didn't try to encrypt it, it seemed like a virus that my wife got. She clicks on advertisements, downloads sketchy files/apps.
It is unrooted, stock recovery.
20+ hours of research and trial.. No success.
Can u use this ?
http://forum.xda-developers.com/showthread.php?t=1074979
Use 2 method.
Write response what happend and it does flash recovery .
You have to unlock bootloader
look here simillar problem :
http://forum.xda-developers.com/showthread.php?t=1571827
http://forum.xda-developers.com/showthread.php?t=1952628
And u do not need any special otg cabel - use stock xoom from package. OTG is for host-usb.
Anyway u will have to do it with fastboot , probably /cache partialy encrypted.
Alright, I just followed the CWM recovery guide.
First off, ADB does not find my device, meaning I cannot reboot into the bootloader. I can flash the recovery only after flashing userdata for some reason. After flashing, it says complete though when I reboot nothing changes. The other 2 links, first one I can't use because adb doesn't find my device, and the 2nd one.. I don't think xoom has a "download mode".
Thanks
Ok, so when u push down button in booting u have only recovery ?
U should have fastboot too ... try to press up vol 1 s after booting, then connect to pc, and check in device manager rmb on "My pc"
And ? .... This must working ... Use fastboot.exe in cmd ( in windows 7 ) on Administrator User.
Also, when I first boot up recovery I get
E: failed to mount /cache (invalid argument.)
E: Can't mount /cache/recovery/command
E: Failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E: Failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E: Failed to mount /cache (invalid argument)
If i try to factory reset or clear the cache, I get the same message.
U do not understand what u reading, u cant do this from recovery ...
U have partialy crypted storage ... its normal!
1. download fastboot on windows
2. install drivers from
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
Click to expand...
Click to collapse
3. run fastboot protocol on xoom press down vol "find fastboot" if not press top vol in booting - should fastboot protocol ... in output
4. Use fastboot.exe from android sdk - run in in cmd ( Run ad Administrator , right click on cmd)
4. unlock bootloader
5. flash rom boot recovery in *.img format!
This must working...
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
bcwest said:
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
Click to expand...
Click to collapse
Is it bad ? - now when u show up "fastboot protocol ... " on xoom run fastboot from android sdk .
Fastboot ran from cmd with admin privileges.
fastboot oem unlock
used volume controls to select yes/i accept
Device unlock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:324 NvStorMgrFileOpen("UDA"):196624
ERROR: Failed to format UDA.
Error while unlocking device.
unplug mmc card from xoom and try again, where did u get files ... system.img ,recovery.img,boot.img ?
I've tried with both the mSD card in, and out. I got the boot/system/recovery/userdata from the stock image post from XDA.
ok, I didnt tryed this with stock rom, try to change recovery with http://forum.xda-developers.com/showthread.php?t=1074979
reboot and try to get to new recovery.
do this:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img <- from http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )
mx600 is the model that I have.
All of the flashing goes through fine
fastboot erase cache fails instantly (Failed to format PDB)
fastboot erase userdata fails instantly (Failed to format PDB)
fastboot reboot
volume down for recovery to see if CWM changes went through
stock android recovery
If I put my mSD card back into the unit, and try to do it all over again..
Flashes go through fine
Cache fails instantly, same error
Erase userdata causes my cmd to hang up, and the xoom sits at "StorMgr Formatting UDA STATUS: | | |"
5 minutes later, still sitting at that message.
Mx600, I restarted the device after flashing everything, If I let it go past the Dual Core Technology big red M, it boots into android but all that I get is the Encryption Unsuccessful screen. It says push restart, but it does nothing.
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )[/QUOTE]
Damn, that mean bootloader is locked or he have problem with gpt ?
ok... I'm not sure what will hapend but u can try to lock it again
fastboot oem lock
then reboot
fastboot oem unlock
output ?
Device Lock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:350 NvStorMgrFileWrite(ff, 0x00004000:00000000):196608
ERROR: Failed to format UDA
Device lock operation FAILED.
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
osos96 said:
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
Click to expand...
Click to collapse
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
osos96 said:
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
Click to expand...
Click to collapse
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
!Lür said:
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
Click to expand...
Click to collapse
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
!Lür said:
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
Click to expand...
Click to collapse
yup i just made it a step by step tut for noobs and your welcome
I unlock the g bootloader got it to root I have the latest cwm recovery been trying different ones also, but some how when I try to install any rom that's out there it won't boot up it only stays on the boot screen . Any ideas
Me too
I have this problem too.
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
forgotter said:
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
Click to expand...
Click to collapse
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
chente323 said:
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
Click to expand...
Click to collapse
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
This is the same thing a friend told me to do we did it had no luck Did it 2 times just in case I dint do it right the first time
Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC rename it to "CM.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\CM.zip /data/media/0/"(to push the CM11rom to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push CM.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11.zip or you can flash stock firmware through mfastboot.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Thanks I will give it a try tomorrow since it's wife phone I don't have it w me now. I'll get back at u let u know if it work
forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
Hi forgotter! I have the same problem... won't boot with any ROM. I've followed your instructions but stil stucked on the boot logo. I will try the second method you provided now, hope that works :crying:
@notnowjohn
Didn't know why first method didn't worked for you but the second one would definitely work. If you get any error then reply to me, and yes in my second method post by mistake there are some extra space added after full stop (.) e.g. in boot. img (it is boot.img ) do please avoid that.
forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
notnowjohn said:
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
Click to expand...
Click to collapse
Don't worry your phone is fine.
Whenever adb shows m mismatched partition it's fine and usual.
I understand your problem now, I just think if I your device now , I would have repaired it within minutes. Never mind, follow the below steps .
Download the philz recovery to your PC, flash it through fastboot on your phone. Then go to recovery on your phone immediately and choose wipe-wipe data and sdcard. And then flash the stock firmware through mfastboot or install any ROM through recovery.
Anyone report which step what must i do to solve this prob
sinkadorable said:
Anyone report which step what must i do to solve this prob
Click to expand...
Click to collapse
Read post #7 on page 1.
I cant push system to device. What tools must be i have?
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
pluiz halp!
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
jamiethomaswhite said:
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
Click to expand...
Click to collapse
Plug the phone to wall charger and leave it to charge for the whole night, the next when you'd restart the phone it should boot up. Sometimes the phone discharged itself to such a level that it didn't have enough juice left to show the battery charging status even.
After that follow instructions from post #7 on page 1 and paste all output commands you see. Well, the phone should boot up.
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
sinkadorable said:
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
Click to expand...
Click to collapse
Mismatched partition size is usual , no need to worry about that. What do you mean by UBL warning message? And yes, after you flash recovery, enter in recovery mode and wipe data and sdcard and then flash any ROM from fastboot.
And if you get into an error or solution doesn't work then post your problem but detailed so I can get to the main cause of the problem.
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??
Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.
I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.
As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.
where can i wirte this codes i dont know , can anyone help me??? i have same problem
i can not connect device also in adb mode pc didnt accept the drivers
y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag
y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file
berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.
Hello, I'm trying to pull files from my Samsung Galaxy tab 2 10.1 while it's in Recovery Mode (I'm using Clockworkmod Recovery 6.0.1.0), with ADB. How do I do this?
I can't copy files when my tablet is booted normally because it restarts unpredictably if it sits in the lockscreen or homescreen long enough. The only time it can stay on for long periods of time is while it's in Recovery Mode, and only in Recovery Mode.
I'm running ADB via the Command Prompt and I need help pulling files off of my device while my device is in Recovery Mode. ADB recognizes my device when I type in 'adb devices', and labels it as 'xxxxxx... recovery'. I'm having trouble accessing the files within, and I'm a noob when it comes to using the right ADB commands.
I've tried typing in the command: 'adb pull /sdcard.../' and that command didn't work, telling me 'remote object not found'. Now I know for sure the path I'm using is the right one, because I was able to pull files using the path when the tablet's booted normally (but my tablet restarts halfway into the copying process when doing this, which I why I need to find a way to do this in Recovery Mode!). I figured that the device's internal sdcard storage probably isn't mounted, so I tried doing that in Recovery Mode via Mounts and Storage, and still, ADB couldn't access my device's internal storage, telling me once again 'remote object not found'.
Then I tried mounting my SD Card in ADB with the following command:
adb shell
~ # mount sdcard
It returns with:
mount: mounting /dev/null on /sdcard failed: no such device
I don't know what else to do ... the only way I can keep the device on long enough to copy ANYTHING is while it's in Recovery Mode, and the ADB commands I'm using aren't working. Someone halp!
I tried installing the latest CWM Recovery 6.0.4.5 (which should let me use ADB in recovery mode, yes?) for the Galaxy Tab 2, and it seems my device is in some kind of ... read only mode. I can't successfully install the .zip file in recovery, because when I reboot it still says, at the bottom of the screen, CWM Recovery 6.0.1.0.
I'm beginning to lose hope, here.