Related
i cant boot my huawei u8180 into recovery
i rooted it by super one click
when i tried to flash recovery with rom manager premium it restarts then freeze in boot screen
tried to reset my phone from settings ,privacy it also reboot but freeze on boot
i dont know wt to do
PLZ HELP ME WITH THIS ISSUE
plz any one tell me anything i can do with this problem
i cant even reset my phone
plz reply
thanks guys , i solved my problem alone ,, and insalled cyanogenmod 7.2
everything is ok now
how do you solved your problem with huawei u8180? i have the same isue.
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Norpan70 said:
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Click to expand...
Click to collapse
So you could only boot into CWM by pressing power+volume+search? The regular way (power+volume) would lock up like it does to me, is that it?
Anyway I tried your key combination and it still freezes...
Codeman666 said:
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Click to expand...
Click to collapse
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Maeur1 said:
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Click to expand...
Click to collapse
I already flashed about 5 times and still freezes
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
bk109 said:
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
Click to expand...
Click to collapse
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Codeman666 said:
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Click to expand...
Click to collapse
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
bk109 said:
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
Click to expand...
Click to collapse
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Codeman666 said:
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Click to expand...
Click to collapse
Nothing specific -you just have to reboot in fastboot mode (just restart the phone while pressing Power and Volume Down. Windows should chirp and install the drivers automagically - afterwards just use that command discussed earlier and it should flash your recovery without any additional prompts (it should only print out a confirmation of a successful flash) and you should have the CWM ready to go
Edit: I put my device into fastboot mode on a clean Windows install (a Win8 Consumer Preview) and it did autodetect and install the relevant driver without restarting itself
No luck... Now it's driver issues
When booting the phone with either the vol up or down pressed and pluging in the USB my PC isn't recognizing the driver, I used both drivers you sent me.
Initially it's detected as Android 1.0 device, upon fetching the drivers it gets named "Android Sooner Single ADB Interface".
As I refresh device manager it goes back to Android 1.0 with an exclamation mark.
I think it's a driver signature issue, I'll try again in a couple of hours in a different PC
edit:in debug mode I have no driver issues and I can even detect my phone with ADB
Finally!
Tried it in another computer, auto downloaded some ASUS adb driver and installed fine.
Flashed latest CWM recovery with fastboot and now I'm able to boot into CWM!
Thank you so much for your help!
Sry for bumping.
So, i had the same trouble with the drivers. But i just downloaded HiSuite directly from the Huawei Site and these fix my problem with drivers to use adb without troubles . Hope this help someone.
BTW, Thanks bk109!
It did helped me thx man
Sent from my U8180 using xda app-developers app
I have a Vibrant T959. I just flashed from the latest official Cyanogenmod (android 4.2), to the latest unofficial cyanogenmod (Android 4.4.4).
However the phone is crashing in the setup process. I need to get back into clockworkmod, however I have tried the hold vol+, vol-, and power technique tons of times, and it does not work. I had trouble with that method before but would always just use rom manager to reboot to recovery, but needless to say, can't do that this time.
I'm currently attempting to use the ADB to reboot to recovery (which I've never used). I installed the latest JRE, and downloaded ADB, however currently I am unable to get the drivers for my phone. I understand I'm supposed to launch SDK manager to download them, however SDK manager does nothing, just pops up an empty command window for a split second and quits. Did some searching to see if I can download the ADB drivers seperate, but just found many dead, or untrustworthy looking links.
Been reading for hours, but i'm stumped now. All I need to do is just get back to clockworkmod recovery. Is there any way to do so?
Well just an update, by sheer luck I found a roundabout way to get back into recovery. Apparently from all the web searching lots of people are having the same problem with the 3 button combo not working. Supposedly it might be hardware locked.
Here is what worked for me.
Hold volume down and power, and after a couple seconds plug in a usb cord (other end was attached to pc, but no software or anything running)
Keep holding those 2 buttons for about 30 seconds, you'll see the battery icon flash a number of times, along with a little round loading cursor type thing which will also be flashing.
After about 30 seconds, release the power button but keep holding the volume down button for awhile.
After about 10 seconds, clockworkmod recovery pops right up.
Tags (for anyone else who may have this problem: Samsung vibrant T959 how to enter recovery. recovery fix. recovery not working. can't get to clockworkmod.
Try this!
servohead said:
I have a Vibrant T959. I just flashed from the latest official Cyanogenmod (android 4.2), to the latest unofficial cyanogenmod (Android 4.4.4).
However the phone is crashing in the setup process. I need to get back into clockworkmod, however I have tried the hold vol+, vol-, and power technique tons of times, and it does not work. I had trouble with that method before but would always just use rom manager to reboot to recovery, but needless to say, can't do that this time.
I'm currently attempting to use the ADB to reboot to recovery (which I've never used). I installed the latest JRE, and downloaded ADB, however currently I am unable to get the drivers for my phone. I understand I'm supposed to launch SDK manager to download them, however SDK manager does nothing, just pops up an empty command window for a split second and quits. Did some searching to see if I can download the ADB drivers seperate, but just found many dead, or untrustworthy looking links.
Been reading for hours, but i'm stumped now. All I need to do is just get back to clockworkmod recovery. Is there any way to do so?
Click to expand...
Click to collapse
ADB will work. Use the process given below and let me know if it works
1. Install stand alone SDK tools from here, they should work. (h ttp://dl .google.com/android/ins taller_r23-windows.ex e)(Delete all spaces in between.)
2.Note the folder where you have installed SDK tools.
3. Move all the ADB driver files ( Probably 2 .exe and 2 .dll files, or just copy all the files from the ADB driver folder in which you installed the ADB drivers ) to the SDK tools folder.
4.Make sure all usb drivers for your phone have been installed. ( If not just google it, you will find them in the first or second link)
5. Connect your phone and make sure it is recognized by your PC.
6.Navigate to the SDK folder where you have also copied the ADB files. Hold down SHIFT and right click, Select Open Command Window Here.
7. Type adb devices .It should show you all the connected devices, mainly numbers. If not, the ADB drivers have not been installed correctly.
8. If Step 8 works, to reboot into recovery just type " adb reboot recovery " without quotes.
9. Your phone will reboot into recovery .
(If the steps above don't work, you will have to install the latest custom CWM recovery for your device and then boot into recovery from Step 5. And if you get errors while flashing the rom or the custom recovery then you may have to check if signature verification toggle is enabled and disabled,it SHOULD be disabled.And then repeat the flashing process.)
Hope this works . Happy Flashing!:good:
Glad to know it works for you, for people who can't gain access to recovery any other way, ^ This is the way
Hello. I just got a HTC ONE X+ yesterday as my first smart phone, iv been using a basic nokia for around 20years lol I choose the HTC mainly because I saw a review of one using the Viper+ rom and love to customise my computers so thought this was right up my street.
I sat down today watched a couple of youtube videos & read a few tutorials, I unlocked the phone through the cmd and did the reset, all went smoothly as far as i was aware, I then went into settings and there was no developers options to select, I dumped the rom onto the storage, and went into the fastboot again since im following a step by step guide, I did the backup, wiped Wipe Cache, Dalvik, then when I went to Factory Reset it said failed, I thought ok ill try again after system, did that went back to FR again said failed. hhmm ok, went ahead with installing Viper and it started installing and said fail. so I went to reboot but told me their is no OP any more, so I tried to do a restore but it shows an empty folder, so now it only boots into the white HTC logo screen and sits there. I can get into the fastboot menu still, but when connected to a laptop it doesn't show up as a device so I cant view any folders or anything.
does anyone know where it went wrong and a way to correct this? it would be a big help to me, thank you
-Marc
you didn't say what recovery you got I suggest you to install TWRP 2.7.1.0 from here:
http://techerrata.com/file/twrp2/enrc2b/openrecovery-twrp-2.7.1.0-enrc2b.img
when you download that .img file install this toolkit, that you will download from here:
https://mega.co.nz/#!ZExEEBJL!jKoitltieeOIb8JV-cjqw9i4ldV1yXFUAf-q1W8-UUE
It's easy very easy to install you have option to install "Your own recovery" select that and press flash and select your .img that you download up, it will say in cmd 2 times Okay.
But before you flash, when you unzip this toolkit from .rar put it in "C:\" not in "C:\something\something & other things" becouse toolkit won't found .img.
After that you download 2.1.1 rom from here:
http://uploaded.net/file/tqmae0zd
and when you download the rom he will be named like ViperX_2.1.1 or something like that you rename it to just viperx.
When you did all that go into recovery wipe all, connect your phone to a PC go to device manager to portable devices and disable HTC One X+ if you don't do that adb won't recognized the phone. Then in recovery go to Advacned - Adb sideloade press that button and on PC through toolkit in section Extras select first option adb sideload press run, and select viperx.zip rom in toolkit folder or in "C:\" where you put it. Sideload will begin counting to 100% when it finish, rom will run automatically, rest is easy just next next pick what you want.
P.S
Don't forget to install latest htc drivers, and latest drivers for usb to avoid some conflicts becouse when sideloading adb won't recognized sometimes, that happends.
Thanks for the reply, I would of liked to have given this ago but now the tool kit keeps saying enable USB debugging first, which I cant do....anyway to do this without the original OS installed?
First of all there is THANKS button in left corner under avatar, so you can click on it instead of saying Thanks.
Second you don't need usb debugging mode in recovery go into recovery wipe all like I write in my first reply, install drivers first for HTC and do everything like i told you up there.
AH **** I REALLY MESSED UP! I unlocked my bootloader then later on I wanted to try out a different version of CM so I went ahead and booted into my CWM touch and I never did replace that v6.bin yet so my touch screen is wonky still. I installed CM 10.2 by BobZhome and now I can't get back into CWM to cat the v6.bin file to fix the touch screen. I also don't have any gapps installed and when I plug in my phone to my computer it won't let me transfer files to the phone memory storage. I also don't have a SD card now because I lost it. I was able to use the fastboot trick to flash the cwm recovery but it still won't let me back into recovery.. I think because the internal memory is blank because of me installing cm 10.2.. I also tried enabling usb debugging mode on the phone with cm 10.2 so I could try to adb and get a shell but it won't work it keeps saying the device is offline... WHAT SHOULD I DO SOMEONE PLEASE HALP ME!!!
CygnusBlack said:
AH **** I REALLY MESSED UP! I unlocked my bootloader then later on I wanted to try out a different version of CM so I went ahead and booted into my CWM touch and I never did replace that v6.bin yet so my touch screen is wonky still. I installed CM 10.2 by BobZhome and now I can't get back into CWM to cat the v6.bin file to fix the touch screen. I also don't have any gapps installed and when I plug in my phone to my computer it won't let me transfer files to the phone memory storage. I also don't have a SD card now because I lost it. I was able to use the fastboot trick to flash the cwm recovery but it still won't let me back into recovery.. I think because the internal memory is blank because of me installing cm 10.2.. I also tried enabling usb debugging mode on the phone with cm 10.2 so I could try to adb and get a shell but it won't work it keeps saying the device is offline... WHAT SHOULD I DO SOMEONE PLEASE HALP ME!!!
Click to expand...
Click to collapse
I had never succeded in unlocking my P768, but everytime i messed up this bad with the phone, the only way to fix it was by reinstalling the software with LG Tool. I don't know if this "locks" the bootloader again, it shoudn't but at least you will have a phone by doing this. Not even adb is accessible in your case, complicated..
My advice is reflash stock rom via LGTool, then you install CM/CWM againwith the screen fixed
back at it again
Ok I just got off work again and I was messing around with it again. I am able to reboot into the touch recovery from CM 10.2 because I was able to enable the developer options and then enable reboot into recovery option from reboot menu. I tried enabling debugging mode but the computer will not recognize the device at all. I use to be able to use adb from CWM Recovery by changing the driver to adb in the device manager however now my device manager is not even showing adb as an option to install now! LOL! I was trying to use the terminal emulator in CM 10.2 but it's ****ing impossible to use with that wonky touch screen. I wrote a shell script and uploaded it to a SD card I got today and then I ran the terminal emulator and managed to do the su command and then I did cd into the external sd card and I tried to bash the script by doing ./a.sh
cat v6.bin > ../../../../../../sys/devices/virtual/input/lge_touch/firmware
then it told me permission denied even though I was SU! LMFAO!!!!!
I'm at my wits ****ing end with this thing I mean HOLY ****! I just can't be bothered with it anymore. I think I'll take it outside later and smash it to pieces.
unless someone knows of anything I can do?! Please don't say to restore original rom because for some reason the computer just won't recognize this ****ing thing.. even in S/W upgrade mode it doesn't install the driver!
CygnusBlack said:
Ok I just got off work again and I was messing around with it again. I am able to reboot into the touch recovery from CM 10.2 because I was able to enable the developer options and then enable reboot into recovery option from reboot menu. I tried enabling debugging mode but the computer will not recognize the device at all. I use to be able to use adb from CWM Recovery by changing the driver to adb in the device manager however now my device manager is not even showing adb as an option to install now! LOL! I was trying to use the terminal emulator in CM 10.2 but it's ****ing impossible to use with that wonky touch screen. I wrote a shell script and uploaded it to a SD card I got today and then I ran the terminal emulator and managed to do the su command and then I did cd into the external sd card and I tried to bash the script by doing ./a.sh
cat v6.bin > ../../../../../../sys/devices/virtual/input/lge_touch/firmware
then it told me permission denied even though I was SU! LMFAO!!!!!
I'm at my wits ****ing end with this thing I mean HOLY ****! I just can't be bothered with it anymore. I think I'll take it outside later and smash it to pieces.
unless someone knows of anything I can do?! Please don't say to restore original rom because for some reason the computer just won't recognize this ****ing thing.. even in S/W upgrade mode it doesn't install the driver!
Click to expand...
Click to collapse
cant you fastboot recovery and do it that way?
Cobra11Murderer said:
cant you fastboot recovery and do it that way?
Click to expand...
Click to collapse
I already used the fastboot trick to flash recovery. I flashed the CWM touch.img then in cyanogenmod i can make it reboot into cwm recovery. But the thing is now my computer will not recognize the drivers for this device so I can't get adb to work with it. ADB will also not work in cyanogenmod for me because of the drivers not being recognized. ADB doesn't even show up in my device manager in windows when I tried to force it to be recognized as an adb interface. Now I think I need adb to work in CWM recovery because that's the only way I can cat the v6.bin file to fix the wonky touch screen. I can't use the terminal emulator to cat the bin file while within cyanogenmod because it's being used while in cyanogenmod that's why I got a permission denied result when I tried to run the command.
I also don't have a backup of my rom or I would have already restored backup from cwm to get the computer to recognize the drivers and then I would have reinstalled the original rom/firmware with lg flash tool.
It won't even let me restore the rom/firmware while in S/W upgrade mode because the lg tool won't recognize the device!
The only way I see out of this now is to get someone here to make me a CWM backup of their europe open rom so then I can download your backup put it on my sd card and restore it from there.. then drivers will recognize and I can flash back to stock rom with lg tool then reroot, rerecovery install and then install cyanogenmod 11 kitkat.
So if someone could do that for me I would be eternally grateful.
FIXED IT!!!
Nevermind. I was able to find a flashable zip that fixes the touch screen issue. Thank God I found that and was able to get a new SD Card otherwise I wouldn't have been able to flash that touch screen fix from the CWM Recovery! Woo! Now I can complete my other guide so no one else comes across these problems!
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"