I can't log to the phone, it is stopped to the boot screen, whitout animation, and the fastboot/adb don't go.
I think I've deleted the internal memory/partition, ex: the folder /storage/ ecc. doesn't exist.
I can only reboot and go in fastboot mode, but the pc doesn't recognize it.
I've tried to reinstall the drivers but it didn't work...
someone know how to do :crying: ?
Related
I accidentally erased all data using recovery. Now I only have access to fastboot and recovery mode. Systems indicate i do not have any OS installed. I can't seem to hook up the phone to pc so that i can transfer the .zip file so that i can flash. I know there is a way to fastboot flash a rom but the instuctions provided is not working somehow. Phone is just stuck on white window. If someone could give me a hand I would appreciated.
i got it.
ADB Push file.zip /sdcard/
those of you who are stupid like me and deleted all the data on the phone. LOL.
Well, long story short my friend royally screwed up his phone.
He screwed up the kernel and even the Recovery. Don't ask how.
We even connected the phone and ADB didn't work on bootloader. But after we went into fastboot and tried a restart it worked. So.. we used fastboot to restore the phone.
Notes before you start: Use command prompt and cd to the directory for your sdk tools. In my case, I simply used the 'data' folder for the Toolkit that was released here that had the sdk tools like adb.exe and fastboot.exe . MAKE SURE you copy the associated recovery zips and ROM zips to the very same folder to prevent complications and for the commands to work like a charm. Finally, uninstall the drivers for your phone and reinstall them (if you need to only, as we had connection issues.. yep he royally screwed up).
Boot into bootloader then select fastboot and hit the power button. Keep it on the fastboot screen. Now you can proceed.
Here is what I did:
fastboot erase cache
fastboot flash recovery recovery.zip *rename your recovery zip to 'recovery.zip' and make sure it's in the same folder as the sdk tools*
You can now then boot into recovery and write the ROM or even use fastboot to write it with the following:
fastboot flash zip rom.zip *once again, rename your ROM zip to rom.zip*
I only put this out there to help those who screwed up their recovery and can't even get the Toolkit to execute commands using ADB.
Good luck!
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
lopuandroid said:
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
Click to expand...
Click to collapse
Glad it worked. Yeah, for some reason my friend's computer was being really fussy. It wouldn't detect the phone or anything, and ADB was rendered useless. We reinstalled the drivers so many times.. And used 2 different laptops.. Thank God fastboot worked. Hopefully this helps anyone else in the same **** zone. I know the heart sinking feel when your Recovery won't work and you only get the bootloader to work..
Hey guys,
I am in a bit of trouble here ..
So last night , I unlocked the bootloader and rooted my HTC One .. Also , I installed TWRP on my phone .. Everything went fine , so I tried to install a few MODs .. The phone wouldn't start so I booted to recovery and tried to factory reset , but by mistake I deleted the system folder. So now, whenever I try to boot up , it says no OS installed and gets stuck on HTC screen.
I read all night on how to solve this, in the process, I also installed ADB on my computer, and finally got it running too.
I found these two guides while searching the internet and I tried them both but to no avail:
http://androidforums.com/international-tegra-3-one-x-all-things-root/549962-usb-mount-recovery.html
http://forum.xda-developers.com/showthread.php?t=2038366&page=5
Only when I boot up to recovery, the computer recognizes my phone and adb lists it.
ADB Sideload through TWRP doesn't work , says *cannot read sideload*.
Also, when I try to execute the command "adb shell" with sideload , it says "error: closed".
If I just put my phone in recovery, then it says phone found in recovery but then I can't mount my internal storage.
I have attached the screenshots to everything. Any suggestions , other than taking it to HTC as my warranty is now void?
Any help would be appreciated. Just need to push the ROM to my internal storage.
nevermind , i found the solution here :
http://forum.xda-developers.com/showthread.php?t=2325853
*starts breathing*
Hi,
I am really desperate! I turned on my rooted Asus MeMO Pad 7 ME176CX after several months of no use, but apps/services won't load (loads of error messages, all apps/services stopped etc.) like it was obsolete or screwed up. So I unrooted it and the issue got worse!
There is a Asus demo app in the notification bar that disables WIFI and software reset and says to plug in the power adapter (no difference, it won't go away).
1) I copied the necessary files to my memory card (to get rid of the Asus demo app as per other threads) but once I insert the memory card, even though it is recognized, it says no files present.
2) I did a hard reset with Vol - (or +, tried both) and Power but nothing happens (no recovery screen, it just stays black).
3) I removed the battery & waited 10 mins, no difference.
4) I formatted a card to FAT32 and copied the cleardata.zip unzipped files from Asus then rebooted pressing just Power but it just reboots normally like the card is not inserted.
Now basically the tablet shows a few apps (Calendar, Gallery etc.) and nothing else.
I cannot connect to wifi, bluetooth does not work, the memory card says no files present, vol + power does not work, cleardata trick did not work, I cannot send it back under warranty (ex-rooted) ... what else can I do??????
Many thanks!
Reboot into Droidboot (Volume Down + Power IIRC, could be up), boot the Temporary TWRP (http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096), flash ROM
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
boredfish said:
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
Click to expand...
Click to collapse
Well, theres quite a lot of options do recover your tablet, before doing anyhing, if you have access to adb, then you should do: download .17 rom and extract it, after extracting go to META-INF\com\google\android\updater-script and open it with notepad, and remove the first 2 lines, then save, and make the zip file (rename it to update.zip {careful not to make the file "update.zip.zip"}), then put the zip file in adb folder (for me its C:\\adb) and do adb push update.zip /sdcard/ (make sure adb is working) after it finishes pushing, go to bootloader (if not there already) and run temp recovery (twrp or cwm), and then install the zip, then clear dalvik and cache, and reboot, if first reboot doesnt work, reboot again, if it still doesnt work, install update.zip again. Hope i helped, if u have any questions tell me :3
=====
edit
=====
if you really cant get out of recovery theres still a way of fixing your tablet (same problem happend to me today and its fixed), if you already did all the steps above on the download .17 and extracting and changing the file of updater script then its already almost done, to access the bootloader you need to shutdown your tablet, press Power, Vol+ and Vol- at same time, it will go to fastboot, copy the file "droidboot.img" from the update.zip and place it in the adb folder (for me its c:\\adb), then do "fastboot boot droidboot.img" and it should download the img to the tab and boot to droidboot (you need to do this a few times, because 5/1 only 1 goes to bootloader), after booting to droidboot you can easily recover from there, on bootloader you have adb access, which means you can push the update.zip to the tablet (with update.zip in adb folder already, do on cmd, "adb push update.zip /sdcard/") after pushing go to temp recovery and install the update.zip normally after installing. format cache and dalvik, and reboot, if its stuck on logo, shutdown and reboot, if still doesnt work install the update once more by turning your device off and go to bootloader normally, (it works now, because it has the software now, (to enter bootloader press press power + vol-), and load temp recovery and reinstall). i hope i helped
Hello guys I have a real problem with my phone right now.
So I just follow this guide but get stuck on 'fastboot devices'.My pc detected the adb on command prompt but not on the fastboot.SOLVED,i just turn off windows driver signature enforcement and then the command prompt detected my phone.
Afterward I install my recovery succesfully even with some difficulties. Then after boot up my recovery & allow the modification my pc detected my phone but when open there are nothing in it.When I click the storage on MTP my device seem does'nt have any space just showing 0MB on Internal Memory. So I cannot flash the supersu nor the dm verity thus I cannot boot my device.The fastboot is still working and I have already tried this page twrp and official twrp but no luck. I also tried disable driver signature,try click on read-only on first boot twrp still no luck. I don't use adb and fastboot because I don't know how to use it.( You could guide me)
P/S: If you want any log please tell me. Right now I don't care anymore even with stock rom. Some one help me.
Try to wipe everything on twrp, data and internal storage included ... Maybe the data partitions is corrupt.
After wipe. Reboot back to twrp and connect the device to computer , you should see an empty drive from computer, but with correct size (make sure you use the latest TWRP by blu_spark)
theduke7 said:
Try to wipe everything on twrp, data and internal storage included ... Maybe the data partitions is corrupt.
After wipe. Reboot back to twrp and connect the device to computer , you should see an empty drive from computer, but with correct size (make sure you use the latest TWRP by blu_spark)
Click to expand...
Click to collapse
I did that and my phone turn on on white notification light.
Skrllux said:
I did that and my phone turn on on white notification light.
Click to expand...
Click to collapse
then you should start trying the following thread
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try method 2
Skrllux said:
I did that and my phone turn on on white notification light.
Click to expand...
Click to collapse
Are you on stock oxygen os and were you trying to unlock your bootloader and flash a custom recovery? I didn't get your post right.