Never had experience in rooting phones and stuff like that. (totally noob on that)
So I asked a friend of mine to install a custom rom for me.
He installed ordroid on my htc one x +. But there were glitches happening so i asked him to repair my phone.
When he tried to repair it he just deleted the rom and somehow the recovery manager too.(don't know how or why)
Now I can only enter the bootloader. Searched in the google means to flash the recovery and the rom again but no success at all. Tried with the cmd using fastboot and adb.
Does anybody knows how to unbrick it? The methods that i found on the internet all used the recovery manager, that i can't use anymore.
Thanks for the help.
eijiiwasa said:
Never had experience in rooting phones and stuff like that. (totally noob on that)
So I asked a friend of mine to install a custom rom for me.
He installed ordroid on my htc one x +. But there were glitches happening so i asked him to repair my phone.
When he tried to repair it he just deleted the rom and somehow the recovery manager too.(don't know how or why)
Now I can only enter the bootloader. Searched in the google means to flash the recovery and the rom again but no success at all. Tried with the cmd using fastboot and adb.
Does anybody knows how to unbrick it? The methods that i found on the internet all used the recovery manager, that i can't use anymore.
Thanks for the help.
Click to expand...
Click to collapse
had succes in flashing again cwm recovery.
it appears that the problem is that i can't acess the internal sd card on my phone. I tried to flash a custom rom using fastboot, it gives me this message.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
(I tried flashing a custom rom because I had no succes finding a ruu in zip format.)
So I'm stuck here. Does anyone know if I only need the ruu and flash it with fastboot? Or I'm missing a step?
Related
Hi, i'm new to this forum and i need help to fix my phone. I tried to mod my phone and I end up brinking it (I think) and here is what I did:
1- Unlock my bootloader. Successfully
2-Flash TWRP recovery image. Successfully
3-Rooted with Android_Revolution_HD_Root_and_BusyBox. Successfully
4-Here is where everything started... I tried to flash a rom (Bulletproof-m7-3.2) and everything went wrong and please do not ask what because i do not know :crying:
now I do not have no OS and my internal storage is not working or missing or it being wipe off I do not know. I can access bootloader and TWRP recovery image but i can't install another rom because of the problem with the storage that do not let me copy files into it. Well hopefully somebody could help me with this and here is a picture from the bootloader.
Can you boot into your twrp recovery? You can always install the rom through side load. Some one correct me if I'm wrong with that because I'm not very experienced with that but I'll look around for a thread for it.
However I use a method I feel is very simple, but you just need a otg usb adapter. Put your custom rom zip on a flash drive and plug it in the otg before booting into recovery. Make sure you have the latest twrp too (2.6.0.0). The n you can install from external SD.
Again though, I think you can install from a side load method or adb.
Sent from my HTC One using xda app-developers app
Jmarv said:
Can you boot into your twrp recovery? You can always install the rom through side load. Some one correct me if I'm wrong with that because I'm not very experienced with that but I'll look around for a thread for it.
However I use a method I feel is very simple, but you just need a otg usb adapter. Put your custom rom zip on a flash drive and plug it in the otg before booting into recovery. Make sure you have the latest twrp too (2.6.0.0). The n you can install from external SD.
Again though, I think you can install from a side load method or adb.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
ADB Sideload and ADB Push should both work with that recovery. I have issues with my Asus Windows 8 machine, even on the Ubuntu side, but the old faithful wife keeps a Gateway POS around with Windows 7 on it. I've used both commands successfully in Windows 7 every time.
Humbly Sent from my HTC One running Stock+GE UI
ajbanks said:
Hi, i'm new to this forum and i need help to fix my phone. I tried to mod my phone and I end up brinking it (I think) and here is what I did:
1- Unlock my bootloader. Successfully
2-Flash TWRP recovery image. Successfully
3-Rooted with Android_Revolution_HD_Root_and_BusyBox. Successfully
4-Here is where everything started... I tried to flash a rom (Bulletproof-m7-3.2) and everything went wrong and please do not ask what because i do not know :crying:
now I do not have no OS and my internal storage is not working or missing or it being wipe off I do not know. I can access bootloader and TWRP recovery image but i can't install another rom because of the problem with the storage that do not let me copy files into it. Well hopefully somebody could help me with this and here is a picture from the bootloader.
Click to expand...
Click to collapse
Bulletproof-m7-3.2 = kernel, just to clarify.
Sounds like you have to sideload a rom on there
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas
Hi! I've managed to brick my device (d610ar) badly, i think
the device doesn't boot normally (message "Secure booting error! Cause: boot certification verify.", and i am stuck there), can't charge it with the wall charger, and the only thing that works is download mode; but flashing a kdz with LG FlashTool (the way i went back to stock a few times) says flashing and at 2% (or 3% sometimes) it says that doesn't find the device, that i have pull out the battery to reconnect my device again and when i do that it does the same thing on a loop, asking to do it again later..
the funny thing is that it appears on device manager on windows, on com port 11 for example, but the FlashTool doesn't recognize it..
so, i can't flash any kdz and doesn't boot.. i've read around here in xda to enter fastboot to fix it, but.. can this device enter fastboot? i couldn't do it, tried adb too and couldn't make the device visible..
i, before this happened, had multirom installed, rebooted to recovery and deleted secondary roms to install in primary rom cm12.1.. there started to happen strange things when rebooted normally to configure it..
after a while trying to boot found around here in xda too that i could enter twrp recovery via hardware keys to reinstall again, so got into it and installed a flashable zip to come back to stock KitKat directly, that have worked for me before..
after that rebooted and i can't do anything else than download mode..
i kinda figured that the problem must be that multirom injected the boot sector after installing the stock flashable zip, and when i did that restored the stock aboot and abootb (these, modified carefully, allowed us to unlock bootloader and flash recoveries, etc, etc.. ; by the way, many thanks to the devs that discovered it and made the guides!)..
now i have read the instructions for flash via fastboot the stock boot.img and so pass the security verification, but i can't enter it..
so, what do you think that could be the next step? or is it really hard bricked and i should forget about it? i'm really hoping to recover it but i don't know what else to do..
sorry for the bad english, not my primary language
thanks for reading and i am hoping to hear some suggestions!
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Thank you very much!
numpea said:
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Click to expand...
Click to collapse
Thank you very much! You made me realize why wasn't working..
Because of you, i started to search threads related with the "flashtool stuck at 2%" and one of the things to look at was a txt file to see what was the problem.. there i found out that the lg FlashTool recognized my device as LGD618..
That's when i realized that i must've messed up when i flashed a lollipop flashable zip for the D618(a while ago), "converting" my cellphone on that model.. so when i connected on download mode and put the LGD610 kdz the comparison of cellphone model and binary model didn't match..
Solution was to flash LGD618 kdz, boot up normally, install towelroot, install supersu, edit a line on build.prop
from persist.multisim.config=dsds to persist.multisim.config=none
rebooted and that's it.. everything works perfectly now! i won't be doing stuff to it for a while
probably will stay stock like that, because now i will be using an OnePlus One in a few days and the G2 mini will be used by my mother, i think..
Thanks again! You saved my device for being bricked forever
i glad i could helped you :good:
I tried installing kitkat having installed lollipop and did not work, also I tried installing lollipop and nothing. Well I think this update lollipop are adding some kind of lock to disallow downgrade or upgrade by KDZ. I try other methods, unlocking bootloader, and install a aboot.img, bricked my phone. I recommend that you do not attempt to unlock the bootloader and install any system image that is not official, or may end up with a dead device.
Hi
I have Coolpad E501 EU (other names: Modena, Y76, Sky). It's dual sim, stock android 5.1, rooted, stock recovery.
After last mini update (9,2 MB) coolpad logo is showing and then it goes only to recovery. Phone was rooted using KingRoot app, and then applied update so I bet it was a mistake to do so.
I have second one same Coolpad phone - working, rooted, stock android, stock recovery. So it might help in restoring bricked one.
I searched almost everywhere on the internet looking for stock roms, recovery or something that I can flash.
I tried using YGDP tool with 4.4 official rom that I found but no luck. I get the message "Bootloader is old" in logs.
Tried to do backup with nandroid of working phone but it's making backup for custom recovery (cwm - .tar or twrp - .wim). My phone doesn't have one.
Recovery has an option to apply update from zip. Last update that messed up is here:
ota.coolyun.com/ota/Android/Coolpad%20E501_EU/P0/5.1.222.51.P0.151216.Y76_U00_5.1.222.61.P0.160510.Y76_U00/update_1464055522221.zip
I dont care about data., only working system.
Anyway I appreciate some help how to bite that, any ideas how to revive that phone. I was trying to do a system.img backup of /system partition in working phone, but no luck, partition is in ext4. I thought I can restore that using adb.
I will answer any questions if something I wrote is not clear. I'm not afraid of adb, flashed many phones, so I'm not looking for step by step tutorial, only to someone point me in right direction to solve this problem
Thanks for any help.
hey i have the same proble do you find any solution???
billtrz said:
hey i have the same proble do you find any solution???
Click to expand...
Click to collapse
No
I found some custom roms and some software on chinese site, but cant flash them and I think it's because bootloader isn't unlocked. I tried unlocking it but no luck (using android sdk).
can you give me backup you made,i have twrp recovery,if you want it i can give it to you but pleas help me with that backup
daithi2233 said:
can you give me backup you made,i have twrp recovery,if you want it i can give it to you but pleas help me with that backup
Click to expand...
Click to collapse
I have twrp for this phone, but I cant flash it. Every time I try to send a command in fastboot mode I get the message: "FAILED (remote: unknown command)". How did you flash it? Did your bootloader was unlocked in developer settings? Mine wasn't so I think I'm screwed.
Backup I have is with my personal data.
MaX2oo said:
I have twrp for this phone, but I cant flash it. Every time I try to send a command in fastboot mode I get the message: "FAILED (remote: unknown command)". How did you flash it? Did your bootloader was unlocked in developer settings? Mine wasn't so I think I'm screwed.
Backup I have is with my personal data.
Click to expand...
Click to collapse
then you shuld get your phone in official service,i send my and they said they are going to fix it,and i installed twrp whyle my phone worked with flashify i think
Hello ppl!
Is yours problems solved? I have soft bricked Coolpad Modena E501_EU and can't find solution.
Searching everywhere on internet, not find nothing about that phone: kernels, drivers, firmwares etc., like "ghost phone". Firmware version 4.4 is for E501-Y76-Sky but not for EU model and cannot be flashed. I need stock 5.1.222.........Y76_U00 and if can someone make backup and upload somewhere he helped me a lot.
Hi, I need help with my phone, I accidentally changed the permissions (using ROM Toolbox Lite) from the system folder making the phone crash shortly after. Now it shows the Alcatel logo and shuts off and back on in recovery mode.
I'm new with adb and CWM/TWRP stuff, but I can't find the device using adb (I installed the usb drivers correctly) , it only finds on sideload and even then I get "error: closed"...and with CWM/TWRP I can't use sideload because:
"You need adb 1.0.32 or newer to sideload to this devices" (and I used 1.0.36)
And with zip file (CWM) method I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted"
Please help, I can't find the stock rom for this phone
Did you find a solution? HAve a Bootloop too
Prestnaut said:
Did you find a solution? HAve a Bootloop too
Click to expand...
Click to collapse
Nope unfortunately
Any news ?
HAve a Bootloop too , after trying to unroot with kingo .
Need stock boot.img or recovery.img in order to build custom rom from source
VTRF8FF.TMP said:
Hi, I need help with my phone, I accidentally changed the permissions (using ROM Toolbox Lite) from the system folder making the phone crash shortly after. Now it shows the Alcatel logo and shuts off and back on in recovery mode.
I'm new with adb and CWM/TWRP stuff, but I can't find the device using adb (I installed the usb drivers correctly) , it only finds on sideload and even then I get "error: closed"...and with CWM/TWRP I can't use sideload because:
"You need adb 1.0.32 or newer to sideload to this devices" (and I used 1.0.36)
And with zip file (CWM) method I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted"
Please help, I can't find the stock rom for this phone
Click to expand...
Click to collapse
Hi, My 6044d also in boot loop, not rooted so I can't get stock boot.img or recovery.img in order to compile CWM and CM from source for this particular phone. Please someone post it and of course, when compiled I'll post back de results for all of us that need a custom ROM for this phone. It's crazy that this phone is not so popular and the common custom roms don't have one for it out of the box, that's why I decided to compile it myself, but I can't get my boot.img or recovery.img to configure build environment for this especific phone.
Thanks in advance!
miuserdexda said:
Hi, My 6044d also in boot loop, not rooted so I can't get stock boot.img or recovery.img in order to compile CWM and CM from source for this particular phone. Please someone post it and of course, when compiled I'll post back de results for all of us that need a custom ROM for this phone. It's crazy that this phone is not so popular and the common custom roms don't have one for it out of the box, that's why I decided to compile it myself, but I can't get my boot.img or recovery.img to configure build environment for this especific phone.
Thanks in advance!
Click to expand...
Click to collapse
Hey, sorry for taking so long to answer, i actually got 2 mega.co.nz links for this, another user gave them to me ^^
https://mega.nz/#F!XAkUDajB!EaYNGGsABPapaVFkeGNqTw
and
https://mega.nz/#!Ncx2VASY!gfxVbnQj9HK9WUGiidKY83pJZA7ToTQu5RFDfu2miWE
I found your other post too, and given that im a noob i tried to reply there, then i was trying to private message you (failed cause im not smart xD) and now im here :3
Tell me if something goes wrong, i didnt check this myself cause i sent my phone to repair, it was so broken they didnt knew it was rooted xD
Best of Luck ^^
And yeah, this phone is not popular at all, not even Alcatel cares, i emailed them to see if they were gonna release some updates, didnt even got a reply until now
But well, im gonna check out what youre doing, sowwie im a copycat xD
Good luck again ^^
I'm a little bit late but if you still need or someone else needs it just let me know as I have Carliv Touch and stuck recovery for this device.
Little late as well, but do you still have that recovery? i picked up my phone again and i wanna mess with it