Related
Ok, Im trying to flashing my EVo 4G to boost mobile. Im following the guide that eljean posted. I got all the way up to step 5 on the guide and got stuck. Heres how im stuck it says to download autoroot w/2.15.00.11.19 which i did then it say make sure you have a sd card in your evo which I do. then it say to duble click autoroot.bat and i do... it starts and this is where i get stuck it look like it start rooting then it say the ADB shell does not heve root permissioms and then it say FAILED TO GET A ROOT SHELL PLEASE RESTART YOUR PHONE AND TRY AGAIN. can somebody plz help me it making me a very angry person
can someone help pleaseee
aldog25 said:
Ok, Im trying to flashing my EVo 4G to boost mobile. Im following the guide that eljean posted. I got all the way up to step 5 on the guide and got stuck. Heres how im stuck it says to download autoroot w/2.15.00.11.19 which i did then it say make sure you have a sd card in your evo which I do. then it say to duble click autoroot.bat and i do... it starts and this is where i get stuck it look like it start rooting then it say the ADB shell does not heve root permissioms and then it say FAILED TO GET A ROOT SHELL PLEASE RESTART YOUR PHONE AND TRY AGAIN. can somebody plz help me it making me a very angry person
Click to expand...
Click to collapse
so you're trying to root? go here http://forum.xda-developers.com/showthread.php?t=1218386
..then go back to the original guide to complete
I did that i redownloaded all the auto root files and still when i go to autoroot.bat it still say the same thing does any of this matter? Im running Android ver: 2.3.3
Baseband ver: 2.15.00.05.02
Build number: 4.24.651 L61076 release keys
Software number : 4.4.651.1
PRI ver:1.77_003
On that guide i think it say it only work for Software versions 1.32, 1.36, 3.29, 3.30 & 3.70 and hBoot Version .76, .93, .97, 2.02 & 2.10 and how do i even find out my hoot version?
I just tried the autoroot quick method and it said unknown bootloader version. Bootloader is the wrong version. Is there anyway i can change my bootloader version?
aldog25 said:
I just tried the autoroot quick method and it said unknown bootloader version. Bootloader is the wrong version. Is there anyway i can change my bootloader version?
Click to expand...
Click to collapse
Don't use autoroot, click the link i posted...use "revolutionary" Not autoroot
follow the link i posted line by line !!
NO AUTOROOT !
Thanks alot i got pass that step now lol im stuck one more time. Ok I found 9 msid's and zerod them and i found 11 esn's before i got done checking all the esn locations i had about 5 or 6 locations left to check but i didnt becouse it say theres only 9 meids and 11 esns, and now after i zero them all out and reboot my phone and press ##786# the msid and esn is not all zeros like it should say. What do i do now?
Hey louforgiveno do you have a messenger aol msn yahoo or anything if so leave your screen name and log on i be on asap thanks
I just downgraded to 2.05.00.06.10 and used the revskills to try and zero meid/esn i ended up with a log file how do i write this to QXDM now?
i must be missing something cause everywhere i see it no one replies to this question or there is no answer...
after removing 0 and 1943, i can't ever commit the **** to the DIAG TX item... the DIAG RX item takes it just fine. I have been trying and re-trying for hours... thanks
You need the version of qpst listed In the guide....double check your version
I used the EFS Explorer to add and extract the files. Edit of course with Winhex. I bet the file is not saved properly if you've done this already.
louforgiveno said:
You need the version of qpst listed In the guide....double check your version
Click to expand...
Click to collapse
I have 2.7 v366, one guide didn't have a number beyond 2.7, another guide lists v355...
Dean_L said:
I used the EFS Explorer to add and extract the files. Edit of course with Winhex. I bet the file is not saved properly if you've done this already.
Click to expand...
Click to collapse
Makes sense. when you drag files back do they have the same look as the ones already in there? What i do notice is that all the other files have a consistent modified date, and there is also a batch of files that show mod dates that are more recent and don't have the red line through them (they look like txt file images on a windows pc). are these temp files that are perhaps messing with writing the ****?
woodz93 said:
I have 2.7 v366, one guide didn't have a number beyond 2.7, another guide lists v355...
Makes sense. when you drag files back do they have the same look as the ones already in there? What i do notice is that all the other files have a consistent modified date, and there is also a batch of files that show mod dates that are more recent and don't have the red line through them (they look like txt file images on a windows pc). are these temp files that are perhaps messing with writing the ****?
Click to expand...
Click to collapse
It's normal that they look different, don't know if you tried it yet, but you need to delete the 0&1943 from the phone before copying them back from pc.
louforgiveno said:
It's normal that they look different, don't know if you tried it yet, but you need to delete the 0&1943 from the phone before copying them back from pc.
Click to expand...
Click to collapse
i do delete them. but i also see a host of other files that are written on boot(or reboot), those are the ones i'm curious about. i also will downgrade qpst to 2.7.555 to see if that matters.
EDIT: Tried it to no avail. so infuriating... so close but so far...
EDIT: thanks to Klown80 - simple answer is it doesn't matter! there is a guide floating around that says it does, i just happened to end up with it. thinking that it was logical i wasn't going to deviate until i got it right... so unnecessary. so there it is, for those of you who are stumped by this issue...
Hi guys. I have a problem with my M8 (international).
Start topic was here http://forum.xda-developers.com/att...-boots-fastboot-factory-t2952954#post57042833 but I took an advice and open the same topic in general theme.
Hi everyone. I got a problem with my HTC M8.
First of all, I didn't make with it any changes (as unlock bootloader, root or installing any custom OS or recovery etc.) Week ago I left device, connected to PC for all night, and, I gess, with "bad" micro-USB cable.
Next day I couldn't boot this phone. I connected it to charger and after little time it was loaded to fastboot. But up today I can't do anything with phone: I can't unlock it, can't factory reset, can't boot to recovery etc...
I tried to find any same simptomes in google, but found nothing
As you can see on screenshots, I made steps for unlock bootloader but on device I didn't see notification about unlocking.
Click to expand...
Click to collapse
Could you help me with advices? Thanks.
I'm taking a bit of a guess but some how system has got wipe but that seems a bit off for a locked phone but since it's locked I would take it back to where you got it from and get them to sort it.
Sent from my One M8 using Tapatalk
Darknites said:
since it's locked I would take it back to where you got it from and get them to sort it.
Click to expand...
Click to collapse
I would normally say the same. But the OP mentioned in another thread posted in the wrong forum section (linked in his post) that he bought from Canada but lives in Ukraine, so I think warranty is not valid. It would have been helpful for the OP to give all the relevant details in this new post.
I agree, it looks like his OS and possibly recovery have somehow become wiped, corrupted, or damaged. Not common for a stock device, but not unheard of, either.
MaggiMag363 said:
Hi guys. I have a problem with my M8 (international).
Start topic was here http://forum.xda-developers.com/att...-boots-fastboot-factory-t2952954#post57042833 but I took an advice and open the same topic in general theme.
Could you help me with advices? Thanks.
Click to expand...
Click to collapse
Hi
I had a similar problem to you where I was stuck in fastboot mode and the only command it would execute was POWER DOWN and when switched back on it returned to fastboot mode. However I ended up in that state due to making a mistake in trying to unlock and root my phone. Also I believe my display showed the RADIO and OpenDSP details rather than the INVALID_VER_INFO that your's is showing.
I thought I had deleted the rom and recovery on my device and I had bricked my phone however I was able to recover my phone by getting a new unlocktoken from HTC and flashing it.
Once I had successfully unlocked my phone I had access to my rom and recovery.
I see from your first image that you tried to unlock your phone and it shows that 'unlock token check successful' but images 2 and 3 show that the phone is still 'LOCKED' so it may be worth going to the HTC site, get a new unlock token and try again.
If it doesn't work, it shouldn't do anymore harm either!
Best of luck.
I see from your first image that you tried to unlock your phone and it shows that 'unlock token check successful' but images 2 and 3 show that the phone is still 'LOCKED' so it may be worth going to the HTC site, get a new unlock token and try again.
Click to expand...
Click to collapse
Yes, I did this And in consol I saw that everything was fine, but on device I didn't see standart notification about unlocking.
A found some topics about "INVALID_VER_INFO" - and they said that it can be ok for some devices (guys checked this on their worked devices, booted to fastboot and saw the same).
http://forum.xda-developers.com/showthread.php?t=2715056 here is the topic about "INVALID...".
btw - I tried unlock phone after another man. He did the same - receive .bin from dev. HTC site etc. I did the same, but from another HTC dev. account and result was the same Phone didn't unlock.
It could be that the recovery has got messed up because I believe recovery is used to do it since unlocking will wipe data. The only things I can think of is a real ruu as in it full rom and firmware exe (good luck with that) or you could try just firmware ruu, riff box or HTC themselves.
Sent from my One M8 using Tapatalk
Darknites said:
It could be that the recovery has got messed up because I believe recovery is used to do it since unlocking will wipe data. The only things I can think of is a real ruu as in it full rom and firmware exe (good luck with that) or you could try just firmware ruu, riff box or HTC themselves.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
I have the riff box but without needed pin-outs (http://i01.i.aliimg.com/wsphoto/v0/...x-Flex-font-b-cable-b-font-for-Samsumg-LG.jpg I'm talking about these pin-outs). And my previous experience with riff box and Samsung S3 was not very good)))) I had been fixing it during 2 months
https://www.dropbox.com/s/oqygsy7ku7o37j5/M8-DEBUG.doc?dl=0
Pin out.
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
elawady.2014 said:
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
Click to expand...
Click to collapse
Does cwm boot?
Sent from my One M8 using Tapatalk
[/COLOR]
Darknites said:
Does cwm boot?
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
yes it's boot
and now i install stock rom via it
i think it's for inernational
so camera not work and wifi not work ??
please help me i can't find any solve
elawady.2014 said:
yes it's boot
and now i install stock rom via it
i think it's for inernational
so camera not work and wifi not work ??
please help me i can't find any solve
Click to expand...
Click to collapse
Not sure of good place for stock roms sorry.
Sent from my One M8 using Tapatalk
Darknites said:
Not sure of good place for stock roms sorry.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
but how can i work wifi and camera ?
elawady.2014 said:
but how can i work wifi and camera ?
Click to expand...
Click to collapse
Not sure but you could give twrp a try to wipe and flash.
Sent from my One M8 using Tapatalk
Darknites said:
Not sure but you could give twrp a try to wipe and flash.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
ok thanks but i can't install other custom recovery
i have 3 backup by cwm and nandroid to my old rom
but when i restore it it not restore
do u know why ?
if other way to restore backup ?
elawady.2014 said:
i have the same problem my device is htc m8_TL
and it still in fastboot
but i have cwm
can anyone help me ?
Click to expand...
Click to collapse
Hey man. Sorry but your problem not the same. You installed custom OS and it could be the reason of this. I install nothing. I have full stock device. And my problem not the same with your problem. Could you create new topic please?
Venomtester said:
https://www.dropbox.com/s/oqygsy7ku7o37j5/M8-DEBUG.doc?dl=0
Pin out.
Click to expand...
Click to collapse
Thanks. But my skill too low for soldering these small parts I talked about completed pin-out connectors for JTAG. I tried to find them on EBAY and other JTAG stores, and failed (look at screenshot with these pin-outs higher).
Could anyone help with RUU process? What information I should have for correct RUU update? I found this post http://forum.xda-developers.com/showthread.php?t=2729173 but I'm not sure that I have SPRINT device.
I need an information, how I can be sure, that I use correct file for RUU my HTC? Is it bootloader version, or operator version (Sprint, Verison etc.) or something else? As I wrote, I can open information about my phone in Fastboot (I can check my SN, CID, bootloader version etc.)
MaggiMag363 said:
Could anyone help with RUU process? What information I should have for correct RUU update? I found this post http://forum.xda-developers.com/showthread.php?t=2729173 but I'm not sure that I have SPRINT device.
I need an information, how I can be sure, that I use correct file for RUU my HTC? Is it bootloader version, or operator version (Sprint, Verison etc.) or something else? As I wrote, I can open information about my phone in Fastboot (I can check my SN, CID, bootloader version etc.)
Click to expand...
Click to collapse
For a ruu to work it needs to have matching cid, guess mid and has to be same version or higher than what's on the phone. You can't flash the wrong one it won't let you.
Edit, also the one you linked to won't work.
Darknites said:
For a ruu to work it needs to have matching cid, guess mid and has to be same version or higher than what's on the phone. You can't flash the wrong one it won't let you.
Edit, also the one you linked to won't work.
Click to expand...
Click to collapse
Ok. And Can I flash version with unlocked bootloader and custom recovery, for example? (I said that there are a lot of recovery but they are custom. Is it ok for me or I should find pack with all stock?)
guess mid
Click to expand...
Click to collapse
It's unknown letters for me. Would you describe what did you mean? Thanks.
Q&A for [ROM] 2.19.40.18 Full ROM - ZE551 - Goodbye Garbage - Rooted
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] 2.19.40.18 Full ROM - ZE551 - Goodbye Garbage - Rooted. 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!
How to flash this custom firmware
Hi everyone, i'm really new with this zenfone 2, just had it since 3 days ago, mine is ze551ml with 4gb ram and 32gb internal, and still has firmware version 2.13... And I have an issue with the battery life, so I was looking for something that can fix my problem, then I found this thread, and honestly I don't have any idea how to do it, and what's the meaning of "you must be unlocked" ? Is that mean I have to unlock bootloader first? If so, than what should I do after that? Can I just download the firmware then put it in my internal storage? Will notification pooped up after i unplug the USB cable ? Or there is something I need to do with the firmware? I hope you guys can help this newbie, and if you can make a tutorial video and upload it to YouTube it will help many people, thank you very much...
Regards from Indonesia
How to remove zenui drive mount.
Thanks for the update, I will keep your rom as a back up, for now I am good just wanted to remove the zenui app mounting when I connect the phone, can someone please guide me in the right direction?
Thanks
Can I make a request for 550ml pls?
After 2.18, my phone not vibrate when connected to a call, so can you make a "no garbage" rom with ver. 2.17 pls?
i heard that 2.19 got too many bugs and they dont prefer to flash to the latest version.
and another thing, would you do it for 500ML too ?
thanks
Hi, one question:
How you have removed annoying notification of micro sd card inserted?
AlanRoot said:
Hi, one question:
How you have removed annoying notification of micro sd card inserted?
Click to expand...
Click to collapse
Also interested in knowing how. I always leave a micro SD in and find it annoying to swipe that notification away every time I boot.
AlanRoot said:
Hi, one question:
How you have removed annoying notification of micro sd card inserted?
Click to expand...
Click to collapse
joel.maxuel said:
Also interested in knowing how. I always leave a micro SD in and find it annoying to swipe that notification away every time I boot.
Click to expand...
Click to collapse
I'm more than likely going to remove that, but if it's in the SysUI, I won't touch it. Since Asus still updates their launcher often, it would have to be re-modified with each update.
Going to see if I can kill it another way though. Pretty sure I can.
ZE550ML
Someone who is working on 2.19.40.12 (ZE550ML)?
agliusmar said:
Someone who is working on 2.19.40.12 (ZE550ML)?
Click to expand...
Click to collapse
He doesn't have that model, but I'm pretty sure nobody will be left out. We just have to be patient:thumbup:
Sent from my ASUS_Z008D using XDA Free mobile app
I look forward !!! I know that you will do an excellent job as always.
I'm waiting ...
I used firmware 2.19.40.20
When i flash it, i got stuck on asus zenfone 2 like a pict in page one.
I think i can't use this, and i hope someone here can tell me what must i do ?
I was flash it more than one.
Thanks
I just unlocked my bootloader, but when I try to adb sideload, it says
e:footer is wrong
e:signature verfication failed
installation aborted.
Does that mean that my bootloader isn't unlocked? (because I followed the step perfectly and got a white bootloader and everything)
Any help is appreciated.
---------- Post added at 03:48 AM ---------- Previous post was at 03:13 AM ----------
When I try installing this with adb sideload, (on a rooted unlocked zenfone2) it says that the signature verification failed.
I thought that it didn't check for verificaton if the bootloader was unlocked.
My bootloader is white so I am fairly certain that it is unlocked.
I'm not sure what I'm dong wrong. any help is appreciated.
My firmware is 2.19.40.18
Update: So I installed TWRP (i think that solved the problem I had earlier), however now when I go into ADB Sideload, it says that there are no adb devices connected.
This is very strange to me because when I exit ADB Sideload, and I check for adb devices, it shows up again.
I have also tried reinstalling drivers and the result is still the same.
If anyone is experiencing similar issues or knows how to fix this, please let me know!
Thanks
update 2: So I was not able to sideload from adb using TWRP, however I was able to use the push function to push the data onto the internal memory and install it from there.
The command I used was "ADB push <filename> /sdcard/"
without the quotatons.
From there I installed it and worked like a charm.
Thanks!
Must choose format / system on cmw ?
simsimono said:
Must choose format / system on cmw ?
Click to expand...
Click to collapse
Don't do that. I did that and was in a lot of trouble.
Rom ze550ml
Can I use this rom for ze550ml?
How can I get this theme on a stock rom (with all the bloatware and stuff).
Is the rom global version?
app names
can you please tell me the names for
Party Link
Power Saver
instead of removing the apps i choose to disable them.
this is what i have disable so far
com.asus.weathertime
com.asus.filemanager
com.asus.kidslauncher
com.asus.sitd.whatsnext
com.asus.zencircle
com.asus.flipcover2
com.asus.backuprestore
com.asus.zentalk
com.asus.supernote
com.asus.browser
com.asus.email
com.asus.gallery
com.asus.zencircle
com.asus.quickmemo
com.asus.quickmemoservice
com.asus.taskwidget
com.asus.task
com.asus.taskwidget
com.asus.task
com.asus.linkrim.service
com.asus.linkrim
com.asus.sharerim
com.asus.userfeedback
com.asus.asuszenuipcsuite
com.asus.minifilm
I've uninstalled everything that the phone allowed me to do by default.
if you know anything else that could be disable could you please make a list.
The reason im not removing them is simple:
1) not an expert in android - in case problems happens
2) i like to be able to update my phone - so far i've made 1 OTA without any problems
3) 64 gb of internal storage is enough to not worry about space.
Just a small and quick question. I'm looking to flash this bad boy and getting most bloat removed in one simple step; but I'm worried about one thing.
Do you plan to keep doing this with future builds, or quitting sometime in the near future?
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere
also
please pm me if u fixed yours
Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now
Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?
The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.
I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore
need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?
Hola, alguien lo consiguió hacer..???
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/
m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse
ayuda
ATT ZE500CL/Z00D rom
Ok so in the last thread I started I learned how flashing ROMS works, with the matching firmware, CID's, and other stuff, but now I have another issue... The ROM that I was able to flash was the TeamVenom Viper One ROM for Android L (Lolipop)....The ROM version I used was Viper 3.5.0, but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x).... I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev) and I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link... I don't think I can update Viper because it says "Flashing the new Android M firmware is a must, else your phone won’t boot!!" (trust me it doesn't boot, I've tried)... But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)... What would I need to do from here, how would I A)fix HTC installer, or B) does anybody have a WORKING flashable stock android zip to update from Lollipop to Marshmallow...
Thanks in advanced!
Forum N00b,
qwsderter
qwsderter said:
but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x)
Click to expand...
Click to collapse
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
qwsderter said:
I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev)
Click to expand...
Click to collapse
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
qwsderter said:
I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link
Click to expand...
Click to collapse
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
qwsderter said:
But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)
Click to expand...
Click to collapse
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Flippy498 said:
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Click to expand...
Click to collapse
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash.... Any other ideas, you are the master at this Flippy, there must be another way...
qwsderter said:
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash....
Click to expand...
Click to collapse
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Flippy498 said:
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Click to expand...
Click to collapse
Ah gotcha... So I used the decryption tool to make a SD flashable zip, and what do you know, TWRP crashes when I swipe to flash... How come I can flash other ROMs but I can't flash stock roms without it crashing (Device turns off)
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok thank you "again" I have officially read your ENTIRE guide 3 times now, Not trying to offend you or make shame of your work, but the problem is I "THINK" that I am following your work.... I download the RUU for my phone (in this case SKU: 502 - CID: CWS__001 VERSION 2.11.502 (I have also tried 3.38.502.41 to no avail)) and everything is going as planned, I have verified that BOTH the CID and MID are matching that of my phone.... But when I plug SD card into Phone in download mode I get no such asked if I want to flash the file (as your guide says to do).... Ok so if I try to flash through TWRP it crashes, and if I try to Fastboot Flash the file I get what is seen in the picture attachment, and then nothing happens, except the bootloader page says "Under flash" and adds another line saying Under flash everytime I press the power button... My phone is S-OFF, is there another possible way to do this.... I swear to go I have read your ReadMe thread and I'm not just being arrogant, but my phone WILL not flash to ANY STOCK ROM downloaded anywhere from the Internet... @Flippy498 I promise there has to be something I missed in your ReadMe (I HAVE NO IDEA HOW I COULD) or i'm getting damaged ROMs... I'm sorry that you have to put up with me and help me thus far, and let me say the XDA community deserves people like you, and less people like me who think they know what they are doing until something breaks...
EDIT: It seems the phone is missing a located at /dev/fastboot_download_j in the CMD screenshot. Should that be said issue how would I go about fixing that...
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Flippy498 said:
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Click to expand...
Click to collapse
Once again Thank you for helping me out, the htc_flashboot command was what I needed, I was able to flash the stock rom through the command.... May I just say, you sir know what you are doing, and I wish you continue to help other people on this forms just like you've helped me.... I Installed the 2.x rom, but the OTA update didn't work for some reason... so I'm gonna flash the 4.x and then install ViperOne again...
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place...
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death...
Thanks again,
qwsderter
qwsderter said:
I Installed the 2.x rom, but the OTA update didn't work for some reason
Click to expand...
Click to collapse
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
qwsderter said:
so I'm gonna flash the 4.x and then install ViperOne again
Click to expand...
Click to collapse
Don't forget that you need to flash one of Sneakyghost's firmware packs if you want to be able to flash 4.x RUUs. (Keyword: encryption keys)
qwsderter said:
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place
Click to expand...
Click to collapse
That's actually the difference between my ReadMe thread and most of the RUU collections on other websites. The files only get linked if they're known to be working whereas other sites link every RUU they can find. There are a lot more RUUs for the M9 out there than the ones I listed. However, these RUUs either aren't able to get flashed successfully or their roms aren't able to receive any OTAs - e.g. there's a second RUU for firmware 1.32.401.15 than the one that is linked in my thread and if you flash that other RUU you're stuck on its firmware version until you flash a different RUU.
qwsderter said:
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death
Click to expand...
Click to collapse
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Flippy498 said:
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
Click to expand...
Click to collapse
Funny, I thought the same thing, until I realized it was ATT who I am paying every month to rip my girlfriend and I off. Well oh well, I know you are in Germany (From your profile) but if you ever come to the United States, I will say from my personal experience (my opinion, not facts) ATT has seemed to have the broadest coverage, but also is the (2nd) most constrictive (Verizon seems very constraining), to me ATT feels premium but they are also (in my opinion) the most likely to royally screw up... Oh well, no OTA time to flash!!!
Flippy498 said:
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Click to expand...
Click to collapse
Trust me, when I tried the SD card in the phone I thought, "That is a little odd", then both of my ASUS MemoPads didn't detect it either EVEN THOUGH THEY WERE RUNNING, I just assumed that they didn't work because MemoPads are the most budget friendly tablets ever and something broke, so I go to my Nexus 7 and realize it doesn't have an SD card slot so I couldn't test, so I popped the card in our Camera... Low and behold it doesnt detect.... Now the true question, why did my desktop detect it, eh whatever not worth my time.... The gods were looking down on me, they broke my $10 microSD and not my more than 10$ phone.....
Once again thank you for the help Flippy, you have no idea how much it hurt using my iPhone 5 for 2 days, I felt so inferior