Related
I tested this out with both the transformer and slider. No need to do anything complicated.
ASSUMPTION:
You have CWM installed.
INSTRUCTION:
(1) Download the latest firmware from asus website.http://support.asus.com/download.aspx?SLanguage=en&p=20&s=16&m=Eee%20Pad%20Transformer%20TF101&os=32
(2) Unzip it. Inside, you should find another zip file. Place that zip file on your micro sdcard.
(3) Plug in your micro sdcard. Go into CWM.
(4) Wipe data/ factory reset, wipe cache partition, wipe davik cache.
(5) Flash in the zip file you just got from the asus website.
(6) Once restarted, you will be back on non-rooted stock rom and stock recovery.
Yeah eyesoftsys posted the same thing a while back
http://forum.xda-developers.com/showpost.php?p=22886559&postcount=1
goodintentions said:
I tested this out with both the transformer and slider. No need to do anything complicated.
ASSUMPTION:
You have CWM installed.
INSTRUCTION:
(1) Download the latest firmware from asus website.
(2) Unzip it. Inside, you should find another zip file. Place that zip file on your micro sdcard.
(3) Plug in your micro sdcard. Go into CWM.
(4) Flash in the zip file you just got from the asus website.
(5) Once restarted, you will be back on non-rooted stock rom and stock recovery.
Click to expand...
Click to collapse
I don't think this wipes data, you need to factory wipe first..IIRC
recovery
Will it remove also cwm recovery? Just wondering
sarriel said:
Will it remove also cwm recovery? Just wondering
Click to expand...
Click to collapse
Yes it will remove CWM
sarriel said:
Will it remove also cwm recovery? Just wondering
Click to expand...
Click to collapse
Look at step 6.
I downloaded the us 9.2.1.11 from Asus website . Will it work if I'm already running revlover ics? Just making sure before I unroot.
Sent from my SPH-D710 using xda premium
parmend said:
I downloaded the us 9.2.1.11 from Asus website . Will it work if I'm already running revlover ics? Just making sure before I unroot.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I don't care if you have the googoogaga rom running right now. Just follow my method to unroot.
There`s one way to back to stock without loosing all my games and apps orden i can back up all? How?
Does this forever block out being able to root again?
RiffyDivine said:
Does this forever block out being able to root again?
Click to expand...
Click to collapse
No. Unless u go back to a stock rom that is not able to be rooted. The hc 8.6.5.21 is the only stock rom that can't be rooted I believe.
Sent from my SAMSUNG-SGH-I777 using XDA
RiffyDivine said:
Does this forever block out being able to root again?
Click to expand...
Click to collapse
You should be able to root again using ViperMod.
viper mod
I flashed viper mod After ics ota was totally stock then having no problems so far but now how do I flash any roms?never had cwm on my transformer . So now what I would like to get revolver but stuck have a b70. Any help?
thunderman98 said:
I flashed viper mod After ics ota was totally stock then having no problems so far but now how do I flash any roms?never had cwm on my transformer . So now what I would like to get revolver but stuck have a b70. Any help?
Click to expand...
Click to collapse
Use RecoveryInstaller to flash CWM recovery.
With CWM recovery you can flash ROMs.
Good post here
http://forum.xda-developers.com/showthread.php?t=1494230&highlight=epic+noob
Also next time, try not to ask questions that's not related to the thread subject.
thunderman98 said:
I flashed viper mod After ics ota was totally stock then having no problems so far but now how do I flash any roms?never had cwm on my transformer . So now what I would like to get revolver but stuck have a b70. Any help?
Click to expand...
Click to collapse
Go here.. http://forum.xda-developers.com/showthread.php?t=1346180
Download and install this app. Run the app and grant superuser access. Then flash the custom recovery. This will install cwm recovery. Then go to the development section and browse the custom roms. Download the rom of your choice, place on sd card, boot into recovery (shut down, then hold the volume down key and power key, then when prompted on screen, press the volume up key) Before flashing a new rom, u will want to do a full wipe first. (back up any needed data first) You will want to install from zip file. Choose the rom you downloaded, and now you have a custom rom installed.
Worked great
I was able to get my TF101 back to stock with this, really easy. Thanks.
kfhughes said:
I was able to get my TF101 back to stock with this, really easy. Thanks.
Click to expand...
Click to collapse
Of course it's really easy. I'm a dummy, too. I speak dummy language
This worked perfectly and it fixed my USB issue from flashing the repacked ICS update. I love that Asus made the App Backup tool so I could just restore all my apps without Titanium!! So awesome!! Thanks again!
This isn't working for me? when i install the .zip from the asus website it says its completed installation but when i boot the tablet back up nothing has cahnged and CWM remains ??? is it because i have a tf101g? Ive also tried flashing stock asus recovery and it seems to work but then when i reboot i still have CWM ??
Will this work if I flash the German over rooted ww-version?
Can't believe it will be that easy also I don't wanna brick my tab.
Sent from my Transformer TF101 using Tapatalk 2
NOT MY CREDITS
Perhaps scryshark should made this post
(This applies both 7500 7510 and was writen when we didn't had the wifi only version, so for 7510 ignore the mention steps)
On step 1, you can use also:
--------------------------------
ODIN->PDA->SELECT FIRMWARE AND AFTER PUT TAB IN FLASH MODE CLICK START
--------------------------------
scaryshark said:
Here's a definitive guide for P7510 owners on how to install stock ICS on their tabs with root. How do I know it's definitive? Well, I'm running it right now with no problems!
NOTE: Obviously I shouln't have to say this but... WiFi only guys may run into a bug of some sort if trying to apply this. I haven't had any prblems yet. Everything works: WiFi, GPS, Camera, Auto-brightness, G-Sensor etc. If something wrong happens, then it's not my fault!
That said there are a few things going on because of running a P7500 ROM on a P7510. Like there is a signal indicator in the status bar showing no signal. There are mobile data options in the settings menu. The device is recognised as a P7510, i think you get the point.
Now to the actual instructions.
Step 1: Putting ICS on
- Create a Nandroid backup!
- Download & install Mobile Odin by Chainfire. [Redistrubution is not allowed so I've linked to his thread] <- Read that properly before you go onto the next step so it's istalled properly!
- Download the firmware and unzip
- Move the file P7500XXLQ8_P7500OXALQ8_P7500XXLQ8_HOME.tar.md5 to the root of your Tab.
- Open Mobile Odin
- Select the .md5 firmware you just put onto your Tab
- *IMPORTANT FOR WIFI TABS* Select Modem and press Clear
(there's no need to select the option of auto root or odin insall 'cos it wont work! )
- Select the 2 wipe options
- Plug your tab into the power supply
- Press the fflash firmware button
---------------------------------------------------
LET IT DO IT'S OWN THING. LEAVE IT AND WAIT FOR IT TO RESTART TO THE SETUP SCREEN
---------------------------------------------------
Done now your running ICS, but wait - you don't have root! or CWM recovery for that matter! :crying: Don't worry, keep reading!
CWM Recovery and Rooting:
- Download this update.zip for rooting your tab and move it to the root of your tab
- Put your tab into download mode
- Plug it into the computer
- Let the computer install the drivers (Automatic on Win 7 - unsure about other OS's)
- Download and unzip Odin 1.85
- Download CWM Touch Recovery & save to same folder as Odin 1.85
- Open up odin
- Click PDA and select the file named recovery.tar.md5
- Click start
-------------------------------------------------------------------------------
LET ODIN DO IT'S THING & WAIT FOR TAB TO RESTART
-------------------------------------------------------------------------------
- Put the tab into recovery mode.
- Select install from sd card and select Samsung_Galaxy_Tab_10.1_root.zip
---------------------------------------------------------------------------------
LET RECOVERY DO IT'S THING
-----------------------------------------------------------------------------------
- Tap go back and then reboot now
There you have it stock ICS for P7500 & P7510 rooted.
Click to expand...
Click to collapse
It works for me. I restored my apps + data using Mybackup Pro. Thanks for your work!
jpl69 said:
NOT MY CREDITS
Perhaps scryshark should made this post
(This applies both 7500 7510 and was writen when we didn't had the wifi only version, so for 7510 ignore the mention steps)
On step 1, you can use also:
--------------------------------
ODIN->PDA->SELECT FIRMWARE AND AFTER PUT TAB IN FLASH MODE CLICK START
--------------------------------
Click to expand...
Click to collapse
Cool! It may be possible to install the CWM recovery during the ROM install by downloading it from the Cwm website and using that recovery . I'm under the recovery option in mobile odin and skipping straight from initial reboot to putting it into recovery mode and installing the root update.zip. However I forgot to do that so I'm not sure if it'll work or not!
Sent from my GT-P7510 using XDA Premium HD app
So the firmware is for the UK. What happens if I flash this on my US tab?
9xnine said:
So the firmware is for the UK. What happens if I flash this on my US tab?
Click to expand...
Click to collapse
nothing. just flash it it will be OK
real77055 said:
nothing. just flash it it will be OK
Click to expand...
Click to collapse
If anyone has the issue where it just sits at the Samsung logo just reboot into recovery and do a data/cache wipe.
I assume the camera works?
awwilson21 said:
I assume the camera works?
Click to expand...
Click to collapse
Everything works.
After pressing flash firmware, I have the odin logo on my tab for 10 mins now.
Is this normal?
If not, what should I do now?
Thanks for bringing this nice guide.
So do I get this right that there is no way to flash the rom without wiping?
Im a little nervous here. Did I just brick my device?
Why is the odin logo still on my tab? Wasnt there supposed to be a restart?
tomerstern said:
After pressing flash firmware, I have the odin logo on my tab for 10 mins now.
Is this normal?
If not, what should I do now?
Click to expand...
Click to collapse
I used Normal ODIN on my PC. When it finished it rebooted and hung at the Samsung logo. I rebooted into recovery and wiped data/cache and it fixed it. You could attempt to reboot into recovery. If Mobile ODIN did it's thing you will be back to stock recovery. If that's the case then wipe data/cache and reboot.
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
tomerstern said:
Im a little nervous here. Did I just brick my device?
Why is the odin logo still on my tab? Wasnt there supposed to be a restart?
Click to expand...
Click to collapse
I doubt you bricked it. Hold power and volume down to reboot into recovery or download mode again. If you can get to recovery and download mode you are fine.
OK, I rebooted, I have the following options:
1. reboot system now
2. apply update from external storage
3. wipe data / factory reset
3. wipe cache partition
4. apply update from cache.
Which one should I choose?
tomerstern said:
OK, I rebooted, I have the following options:
1. reboot system now
2. apply update from external storage
3. wipe data / factory reset
3. wipe cache partition
4. apply update from cache.
Which one should I choose?
Click to expand...
Click to collapse
OK so you have the stock recovery. Thats good. first wipe data/factory reset. Then wipe cache partition, then reboot.
Thanks so much!
I now have ICS running!!
That was a tough 30 mins
tomerstern said:
Thanks so much!
I now have ICS running!!
That was a tough 30 mins
Click to expand...
Click to collapse
We've all been there. Just remember before you start flashing make sure you know which buttons will get you into recovery and Download mode. If you can get to recovery or download mode there is no reason to freak out. Also, ODIN is your friend. I recommend having a copy of the PC version installed on your PC just in case something goes wrong with a flash or Mobile ODIN. Glad it's up and running for you!
I can get the Rom running alright. My problem is that I get the rolling recovery issue. With the a 5.0.... recovery I get rolling recovery, but the Rom runs fine. If I install the recovery from Pershoots page which is 5.5.0.4, then I get no Rolling recovery, but I get a rolling Rom instead! Frustrating!
Edit: Installed Pershoots recovery v6.0.1.0, didn't solve the issue, but flashing the bootloader method from here: http://forum.xda-developers.com/showthread.php?t=1555984 fixed things. The bootloader change didn't work for me on the older recovery's.
Edit 2: Scrap that, I hadn't turned the screen off yet, that's when it happens lol.
9xnine said:
Everything works.
Click to expand...
Click to collapse
Awesome! So CM10 should be fully functional soon!
Yeah, I tried the bootloader thing as well with the rolling recovery here. Wasn't a great idea anyhow, I guess we need to flash the bootloader from the 4.0.4 ROM, I just don't know how or how to make such a tar on Windows...
Sent from my GT-P7510 using XDA Premium HD app
Yeh I'm not sure either. I managed to get the recovery and rom working for honeycomb and then on to ICS AOSP, but not sure what to do to get this rooted etc!
Sent from my GT-P7510 using xda app-developers app
Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse
has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app
It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app
New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable
CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440
6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7
Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD
No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?
Fastboot img recoveries:
http://androidhosting.org/Devs/Dhacker29/recovery/
Flash-able xt907/xt926 versions: at My goodies homepage: http://forum.xda-developers.com/showthread.php?p=42656451#post42656451
Edit I have tested all the xt907 & xt926 (on my 907) flash-able recoveries to some degree & the xt907-OUDhs-touch-recovery.img is in the xt907-OUDhs-1.0.3.5-key-recovery.zip and is My daily recovery. OUDhs swipe does not work for the xt907.
aviwdoowks said:
http://androidhosting.org/Devs/Dhacker29/recovery/
Click to expand...
Click to collapse
Thanks. I was about to go fastboot back to the earlier JB OTA because the old recoveries weren't sticking.
EDIT: I spoke too soon. So far none of the linked recoveries are working...
mentose457 said:
Thanks. I was about to go fastboot back to the earlier JB OTA because the old recoveries weren't sticking.
Click to expand...
Click to collapse
Not yet willing to try Rom Mgr with the Photon Q flash?
aviwdoowks said:
Not yet willing to try Rom Mgr with the Photon Q flash?
Click to expand...
Click to collapse
What? Im not sure what you are asking.
mentose457 said:
What? Im not sure what you are asking.
Click to expand...
Click to collapse
I predict Rom Manager will work on the Razr HD.
http://forum.xda-developers.com/showthread.php?t=2382638
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2382638
Click to expand...
Click to collapse
It did work. Thanks.
mentose457 said:
It did work. Thanks.
Click to expand...
Click to collapse
Let others know on the thread....
mentose457 said:
Thanks. I was about to go fastboot back to the earlier JB OTA because the old recoveries weren't sticking.
EDIT: I spoke too soon. So far none of the linked recoveries are working...
Click to expand...
Click to collapse
Strange the XT907's do. The oudhs use keys, not swipe ready. Could be true for the HD too.
mentose457 said:
Thanks. I was about to go fastboot back to the earlier JB OTA because the old recoveries weren't sticking.
EDIT: I spoke too soon. So far none of the linked recoveries are working...
Click to expand...
Click to collapse
Btw how did you install the img file?
You might want to try the zips I made.
aviwdoowks said:
Btw how did you install the img file?
You might want to try the zips I made.
Click to expand...
Click to collapse
I flashed it the same way you flash any image:
Fastboot flash recovery <recovery>.img
If your zips are made from the images then i doubt they will work. Plus, I dont have a recovery to flash them in.
Anyway the Photon Q recovery worked for one reboot then it was somehow overridden by the stock recovery. In other words: I flashed the Photon Q recovery via Rom Manager > rebooted into recovery via Rom Manager > from recovery, booted normally > rebooted into recovery and found it had reverted to the stock one.
The N7 originally had this issue. Ill look into how they fixed it. Found it...
You simply navigate to /system and delete or rename the file named: recovery-from-boot.p. Once you do that, reboot to download mode (fastboot) and flash the recovery like normal. Then reboot into recovery.
Upon exiting the recovery (OUDhs) it noticed that the system would potentially overwrite the recovery so it asked it i would like to disable it. I selected 'yes' as I obviously want to retain the custom recovery.
mentose457 said:
I flashed it the same way you flash any image:
Fastboot flash recovery <recovery>.img
If your zips are made from the images then i doubt they will work. Plus, I dont have a recovery to flash them in.
Anyway the Photon Q recovery worked for one reboot then it was somehow overridden by the stock recovery. In other words: I flashed the Photon Q recovery via Rom Manager > rebooted into recovery via Rom Manager > from recovery, booted normally > rebooted into recovery and found it had reverted to the stock one.
The N7 originally had this issue. Ill look into how they fixed it. Found it...
You simply navigate to /system and delete or rename the file named: recovery-from-boot.p. Once you do that, reboot to download mode (fastboot) and flash the recovery like normal. Then reboot into recovery.
Upon exiting the recovery (OUDhs) it noticed that the system would potentially overwrite the recovery so it asked it i would like to disable it. I selected 'yes' as I obviously want to retain the custom recovery.
Click to expand...
Click to collapse
When on stock always choose yes on reboot. To let cwmr make "install-recovery.sh" into ....bak.
Yet once on a custom rom- choose any no.
Thanks
So both the img file & Rom Manager may be working for you?
aviwdoowks said:
When on stock always choose yes on reboot. To let cwmr make "install-recovery.sh" into ....bak.
Yet once on a custom rom- choose any no.
Thanks
So both the img file & Rom Manager may be working for you?
Click to expand...
Click to collapse
Yes, I used one of DHs imgs. I didn't try the Photon Q recovery from ROM Manager because the ones made for the HD work.
Sent from my DROID RAZR HD using Tapatalk 4
Rom manager doesn't work for me. Says device not supported. So all I do is install the cwmr img file in fastboot? Monday computer needed?
Sent from my DROID RAZR MAXX HD
Yes, fastboot. ADB is your friend!
Sent from my XT926 using Tapatalk 2
BTW, thank you for this thread! Made things much more simple for me this afternoon.
Sent from my XT926 using Tapatalk 2
jfriend33 said:
Rom manager doesn't work for me. Says device not supported. So all I do is install the cwmr img file in fastboot? Monday computer needed?
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
During setup what recovery did you choose?
Was it Photon Q?
Maybe I'm just paranoid, but I wouldn't trust ROM Manager to properly flash a recovery on my phone after picking a different device.
Doing it with fastboot takes about 5 secs anyway.
I don't even remember I'm pretty certain it automatically said my device wasn't supported. I wouldn't have chosen a different model.
Sent from my DROID RAZR MAXX HD
jfriend33 said:
I don't even remember I'm pretty certain it automatically said my device wasn't supported. I wouldn't have chosen a different model.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Yes the photon Q recovery (hard key ver) works on the M 100%.
http://forum.xda-developers.com/showthread.php?t=2382638
read carefully.
All hard key 926 recoveries (3 hard key versions Here: http://forum.xda-developers.com/showthread.php?p=42656451#post42656451)
work on my M therefore .....
Is there a version that works with Link2SD sdext2?
The latest one from dhacker does not. On backup, it says:
No sd-ext found. Skipping backup of sd-ext.
Click to expand...
Click to collapse
sd-ext is not in the fstab. If I manually mount /dev/block/mmcblk1p2 to it and try to back up, it says:
Backing up data...
Error while making a backup image of /data!
Click to expand...
Click to collapse
Anyone know where the github of CWM is?
So I just got a 2nd HTC 10 Verizon, I noticed that this phone got S-OFF already so I install TWRP and succeeded.
After that I try flashing others ROM I found here in this HTC 10 Verizon sub-forum but after flashing and reboot, my phone stuck at boot loader and can't get into the OS.
Can you guys please help me out here, it's getting frustrated flashing ROM after ROM and still get stuck like that.
Thanks in advance.
polepoe said:
So I just got a 2nd HTC 10 Verizon, I noticed that this phone got S-OFF already so I install TWRP and succeeded.
After that I try flashing others ROM I found here in this HTC 10 Verizon sub-forum but after flashing and reboot, my phone stuck at boot loader and can't get into the OS.
Can you guys please help me out here, it's getting frustrated flashing ROM after ROM and still get stuck like that.
Thanks in advance.
Click to expand...
Click to collapse
Is the bootloader unlocked? How did you flash the ROM? Have you tried one of the pure stock RUU's in these forums? Do you know which version of the firmware is on it? (These are a few questions which may help diagnose the problem).
hgoldner said:
Is the bootloader unlocked? How did you flash the ROM? Have you tried one of the pure stock RUU's in these forums? Do you know which version of the firmware is on it? (These are a few questions which may help diagnose the problem).
Click to expand...
Click to collapse
I think the boot loader is unlocked because I can access the boot loader screen. It said:
*** Software status: Offcial ***
*** LOCKED ***
*** S-OFF ***
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
DDR TEST
DDT TEST (LOOPING)
POWER DOWN
Click to expand...
Click to collapse
Well, I flash the custom ROM using TWRP (copy ROM into SD card, then install the ROM with TWRP).
I did flash the pure stock RUU in those forums and got it working, but I don't want to use it because I'm using the phone out of US, I have countered so many problems and little things that bugging me off.
This is the detail info I get in the boot info:
hTC download mode
*** LOCKED ***
htc_pmewl XC S-OFF
CID-VZW__01
MID-2PS650000
ColorID-WHT00
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.605.20
Jun 8 2017, 11:30:46(857212)
Click to expand...
Click to collapse
Wondering whether you have a firmware/ROM mismatch.
polepoe said:
I think the boot loader is unlocked because I can access the boot loader screen. It said:
Well, I flash the custom ROM using TWRP (copy ROM into SD card, then install the ROM with TWRP).
I did flash the pure stock RUU in those forums and got it working, but I don't want to use it because I'm using the phone out of US, I have countered so many problems and little things that bugging me off.
This is the detail info I get in the boot info:
Click to expand...
Click to collapse
what rom are you trying to flash?
aer0zer0 said:
what rom are you trying to flash?
Click to expand...
Click to collapse
Well I did flash PERFUME_WL 2.51.617.1 from this sub-forums.
And others popular Rom like I found in the htc 10 sub-forums
polepoe said:
Well I did flash PERFUME_WL 2.51.617.1 from this sub-forums.
And others popular Rom like I found in the htc 10 sub-forums
Click to expand...
Click to collapse
And they all do the same thing?
aer0zer0 said:
And they all do the same thing?
Click to expand...
Click to collapse
Yes, it stuck in boot loader after done flashing and restart.
polepoe said:
Yes, it stuck in boot loader after done flashing and restart.
Click to expand...
Click to collapse
Hmm, you may have already done this. Did you flash the 2.41.605.20 ruu in the development thread (it will wipe data, back up prior)? That will place all current firmware and stock rom (which reading sounds like you don't want).
Once it boots to at least the login screen, reboot to bootloader, flash twrp, format data (type yes) then reboot to twrp.
From here (making sure you have rom of choice on your SD viper, leedroid etc...) wipe everything but your external sd card, and install the rom. It should work from here...
I also gave you the scorched earth method of making it boot up.. This most definitely should work. I would be more than glad to help if I can.
aer0zer0 said:
Hmm, you may have already done this. Did you flash the 2.41.605.20 ruu in the development thread (it will wipe data, back up prior)? That will place all current firmware and stock rom (which reading sounds like you don't want).
Once it boots to at least the login screen, reboot to bootloader, flash twrp, format data (type yes) then reboot to twrp.
From here (making sure you have rom of choice on your SD viper, leedroid etc...) wipe everything but your external sd card, and install the rom. It should work from here...
I also gave you the scorched earth method of making it boot up.. This most definitely should work. I would be more than glad to help if I can.
Click to expand...
Click to collapse
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
polepoe said:
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
Click to expand...
Click to collapse
@aer0zer0's own thread (which you should have looked for first): https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
hgoldner said:
@aer0zer0's own thread (which you should have looked for first): https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
Click to expand...
Click to collapse
I did flash this RUU rom 1 week ago, so all I have to do now is the rest of the step right?
polepoe said:
I did flash this RUU rom 1 week ago, so all I have to do now is the rest of the step right?
Click to expand...
Click to collapse
Reread post #9 of this thread.
hgoldner said:
Reread post #9 of this thread.
Click to expand...
Click to collapse
TWRP flashing is done and it freeze at REBOOT phase so I have to hard restart the phone (with volume down + power for 11 seconds)
It still stuck in the boot loader.
This error message show up with the boot loader:
Code:
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:adsp_boot_store+0x2cc/0x368
polepoe said:
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=961840155545582647
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
There you go, flash via SD card or fastboot. Any instructions required you can get from there
aer0zer0 said:
https://www.androidfilehost.com/?fid=961840155545582647
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
There you go, flash via SD card or fastboot. Any instructions required you can get from there
Click to expand...
Click to collapse
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
polepoe said:
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
Click to expand...
Click to collapse
What error message?
polepoe said:
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
Click to expand...
Click to collapse
Your reboot error appears to be a kernel panic.
What version of Twrp are you using to flash the custom rom/s?
I'm guessing an older one which isn't allowing Magisk to properly root the boot.img/kernel, therefor causing your kernel panics and inability to boot after flashing.
So,....again, what version of Twrp are you using?
You should be using the latest Official build.
Sent from my HTC6545LVW using Tapatalk
aer0zer0 said:
What error message?
Click to expand...
Click to collapse
This
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:adsp_boot_store+0x2cc/0x368
Click to expand...
Click to collapse
santod040 said:
Your reboot error appears to be a kernel panic.
What version of Twrp are you using to flash the custom rom/s?
I'm guessing an older one which isn't allowing Magisk to properly root the boot.img/kernel, therefor causing your kernel panics and inability to boot after flashing.
So,....again, what version of Twrp are you using?
You should be using the latest Official build.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I'm using the latest TWRP at this link: https://twrp.me/devices/htc10.html
polepoe said:
This
I'm using the latest TWRP at this link: https://twrp.me/devices/htc10.html
Click to expand...
Click to collapse
And you've made sure to allow system modifications via Twrp swipe option when you first loaded it?
Check under Advanced > Mount and make sure system is not selected as Read Only.
Sent from my HTC6545LVW using Tapatalk