[Q] Cannot boot into any custom ROM! - myTouch 4G Q&A, Help & Troubleshooting

A friend of mine wanted to change the stock rom on his old tmobile MyTouch 4G to CM7.2
It is currently running the latest 2.3.4 (hboot_0.89.0007, radio 12.62.60.27_26.13.04.19), I unlocked the phone following the steps from HTC Dev website. And they explained that unlocking is enough to flash custom rom since it enabled write access to recovery, system and boot http://www.htcdev.com/bootloader/about_unlock_process.
I was able to flash and run both TWRP and CWM (twrp2.2.2.1-glacier-recovery & recovery-clockwork-touch-5.8.1.0-glacier) adn used them to flash CM7.2 stable and the latest nightly and some other custom ROMs i found on the developers forum at XDA, however, not of them do boot. The phone will get stock at the first screen showing Tmobile and myTouch 4g logo.
I followed many threads/steps that recommended downgrading to stock froyo first to turn security off (S-OFF) but it won't let me since it is older version, then some says to downgrade the radio first, but that is also not possible with S-ON and i get signature error. i tried doing it from the sd-card using the file name "PD15IMG.zip" for the stock rom but didn't work neither from the fastboot rebootRUU thingy.
From the recovery i wiped every thing even system, then checked it to make sure it is empty, flashed CM7.2 and mounted system and there are the files as they should be but it won't boot, and "adb devices" won't show anything so i cannot see the log. which means it didn't even start.
Am I missing something trivial?
* BTW, i had to lock the bootloader again to flash the stock 2.3.4 back, but I have the unlock token "Unlock_code.bin" and I can unlock it again if someone knows the answer to this problem

Related

[INFO] Possible workaround root for 802w dual sim on KitKat 4.4.2; Needs confirmation

After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
gaguzman said:
After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
Click to expand...
Click to collapse
Alternatively... just install TWRP !!
ascot17 said:
Alternatively... just install TWRP !!
Click to expand...
Click to collapse
Agree it would be much easier and cleaner, if it had worked for me. Touch didn't work after install of 2.7.0.0b, so I gave up on it, and had to reflash CWM to get recovery function and proceed with root. I guess there are still some variations in there that can't be accounted for. I posted this as an interesting observation that might be useful to the devs.

COS13 rooting failed, stuck in boot loop

Hi all,
I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.
After updating I followed this guide: http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992
And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper
Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.
I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).
When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:
<bootloader> Device already : unlocked !
OKAY [ 0.000s]
finished. total time : 0.000s
Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...
I continued to start rooting it, but not before testing if I could still boot but everything was fine.
I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.
I checked if everything still was ok and it was. I could boot and everything.
So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.
I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.
I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.
This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.
I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.
I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).
So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.
I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.
And now the rom is in a boot loop.
I already tried a full factory reset but it's still boot looping.
I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.
The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".
But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?
I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..
Thank you in advance.
Edit: I've found my solution and had to change something.
You can read it here starting from Edit 2.
http://forum.xda-developers.com/showpost.php?p=68632922&postcount=84

How to unbrick my ZTE Axon 7 mini b2017g

Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.
Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.
mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks

[Help] updating from kitkat to marshmallow on A5_dug

Okay so I have a desire 816 dual SIM A5 DUG S-on model, and wanted to update it to LL then MM in order to use external storage as internal to expand storage.
Tried the OTA update but failed (red triangle appears halfway through the process)
So I decided to try and flash custom Rom's; I unlocked boot loader and installed custom recovery then flashed this Rom:
https://forum.xda-developers.com/desire-816/general/official-rom-desire-816-dual-sim-a5dug-t3552060
After several attempts (both with CWM & TWRP) I got it running, but WiFi wasn't working. Thankfully I made a backup of my stock kitkat before flashing, so I restored it.
After some research here, I found that I needed the LL firmware in order for the WiFi to function, and cannot update to MM directly from kitkat...
Please help, what should I do?
I remember reading something about downloading the OTA package, unzip it and extract firmware.zip then flash it, which should solve the problem. Is that right?
Thanks
xyz
you can relock bootloader and run a RUU with your region or you must s-off, change to super ID and run any RUU. Good luck
link some RUU : gsmhelpful.com/2015/05/htc-desire-816-official-stock-roms.html

Help recovering device

I'd like to give this Nuclear ROM a try. My device is bootloader unlocked and currently has no OS on it. My device was rooted and last thing I tried doing with it was installing the recent stock Nougat release. Reading that one thread I never went through the steps of restoring what was needed I believe in step two to be able to put stock Nougat on it.
I don't care about stock anymore and will try out this ROM. Holding Power and Volume Down I can get to the options for recovery mode/etc. When I select recovery mode the device reboots and sits at the bootloader unlocked screen. Regardless of which option I select the device reboots and sits at the bootloader unlocked screen. If it's bricked so be it. If it can be restored can anyone point to a thread or have any suggestions?
Flash full stock Nougat:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Files for fastboot you have to find:
https://forum.xda-developers.com/moto-x-style/general/page1
After one boot you can flash twrp & custom rom, f.e. Nuclear. @lip008
Thanks. I just needed a refresher. Everything for fast boot was installed and TWRP was still in the folder. For some reason i thought i was worse off than i was.
Back up and running with this NucleaROM. I may retire the s8+ and go back to this as my DD.

Categories

Resources