I could use some help. My phone ran 10.2(4.3.1 ) for the past year, and I've decided to give 11 a try with the swapped partitions.
I can't for the life of me get the rom to install. it goes through the motions, but never installs. I also can't get the adb drivers to load, and I know they did a year ago when i rooted and installed 10.2.
any help please?
Dan
DanPFW said:
I could use some help. My phone ran 10.2(4.3.1 ) for the past year, and I've decided to give 11 a try with the swapped partitions.
I can't for the life of me get the rom to install. it goes through the motions, but never installs. I also can't get the adb drivers to load, and I know they did a year ago when i rooted and installed 10.2.
any help please?
Dan
Click to expand...
Click to collapse
I connected the phone to my linux machine, where adb does work. I tried adb sideload romname.zip, but when i reboot, i just get the spinning cyanogenmod boot logo. I don't think the rom is actually installing. Can anyone offer any guidance?
I have TWRP 2.8.7.0 on the phone.
in fastboot, my phone lists:
DirtyRacun
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.1111
RADIO-1.53.06.1009
OpenDSP-v29.1.0.45.0622
thanks
DanPFW said:
I connected the phone to my linux machine, where adb does work. I tried adb sideload romname.zip, but when i reboot, i just get the spinning cyanogenmod boot logo. I don't think the rom is actually installing. Can anyone offer any guidance?
I have TWRP 2.8.7.0 on the phone.
in fastboot, my phone lists:
DirtyRacun
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.1111
RADIO-1.53.06.1009
OpenDSP-v29.1.0.45.0622
thanks
Click to expand...
Click to collapse
I was trying to use the new F2FS file system. I just switched the 2 partitions back to ext4 and it appears to be flashing. Has anyone used F2FS with this device and ROM?
If a bear ****s in the woods..
Related
I know I'm late to the party (more like the party is over and Im putting on clothes... none the less) I really need help (dont we all) my problem is Im stuck on a boot loop. I can access twrp all functional but I cant get the OS to boot. I've read about all the post I can find about the situation without resolution. I beg of you adroid god reading this to help me out.
----My Rig----
HTC Evo 4g lte
***Tampered****
***Unlocked****
Jewel PVT Ship S-on RL
Hboot- 2.09.0000
Radio 1.12.11.1210
Open DSP-V 31.1.0.45.0815
eMMC-boot
----story---
I was running fine on 4.3.rom (beanstalk), I flashed Haunted kernel through GUI. I rebooted and then flashed beanstalk again, wiped d /c and got stuck in boot loop. I set up ADB tried to flash recovery ( after exhausting TWRP option) didnt work, then I started reading threads so far cant seem to get it going. As I stated I have access to TWRP functions, I tried RUU (unlocked and relocked) didnt work. I am at a loss please help.
Im sure it can be fixed, but I dont know how.
AndroidIsland said:
I know I'm late to the party (more like the party is over and Im putting on clothes... none the less) I really need help (dont we all) my problem is Im stuck on a boot loop. I can access twrp all functional but I cant get the OS to boot. I've read about all the post I can find about the situation without resolution. I beg of you adroid god reading this to help me out.
----My Rig----
HTC Evo 4g lte
***Tampered****
***Unlocked****
Jewel PVT Ship S-on RL
Hboot- 2.09.0000
Radio 1.12.11.1210
Open DSP-V 31.1.0.45.0815
eMMC-boot
----story---
I was running fine on 4.3.rom (beanstalk), I flashed Haunted kernel through GUI. I rebooted and then flashed beanstalk again, wiped d /c and got stuck in boot loop. I set up ADB tried to flash recovery ( after exhausting TWRP option) didnt work, then I started reading threads so far cant seem to get it going. As I stated I have access to TWRP functions, I tried RUU (unlocked and relocked) didnt work. I am at a loss please help.
Im sure it can be fixed, but I dont know how.
Click to expand...
Click to collapse
You of course checked the md5 on the kernel before flashing, right? You should really get s-off to save yourself some issues. If you are certain you have a good download of the kernel, do a full wipe system, data, and cache. Flash the ROM in TWRP, do not reboot, then adb the boot.img and reboot. Should take care of you.
Here is some light reading for you: http://forum.xda-developers.com/showthread.php?t=2256478
wolfclan68 said:
You of course checked the md5 on the kernel before flashing, right? You should really get s-off to save yourself some issues. If you are certain you have a good download of the kernel, do a full wipe system, data, and cache. Flash the ROM in TWRP, do not reboot, then adb the boot.img and reboot. Should take care of you.
Here is some light reading for you: http://forum.xda-developers.com/showthread.php?t=2256478
Click to expand...
Click to collapse
Md5? I didnt check it...I tried the moonshine s-off method but it didnt work (i was already boot looping by then tho) I am downloading a new version of the kernel now. Ill let you know how it works. Thank you for responding....
AndroidIsland said:
Md5? I didnt check it...I tried the moonshine s-off method but it didnt work (i was already boot looping by then tho) I am downloading a new version of the kernel now. Ill let you know how it works. Thank you for responding....
Click to expand...
Click to collapse
nope didnt work.... I entered TWRP reloaded the kernel file flashed it, then flashed the rom (beanstalk) used twrp to boot into the bootloader fastboot flash the boot.img file used cmd command to reboot phone no dice. any other suggestions (or problems evident in my process) ? Im game to try anything at this point. I on a supersonic I borrowed from a friend. try the same process with just flashing the rom now. BTW Haunted-Kernel-AOSP-v29.3. I try version 30.2 of haunted next
The back story...
I had to ditch Verizon. I didn't want to fork over $300 for a Republic Wireless phone only to be stuck with their crappy ROM, and the only 4G LTE android phone supported by Ting is the Evo 4G LTE; picked one up for $50 on ebay. I installed Cyanogenmod on a half dozen devices, newer and older than this phone, and thought this HTC Evo 4G LTE would be as easy as they were to unlock, root, S-OFF and flash. I've been more wrong before, but not without resulting in bodily harm. A hearty 'get stuffed' to HTC for this, and a plea for future rooters to have a concise guide on how to repair their phone under these circumstances.
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere). No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed. This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone. Now we have problems; phone is stuck in a bootloop. After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means. I then tried the closest RUU for my phone, and it failed. I then tried every RUU I could find, all failed. I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
The repair process that worked for my situation...
Once I focused on the HBOOT as a potential issue, I found this thread: http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Quite simply, MeanBean 3.09 worked as advertised, and my phone has booted into a ROM for the first time in days! A HUGE thanks to both Magnum_Enforcer and mikeyxda.
Specific phone information
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
IMAGE CRC
rpm: 0xBC1CB8D
sbl1: 0x507A9B32
sbl2: 0xEAF345D0
sbl3: 0xD5BB18AD
tz: 0xFB084399
radio: 0xC78A66EB
boot: 0xB683E2D
recovery: 0xB47A92E4
system: 0x376A0C9B
Software Version Reported by RUU: 3.17.651.5
Glad to help:thumbup:
Sent from my HTC device
I'm going to keep this log going, since I think quite a few people will follow a similar path as I'm following.
Just tried to achieve S-OFF with the new MeanBean ROM I'm running.
First attempt: Firewater
All of the steps went exactly as expected. The command line dialog was amusing, and ended in "nasty, needs a chaser" or something and rebooted to the ROM. Once rebooted into recovery to verify s-off status, S-ON is reported.
Second attempt: Rumrunner
More interesting dialog in the process, and it, too, went smoothly. Rebooted into bootloader and voila...S-OFF achieved.
Installed Dirty Unicorns 4.4.4
So, after the first day's use I've come to realize that my PRL needs updating and the Dirty Unicorn 4.4.4 ("du_jewel_4.4.4_20140621-0657") ROM doesn't have a 'Update PRL' function as far as I can tell. I backed up DU 4.4.4 and restored MeanBean, updated the PRL, and restored back into DU 4.4.4 with ease.
After using DU for a week, I've come to realize it's fairly unstable. I'll be looking for a different rom soon.
OMG!!!! FINALLY!!!
I've been reading and reading and pulling my hair out for 3 days after attempting to load a custom Rom on my Evo 4G LTE.
I have almost exactly the same situation/experience as you did. I was able to get the CyanogenMod to load but for the life of I can't get any gapps installed. I've tried loading from TWRP and the SDcard to no avail. It looks like it flashes fine but when I reboot the phone no apps are installed. I like CM 10.2.0 but I need the Google apps. Right now I'm missing so many things like contacts, etc. I've tried to install Google Play and just download each app individually but it crashes on start. I'm really feeling lost here and helpless. I never had problems like this with my original EVO or EVO 3D. Tried to go back to stock using Sprint RUU's but nothing works...
I've highlighted my differences in RED.
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
SethW said:
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere) (I loaded TWRP 2.7.1.0 which seemed to work) . No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed (I was able to load CM 10.2.0 through Fast Boot boot.img command) . This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone (Same here, Backup gone). Now we have problems; phone is stuck in a bootloop (I watched the CyanogenMod screen spin for 2 hours). After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means (same here, tried several ways but nothing worked for Windows 7). I then tried the closest RUU for my phone, and it failed (same here). I then tried every RUU I could find, all failed. ( I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
Specific phone information My Info is exactly the same
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
Software Version Reported by RUU: 3.17.651.5
Click to expand...
Click to collapse
airdog99 said:
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
Click to expand...
Click to collapse
I just ran the program as it specified. Make sure your drivers are installed correctly... that step usually caught me up because some Android device drivers conflicted with some of my other Android device drivers.
Recently my device was running 4.4.3 gpe ROM. I wanted to update it to 4.4.4 so i saw this "http://htc-one.wonderhowto.com/how-to/update-your-rooted-google-play-edition-htc-one-4-4-3-without-losing-any-data-0155404/" I thought it would work for 4.4.4 but i guess not and now i'm bricked. I did reflash TWRP but adb sideload cant mount system or cache and when i type in adb sideload desktop/ROM.zip it cannot read. It also said error closed. PLEASE SOMEONE HELP ME.
M8_UL_CA PVT SHIP S-OFF
CID-11111111 (originally had cws_001 then GOOGL001 now supercid)
HBOOT-3.18.0.0000
RADIO-1.16.21331931.LA11G
OS- (no os :crying
eMMC-boot 2048
xxnatanxx said:
Recently my device was running 4.4.3 gpe ROM. I wanted to update it to 4.4.4 so i saw this "http://htc-one.wonderhowto.com/how-to/update-your-rooted-google-play-edition-htc-one-4-4-3-without-losing-any-data-0155404/" I thought it would work for 4.4.4 but i guess not and now i'm bricked. I did reflash TWRP but adb sideload cant mount system or cache and when i type in adb sideload desktop/ROM.zip it cannot read. It also said error closed. PLEASE SOMEONE HELP ME.
M8_UL_CA PVT SHIP S-OFF
CID-11111111 (originally had cws_001 then GOOGL001 now supercid)
HBOOT-3.18.0.0000
RADIO-1.16.21331931.LA11G
OS- (no os :crying
eMMC-boot 2048
Click to expand...
Click to collapse
Can you adb push it? Adb devices shows a phone?
Sir-Fix-a-Lot said:
Can you adb push it? Adb devices shows a phone?
Click to expand...
Click to collapse
I adb pushed it and rerooted my device again. I tried to flash a rom and it wont work it fails every time. The rom was ARHD.
xxnatanxx said:
I adb pushed it and rerooted my device again. I tried to flash a rom and it wont work it fails every time. The rom was ARHD.
Click to expand...
Click to collapse
When you say you were running GPE, does that mean you did the full conversion re-sizing your system partition?
Sir-Fix-a-Lot said:
When you say you were running GPE, does that mean you did the full conversion re-sizing your system partition?
Click to expand...
Click to collapse
I'm not sure but it wouldn't reboot and install 4.4.4 until I factory reset my device on GPE then it downloaded the update. I had a stock factory recovery.img and it said it was successful until i rebooted it. I changed my recovery back to TWRP so I can fix the problem and so far no luck.
xxnatanxx said:
I'm not sure but it wouldn't reboot and install 4.4.4 until I factory reset my device on GPE then it downloaded the update. I had a stock factory recovery.img and it said it was successful until i rebooted it. I changed my recovery back to TWRP so I can fix the problem and so far no luck.
Click to expand...
Click to collapse
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=2733523
Even if you weren't full converted to GPE it will still restore your phone.
Have a ROM on your extSD or adb push it for the last steps
Sir-Fix-a-Lot said:
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=2733523
Even if you weren't full converted to GPE it will still restore your phone.
Have a ROM on your extSD or adb push it for the last steps
Click to expand...
Click to collapse
my device is now booting thanks again :good:
xxnatanxx said:
my device is now booting thanks again :good:
Click to expand...
Click to collapse
NP man, just remember that if you do the GPE conversion again, you'll have to follow that guide to flash Sense again, but an AOSP ROM will flash fine.
Btw. The no os is a twrp bug. Philz doesn't do it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hi,
I've spend 3 days on this now, I tried to update my ROM, but it failed to load and whilst trying to sort it managed to wipe everything on my phone. So I'm now stuck with only being able to get into recovery either TWRP or CWM. But I've tried reverting back to the RUU, but this just stops with error 158 wrong image, which I have tried on three different machines running windows 7 and 8.1. I then tried to access the internal storage via TWRP to either place a backup on there or a new rom to update from, but this will not allow me access, I can see the drive and open it, but as soon as I try and do anything with it, it stops and says device has either stopped working or has been disconnected every time. I then tried to sideload a ROM via TWRP but that doesn't connect. I then tried to install from a sideoaded ROM in CWM and I managed to get it to work once and send the file OMNI rom, but it failed to update with a error 7. Now I cant get it to work at all and I can't get ADB to start and find my device. Im now also fighting a battle to keep the battery charged and using a BAT to charge it currently at 3888mV. FASTBOOT works fine and so I can flash the boot and recovery parts but everything else is not working
Can any one please help me.
My phone is a UK spec HTC One X+
CID HTC__001
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-None
MICROP-None
RADIO 3.1204.171.33
eMMC bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH : OFF
Jun 21 2013,17:36:36
i've managed to get sideload to work in CWM, but every ROM I've tried to install will not work, can anyone recommend a ROM that may work
Thanks
Phil
Hi, thanks for everyone who viewed this, but managed to get my phone working, I managed to push a rom zip to my phone with ADB and used TWRP to install it. Fully working again!!!
Please could you kindly put the steps you went through as a tutorial for others?
Sprint HTC One Max US
I unlocked bootloader and proceeded to use RumRunner and after flashing boot.img (first time for the exploited kernel) It wouldn't boot into android after. Only show pink fuzz on screen.
I get a hang on the first pour that never ends and phone was frozen. System doesn't have an OS TWRP says and wont boot.
tried using multiple RUUs
RUU_T6_UL_K44_SENSE60_MR_BrightstarUS_WWE_3.23.1540.1_Radio_4T.27.3218.14_10.33C.1718.01_release_387431_signed_2
RUU_T6_WHL_JB43_SENSE55_SPCS_Sprint_WWE_1.16.651.4_Radio_1.35.50.1106_NV_SPCS_4.54_003_release_340074_signed_2
even a few 0P3PIMG.zip I could find online all of which never gets picked up by bootloader
I have a feeling the filesystem is corrupted but I'm completely lost on what to do.:crying:
EDIT:
I do have adb access in recovery but can't push files to /sdcard/ or /external_sd/ .
no such file or directory
T6WHL PVT SHIP S-ON RH
HBOOT-2.49.0000
RADIO-1.48.50.425
OpenDSP-V33.120.274_T6.0829
QSC-
OS-3.02.651.5
apr 28 2014, 15:06:18.0
CrazyEye said:
Sprint HTC One Max US
I unlocked bootloader and proceeded to use RumRunner and after flashing boot.img (first time for the exploited kernel) It wouldn't boot into android after. Only show pink fuzz on screen.
I get a hang on the first pour that never ends and phone was frozen. System doesn't have an OS TWRP says and wont boot.
tried using multiple RUUs
RUU_T6_UL_K44_SENSE60_MR_BrightstarUS_WWE_3.23.1540.1_Radio_4T.27.3218.14_10.33C.1718.01_release_387431_signed_2
RUU_T6_WHL_JB43_SENSE55_SPCS_Sprint_WWE_1.16.651.4_Radio_1.35.50.1106_NV_SPCS_4.54_003_release_340074_signed_2
even a few 0P3PIMG.zip I could find online all of which never gets picked up by bootloader
I have a feeling the filesystem is corrupted but I'm completely lost on what to do.:crying:
EDIT:
I do have adb access in recovery but can't push files to /sdcard/ or /external_sd/ .
no such file or directory
T6WHL PVT SHIP S-ON RH
HBOOT-2.49.0000
RADIO-1.48.50.425
OpenDSP-V33.120.274_T6.0829
QSC-
OS-3.02.651.5
apr 28 2014, 15:06:18.0
Click to expand...
Click to collapse
You still need help? I can help you remotely using team viewer to see what we can get going.
dottat said:
You still need help? I can help you remotely using team viewer to see what we can get going.
Click to expand...
Click to collapse
Yes and No
I figured out that CWM and TWRP were able to do different things(one would mount in ADB and the other would be able to actually mount the "partitions" to flash the /system and /cache) So I put a jellybean version of CM (since I was last running JB on the device)
It boots and loads into CM but also auto starts car mode and has the orientation on when I changed in settings or use a third party app to lock the orientation it would still remain unlocked.
When I plug the device into my pc (with or without dev) it accepts it for about three seconds and rejects the device and says nothing is plugged in.
Are you able to sideload a stock sprint rom?
Ƒłƴнαłƒ205 said:
Are you able to sideload a stock sprint rom?
Click to expand...
Click to collapse
I have to flash TWRP and the sideload reflash to CWM and then install sideload.zip (as long as its JB)
I Can't try now because I gotta go to work but I'll make a reply to this one once I do.
What should I try to do after it boots into stock?