Related
Dual / Multiple Rom Booting For Our HTC Evo 3D
Jelly Bean - Gingerbread - Ice Cream Sandwich - Paranoid Android
all "booting" succesfully
new edits 15/07/2014
im now gonna try kitkat and other rom versions, bare with me though, i only just got my new phone
s offed, unlocked bootloader, rooted and recovery all done, but now i gotta trial and error roms
ive noticed bootmanager fails to download neccessary files, i think this is due to the init 2 winit servers no longer online
but i have a fix, download my titanium back files in attachments, and place on your sd in your tb back up folder, then restore data, worked for me
But......
also compatible with HTC Desire, HTC Desire HD, HTC Desire S, HTC Supersonic 4g, HTC Incredible 1, HTC Incredible 2, HTC Incredible s, HTC Inspire 4g, HTC Vision, HTC Thunderbolt, HTC Sensation, Motorola Droid 1, Motorola Droid 2, Motorola Droid 2 global, Motorola Droid x, Nexus One, MyTouch 4g, Samsung Galaxy Nexus
If you have a device above and want help please pm the link to your thread
AS MENTIONED ON DRIPPLER
\/\/\/\/
\/\/\/
\/\/
\/
<ROM 1
<ROM 2
ROM 3>
Rom 4>
NINO-BOOT VIDEO IN POST 2
First things first
S-off and Root required
"At the moment" Aroma scripted Roms and Kernels are not yet compatible on slot 2+, unless restoring from a Nand backup, which is pre configured
:victory: Good luck, and enjoy :victory:
STEPS ON HOW TO DO IT
1. ensure your happy with the current state of your main/daily rom
2. NAND - back it up
3. download, install and configure either the free boot manager lite app or the pro version
4. NAND - back it up (not necessary, but advised)
5. download your scondary rom zip
6. open your downloaded bootloader app and slide accross to slot 1
7. install your chosen rom (do not wipe anything on first install)
DO NOT BOOT SECONDARY ROM
8. NAND - back it up, again (if your low on sd space, delete your earliest nand, and then next etc etc)
9. open boot manager when booted, and slide to slot 1, and boot rom
10. "Ta da". your now dual booting,
11, repeat these steps for further slots for tri/quad/etc booting
Tips
DO NOT RUN V6 SUPERCHARGER OR SIMILAR SCRIPTS ON ANY ROM OTHER THAN PHONE ROM, YOU WILL GET STUCK IN A BOOT LOOP
DO NOT SET UP PHONE ROM WHILE BOOTED TO A SLOT ROM
revert hboot
(read below and follow my guide)
........................................................................................................................................................................................................................................................................................................................
HELPPLEASE READ ALL THIS, BELOW, BEFORE TRYING STEP 1
..........................................................................................................................................................................................................................................................................................................................
HBOOT
after a major error recently I' found that for some reason I was struggling to even dual/tri/quad boot, after reverting to stock ics and updating my hboot to 1.49.0053 , I managed to find a patch to revert my hboot back to its original 1.49.0007 , il attach below, I recommend everyone flash this GO USE THE GUIDE HERE , all you do is place on root of your sd card (GSM USERS ONLY AS FAR IS I'M AWARE (CDMA TESTING APPRECIATED)), Then boot into bootloader and select yes when it reads the PG86IMG, I found after going back to this hboot , bootmanager was then able to edit boot.IMG correctly again
(added ALL CID'S to the pg86img.zip android text folder)
WILL WORK FOR EVERYONE
AROMA ROMS / KERNELS
Some people are having issues with certain roms/aroma scripted roms, the best way around it is to set up all roms on phone Rom slot (main) then back up, restore your original Rom to main, boot it, then in boot manager . Restore nands of other set up roms to other slots
SWITCHING ROMS
Ensure all roms you want to boot into and out of, are Gapps (google apps) installed, ensure you have set up phone in bootmanager while booted to your phone Rom, and that you have opened boot manager in your slot rom(s) at least once so bootmanager app can download files needed and to write folders to sd
BOOT IMG
If you find that your bootmanager can't create boot.IMG (not edit), navigate to the bootmanager folder on your sd, find the boot.img file in the slot your trying to install on, delete it, then restart bootmanager , and it should create it without problems,
IF NOT,
Try putting boot.img in the rom1/rom2/whateverslot you are using n the bootmanager folder on the sd card, then try just installing a different kernel to overwrite it, so it fixes it. thanks to meangrenie or making this common knowledge
if you ever run into problems, pull the battery, boot to hboot, select recovery, and flash the update.zip inside the phoneRom directory. It writes your backed up boot image. thanks too $MyName for making this common knowledge
BUGS
(currently)
When booted to a jellybean Rom there is a charging/battery reading issue and in some cases data drop/connection problems
...................................................................................................................
THANKS
Please go here for full developer support
http://init2winitapps.com/stories/B...a-developers.com/member.php?u=469311"]Pauly_k , for bringing the app to my attention
Youtube videos
sorry about the quality, had to do a lot of converting to get youtube to allow it, and also to keep my data down, using 3g
part 2 begins 3 seconds before part 1 ends, just to show it is 1 complete video with no breaks in recording
Part 1
Part 2
HERES A VIDEO OF ME NINO-BOOTING BETWEEN
Jelly Bean , Paranoid Android, Gingerbread and ICS Roms,
some stock, some custom
Thanks for the guide.
I think its "ta da" lol
youdug said:
Thanks for the guide.
I think its "ta da" lol
Click to expand...
Click to collapse
Yeah lol, your right , edited
Dual booting jellybean&Meanrom 1.9
Phone:HTC Evo 3D CMDA
HTC Sense:3.6
Software number:MeanROM ICS v1.9
Kernel version:?????
Baseband version:1.06.00.1216
Build number:1.13.662.2_RC
HBOOT:1.50 S-off (juopunutbear)
Recovery:4EXT Recovery Touch v1.0.0.5 RC 5
Thank, I'm using its apk the different 3 ROM ( gingerbre, Mwakious and Yoda).
Sent from my HTC EVO 3D X515a using xda app-developers app
ok i'm maybe having a slow moment. are there any stock unrooted rom zips that are compatible with this app.
because i couldn't find any stock unrooted rom zips.
or is it possible to dowload an ruu exe, and rename it to ruu zip
gingerbread preferred
No, the app requires root to work.
So, if you install any unrooted Rom in a slot , you will not be able to boot back to phone Rom. Your phone Rom needs to be rooted to install any other Rom on a slot.
---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------
msuug said:
ok i'm maybe having a slow moment. are there any stock unrooted rom zips that are compatible with this app.
because i couldn't find any stock unrooted rom zips.
or is it possible to dowload an ruu exe, and rename it to ruu zip
gingerbread preferred
Click to expand...
Click to collapse
...
Sounds great! i will surely try this out.
No more endless recovery circles like wipe cache/dalvik, install from zip blah blah restore etc.
Could be very practical.
Is it reliable once its up and runnig?
Hello everybody, I need a help, the program installed correctly but when I boot my phone in the second rom not leave the screen of htc.
bohdee said:
Hello everybody, I need a help, the program installed correctly but when I boot my phone in the second rom not leave the screen of htc.
Click to expand...
Click to collapse
Are you sure your second Rom is a complete version ? Bootable normally as a main Rom ? If it is. Restore from your most recent back up and try again, bit give your dalvik cache a wipe , once you have restored your back up and before trying again
flash the zip located in bootmanager/phonerom....in recovery and you should be able to boot your phone Rom just fine.
Thanks for the help guys.
It works
Thanks 4 the guide!
Works as it is declared. I installed the free app and installed a ROM to slot1.
Unfortunately the app needs constant internet connection? Well i had a situation where the installed rom had a Wi-fi issue and I coludn't start the app and boot back to my phone ROM. That's a bit of a shortcoming. Or it may be that I don't see all the issues straight (why there has to be an internet connection at all for the app to do its thing)
One more thing... the installed ROM had taken 2GB of space on my SDCARD. And a 4ext recovery backup takes up to 1GB max.
marC00Linho said:
Thanks 4 the guide!
Works as it is declared. I installed the free app and installed a ROM to slot1.
Unfortunately the app needs constant internet connection? Well i had a situation where the installed rom had a Wi-fi issue and I coludn't start the app and boot back to my phone ROM. That's a bit of a shortcoming. Or it may be that I don't see all the issues straight (why there has to be an internet connection at all for the app to do its thing)
One more thing... the installed ROM had taken 2GB of space on my SDCARD. And a 4ext recovery backup takes up to 1GB max.
Click to expand...
Click to collapse
If you read the guide again, I tell you to nand back up at each step, and give information on how to keep both roms safe and working and if neccessary, delete a back up before making a new ,one also I use a 32gb sd, and I use 4 ext, latest, and I've never had a problem backing up, its also such a big back up, because it backs up, both roms , every back up. Try re reading the guide and starting again with your daily Rom
if you are connected to internet/wifi it will take time to start , if you turn them off, it will start quickly....
mnomaanw said:
if you are connected to internet/wifi it will take time to start , if you turn them off, it will take time...
Click to expand...
Click to collapse
??? So either way it takes time... awesome to know... gonna have to try this on the wifes phone! Thanks!
flastnoles11 said:
??? So either way it takes time... awesome to know... gonna have to try this on the wifes phone! Thanks!
Click to expand...
Click to collapse
oops.! corrected..
Just to be clear, is this simply a guide to set up Boot Manager or will this setup give me a bona fide dual booting machine?
Stikman72 said:
Just to be clear, is this simply a guide to set up Boot Manager or will this setup give me a bona fide dual booting machine?
Click to expand...
Click to collapse
Both?
Sent from my HTC EVO 3D X515a using xda premium
Looking for a compatible rom for an htc one m7wls (sprint) running twrp 2.6.3 I have tried several and cant seem to find any that are compatible. Secondly do I have to flash the unzipped boot.img file that's with the rom after I flash the rom? I have tried viper, beanstalk, android revolution and cant seem to find any to get my phone back up and working again, it has no os on it at the moment. Thanks for all your help any suggestions and help would be awesome
Tommyboy77 said:
Looking for a compatible rom for an htc one m7wls (sprint) running twrp 2.6.3 I have tried several and cant seem to find any that are compatible. Secondly do I have to flash the unzipped boot.img file that's with the rom after I flash the rom? I have tried viper, beanstalk, android revolution and cant seem to find any to get my phone back up and working again, it has no os on it at the moment. Thanks for all your help any suggestions and help would be awesome
Click to expand...
Click to collapse
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
hello
es0tericcha0s said:
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
Click to expand...
Click to collapse
Well I installed the ecliptic custom rom and it installed correctly however I can not text or use the phone features just wifi works.....I accidentally erased the os before I put the custom rom on.....could you help me figure out how to know what sprint stock rom I can go back to stock on ? I was told in order to get my calling and text features back I need to reload a sprint stock rom then go back to a custom rom if I wished however I just need to know what sprint stock rom I can use. thanks for all your help
es0tericcha0s said:
Unless you are S-Off (not just HTC Dev unlocked) then you will need to fastboot flash the boot.img in fastboot mode as well. Any of those roms should work fine if installed correctly. Just make sure that you have the appropriate firmware installed as well to make sure that the touch and other functions work properly. This means if you're original stock system was 4.2.2 and you are installing a 4.3 or 4.4.2 rom (at least Sense based) then you will need to install the firmware package as well for that update. How you install that depends on S-Off or HTC Dev unlocked, I believe.
Click to expand...
Click to collapse
If you could please send me a link to the correct sprint m7wls sprint stock rom I can use to get back to root to get phone working that woujld be awesome....so after adb pushing the zip to my internal sed card I can use twrp to install it I take it? then flash the included boot .img with the rom after flashing the rom to get it to work correct right?? just want to make sure im doing the right thing instead of going in circles.
Tommyboy77 said:
Well I installed the ecliptic custom rom and it installed correctly however I can not text or use the phone features just wifi works.....I accidentally erased the os before I put the custom rom on.....could you help me figure out how to know what sprint stock rom I can go back to stock on ? I was told in order to get my calling and text features back I need to reload a sprint stock rom then go back to a custom rom if I wished however I just need to know what sprint stock rom I can use. thanks for all your help
Click to expand...
Click to collapse
Weird that that one isn't working, but just shoot for a regular Sprint based custom rom like Bad Boyz and you should be fine. What was your previous firmware/OS before you wiped it? Which baseband are you using? Which version of the rom are you trying to use now? What recovery are you using? What happens when you try to make a call or text - error code or message? But either way, if you load a regular or custom Sprint based rom and update your PRL and Profile, then you should be fine to switch back to another rom, if wanted. This is why it's always good to both make a nandroid, and to save it in a save space, if needed, for times like this.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Tommyboy77 said:
If you could please send me a link to the correct sprint m7wls sprint stock rom I can use to get back to root to get phone working that woujld be awesome....so after adb pushing the zip to my internal sed card I can use twrp to install it I take it? then flash the included boot .img with the rom after flashing the rom to get it to work correct right?? just want to make sure im doing the right thing instead of going in circles.
Click to expand...
Click to collapse
You are correct about adb pushing the zip to internal, flashing, then fastboot flashing the boot.img to finish. I can't make a suggestion of which rom to use without knowing what you were using before though so everything will match up and work properly (firmware, baseband, OS, etc).
Hello
es0tericcha0s said:
Weird that that one isn't working, but just shoot for a regular Sprint based custom rom like Bad Boyz and you should be fine. What was your previous firmware/OS before you wiped it? Which baseband are you using? Which version of the rom are you trying to use now? What recovery are you using? What happens when you try to make a call or text - error code or message? But either way, if you load a regular or custom Sprint based rom and update your PRL and Profile, then you should be fine to switch back to another rom, if wanted. This is why it's always good to both make a nandroid, and to save it in a save space, if needed, for times like this.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
You are correct about adb pushing the zip to internal, flashing, then fastboot flashing the boot.img to finish. I can't make a suggestion of which rom to use without knowing what you were using before though so everything will match up and work properly (firmware, baseband, OS, etc).
Click to expand...
Click to collapse
Well I tried installing bad boyz 5514 and the old version 5512.....then I flash the boot img.....it installs fine however when it gets to unlock the screen it sneds me in a reboot...happened for both versions any ideas whats wrong?
Tommyboy77 said:
Well I tried installing bad boyz 5514 and the old version 5512.....then I flash the boot img.....it installs fine however when it gets to unlock the screen it sneds me in a reboot...happened for both versions any ideas whats wrong?
Click to expand...
Click to collapse
Might need to do another factory reset. But I've already said repeatedly that it is important to know what the original firmware / software was on the phone before it started having issues and its because of troubleshooting issues like this as well as it is just important on most HTC phones to have these things matching properly between the firmware and OS as well as the radio.
hello
es0tericcha0s said:
Might need to do another factory reset. But I've already said repeatedly that it is important to know what the original firmware / software was on the phone before it started having issues and its because of troubleshooting issues like this as well as it is just important on most HTC phones to have these things matching properly between the firmware and OS as well as the radio.
Click to expand...
Click to collapse
I completely erased my entire phone including the os and don't know what firmware software was on the phone to begin with was stock sprint....so I don't know what firmware was on there or os or radio
Tommyboy77 said:
I completely erased my entire phone including the os and don't know what firmware software was on the phone to begin with was stock sprint....so I don't know what firmware was on there or os or radio
Click to expand...
Click to collapse
Then it is recommended to run the newest RUU to make sure your partitions, OS, radio, and firmware are all properly matched. Once that happens, you can just fastboot flash a recovery back and then redo whatever 4.4 rom you want at that stage. Yea, it sucks to have to do the extra steps, but some things you just have to do to make sure everything works properly. It never pays to cut corners when you need your phone to function correctly.
http://forum.xda-developers.com/showthread.php?t=2658910
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....
so my charging port has a factory defect and I need to return to stock htc sense before I send it in,
I flashed skydragon rom and i tried to return to a backup and it keeps giving me errors
i've tried everything from a ruu to nandroid backups i am stuck and i have no idea what to do no other roms will flash except cyanogenmod and i cant flash anything from there either please help!
noahthefrancis said:
so my charging port has a factory defect and I need to return to stock htc sense before I send it in,
I flashed skydragon rom and i tried to return to a backup and it keeps giving me errors
i've tried everything from a ruu to nandroid backups i am stuck and i have no idea what to do no other roms will flash except cyanogenmod and i cant flash anything from there either please help!
Click to expand...
Click to collapse
Are you S-OFF by chance ?
All you did was flash Skydragon ?
Are you using an up to date custom recovery ( try an alternative custom recovery with a stock backup zip/ROM )
thank you so much for the fast reply and ya i am s-off and all i did was flash skydragon (lollipop 5.0.1) and i could try flashing an alternate recovery.
tried updating twrp.. no luck gonna try phillz recovery
update tried phillz recorvery same issues when going to flash roms. (some sym_link errors/Installation error status 7) and if i go to reboot the rom with the errors for some reasons it thinks im not rooted. I am able to flash to cyanogenmod 4.4x and 5.x.x no problem and the skydragon rom that messed me up in the first place. ANY HELP WOULD BE GREATLY APPRECIATED.
K so your S-OFF and all you did was flash Skydragon ROM .
So follow the instructions in the below thread to the "T" as it is an ruu of At&t 4.4.3 as if you took the OTA
http://forum.xda-developers.com/showthread.php?t=2860486
Then if you need to go through any of the steps in the next thread than pic and choose witch you need removed and follow them
http://forum.xda-developers.com/showthread.php?t=2751011
Latest version (2.8.3.0) of TWRP require updated hboot (don't know about Philz). So if you are hboot <3.19, this may be part of your issue. TWRP 2.8.1.0 should be okay. Normally, I recommend having the most up-to-date recovery version, but this is an exception.
If all you did was flash Skydragon ROM, then you should have any issue going back to Sense simply by flashing a different ROM. Errors with ROMs not flashing are often resolved by wiping cache and re-installing recovery.
so i tried downgrading twrp to the 2.8.1.0 and viper wont work. not sure how i am supposed to flash the ruu file through hboot i really need to figure this out before tonight ive spent countless hours on trying new things
**tried other roms maybe its the aroma installer? everything i try gives me the "symlink: some symlinks failed
noahthefrancis said:
so i tried downgrading twrp to the 2.8.1.0 and viper wont work. not sure how i am supposed to flash the ruu file through hboot i really need to figure this out before tonight ive spent countless hours on trying new things
**tried other roms maybe its the aroma installer? everything i try gives me the "symlink: some symlinks failed
Click to expand...
Click to collapse
You download the ruu that's not an exe file and rename it to
" 0P6BIMG.zip" and place it in the root of your external sdcard
Once you have it renamed and where it should be than boot to hboot/bootlooader and it will read the zip and ask what you want to do(push volume-up )
If you want the thread that explains how to do this than you can Google
" how to ruu using hboot HTC one m8 Xda"
and I guarantee it will lead you back to Xda with more detailed instructions that we all have followed
I do enjoy helping but sometimes we can benefit from searching and learning from what's already posted
so i tried that and done a large amount of research and everytime i add the file to the root of my sd card it gives me an error and tells me to power down and i do that and it repeats the only way to stop it is to take the sd card out. Im going to try flashing a stock htc rom without aroma (for some reason i think this is the issue) For what its worth im on hboot 3.19 and cws__001 any further help would be fantastic
noahthefrancis said:
so i tried that and done a large amount of research and everytime i add the file to the root of my sd card it gives me an error and tells me to power down and i do that and it repeats the only way to stop it is to take the sd card out. Im going to try flashing a stock htc rom without aroma (for some reason i think this is the issue) For what its worth im on hboot 3.19 and cws__001 any further help would be fantastic
Click to expand...
Click to collapse
I'm still here trying so bare with me.
Are you making sure the first character is a "zero" and not an "o" and the extension is lower case ".zip"
So hboot finds the update and fails so matter what
jball said:
Are you making sure the first character is a "zero" and not an "o" and the extension is lower case ".zip"
Click to expand...
Click to collapse
Also, make sure you don't have the Windows option enabled to hide the file extensions (its enabled by default). You might have renamed the file named .zip.zip and not realized it (a relatively common mistake).
So I have downloaded the file to both my PC and my phone and I copy it to the root of the SD card. I used root browser to do that on my phone and I made all the letters caps,retried it 100 times and it doesn't work.it gives me an error when I boot into the boot loader that says its not the correct zip. Do I need to wipe the cache before I do it or am I missing something .
noahthefrancis said:
So I have downloaded the file to both my PC and my phone and I copy it to the root of the SD card. I used root browser to do that on my phone and I made all the letters caps,retried it 100 times and it doesn't work.it gives me an error when I boot into the boot loader that says its not the correct zip. Do I need to wipe the cache before I do it or am I missing something .
Click to expand...
Click to collapse
Can you take a picture of your bootlooader/hboot and post it
jball said:
Can you take a picture of your bootlooader/hboot and post it
Click to expand...
Click to collapse
here you go.. It seems to recognize that its an 0p6Bimg.zip but it fails
Your hboot shouldn't be dark unless you are GPE out of the box or you ruu GPE .
The file should look just like this
0P6BIMG.zip
---------- Post added at 03:23 AM ---------- Previous post was at 03:10 AM ----------
@noahthefrancis
With the no os being blank you need a Sense firmware named correctly to ruu first and then follow up with the full stock based ruu named correctly
thats so weird i never did the ruu for the gpe and it was white before i flashed the rom... hmm soi need to flash the sense firmware then boot into hboot and it should work.
noahthefrancis said:
thats so weird i never did the ruu for the gpe and it was white before i flashed the rom... hmm soi need to flash the sense firmware then boot into hboot and it should work.
Click to expand...
Click to collapse
Can try
---------- Post added at 05:20 AM ---------- Previous post was at 05:12 AM ----------
Reading back it now sounds like the failed message is cause it thinks your fully converted and rejects cause of the partition sizes are substantial different (just a thought)
jball said:
Can try
---------- Post added at 05:20 AM ---------- Previous post was at 05:12 AM ----------
Reading back it now sounds like the failed message is cause it thinks your fully converted and rejects cause of the partition sizes are substantial different (just a thought)
Click to expand...
Click to collapse
so my os slot is no longer blank which is good. but the ruu file still is giving me the same errors, what do i have to do to get my bootloader from black
(gpe) to the white it came with before flashing the initial rom?
noahthefrancis said:
so my os slot is no longer blank which is good. but the ruu file still is giving me the same errors, what do i have to do to get my bootloader from black
(gpe) to the white it came with before flashing the initial rom?
Click to expand...
Click to collapse
So what did you do to get an OS ?
Did you flash a firmware ?
Q&A for ★ ☆ [ROM/RADIO][4.4.2] Stock 4.09.605.5 | Rooted | Sense 5.5
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/RADIO][4.4.2] Stock 4.09.605.5 | Rooted | Sense 5.5. 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!
bootloop when flashing 4.09.605.5 Rooted to DNA using CWMR
Hi there, long time follower of these forums, first time posting. I can usually find what I need but I couldn't in this case. My primary question is, do I HAVE to flash the ROM zip with oem RUU?
I am unlocked with s-off. I installed CMWR and CWM SU. For some reason I originally thought I had to install the ROM update before the updated FW. I tried to Flash odex debloated update with CWM (selecting option in Rom Manager to delete data and cache before flashing), but it boot loops on white htc splash screen. I recovered/restored previous image via CWMrecovery. I installed CM11 (4.4.4 base), then flashed RUU via fastboot, in order to install new FW via fastboot (had to flash twice, just like instructions state), rebooted into CM11/4.4.4, FW seems to have installed fine. Flash CWM recovery again, make ROM backup. Tried to flash odex/debloated 4.09.605.5 with CWM (again selecting delete data / cache before flashing), but now freezes on the black/red android eye every time I try to boot. Tried to flash full odex with CWM (after full wipe again), again it freezes on the black/red android eye screen. Each time it freezes or bootloops I am at least able to reboot into recovery and revert to CM11. I recovered to my original backup (rooted stock 4.2.2), verify it shows I have the updated radios, and from there try to flash the full odex update (without wiping data/cache this time) through CWM since I have the updated FW. Bootloops on HTC splash screen, as it did before. Then I wiped everything and restored to CM11/4.4.4 ROM.
I am afraid that if I fastboot flash the update with RUU and I get bootloops or frozen boot that I won't be able to recover from it, unless the answer is that I have to do it that way.
ra2dc said:
Hi there, long time follower of these forums, first time posting. I can usually find what I need but I couldn't in this case. My primary question is, do I HAVE to flash the ROM zip with oem RUU?
I am unlocked with s-off. I installed CMWR and CWM SU. For some reason I originally thought I had to install the ROM update before the updated FW. I tried to Flash odex debloated update with CWM (selecting option in Rom Manager to delete data and cache before flashing), but it boot loops on white htc splash screen. I recovered/restored previous image via CWMrecovery. I installed CM11 (4.4.4 base), then flashed RUU via fastboot, in order to install new FW via fastboot (had to flash twice, just like instructions state), rebooted into CM11/4.4.4, FW seems to have installed fine. Flash CWM recovery again, make ROM backup. Tried to flash odex/debloated 4.09.605.5 with CWM (again selecting delete data / cache before flashing), but now freezes on the black/red android eye every time I try to boot. Tried to flash full odex with CWM (after full wipe again), again it freezes on the black/red android eye screen. Each time it freezes or bootloops I am at least able to reboot into recovery and revert to CM11. I recovered to my original backup (rooted stock 4.2.2), verify it shows I have the updated radios, and from there try to flash the full odex update (without wiping data/cache this time) through CWM since I have the updated FW. Bootloops on HTC splash screen, as it did before. Then I wiped everything and restored to CM11/4.4.4 ROM.
I am afraid that if I fastboot flash the update with RUU and I get bootloops or frozen boot that I won't be able to recover from it, unless the answer is that I have to do it that way.
Click to expand...
Click to collapse
Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
santod040 said:
Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
Click to expand...
Click to collapse
tarp? was that an auto-correct fail? the only thing I could dig up as what you might have meant is TWRP, have never used it before, but should I flash TWRP if I'm on CM11, and then flash the odex debloated rooted 4.09 ROM directly from CM11, or should I recover to stock (rooted) 4.2.2 first and then flash the update with TWRP? Should I do a full wipe? I assume if I'm doing a full wipe it doesnt matter where I'm coming from (which means I can try right from CM11), and I also assume I can flash TWRP while on CM11, but haven't tried yet.
thanks for the answers
santod040 said:
Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
Click to expand...
Click to collapse
Thanks I tried with TWRP and at first I thought it froze again on the android eye, so I restarted and it froze again, but I put my phone down and left, came back in 10 minutes and it was on the home screen. It must take a while to boot the first time, doh! Maybe CWM actually worked and I was just impatient.
Now I have new issues though, adroid wifi tether app doesn't work (I've read many blogs, I tried all of the suggested settings), it starts with errors but the log doesnt record anything, and I get terrible reception. Maybe I'll try the debloated but that probably won't fix the reception thing. Verizon says I might have to factory reset, but I don't know how that will impact my root-ability
ra2dc said:
Thanks I tried with TWRP and at first I thought it froze again on the android eye, so I restarted and it froze again, but I put my phone down and left, came back in 10 minutes and it was on the home screen. It must take a while to boot the first time, doh! Maybe CWM actually worked and I was just impatient.
Click to expand...
Click to collapse
I've seen the same thing after flashing certain things - adb shell "top -m 10" revealed that it was dex2oat which I believe is handling one-time code compilation on first boot. Eventually the GUI loads and I see "android is upgrading (apps)..." for part of the first boot process.
ra2dc said:
Now I have new issues though, adroid wifi tether app doesn't work (I've read many blogs, I tried all of the suggested settings), it starts with errors but the log doesnt record anything, and I get terrible reception. Maybe I'll try the debloated but that probably won't fix the reception thing. Verizon says I might have to factory reset, but I don't know how that will impact my root-ability
Click to expand...
Click to collapse
Factory reset should not impact your root-ability but mostly the same system software will be running afterward so I find it rarely resolves core issues with ROM compatibility or my installation of it. Might be worth a shot tho, I suppose clearing out device settings and such could help fix tethering.
firmware update question
First...A big thank you for all the tremendous development work!
Wanted to report a curious thing. When I updated firmware using 4.09.605.5 NoBootImg_firmware.zip; it finished in one step without stopping. Never asked to "flush again" as mentioned in the OP. So I was just wondering if I did something wrong. After reboot, the phone now shows the updated baseband 1.02.01.0818. So far, seems like all is in order. Any comments would be greatly appreciated.
DNA (HTC6435LVW) RELOCKED S-OFF problems flashing to rooted stock
First time poster on XDA. Please forgive any impropriety!
I went through the process of flashing the 4.09.605.5 Rooted Full Odex Stock Kitkat (RUU RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2.exe) and latest firmware for the DNA from this thread. Everything went fine but when I tried to boot into stock the Verizon splash screen came up for a second and then the image became scrambled and then nothing. I waited for several minutes to see if the phone would boot to the Stock rom but didn't.
My phone is a relocked s-off DNA currently running latest version of CM and TWRP. More phone details:
hboot 1.57
radio 1.02.01.0818
CM 11-20141112-SNAPSHOT-M12-dlx
kernel 3.4.10-CM
Here's the steps I followed:
Downloaded latest stock RUU rom ( RUU RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2.exe) from this thread - http://forum.xda-developers.com/showthread.php?t=2560010
Downloaded latest firmware from same thread - 4.09.605.5_NoBootImg_Firmware.zip.
Verified MD5 on both downloads
Boot into fastboot
Successfully flashed latest firmware via fastboot RUU
Boot into TWRP
Wiped phone from TWRP
Successfully flashed latest stock rom via TWRP
Reboot phone
Stuck on scrambled Verizon splash screen
I was able to restore my CM rom from backup using TWRP, but I'd really like to go to rooted stock because some functionality is missing in CM (headphone jack doesn't work for one thing, intermittent radio/3g issues).
Thanks in advance for any help you can provide!
DNA (HTC6435LVW) RELOCKED S-OFF problems flashing to rooted stock
I'm familiar with flashing custom roms/recoveries and have been doing so for a few years now with no problems. I have a DNA that is Relocked with S-Off. Recovery is ClockWorkMod recovery. Backups and restore of CM 11 ROM works fine. I've been having intermittent problems with signal strength and 3G as well as headphone jack doesn't work with CM, so I decided to try going back to a rooted 'stock' ROM which I found at http://forum.xda-developers.com/showthread.php?t=2560010. I flashed the latest firmware update from the same thread. Then I downloaded the file marked "4.09.605.5 Rooted Odex Debloated Stock Kitkat" and installed it from CWM with no problems. I did a wipe data/factory reset before I flashed the ROM as suggested. When I attempted to boot up to the new ROM it got stuck on the Verizon splash screen. The splash screen came up and almost immediately the image became scrambled (no, not like eggs . I waited about 5 mins for it to come up and then forced a hard-reboot into CWM by holding down the power button and reflashed my backup of CM 11.
Anyway, anyone have any ideas on what I can try to get the stock rooted ROM image up and running?
Current system is...
HBOOT 1.57
RADIO 1.02.01.0818
S-OFF
CID VZW__001
ANDROID 4.4.4
CM 11 ROM
KERNEL 3.4.10
CLOCKWORKMOD RECOVERY
Nice ROM Cook
I love it, stable is so good
Santod, Will Xposed framework work with 4.09.605.5 Rooted Deodex Debloated Stock Kitkat. I do not see it installed and was wondering which one would work with this ROM. Thank you
Update, found it installed it, working great, cheers
I just can feel gratitude
I JUST CAN FEEL GRATITUDE
TY TY TY TY TY ...
Friend you are the best develoader for Android and for HTC DROID DNA,
your work is impeccable, faultless, dapper, and Excelent.
I hope someday give you more that the thanks.
a hug, you're the best.
greetings from Latin America.
Any eta on de bloated versions bring available? Grandfathered in on Verizon unlimited plan and need my high speed laptop internet fix with hotspot and would like to update firmware and ROM at same time. Thank you at for the best ROM I've found so far
Can I use this ROM in HTC J Butterfly HTL21 Japan Version?
Hi, I have HTC J Butterfly HTL21 japan version (au KDDI operator).
Right now, it is installed with the ported ROM from here [ROM][GSM/CDMA] HTC One *STOCK* ROM Port | 4.19.401.8 | 4.4.2 | HTC Sense 5.5. But, that ROM gives me unstable internet connection. I wonder if I can install this ROM on my J Butterfly, and is the 4G will also working?
Any help would be a great things for me.
Thanks in advance.