Hello.
I have a problem with friend's phone.
It's HTC Desire Z (Vision). I S-OFFed how it's described on CM wiki. Latest radio.
About month ago I installed CM 10.1 AlterNdromadus.
It worked until yesterday, when it unfortunately installed some system update.
After that phone didn't booted anymore. In recovery it says, that it can't access system partition and formatting is not possible.
I tried connect the phone via fastboot in bootloader, but it also doesn't work. Under windows I have it as unknown device and when I tried manually install drivers from google, it says that they are not compatible with the HW (under ROM it worked before).
I tried also install stock RUU rom (extracted the zip and deleted H-BOOT, radio and recovery) from SD-card (PC10IMG.zip). But it also got frozen on system update.
Here you can see error from 4EXT recovery and CRC images from bootloader.
Any suggestions? :crying:
Thanks
Well, I guess I meant to keep this thread in the desire z q&a thread but this works
I wish we could know what kind of system update was flashed as it may be easier to fix this
There shouldn't have been any system update as there is no ota associated with that ROM, but we can try anyway
http://forum.xda-developers.com/showthread.php?t=2348266
Here you will find links to get you proper drivers, being your on windows try using a free program called USBDeviw, I have had to use this a lot to erase drivers and then manually install the proper ones (windows is terrible at this)
Or if you can dual boot Linux you may find life easier as once you get fastboot working you should be able to quick fix this.
Otherwise try out the aio wipe tool and or superwipe script that is linked in the guide I sent you
But really, try to get the drivers working and we should be good
Sent from my Nexus 4 using XDA Premium 4 mobile app
Tried both superwipes. Doesn't work :/
The problem with fastboot is, that windows totally doesn't recognize the device. So I'm not able to install any drivers (see attachment).
The reason why I posted it in this section is, that I found people with similar problem on other phones. But noting work to get it back...
Any recommendation for the linux?
I booted successfully SystemRescueCD. After a half hour I also went ADB but no devices were found...
The screenshot is blurry when looking at it from my phone but it looks like windows 8/8.1 which many have issues getting adb/fastboot to work right. Usually the fix involves using usb3.0 ports
Can you just dual boot a Linux distro? Ubuntu is a very simple one to work with and you will easily find guides how to get fastboot working on it, actually if you see the thread I linked you there is one on fastboot that walks you through the process
If you don't want to dual boot a live CD is fine, but you still need to get the adb/fastboot binaries installed and working from that disc
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yes, it's windows 8.1. I don't have USB3.0.
I have here also one really old desktop with windows 7, I will give it a try.
Otherwise last chance is the Ubuntu (I don't want to dualboot, so I will made live USB).
I downloaded from XDA two files - ADB and fastboot for Linux.
Downloading and installing adb from SDK from google doesn't look so easy as on windows...
Also should I use drivers from HTC sync or from google SDK?
Because through ROM it worked right with the google's drivers...
although this is not what you may want as an answer but why don't you copy a ROM to SD card n flash via recovery,, it'll regenerate system,, once it is regenerated,, you can connect to your PC and carry on to what you want.
Nope. It doesn't work. I tried it as first option.
I just forgot to write it here....
seems like you might have actual physical damage/bad sector on ur device.
this is what happens in hard drives, they can't be formatted, no read/write etc.
i don't know if there's any app that can help fix you this coz you can't connect to system/OS in first place to do so,
Best option seems like to dust off the warranty papers n get it to service center for repairs as it might need physical parts replacement.
I got working fastboot (not ADB) on Windows7.
When I tried fastboot format /system I got error "Uknown command".
When I tried fastboot erase /system I got error "No partition found"
Yes, it's probably problem with bad blocks...
The issue at hand depends on what this 'update' was as the ROM that was running on the phone at the time would not have had one which means something was flashed to it that shouldn't have been.
Being the phone had security flags removed (soff) a number of things that shouldn't be allowed to flash can be, so depending on what it was will determine how fixable it is
At this point the only way to fix it or at least dertimine if it is fixable is to get phone and PC to connect via fastboot and adb
So use the windows 7 or Linux, set it up with drivers found in xda wiki or write the android rules for Linux and work on this, its doubtful you can move forward until this is done
Sent from my Nexus 4 using XDA Premium 4 mobile app
As I wrote, I got Fastboot worked.
BTW isn't possible to acces ADB only from the ROM?
I tried to get it work without success. I tried HTC and google drivers...
Must have posted while I was posting and I missed that
Fastboot only works from bootloader and adb only works in os and recovery
The commands you were using isn't correct, I suggest you read again the two fastboot links from the link I sent you for clear instructions.
For right now I would grab the latest cwm, twrp or 4ext recovery (4ext still best for this phone)
Then
fastboot erase system -
fastboot erase recovery
fastboot erase boot
Then
fastboot flash recovery nameofrecovery.img
Then if all goes well grab a known stable ROM and flash it (along with gapps if needed) from new recovery
If things don't work as planned be sure to copy and paste all input/output from cmd
Sent from my Nexus 4 using XDA Premium 4 mobile app
Related
I have this old Galaxy SGH-T959, which I'd like to get on CM10.1. I started out with a phone facory reset (it's on 2.2) and then followed the instructions on the CM site: First I pushed CWMR using Heimdall, which worked ok (I can get into CWM recvovery), but after that the phone seems to be soft-bricked (hangs after the splash screen when doing a regular rebooot). No big deal I thought, since I just need to get a ROM on there. I went through some troubles with installing USB drivers (eventually, I installed Kies and the drivers that came with it made it show up properly in the device manager). Now I just wanted to push my ROM zip via adb. So "adb devices" (after adb kill-server, adb start-server) shows the phone as 'T959xxxxx recovery'. So far so good. But now when I issue a push command (or any other adb command like shell or remount), there is just a blinking cursor and nothing else happens. Any idea wha's the problem?
pipetman said:
I have this old Galaxy SGH-T959, which I'd like to get on CM10.1. I started out with a phone facory reset (it's on 2.2) and then followed the instructions on the CM site: First I pushed CWMR using Heimdall, which worked ok (I can get into CWM recvovery), but after that the phone seems to be soft-bricked (hangs after the splash screen when doing a regular rebooot). No big deal I thought, since I just need to get a ROM on there. I went through some troubles with installing USB drivers (eventually, I installed Kies and the drivers that came with it made it show up properly in the device manager). Now I just wanted to push my ROM zip via adb. So "adb devices" (after adb kill-server, adb start-server) shows the phone as 'T959xxxxx recovery'. So far so good. But now when I issue a push command (or any other adb command like shell or remount), there is just a blinking cursor and nothing else happens. Any idea wha's the problem?
Click to expand...
Click to collapse
try a pc they are a lot easier to work with with android.
If you are on a pc then try odin... I usually understood heimdall as a mac alternative to odin or just an alternative to odin, odin is made directly by samsung so its gotta be quality stuff. vibrants do have bad ports too, i have two of them and both wont connect to the computer anymore and one doesn't even charge so try putting the rom on an external microsd card and throwing it in it then flash that through recovery, but if you are going to jelly bean usually you install cm7 first then cm10.1... not sure what guide you are using, a link would be nice, maybe a problem could be found there. theres a thread about the whole cm7 read post 2 here http://forum.xda-developers.com/showthread.php?p=43706442#post43706442 haha thats me i had a similar problem
Thanks for the reply.
I am on a PC. The guide I was working off is here: [apparently as a newbie I'm not allowed to post links]
I tried ODIN to push the ROM, but ODIN accepts only tar files etc. and not the CM zip files (at least I didn't find any CM tar's). I also tried putting the ROM on the external sd card, but that was non-starter as well. CWMR would not find the external SD and any attempt to mount it failed.
Find tar versions. I'm not sure how to convert it but if you can't find one just ask and I'm sure somebody with some spare time will put one together for ya
Sent from my SPH-L300 using xda app-developers app
blu422 said:
Find tar versions. I'm not sure how to convert it but if you can't find one just ask and I'm sure somebody with some spare time will put one together for ya
Sent from my SPH-L300 using xda app-developers app
Click to expand...
Click to collapse
I found a tar for android 2.3 and managed to flash it via ODIN and get the phone back up and running (2.3 will do, since I need it only for one particular app to run and that required 2.3). Thanks for the help!
pipetman said:
I found a tar for android 2.3 and managed to flash it via ODIN and get the phone back up and running (2.3 will do, since I need it only for one particular app to run and that required 2.3). Thanks for the help!
Click to expand...
Click to collapse
Pipetman, I have the same exact issue now. Can you provide a link to the tar file and to ODIN. I am new to all this stuff.
Thank you
Hi, everyone. I wiped the internal storage on my htc one on accident while trying to wipe the dalvik cache on twrp. Now when I turn on my phone it gets stuck on the splash screen. I hold down the volume button when turning it on and it goes to hboot where I am able to navigate to fastboot and my twrp recovery. Besides those two things all data on my phone is completely gone the storage only has about 16 megabytes on it now. In the cmd prompt typing in adb comes up with device not found and adb device shows an empty list. Fastboot devices in cmd however dpes find my phone which is odd. Updating my drives doesn't work and the mtp driver can not install for some reason. So I can not use adb to push or sideload anything. I could use twrp to sideload something maybe if I could somehow get something onto my phone. RUU won't work because I never turned my s-off and since I am now at this stage I don't know of anyway I can turn my s-off. Could someone maybe tell me how I could get my adb to find my device(updating drivers doesn't work). Really any way to solve this would be appreciated I tried so many things. I've unlocked and relocked bootloader so many times for different things. Basically there is no os on my phone. I can not use adb to put a rom on my phone. I only have access to hboot fastboot usb and twrp recovery. Please links and some instructions would be very much appreciated. If you help me fix my phone I will ofcourse give you thanks on your reply and when I can I will donate money to you(not saying any time soon as I do not have a job and am currently looking but I will remember you for saving my phone and I am the type of person to return favors).
No need for thanks or money, but if your device supports otg cable you may be able to load a ROM on there, don't have a one so I can tell you if it does
True, without s-off or super cid you can't flash older versions of an os than you're currently on but that doesn't mean in the future there won't be an ruu that is newer, of course that won't help you now but its something at least (and another reason why s-off is key for any HTC phone)
But If otg doesn't work than you need to find something that will flash in bootloader (double check if there are any stock ROMs, try them all - at least look into them all) and as for adb see if you need to update binaries on your PC, open the SDK and try to update. Also try to uninstall first then reinstall drivers
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
.
demkantor said:
No need for thanks or money, but if your device supports otg cable you may be able to load a ROM on there, don't have a one so I can tell you if it does
True, without s-off or super cid you can't flash older versions of an os than you're currently on but that doesn't mean in the future there won't be an ruu that is newer, of course that won't help you now but its something at least (and another reason why s-off is key for any HTC phone)
But If otg doesn't work than you need to find something that will flash in bootloader (double check if there are any stock ROMs, try them all - at least look into them all) and as for adb see if you need to update binaries on your PC, open the SDK and try to update. Also try to uninstall first then reinstall drivers
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just got my adb to recognize my phone however it only recognizes it while in twrp recovery.
That's normal, it won't work in bootloader ever, just recovery and os
So your good now right? Just need to adb sideload and your off to the next ROM!
Seriously consider s-off though, I highly recommend it when possible
Happy flashing!
Sent from my Nexus 4 using XDA Premium 4 mobile app
.
demkantor said:
That's normal, it won't work in bootloader ever, just recovery and os
So your good now right? Just need to adb sideload and your off to the next ROM!
Seriously consider s-off though, I highly recommend it when possible
Happy flashing!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload wont work it says unable to mount data and unable to mount internal storage and unable to mount everything else it is supposed to mount
Sounds suspiciously like corrupt partitions, hopefully formating within recovery will fix this, may need to flash recovery again from fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hello everyone,
I have been searching in vain for a while now to find a solution to my problem and I fear that I may have done something daft to my phone.
I am using a HTC One X+ that was unlocked, s-off and rooted for about a year, i had TWRP and stock android 4.1.1. For ages I have been getting an update alert saying a software update is ready and i think it was some Vodafone update (1.17.161.7). Whenever i accepted and tried to install this it would obviously reboot into TWRP and then the update would fail. This was fine until last night when I decided to install it through TWRP, it said it failed again and i rebooted to find that WiFi wouldnt turn on, my phone was no longer rooted or s-off and that I get no signal. I tried to re-root it but command prompt on the computer or HTC Sync wouldnt recognise my device however it was appearing as HTC One X+ in My Computer and i could access the internal storage.
I restarted into recovery and managed to flash a new root using twrp and the root file using the unlockr.com - how to root the htc one x
Then thinking it was a ROM issue i downloaded and installed InsertCoin Evolution ONE X+ 5.0-6 Sense 5 Android 4.2.2.
This all went through ok however when i reboot from this install it just sticks at the HTC Quietly Brilliant screen. I wiped everything using twrp beforehand.
When i restart into bootloader, it says unlocked, S-On and HBOOT -1.30.0000
Not sure what else to do as now i have no ROM, i read that you have to partition the SD card for InsertCoin to work but the option to partition SD card isnt there in my TWRP (ver. 2.3.3.0)
Any help to even reset my phone back to basic stock everything would be amazing, i have a Titanium Backup of most of my stuff saved btw.
Thanks to anyone who can help.
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
EDIT - Now seen the instruction to flash the boot.img - what a fool i am. Now i need to get it recognised by USB again so i can transfer the zip file to it and go again.
maxwell689 said:
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
Click to expand...
Click to collapse
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Without a rom installed you're not able to acces the internal memory of your phone directly. You have to use "adb sideload" command to transfer a rom onto your phone. Look in the General and/or Q&A forum of this device, there are enough guides or topics on how to solve this "problem".
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Optimus said:
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Click to expand...
Click to collapse
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
maxwell689 said:
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
Click to expand...
Click to collapse
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Ghand0ur said:
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Click to expand...
Click to collapse
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
maxwell689 said:
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
Click to expand...
Click to collapse
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Lol.. Well, as i said try to run the Toolkit/cmd as administrator and try different usb ports.. It took me 5 minutes on windows 8 for the adb to properly read the device , had to try different usb ports, unplug , replug, and so on..
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Optimus said:
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
maxwell689 said:
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
Click to expand...
Click to collapse
Thats great news that all is well now..feel free to post.. and dont forget to press the Thanks button
HELP Please !
My htc explorer initially got stuck at the htc logo at boot and won't go any further.
I searched for solutions on xda and tried to install Cyanogenmod 10.2 on it. Now the device gets stuck at cyanogenmod boot animation (was going on until half -an-hour ! )
Next i searched some more, caught TWRP recovery on a glance. Tried installing it, but my Laptop ( Win8.1 x64 ) doesnt recognize the device whatsover, even after installing the adb drivers and HTC SYNC. !
Now i finally installed FLYROM v4 refined, and the phone is stuck at htc 'quietly brilliant' logo . !
PLEASE get me out of this misery ! I want my little buddy back in action
Please .. Anybody ?
Nobody to help ?
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Thanks, but no luck
pjohn23 said:
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Click to expand...
Click to collapse
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
DrSakethReddy said:
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
Click to expand...
Click to collapse
dont you have flashtools?
More INFO needed.
pjohn23 said:
dont you have flashtools?
Click to expand...
Click to collapse
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
DrSakethReddy said:
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
Click to expand...
Click to collapse
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Thank you very much, for your reply
I hit thanks button too
I'll get back to you soon as i perform the steps you've stated in a Win 7 PC.
sadly NO
pjohn23 said:
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
Click to expand...
Click to collapse
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
pjohn23 said:
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
Click to expand...
Click to collapse
Hey ! C'mon. Don't say u didn't help !
Providing a light to this thread for others to answer it too was the read deal you made !
Thanks again, bro
AWESOME !
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
Great ! I love getting things done easier with tools !
I'll give this a shot too, and then if this doesn't work, i'll head for the recovery.img flashing .
Thanks
Unsuccessful ! (error)
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Alas ! Error again
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
I've done the adb command method and failed, now i've even performed updating it with RUU, but i have this result :
ERROR 155: unkown error
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and update your phone.
DrSakethReddy said:
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Click to expand...
Click to collapse
I'm so sorry! I left out something in that command! It's:
fastboot flash boot boot.img
Sorry, poor proofreading skills.
As far as the 155 error, I think you also might need to do this in bootloader / fastboot mode (if the previous command doesn't get you going with the rom you are already on - it should):
fastboot oem lock
Then re-run RUU.
Sorry guys, for a very late reply.
I tried all the methods you said, with the new command too, but alas ! The device didn't get a life.
I'm gonna use it as a very costly paperweight now !
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.