Hello all!
Recently, I had a request from a GSM 3VO user for a port of my/CMB's Jellybean ROM from CDMA to GSM. As our ROM is based on CM10 Disarmed Toaster, I didn't think it would be very difficult to copy his GSM bits in and make it go.
Now, as I am obviously not using a GSM device, I can't test this...at all. I don't know if it boots. However, my ICS build is actually a port from GSM to CDMA, so I'm pretty familiar with the process. Having CM10 as a guide should help too.
So, for the more intrepid of you, I present my super-duper-alpha-omega-beta build of MIUI 3.2.1. To make it, I literally diffed the CDMA and GSM builds of CM10, copied out the bits that are different from GSM, and plugged them into the appropriate spots in MIUI.
I can't promise anything. I don't know if it will boot. I don't think it will break anything, but I don't even want to say that much. I did make sure that the installer only touches /system and /boot partitions, so there shouldn't be any risk to recovery or anything.
Also, most features in the Aroma installer should work, but obviously, the stuff for Virgin Mobile users doesn't apply. Not all of the wipe features actually do anything (need to look up what mmcblk's your device uses for cache and devlog), but nothing should hurt anything.
Once again - THIS IS AN ALPHA VERSION. IF YOU DON'T KNOW HOW TO LOGCAT AND DON'T FEEL LIKE TESTING, DO NOT DOWNLOAD THIS.
Have I scared you away yet? No? Okay then...
http://goo.im/devs/digitalhigh/miuijbU/MIUI_3.2.1_SHOOTERU_JB_DH_Test2.zip
So, instructions:
1. Download. Put on SDcard.
2. Boot to Recovery.
3. Do a full wipe.
4. Open le .zip
5. Under wipe settings, check whatever you want. Only "system" and "boot" are currently attached to anything, the rest are placeholders.
6. For the carrier option, leave it checked on "sprint", not "virgin". This is another placeholder, will be modified once we get this going.
7. For customization options, please pick "minimal". All custom options should work, but for testing purposes, minimal will keep the variables down.
8. Hit next, and watch the installer go.
9. Reboot.
10...?
And, again, can't even say that this will boot yet. If it does, awesome! If not, head on over to your favorite computer and spit me out a logcat report. Upload that to pastebin or as an attachment, and let me know what hboot and firmware you're running. As this is a jellybean/cm10 variant, all rules that apply to that ROM should apply to this.
To the mods - I apologize for posting a ROM that I can't confirm as working, but this is based on a working ROM and my experience with porting, so I anticipate any issues with booting will be resolved quickly, and I can make this a part of my weekly release schedule.
Thanks everybody in advance for the help! Once we get this booting, I'll focus on features and such as I have in my CDMA version. I'll work on making the thread purdier too.
Code:
[B]Changelog:[/B]
[I]2.7.13[/I]
Fixed error in installer where boot.img wasn't being pulled from right directory.
Modified boot.img to include missing commands present in MIUI boot image.
Added latest ButteredToast kernel to boot.img - modules to /system/libs/modules
Edit: As per mod request, kernel used is Butteredtoast by bigwillyG. All source info can be found in his thread:
http://forum.xda-developers.com/showthread.php?t=1935860
Reserved
What the heck...this one too.
Thanks, will flash once download is complete and will post results.:thumbup:
Sent from my HTC EVO 3D X515m using xda app-developers app
hey_joe said:
Thanks, will flash once download is complete and will post results.:thumbup:
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
Your bravery is highly appreciated.
Ha ha ha! I'm always into testing new roms. Download just finished so will nandroid and flash. Might take a bit before I can come back online. If you did not see any post from me that means I have a problem with the phone and can't post since I'm not near any pc as I'm currently at work.
Thanks.
Sent from my HTC EVO 3D X515m using xda app-developers app
---------- Post added at 01:20 AM ---------- Previous post was at 01:01 AM ----------
Installation went without a hitch but it always boots up in the bootloader and can't get past that.
Sent from my HTC EVO 3D X515m using xda app-developers app
Welcome!:highfive: Long Live Evo 3D!!!:good:
收件人： [ROM][JB](2/5/13) MIUI 3.2.1 Digitalhigh Edition - ALPHA
welcome from CDMA.GSM need more developer........
Sent from my HTC X515d using xda premium
Lollllllllllllllll!!! I love miui!!!!
Gave it another go. This time wiped everything except sd in recovery and unchecked all format option in aroma. When it rebooted, It's looping on the splash screen. Unfortunately I can't provide logcat for now as I'm not near any pc.
Sent from my HTC EVO 3D X515m using xda app-developers app
can't boot.it will boot into bootloader
Can't wait to try this.... Off to Nand now and see how things run.. :sly:
I will report any bugs I find..
Thanks for your hard work..
Sent from my shooteru using xda premium
As I pointed out in the OP - as of right now, I wasn't expecting it to boot. This is why I need you guys help. If anybody can get me a logcat of the bootloop, I can see what's going on and potentially fix it.
digitalhigh said:
As I pointed out in the OP - as of right now, I wasn't expecting it to boot. This is why I need you guys help. If anybody can get me a logcat of the bootloop, I can see what's going on and potentially fix it.
Click to expand...
Click to collapse
For me after installing rom phone stuck in fastboot (even didn't want to start booting) so i use latest ButteredToasT kernel for collecting some data
How did you managed to install butterted toast? For me it fails while installing the boot.img (Status 7). I always have that on MIUI, so I'm just curious.
digitalhigh said:
As I pointed out in the OP - as of right now, I wasn't expecting it to boot. This is why I need you guys help. If anybody can get me a logcat of the bootloop, I can see what's going on and potentially fix it.
Click to expand...
Click to collapse
did you edit accordingly init.rc and updater-script?
$tefanDroid said:
How did you managed to install butterted toast? For me it fails while installing the boot.img (Status 7). I always have that on MIUI, so I'm just curious.
Click to expand...
Click to collapse
First time on miui you have to flash kernel whit boot.img inside zip,whit flash image gui apk,and after that,you'll be able to flash other kernels like BT....
Sent from my Evo 3D GSM using xda app-developers app
dr_jerremy said:
First time on miui you have to flash kernel whit boot.img inside zip,whit flash image gui apk,and after that,you'll be able to flash other kernels like BT....
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Or you can grab boot.img from any rom, flash it via fastboot (fastboot flash boot boot.img) and then install your favorite kernel from recovery. It's because MIUI uses stock kernel with some kind of lock (don't really known how to describe it).
helicopter88 said:
did you edit accordingly init.rc and updater-script?
Click to expand...
Click to collapse
Define "accordingly". I did modify updater-script to flash to the right block for boot and put system in the right spot, however, I'll sit down with kitchen and take a look at the init.rc. I assumed it would be happy because I was using the same boot.img from Cm10, which usually just works.
Edit: Yep, thar's one big problem. My dumb as$ has the boot.img in a folder called "vanilla", when the updater-script calls for "kernel/vanilla". Sure that doesn't help.
nice work , thanks, downloading now
Related
Since i got my Evo 3D ive always wanted to be able to run Boot Manager on it. My Evo has the 1.50 hboot from factory. Anyways, the first time i ran boot manager it failed at the boot.img part towards the end. I personally assumed it was due to the fact i didnt have S-Off available to me. Since yesterday I was able to downgrade my bootloader to 1.40 and put S-Off using revolutionary. However, Boot Manager still wont work properly. Does anyone have any ideas as to how to get around or fix this?
Are you flashing a new ROM or restoring a nandroid in bootmanager?
Sent from my PG86100 using xda premium
ssojyeti2 said:
Are you flashing a new ROM or restoring a nandroid in bootmanager?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
im trying to flash a new rom... am i supposed to do nandroid backups?
I had a similar issue at first. The problem he has solved. It could be ROM your trying to flash is a cdma/gsm version, so in turn it didt know what img to use he fixed it to ask what one.
If not try forcing large img under settings, and keep screen on.
If not I would recommend email them. They very quick to get back to you. And can solve the issue. When. You email them, let him know what your running, what your trying to install, also attach the log.txt from SD/boot manager.
Hope it helps, it is a FANTASTIC app, GREAT SUPPORT
Sent to the third dimension from the 3rd.dimensional 3VO
Linsalata28 made a great guide for boot manager in the q/a section. Anyone that has this app should read it.
http://forum.xda-developers.com/sho...scussion Thread also works on hboot 1.50 s-on
tomcat420m said:
I had a similar issue at first. The problem he has solved. It could be ROM your trying to flash is a cdma/gsm version, so in turn it didt know what img to use he fixed it to ask what one.
If not try forcing large img under settings, and keep screen on.
If not I would recommend email them. They very quick to get back to you. And can solve the issue. When. You email them, let him know what your running, what your trying to install, also attach the log.txt from SD/boot manager.
Hope it helps, it is a FANTASTIC app, GREAT SUPPORT
Sent to the third dimension from the 3rd.dimensional 3VO
Click to expand...
Click to collapse
+1 on great support. i tried getting bmp to work and had all kinds of issues. service was top notch, but unfortunately I came to the realization that my 3D just doesn't play well with bmp. went back to my old way of flashing between roms - nandroids. I will try again down the road to see if I can get it working as it is a great app.
I have it running cm9 right now, for some reason. That's the only ics that actually runs for me. I tried other ics on bootmanager but they normally got stuck on the white HTC screen.
Sent from my PG86100 using Tapatalk 2 Beta-2
what rom did you try?
i use
Phone Rom: Mean 2.6
Slot 1: MIUI 2.2.10
Slot 2: FreEVO
Slot 3: ZR3D
All works well. Dont forget to read the manual.
Force large boot and uncheck superuser logging.
Gonna try Playground ICS on slot 4 now
I want to run Mean Rom. My new Evo was updated and has stock 2.13. From what I can read, it looks like I am pretty much screwed because I took the update before I knew I wanted to root. If I am wrong about this and you can help me get Mean Rom on my phone I will send you $20 whole dollars via paypal. - Josh
It would prob be best to send me a PM
Koviak said:
I want to run Mean Rom. My new Evo was updated and has stock 2.13. From what I can read, it looks like I am pretty much screwed because I took the update before I knew I wanted to root. If I am wrong about this and you can help me get Mean Rom on my phone I will send you $20 whole dollars via paypal. - Josh
It would prob be best to send me a PM
Click to expand...
Click to collapse
Wrong place, but try the regawed htc unlock for root
All you have to do is unlock your phone, install the latest twrp, and then install MeanROM. There is no trick to it. You can use the HTC Developer unlock or use regawmod unlock for root. I have heard that regawmod has some problems automatically loading the new hboot and you have to manually enter the bootloader but he may have that fixed now. The easiest method for you might be to go to HTCdevelopers.com, unlock using htc's method, install goomanager from the play store and use it to install the latest twrp, then download MeanROM 3.9 and install it in recovery. You are already on the new baseband and kernel since you took the update so you won't have to do anything extra when you flash MeanROM.
1. Follow this guide to get unlocked bootloader, and custom recovery: http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
Note: it says its for 1.22.651.3, but it also works for your version, and when it asks you to download TWRP, download the latest version, 2.2.2.0
2. Make a backup of your current rom by going through TWRP, and select back up
3. Now you want to do a fresh install, because you will be s-on, but use the attached superwipe file to clear everything (this way you don't have to wipe everything manually, it does it for you)
Note: this wipes everything! your OS included, except for your backup
Note2: to install this, you are going to go into recovery (first get into bootloader and then use the power keys and go down to recovery) --> install --> look for the smw6180 zip file that you put on your EXTERNAL card (you can do internal card as well) --> swipe to install and you will see a process that wipes EVERYTHING, give it some time, the erasing boot part takes the longest
4. Have the rom that you want, aka meanrom downloaded, and follow these steps (choose option 1: http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
5. Now put mean rom (the .zip file) on your external sd or internal (whichever you prefer), and then go back into recovery, and install it just like how you did super wipe
6. Reboot to system and enjoy
Note: first time launching it takes time
Note: DO NOT forget to make a backup
Extremely easy to do. just make sure you fast boot flash the kernel
Sent from my EVO using Tapatalk 2
Rxpert said:
Extremely easy to do. just make sure you fast boot flash the kernel
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
He's already on the latest ota so no need to fast boots the kernel.
Sent from my A500 using Tapatalk
regardless of the latest ota he may want to fastboot the kernel if mikey has made any significant changes to the kernel. Though I'm not too familiar with it, I have yet to try mean but i hear nothing but good things so I may have to now
Thank you! You all are awesome! Phone works great. Regawmod did not work. It was midfieldmaestro who got me going on the right track! Shoot me a PM with your paypal email if you want the bounty, otherwise it is going to MeanRom. - Josh
Koviak said:
Thank you! You all are awesome! Phone works great. Regawmod did not work. It was midfieldmaestro who got me going on the right track! Shoot me a PM with your paypal email if you want the bounty, otherwise it is going to MeanRom. - Josh
Click to expand...
Click to collapse
u should donate the $$ to mean rom/mikeyxda he the one that should get it
Agreed
Sent from my EVO using Tapatalk 2
Send it to mikeyxda.
Sent from my A500 using Tapatalk
om4 said:
regardless of the latest ota he may want to fastboot the kernel if mikey has made any significant changes to the kernel. Though I'm not too familiar with it, I have yet to try mean but i hear nothing but good things so I may have to now
Click to expand...
Click to collapse
You can also to use Flash Image GUI instead of fastbooting. But it's not needed as the kernel is stock for now.
Sent from my EVO using xda premium
Don't use the app unless you know how to manually do it via fastboot....
That's asking for trouble. Trouble I don't want to have to deal with
Sent from my EVO using Tapatalk 2
I personally don't trust new users woth flash image, it works, but if you tell them hey use this, they may out of confusion, flash only the kernel and then end up back here with another problem lol and as much as I dislike HTC Dumlock, its the most flexible solution and after their last update to compare ramdisks its pretty rock solid
Rxpert said:
Don't use the app unless you know how to manually do it via fastboot....
That's asking for trouble. Trouble I don't want to have to deal with
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I use to flash the kernel via fastboot/adb but Flash Image GUI is so much easier. I download the ROM, flash the kernel via Flash Image GUI, reboot to recovery and flash the rest of the ROM and then reboot.
But I agree that you should at least know how to manually flash it via fastboot though.
Sent from my EVO using xda premium
Koviak said:
Thank you! You all are awesome! Phone works great. Regawmod did not work. It was midfieldmaestro who got me going on the right track! Shoot me a PM with your paypal email if you want the bounty, otherwise it is going to MeanRom. - Josh
Click to expand...
Click to collapse
I don't use MeanRom, but I would prefer if you send it to them
Done, thanks guys. - Josh
Hi,
For 2 days my Wifi is giving an error. It says turning on but never does. I have not installed anything or changed a thing. It stopped working for some strange reason. I am on stock mobility with stock kernel, never changed it and I have s-on.
Please help,
Thanks
Try a hard reset
Sent from my HTC_Amaze_4G using xda app-developers app
Is there any way besides a hard reset?
Sent from my HTC Amaze 4G using xda premium
Are you rooted!
Sent from my HTC_Amaze_4G using xda app-developers app
Unlocked bootloader & rooted.
Sent from my HTC Amaze 4G using xda premium
Try clearing Dalvik-Cache in recovery then Fix Permissions. It should help it.
Wipe and reflash stock via hasoon's zip files.
I reset and its still the same. When I try to flash a different kernel it restarts without changing but starts with an error message to contact HTC. I'm fully rooted, unlocked bootloader and s-on and I tried flash.bat and the kernel flasher app but none can change my kernel. Does anyone have any suggestions?
Just noticed bt is not working too
Sent from my HTC Amaze 4G using xda premium
pokey77 said:
I reset and its still the same. When I try to flash a different kernel it restarts without changing but starts with an error message to contact HTC. I'm fully rooted, unlocked bootloader and s-on and I tried flash.bat and the kernel flasher app but none can change my kernel. Does anyone have any suggestions?
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Well if you are using 4ext recovery (which i highly recommend, best recovery ever made)then there is an option that asks if you are are s-on and you click yes because you are s-on which then allows the recovery to flash any kernel (given its compatible of course) as if you were s-off. That should work, if for some odd reason (for me 4ext never failed even when i was s-on while flashing kernels) it doesnt work then i would suggest attempt to s-off your device via wire trick but be sure to read up thoroughly before you attempt that as some people have bricked their device doing so.
Edit: also i would suggest wipe all partitions except sd card then flash rom and then flash kernel right after to avoid issues.
Could I try to flash a kernel first before flashing. I tried looking for a kernel all day and can't seem to find 1. I used the mobility ota Kernel which does not seem to work.
Sent from my HTC Amaze 4G using xda premium
pokey77 said:
Could I try to flash a kernel first before flashing. I tried looking for a kernel all day and can't seem to find 1. I used the mobility ota Kernel which does not seem to work.
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Hmm I haven't heard of that kernel before and there aren't many to choose from on this device. First off do you have the ICS ruu? If so just flash faux's kernel with any of theroms that are based off of sense 3.6. Here is the link that is also under the development section of the forums http://faux.androidro.ms/ruby-faux123-kernel-v017.zip for the ICS version ROMs (most of them are) I would suggest speedrom 7.5 as I found it pretty decent for a sense based rom. But you have to flash the ROM first then the kernel but if I recall 4ext recovery with the feature of s-off automatically flashes the kernel that is packaged with the rom it just ends up having to boot twice. So first just flash one of the new sense 3.6 ROMs via 4ext recovery - settings-recovery-check smartflash on and then flash the ROM kernel should automatically flash
Edit: stumbled across this in faux kernel thread might help if 4ext still doesn't work
http://forum.xda-developers.com/showthread.php?t=1359951&page=181
I also had the wifi error problem for some reason when I tried to flash Speedrom 6.5 and 7.0 coming from Supersaiyan 3. Kinda fixed itself after installing Speedrom 7.5/7.6 so maybe try these two steps and it might work for you:
1 ) Of course make a backup
2) When flashing a new or old rom I always Wipe/Factory Reset from 4ext and then just clear dalvik cache, then install whatever rom you like. Never had any probs with this method such as the wifi error you're encountering. Just never got bt error.... weird...
Btw what rom are you currently on?
+1 if this helped anyone!
Sent from my HTC Ruby using xda premium
I'm on mobility stock rom
Sent from my HTC Amaze 4G using xda premium
I switched to speed Rom and bt works but not WiFi.
Sent from my HTC_Amaze_4G using xda premium
I've tried a few roms all day and still no luck.
1. After installing a rom, it always does 1 final step before a restart. It uses a previously saved boot.img which i think is causing my issue but i could be wrong.
1. One thing i noticed is when a rom boots up, the 1st thing it does is turn on WIFI followed by an error.
Has this happened or does any of this makes sense to anyone?
Once again, please help & thanks.
pokey77 said:
I switched to speed Rom and bt works but not WiFi.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Bro its most likely a kernel issue you are facing WiFi issues usually are due to the incorrect kernel flashed or the kernel not flashed at all with the ROM however I would suggest that you flash the stock ruu file (however you will lose both root and recovery but those are easy to reinstall using hasoons tool or various other methods) I say this because this way you will know for sure if you have a hardware or software problem for sure. WiFi should work with stock ruu from your carrier (make sure to download your carrier specific ruu).if you feel you can do s-off via wire trick and then super cid your amaze you will be able to flash any and every ROM for the amaze. I have a suspicion that the ROMs that are out are based off of T-Mobile ruu and people with mobilicity have their amaze super cid to work with any carrier.however did you try flashing cm10 via 4ext maybe since that has an aosp kernel and if flashed with smart flash option in 4ext it may work.
1. After installing a rom, it always does 1 final step before a restart. It uses a previously saved boot.img which i think is causing my issue but i could be wrong.
1. One thing i noticed is when a rom boots up, the 1st thing it does is turn on WIFI followed by an error.
Click to expand...
Click to collapse
Yea it could be the kernel because the thing you said about the 4ext recovery telling you that its loading the saved boot.img is what I always get and whenever i do get it, the rom always works perfectly. Also which version of speedrom did u try because I had the problem when I was using both 6.5 and 7.0. Try flashing the Supersaiyan 3 rom and then choose faux kernel from the AROMA INSTALLER. Then wipe as I told you in the posts before and then flash speedrom. It worked like that for me. Sorry if you still dont have luck!
What would happen if i deleted the boot.img file and flash a kernel?
Sent from my HTC_Amaze_4G using xda premium
pokey77 said:
What would happen if i deleted the boot.img file and flash a kernel?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Well OK I really want this to work for you after you mentioned the boot.IMG issue it may be that you need to flash an insecure boot image first. Here is the link http://forum.xda-developers.com/attachment.php?attachmentid=1223086&d=1343307912 for s-on people this usually needs to be flashed via fastboot and not recovery. However since 4ext recovery seems to be an exception to almost every rule regarding recoveries it may be able to flash it. If not just flash via fastboot I posted the forum topic link that this issue has been discussed on in one of my previous posts in this thread. I'm positive this is your problem now.
---------- Post added at 12:44 AM ---------- Previous post was at 12:36 AM ----------
Read through the issue on this page http://forum.xda-developers.com/showthread.php?t=1359951&page=181 seems like this is exactly the issue you are facing. I suggest after flashing which ever ROM flash fauxs kernel it's the best for the amaze anyway hope you get this to work I have exhausted the last bit of knowledge I have regarding this issue. Hence I s-off my device to avoid stupid issues such as these once and for all.
Should I try s-off before installing the GB ruu?
Sent from my HTC Amaze 4G using xda premium
I have officially stressed myself to the brink. I try to be calm but nowhere do I find how to fix my problem. I have tried flash image gui, I have tried htc dumlock, and I have also tried flashing the .img manually through fastboot usb then flashing the entire zip with twrp 2.2.2.0. Almost every time, I must recover from my TWRP and then use bootimg flasher v1.1 to stop my evo from getting stuck at the boot screen.
Everytime I attempt, I wipe the system and cache, then flash the boot.img, then flash the zip, then the gapps and reboot and it gets stuck on the splashscreen. I must note also that when I had first rooted, and installed Rom toolbox pro, I picked out a boot animation and installed it, restarted the phone, and it didnt work. BUT NOW sometimes after i flash the CM10 that random boot animation appears. WTF? even after i wipe the memory and everything. So I turned off the boot animation, and even deleted them from the phone off the app and it still comes up. I believe this is part or maybe IS the problem. But either way, I do not know how to deal with it. I have had the Cyanogenmod 10 boot animation ONCE out of the many times I have tried flashing but it was stuck on that screen forever like I have read other users have had happen. I REALLY, REALLY would like to be able to use the rom, as it has the new google now voice and all the cool features that i would like to have now that I am rooted.
NOTES:
I am running my stock rom. I have not installed any other ROMS on my phone. The backup i created was after I installed the stupid boot animation. (In case thats another problem)
When i tested the "current" boot animation from within rom toolbox pro, the normal htc evo 4g lte Sprint one loaded but yet, the retarded one i chose for ****s and giggles is what keeps loading. FML (I shouldve chose at least a cool one.)
My backup works fine. I am damn glad i made it!!!
Sorry for any grammatical errors, lowercase i's and what not. im too lazy to press the shift key sometimes. (Caps lock is broken. FML.)
Also sorry for it being so long. I am trying to be thorough to give you experts what you need to help me out.
If you need anymore info as far as detail instructions i will be happy to write back on this forum.
PLEASE do not tell me that my answer is on another forum, because I believe that it is not due to the special situation I have. I have tried looking for days for an answer.
I will be periodically checking this forum for any replies and will reply ASAP, whenever i am available.
Thank you for your time and patience!
Here is my phone's specs. I tried to get as much as possible. Again, if there is more info that would be needed I will gladly get it and post it here.
I am running on booloader:
Tampered
Unlocked
Jewel PVT SHIP S-ON RL
HBOOT- 1.19.0000
Radio- 1.12.11.0009
OpenDSP-v29.1.0.45.0622
eMMc-boot
Aug 9, 2012, 15:14:25
About Phone:
Hardware Version 0003
Android Version 4.0.4
Sorftware 2.13.651.1 710RD
HTC Sense Version 4.1
HTC SDK API level 4.24
HTCExtension_403_1_GA_22
PRI Version 2.45_003
PRL Version 25006
Anyone?
Sent from my EVO using xda app-developers app
What happens when u fastboot the kernel? Does it say success?
Sent from my EVO using xda premium
Use fastboot to flash the kernel, if you still have trouble wipe the partion and try again
Fastboot flash boot boot.img extract it from the Rom and place in adb folder.
Fastboot erase boot to wipe partition
I had problems trying out CM10 also. This worked for me.
Edit:: I'm assuming you have TWRP recovery and are unlocked before you start this...
Buy Flash GUI from app store. Worth the 99 cents!
Open it and point it to the CM10 zip. It will extract the parts it needs and flash the kernel.
Once that is done have it reboot (it prompts you) into recovery and then wipe system, do factory reset, then flash the CM10 zip and gapps zip.
Reboot one last time
The CM10 animation went on for a couple/few minutes the first time, don't panic.
You should be good after that.
Make sure to install Flash GUI again though. You will need to use it to go back to a ICS/Sense ROM later (using same method). And my guess is you might want to.
CM10 is incredible on this phone but it's not quite ready. I have tons of data connection issues and NEVER get 4G in the places where I've always had good signal. Also, the camera is just about worthless. No disrespect to the devs working on it. I'd have no idea how to work the magic they are doing and I appreciate their time.
Good luck.
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
When I fast boot the kernel everything says success with no errors
Sent from my EVO using xda app-developers app
How do you partition? Do you think that is my problem?
Sent from my EVO using xda app-developers app
You don't need to partition anything, just flash kernel and reboot
Hey guys thanks to everyone replying! I'm currently at work as a delivery driver trying to write back.... Dangerous! Lol but also I have the 5 min limit to post so I will try and do some of these methods when I get home and report my findings to you all ASAP! But to anyone with more suggestions please keep bringing Em!
Thanks!
Sent from my EVO using xda app-developers app
Hey guys its me again. I just got home and I'm dead beat tired. I had to work later than I thought. Im gonna get some sleep but once again thank you everyone for giving me some answers that I can try tomorrow! I will, without a doubt, try some of them tomorrow after my classes. But first I would like to leave you all with a VERY important question that I did not think of. Is there a stable release of cm10 that has worked for you all that I can try? Perhaps that was the problem too? I was trying the nightly release that came out October 2. Once again thank you all for replying and i will try to do this ASAP after class. Sorry to leave you guys hanging so much!
Sent from my EVO using xda app-developers app
Thing is it's a nightly, some people have flashed back to earlier versions and others upgrade with out any issues. Ymmv
padrino121 said:
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
Click to expand...
Click to collapse
Which nightly did you use?
Hey guys so I used padrino121s suggestion for flashing. At first I tried flash gui again like you had suggested but it got stuck in the boot screen. So I decided to download a different nightly release (20121002) and it flashed perfectly and everything transferred over correctly! Thank you guys so much for all of your help! Now one more question... If I decide to get a new nightly build, do I have to flash everything all over again like I had to the first time? Or because I have flashed cyanogen mod already do I just do something else to update it?
Sent from my EVO using xda app-developers app
I have followed all instructions for flashing carefully. I have tried going back to TWRP 2.7.0.0b I have tried putting ROM zip on internal and external storage. I have rebooted recovery after wiping also tried without wiping. Tried to flash: Beanstalk, Paranoid, Carbon, PAC. All for new partition layout. I am S-off with firewater hboot 2.10.5555. The only ROM that has flashed successfully is Omni. I keep getting this error:
See picture.
Any help or info would be much appreciated.
Sent from my Nexus 5 using XDA Premium 4 mobile app
After wiping did you reboot to recovery before trying to flash again?
HTC Jewel
HBOOT 2.10 S-OFF (rumrunner)
Android 4.3 Sense 5.5 V3
Yes.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
naveen6252 said:
I think the ROM you want to flash doesn't seems for your device. Contact the rom developer it looks like the developer doesn't get the assert file correctly.
Try the toggle signature verification option in recovery before installing the rom. Check that the rom is for your device or not. The recovery prevent the user to install any incorrect ROM as it can hard brick your device. So make sure that ROM is for your device or not.
Sent from unnamed ROM using xda premium app
Click to expand...
Click to collapse
Thanks but I am sure I'm flashing the right ROM for my device. This just started happening recently. I just flashed the newest Omni just posted and that flashes too. Superuser flashes as well as gapps. I thought this might have been related to updating my TWRP to 2.7.0.4b which is why I flashed back to 2.7.0.0b and I got the same errors. Backups restore with out issue as well.
Sent from my EVO using XDA Premium 4 mobile app
Could this possibly be an issue with the firewater hboot?
EVOlved human
Evolution_Freak said:
Could this possibly be an issue with the firewater hboot?
EVOlved human
Click to expand...
Click to collapse
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
FinZ28 said:
Don't see that being an issue, unless you're on the older partition setup, which it seems you aren't. Have you tried an older version of TWRP that's built for the updated partition setup?
After looking at your picture of the failed flash, it appears that the issue is with the updater script. You can extract all the files and edit the updater script, then zip everything back up. You might also disable signature checking in TWRP if it's enabled. I've run across the same issue using CWM Touch and I usually either revert to TWRP or edit the updater script.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Fin! I will check on the signature checking. I did try going back to 2.7.0.0b but didn't try any older versions. As I said, this just started happening and is only with some ROMs.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Just checked and signature checking was disabled already. I will try your other recommendations next.
EVOlved human
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
aarsyl said:
Are those roms that were on your device from before? Or are they all new downloads?
I really suggest rolling ball to TWRP 2.6.3, and see if you have better luck. I have had zero issues, and I have no reason to update TWRP until there's a new feature that I will actually want/need.
Click to expand...
Click to collapse
New downloads.
EVOlved human
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
aarsyl said:
And you are sure that you are downloading the correct files? Maybe it's just me, but it took me a while to find the correct version of numel's PAC rom.
Click to expand...
Click to collapse
Yes, I'm sure. I just reverted back to TWRP 2.6.3.1b and I'm downloading Paranoid at the moment. Will update if it flashes.
Sent from my EVO using XDA Premium 4 mobile app
I'll be waiting for your response.
aarsyl said:
I'll be waiting for your response.
Click to expand...
Click to collapse
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Evolution_Freak said:
Negative. Failed with the same error. From what I can determine, the updater script is looking for HBOOT 2.10.0000 and I have firewater 2.10.5555. I'm pretty sure this is why some ROMs are failing and others are not. I've got to learn how to edit the updater script as I've never done that before.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Update:
I re-ran the RUU to bring my HBOOT back to 2.10.0000. I remained unlocked and S-off as is well known. I installed twrp 2.7.0.0b via bootloader and I'm now about to try flashing again. Will update again after trying.
Sent from my EVO using XDA Premium 4 mobile app
aarsyl said:
Can't the script be updating in simple notepad? There is a lot of English in the updater-script file. Not entirely sure what you'll have to do, but I will surely check for you.
Click to expand...
Click to collapse
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
FinZ28 said:
I always edit it with Root Explorer on my phone. You just have to edit out the lines dealing with the bootloader & device name. Fairly simple. It takes longer to extract the files and zip everything back up once you're done:thumbup:
Sent from my EVO LTE
Click to expand...
Click to collapse
That's what I figured, but I'm at work, so my assistance is limited.
aarsyl said:
That's what I figured, but I'm at work, so my assistance is limited.
Click to expand...
Click to collapse
No worries. The biggest thing is to make sure you don't flash the wrong ROM on the wrong device when you edit out those parts of the updater script. Could spell trouble
Sent from my EVO LTE