Hello Everyone.
I need some help, I came from a good old HTC Diamond and have that one flashed så manny times as we change underwear
BUT now I can't flash the new Desire with Bootloader 0.80 and stock rom.
Think that I have tried various attempts of ways to get a new rom in the phone.
followed different links to flash the phone here in this forum
and other links to should do the work, WHAT AM I DOING WRONG????
have you used this guide?
http://forum.xda-developers.com/showthread.php?t=672770
From what I know you do not need to root your phone to flash a stock ROM. If your phone is branded then you need to make a GOLD CARD and flash the stock ROM http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
If I'm wrong, please correct me.
The phone is not branded or anythig, maybe I just have problems with loading the files into the phone?
More Details
What ROM are you trying to flash? What method are you using? What errors are you getting?
For example, I flashed mine with RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe http://forum.xda-developers.com/showthread.php?t=684259 just by executing the file.
I did the same thing and that is working fine, but now I want to try one of those custom rom, but I am not able to flash the phone?
Have you rooted your phone already?
If yes, you can use this guide to flash a new rom
http://forum.xda-developers.com/showpost.php?p=6364280&postcount=2
In the first post you said you were having problems installing a stock ROM. If you want to flash a custom ROM you have to ROOT first.
At least that is what I understood.
Do I get Chinese input if I flash this ROM? Thanks!
I think that I got it wrong, Just brough the phone and now I am starting to know it, but still I dont have a custom ROM in it, But working on that.
The problem that I think I have is to rooted the phone got Step1 right (I think) but when I am trying step2 it cant find the device? (go in recovry mode)
I think that step1 was going well I cant do it again, copyed rootedupdate to SD card and booted in recovery mode used the VOLUP+Power and have access to recoverymode, But now it says that rootedupdate.zip dosnt have a Signature verification fail?
maxermaxer said:
Do I get Chinese input if I flash this ROM? Thanks!
Click to expand...
Click to collapse
you need to search the forum and install chinese input after you have rooted
otto_di2 said:
I think that step1 was going well I cant do it again, copyed rootedupdate to SD card and booted in recovery mode used the VOLUP+Power and have access to recoverymode, But now it says that rootedupdate.zip dosnt have a Signature verification fail?
Click to expand...
Click to collapse
That would suggest you are not rooted, have you not rooted your phone first?
Related
Hi 2 all!
I just flashed my device with android 2.2
But how can I get back to stock rom (RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865)?
The update program does not recognize my phone?
thanks
If you have flashed 2.2 then you have obviously rooted. It is just a matter of finding the rom you want. Put it on your SD card, and then use rom manager to flash it.
What exactly is not recognised?
socktug said:
If you have flashed 2.2 then you have obviously rooted. It is just a matter of finding the rom you want. Put it on your SD card, and then use rom manager to flash it.
What exactly is not recognised?
Click to expand...
Click to collapse
...the htc rom update util does not recognice my handset...but I finally managed it. I had a backup and restored it with the rom manager.
How can I add the stock rom to the sd card. I looked at the files included in the stock rom (when it was extracted when entering setup) - do I need all files? Must I zip them??
cyron_at said:
...the htc rom update util does not recognice my handset...but I finally managed it. I had a backup and restored it with the rom manager.
How can I add the stock rom to the sd card. I looked at the files included in the stock rom (when it was extracted when entering setup) - do I need all files? Must I zip them??
Click to expand...
Click to collapse
Check the stickies. There's a thread full of stock ROMs (as .zips). Put it on your card, backup existing ROM, flash from zip (via ROM Manager or recovery).
cyron_at said:
Hi 2 all!
I just flashed my device with android 2.2
But how can I get back to stock rom (RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865)?
The update program does not recognize my phone?
thanks
Click to expand...
Click to collapse
whats wrong with 2.2? its geting better and better . now with apps2sd installed inside your rom. when i firstly root my phone(2.2) i really want to go back to stock.. and did not find any guide to do that. but when i used this 2.2 about few days i think its better than the previous one . internet browsing was fantastic . anyway if u find a way to install desire to stock pls share here ok. maybe can help others.
There's a complete tut here including how to unroot to stock rom, works fine.
forum.xda-developers.com/showthread.php?t=696189
junkiepilot said:
There's a complete tut here including how to unroot to stock rom, works fine.
forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
thanks for sharing
I know this is for another thread but ROM manager is a tad temperamental on my phone. Won't let me install clockwork and Won't boot into recovery. All other tasks are greyed out. I do have ROOT and I am running a debranded ROM on an Orange phone.
Will take a look at the link above
azrudin99 said:
whats wrong with 2.2? its geting better and better . now with apps2sd installed inside your rom. when i firstly root my phone(2.2) i really want to go back to stock.. and did not find any guide to do that. but when i used this 2.2 about few days i think its better than the previous one . internet browsing was fantastic . anyway if u find a way to install desire to stock pls share here ok. maybe can help others.
Click to expand...
Click to collapse
....how I got back to stock:
I had a backup og my current stock rom with the rom manager. Within the rom manager I restored it. Thats all.
PS: There is nothing wrong with 2.2, but I like 2.1 stock ;-)
I currently have bootloader .79.000 and can't flash cyanogen roms.i get an error saying i need .76.200. Is there a file i can download? I was able to download those roms before and now i can't.can someone please help.I don't know how I got .79.000 version.
gdiaz76 said:
I currently have bootloader .79.000 and can't flash cyanogen roms.i get an error saying i need .76.200. Is there a file i can download? I was able to download those roms before and now i can't.can someone please help.I don't know how I got .79.000 version.
Click to expand...
Click to collapse
have you tried rom manager from the market? It's the easiest way to download and install CM6 nightlies.
Yes that's wat I used and it tells me I need bootloader .76.200.i even downloaded the rom off of xda and went into recovery and tried to flash the rom.i get the same results.its weird bcuz i can flash any other rom.just not cyanogen.
gdiaz76 said:
Yes that's wat I used and it tells me I need bootloader .76.200.i even downloaded the rom off of xda and went into recovery and tried to flash the rom.i get the same results.its weird bcuz i can flash any other rom.just not cyanogen.
Click to expand...
Click to collapse
sorry - can't help you then. Sounds like it's specific to CM6, and I haven't used it in a while. Try posting your issue in the Unofficial Cyanogen Mod 6 Nightly KNOWN BUGS/FAQ thread in Q&A, maybe someone there can help you.
Somehow you lost NAND unlock. Follow Toast's part 2 of root method for NAND unlock. Essentially you need to flash the eng-PC36IMG.ZIP to give you the engineering hboot (76.2000).
Sent from my PC36100 using XDA App
I followed toast's method but it tells me main version older. I'm lost here.i deleted the mtd-eng.Ingram and put it bak on the sdcard but it keeps saying the same thing.please help.I'm rooted with simpleroot.
Have looked at whitslack's "How to Start Over" thread? I ran into this problem when I rooted and I remember that it came down to having the wrong PC36IMG.ZIP to flash the hboot. SteelH wrote a method too which might have a link to a better file. You're close. You just need the right zip file.
Sent from my PC36100 using XDA App
I tried the new simpleroot and I still get main version older!!!! I tried a few times and got the same results.does anybody know how to make this work so i can get bootloader to .76.2000????????????
I've been flashing ROMs on my One V for a while now. I've tried out the CM10 beta, CM9 beta, JMV4, Paranoid Android, most of them out there.
However, now they will not flash. Does anyone know why? I tried to go back to the CM9 ROM using the same file (I even re downloaded it) and it fails to flash.
I'm using TWRP 2.2 and have been. I even reflashed TWRP and reformated my SD. What went wrong?
because you are trying to flash cdma roms
cm10 is for cdma
ur device is primo u
soo u need to flash that only.. i mean the primo u roms
Sent from my HTC One V
I know the difference. I have PrimoC. I have Virgin Mobile in the US. I'm wondering why the ROMs that were working for me will no longer flash.
I'm not trying gsm ROMs for PrimoU
Alrighty. Lot of helpful people around here LOL
instead of being a sarcastic btard how about you expand on why they wont flash? errors? what?
That's exactly my question lol Why won't they flash? I flashed them and they worked fine. I went to flash to a different ROM and it says flash failed in red letters. I tried flashing a ROM that previously worked and it said flash failed. I know how to flash ROMs as I have been successful in the past with the same files. I ended up just flashing stock and unrooting. Do you think it's possible that it was bricked? As I"m not sure exactly what a bricked phone acts like because I've never had it happen.
jacobcummings said:
That's exactly my question lol Why won't they flash? I flashed them and they worked fine. I went to flash to a different ROM and it says flash failed in red letters. I tried flashing a ROM that previously worked and it said flash failed. I know how to flash ROMs as I have been successful in the past with the same files. I ended up just flashing stock and unrooting. Do you think it's possible that it was bricked? As I"m not sure exactly what a bricked phone acts like because I've never had it happen.
Click to expand...
Click to collapse
well cant answer about the issue but chill out ur phone not bricked...:silly::silly::silly::silly:
bricked looks as bricked sounds ur phone becomes dead and it remains nothing more than a piece of asooted plastics and metals!!
jacobcummings said:
That's exactly my question lol Why won't they flash? I flashed them and they worked fine. I went to flash to a different ROM and it says flash failed in red letters. I tried flashing a ROM that previously worked and it said flash failed. I know how to flash ROMs as I have been successful in the past with the same files. I ended up just flashing stock and unrooting. Do you think it's possible that it was bricked? As I"m not sure exactly what a bricked phone acts like because I've never had it happen.
Click to expand...
Click to collapse
Are you using the CDMA version of clockworkmod? That's the other issue sometimes faced.
No, I use TWRP instead of CWM. I never got the CWM to work right. TWRP has been great. I'm not sure what happened. I just relocked boot loader and went back to stock. I'll try everything again once there are things 100%.
Plus, it's hard for me to give up the Sense camera and weather widget! lol
Off topic ...
jacobcummings said:
No, I use TWRP instead of CWM. I never got the CWM to work right. TWRP has been great. I'm not sure what happened. I just relocked boot loader and went back to stock. I'll try everything again once there are things 100%.
Plus, it's hard for me to give up the Sense camera and weather widget! lol
Click to expand...
Click to collapse
Could you please send me TWRP, cause I also have problems with CWM and I can't download it, cause the link in the threat is dead. Maybe you have dropbox or something else to share it ...
What problems are you having with cwm? I'm not having any issues...
Sent from my One V using xda app-developers app
MasterTec said:
What problems are you having with cwm? I'm not having any issues...
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Herr you can see:
http://forum.xda-developers.com/showthread.php?p=30471406
Send from my HTC One V using xda app-developers app
Do you still need the recovery file? I didn't see this until now. I have it.
jacobcummings said:
Do you still need the recovery file? I didn't see this until now. I have it.
Click to expand...
Click to collapse
I got a new sdcard, now it works with TWRP and i think it would work with CWM also.
Thank you, no need at this moment.
help_rom
hey there;i am using the custom rom: my-onev-4fx_software number: 2.22.401.1
i wanted to install the official ruu; my first RUU was (asia_wwe_1.58.707.3)_ i have downloaded this rom;
i know that i cant install this now because of the lower image version; so i installed the stock recovery ( 1.58.707.3 ) and relocked bootloader;
then switched to bootloader and run ruu;
but when i tried to install the RUU, it gave me error 155; and when i saw my bootloader it was written:
the hboot is older
update fail
so what should i do?
mohammad0089 said:
hey there;i am using the custom rom: my-onev-4fx_software number: 2.22.401.1
i wanted to install the official ruu; my first RUU was (asia_wwe_1.58.707.3)_ i have downloaded this rom;
i know that i cant install this now because of the lower image version; so i installed the stock recovery ( 1.58.707.3 ) and relocked bootloader;
then switched to bootloader and run ruu;
but when i tried to install the RUU, it gave me error 155; and when i saw my bootloader it was written:
the hboot is older
update fail
so what should i do?
Click to expand...
Click to collapse
Ok, here's what I did when I went back to stock. Run that file that you downloaded for your area. After it's done running, open up a folder or internet explorer and type %temp% That file that you ran created a couple of temporary folders and inside one of those folders you'll see a zipped file that says ROM. Copy that ROM file and paste it on your desktop, open it up and take out the recovery image and boot image. Flash the stock recovery and boot image files and then relock your bootloader and then continue on with the first downloaded file you ran.
If you locked your bootloader before flashed the stock recovery and boot image I'm not sure what to do.
mohammad0089 said:
hey there;i am using the custom rom: my-onev-4fx_software number: 2.22.401.1
i wanted to install the official ruu; my first RUU was (asia_wwe_1.58.707.3)_ i have downloaded this rom;
i know that i cant install this now because of the lower image version; so i installed the stock recovery ( 1.58.707.3 ) and relocked bootloader;
then switched to bootloader and run ruu;
but when i tried to install the RUU, it gave me error 155; and when i saw my bootloader it was written:
the hboot is older
update fail
so what should i do?
Click to expand...
Click to collapse
Not sure whether you solved your problem or not.
If not.. use the latest official RUU - http://forum.xda-developers.com/showpost.php?p=30994089&postcount=121
J hope u have a copy of ur nandroid..... now just revert to stock...then try reflashing
Sent from my One V using xda app-developers app
cybervibin said:
J hope u have a copy of ur nandroid..... now just revert to stock...then try reflashing
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I'm all good now. I think the problem was my kernel was JB and I was trying to flash a ICS ROM. Not sure though because I just ended up starting completely over and I can flash anything now.
Good than...kiss kernels I recommend
Sent from my One V using xda app-developers app
Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.
Just flash the RUU, update OTA and reroot.
Alright, will do and I'll let you know how it goes. Thanks
Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.
MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!
dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.
Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !
That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?
I tried to flash my p6 to B512 ROM, and I had changed my recovery, duno what is my recovery version now, but just cant install any new ROM.
Actually this is the first time i hit this problem and I hv really no idea how to proceed, i flashed successfully many times previously using twrp cwm or stock recovery, just dont know what happen this time, I know how to flash a new ROM from recovery anyway, just put dload folder with UPDATE.app inside in FAT32 sdcard, but it just not success during flashing, any expert can guide me, i really appreciate your help, I attached with a photo below, i stuck at here when reboot with USB plug in, and for your information my adb cant read my device
sasadeaunty said:
I tried to flash my p6 to B512 ROM, and I had changed my recovery, duno what is my recovery version now, but just cant install any new ROM.
Actually this is the first time i hit this problem and I hv really no idea how to proceed, i flashed successfully many times previously using twrp cwm or stock recovery, just dont know what happen this time, I know how to flash a new ROM from recovery anyway, just put dload folder with UPDATE.app inside in FAT32 sdcard, but it just not success during flashing, any expert can guide me, i really appreciate your help, I attached with a photo below, i stuck at here when reboot with USB plug in, and for your information my adb cant read my device
Click to expand...
Click to collapse
So first unplug your phone from your pc otherwise it won't work.
Than I had the same as you in the picture with the recovery 'stuck' but for it simply worked if I reboot straight again into recovery via the three buttons.
Hope I could help
hi
taaeem said:
So first unplug your phone from your pc otherwise it won't work.
Than I had the same as you in the picture with the recovery 'stuck' but for it simply worked if I reboot straight again into recovery via the three buttons.
Hope I could help
Click to expand...
Click to collapse
Hi, if i reboot without plug-in the usb, it will also fail like (attached photo124)
hm..tried to use a jb rom (b125/132)..maybe you flashed a jb recovery
blueIBI said:
hm..tried to use a jb rom (b125/132)..maybe you flashed a jb recovery
Click to expand...
Click to collapse
Different stock recovery only can install certain ROM? I tried B125 already cannot. Any other recommend ROM for me to try? I rmb I flashed a quite latest stock recovery
then try the b510 or the b634..
jb recovery can only install jb rom..so do kk recovery only install kk rom as i know..
if nothing brings success try the unicom rom..
blueIBI said:
then try the b510 or the b634..
jb recovery can only install jb rom..so do kk recovery only install kk rom as i know..
if nothing brings success try the unicom rom..
Click to expand...
Click to collapse
hi, my stock recovery is 4.4.2, and I just downloaded B634 ROM and tried to flash it, but the flashing fail......
stuck at this
ro.build.version.release = 4.4.2
ro.product.name = UEDGE
Current build version is not 4.2, dont need move.
USB Update Enter...
HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0
This phone is secureboot phone.
This phone is UNLOCK state.
sasadeaunty said:
hi, my stock recovery is 4.4.2, and I just downloaded B634 ROM and tried to flash it, but the flashing fail......
stuck at this
ro.build.version.release = 4.4.2
ro.product.name = UEDGE
Current build version is not 4.2, dont need move.
USB Update Enter...
HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0
This phone is secureboot phone.
This phone is UNLOCK state.
Click to expand...
Click to collapse
You still have your usb cable plugged in. It will NOT work like that. @taaeem has already mentioned that.
What was the previous firmware that you had installed?
If it was a Chinese firmware, you need to try flashing this file first: https://mega.co.nz/#!8kcVADpB!JKeDlX4WQhmAP3mclNTfIzIjVllw5sMhnrj-3KSpSc4
maybe the sdcard causes this error too..had this with a 16gb fuji card..with a 8gb noname it worked..
and unplug your phone before flashing..as mentioned..
miz_pimp said:
You still have your usb cable plugged in. It will NOT work like that. @taaeem has already mentioned that.
What was the previous firmware that you had installed?
hi miz_pimp, if i do not plug in the usb cable, it will directly go into fail as showed in the picture124 i attached below, I do not rmb what firmware i installed previously, but I did a full wipe, I do not think thr is still firmware inside beside stock recovery.
Click to expand...
Click to collapse
blueIBI said:
maybe the sdcard causes this error too..had this with a 16gb fuji card..with a 8gb noname it worked..
and unplug your phone before flashing..as mentioned..
Click to expand...
Click to collapse
I tried with different sdcard without usb plugged in, still giving me fail
very strange..
maybe you do a all again..
starting with flashing a stock boot.img and recovery.img (from the b512 rom..you can extract them by the update extractor from here..just search)..
then try to flash the b512 rom by the force update method (press and hold the buttons until you see the update process starting!)..
id this fails too..well..i don't know how to help then..
if there was a cn firmware on your device (as mentioned) then search for the unicom firmware and read how to flash this and do a eventually downgrade at first)..
blueIBI said:
very strange..
maybe you do a all again..
starting with flashing a stock boot.img and recovery.img (from the b512 rom..you can extract them by the update extractor from here..just search)..
then try to flash the b512 rom by the force update method (press and hold the buttons until you see the update process starting!)..
id this fails too..well..i don't know how to help then..
if there was a cn firmware on your device (as mentioned) then search for the unicom firmware and read how to flash this and do a eventually downgrade at first)..
Click to expand...
Click to collapse
i cant even flash my recovery, when i use adb, it just shows me waiting for device, then no response. I tried most of the ways but no one can help......
hm..what might help is that you install the device drivers again..i had in the beginning a similar problem..after reinstall of the device driver (there is a package by lesscro on this forum) my device was seen even in bootloader mode correct..
blueIBI said:
hm..what might help is that you install the device drivers again..i had in the beginning a similar problem..after reinstall of the device driver (there is a package by lesscro on this forum) my device was seen even in bootloader mode correct..
Click to expand...
Click to collapse
i reinstall the driver setup from lesscro, is still the same, nth works for me, I cannot change recovery cannot flash new ROM, everything just a mess
miz_pimp said:
If it was a Chinese firmware, you need to try flashing this file first: https://mega.co.nz/#!8kcVADpB!JKeDlX4WQhmAP3mclNTfIzIjVllw5sMhnrj-3KSpSc4
Click to expand...
Click to collapse
sasadeaunty said:
i reinstall the driver setup from lesscro, is still the same, nth works for me, I cannot change recovery cannot flash new ROM, everything just a mess
Click to expand...
Click to collapse
Have you tried the file that I linked to above?
I think your problem is that you flashed the incorrect recovery version for the firmware you had on your device.
Unless you used TWRP to completely wipe your device before you flashed your stock recovery (which was not at all necessary), then you should still have a firmware on your device.
miz_pimp said:
Have you tried the file that I linked to above?
I think your problem is that you flashed the incorrect recovery version for the firmware you had on your device.
Unless you used TWRP to completely wipe your device before you flashed your stock recovery (which was not at all necessary), then you should still have a firmware on your device.
Click to expand...
Click to collapse
hi miz_pimp, thank you so muchhhhhhhhhhhhh, I am able to recover my p6 with the firmware u linked to me. Really thank you and thanks for others too for helping me too. Thanks all.
Glad you got it sorted, and you're very welcome. [emoji2]