Related
Hey all,
I've had my T-Mobile One S for a while. I finally rooted it about a month ago, after I switched to Verizon and picked up a Droid DNA. I'm only using my One S for apps that are not updated to support my DNA. My issues are a little strange, I haven't found anyone else posting the RUU errors I get or having the same issue changing ROMs as I am having after reading for almost a month.
I can only install JellyBam 4.0.0 and fully boot. I have tried many ROMs and only JellyBam works with my phone. Since I was having so much trouble with ROMs, I decided I would go back to stock and start over. NONE of the RUUs will complete successfully. I get this error: FAILED (remote: 02 data length is too large). Basically the RUU is telling me that my phone's system partition is too small to be flashed with the RUU image.
I have been rooted and flashing since the early days of my G1, before Cupcake was released, I am not new to that aspect. I have followed the methods as written in each respective thread. With the RUUs, I have tried locked, unlocked, stock recovery, TWRP, and CWM. I also tried flashing it by grabbing the firmware.zip out of the temp folder and doing a fastboot flash zip firmware.zip in RUU mode. I have tried this with superCIDs 11111111 and 88888888 as well as HTC__001 and the T-MOB010. I pass the CID check.
It would be nice to install different ROMs, but I would rather be able to put in stock firmware from a RUU that can get OTA updates so that I could sell it if I feel like it.
Anyone have any idea as to what is going on with my phone? Did my partition size change somehow with S-ON?
HBOOT is 1.14 and I was on the 4.0.4 OTA before rooting.
dclaw_fantum said:
Hey all,
I've had my T-Mobile One S for a while. I finally rooted it about a month ago, after I switched to Verizon and picked up a Droid DNA. I'm only using my One S for apps that are not updated to support my DNA. My issues are a little strange, I haven't found anyone else posting the RUU errors I get or having the same issue changing ROMs as I am having after reading for almost a month.
I can only install JellyBam 4.0.0 and fully boot. I have tried many ROMs and only JellyBam works with my phone. Since I was having so much trouble with ROMs, I decided I would go back to stock and start over. NONE of the RUUs will complete successfully. I get this error: FAILED (remote: 02 data length is too large). Basically the RUU is telling me that my phone's system partition is too small to be flashed with the RUU image.
I have been rooted and flashing since the early days of my G1, before Cupcake was released, I am not new to that aspect. I have followed the methods as written in each respective thread. With the RUUs, I have tried locked, unlocked, stock recovery, TWRP, and CWM. I also tried flashing it by grabbing the firmware.zip out of the temp folder and doing a fastboot flash zip firmware.zip in RUU mode. I have tried this with superCIDs 11111111 and 88888888 as well as HTC__001 and the T-MOB010. I pass the CID check.
It would be nice to install different ROMs, but I would rather be able to put in stock firmware from a RUU that can get OTA updates so that I could sell it if I feel like it.
Anyone have any idea as to what is going on with my phone? Did my partition size change somehow with S-ON?
HBOOT is 1.14 and I was on the 4.0.4 OTA before rooting.
Click to expand...
Click to collapse
I imagine you know all about relocking your bootloader and having your phone in bootloader before trying the RUU... I also imagine you have verified your RUU downloadusing md5 checksums? And of course, flashed stock recovery before relocking?
You can also wait for the OTA update for T Mobile... There are a few custom ROMs that will allow a download of it... Even if they dont im sure someone will post the OTA, which you can then download to your SD Card, flash stock recovery and update from there...
Yep. I've been through a bunch of steps. Started in bootloader and locked. I have tried OTAs already, the stock recovery errors, then if I choose any option it errors an reboots my phone. MD5s are good.
Sent from my HTC6435LVW using xda app-developers app
dclaw_fantum said:
Yep. I've been through a bunch of steps. Started in bootloader and locked. I have tried OTAs already, the stock recovery errors, then if I choose any option it errors an reboots my phone. MD5s are good.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
---------- Post added at 01:23 PM ---------- Previous post was at 01:12 PM ----------
AKToronto said:
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
Click to expand...
Click to collapse
As an absolute last resort, I would try using the bootloader downgrade method shown in the Dev section but instead of reflashing a bootloader, flash an image to the recovery partition. This would more or less force the image to take... I think... But I cant say ive tried it. Could have other risks
Couple questions
AKToronto said:
I .. I also imagine you have verified your RUU downloadusing md5 checksums? And of course, flashed stock recovery before relocking?
Click to expand...
Click to collapse
How do you verify checksums?
Do you mean we need to flash stock recovery before we start the process and lock bootloader initially?
Where would we find the stock recovery or do we use the one in the temp folder during the install?
AKToronto said:
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
---------- Post added at 01:23 PM ---------- Previous post was at 01:12 PM ----------
As an absolute last resort, I would try using the bootloader downgrade method shown in the Dev section but instead of reflashing a bootloader, flash an image to the recovery partition. This would more or less force the image to take... I think... But I cant say ive tried it. Could have other risks
Click to expand...
Click to collapse
The stock recovery is working, it errors when it tries to mount cache or the SD card. I can mount the SD in TWRP and CWM. It also mounts as a USB drive in Windows. I'm trying my hardest to get this to take other files without doing the HBOOT downgrade. I don't like bringing down my main PC for any reason. I have checked the MD5s each time, all is good with that. I have a sneaking suspicion that it the FS on one or more partitions may be different than factory and is causing the issue. Going to have to find a table of the factory partition FS structure before I jump to messing with the HBOOT downgrade.
I have just recently ran an RUU, however, I did not flash the stock recovery beforehand. All I did was relock the bootloader and run the RUU. It seemed to work fine, but I am having some wifi and airplane mode issues and I also can not update the software. Is this because I did not flash the stock recovery beforehand? and if so, what can I do to fix the problem? I ran the 2.35 RUU that was recently posted, thanks in advance
I have a one xl cid rogers001 hboot 2.14, baseband 0.23a.3 2.09.29.... jb 4.1 with sense 4+
I tried unlock bootloader by htcdev => ok
install recovery => ok. and when i installed this rom: http://forum.xda-developers.com/showthread.php?t=1868236, it was stuck in bootloader. i fogot root my phone before.
so i relock my device, and tried to flash this stock rom using adb : OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (was found in this thread: http://forum.xda-developers.com/showthread.php?t=2119610)
On cmd via fastboot i type fastboot erase cache =>ok
fastboot oem rebootRUU => ok
fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail") in the end cmd
What should i do now?
Thanks for reading and help me pls!!!!
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
timmaaa said:
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
somebody help me pls
veveve said:
somebody help me pls
Click to expand...
Click to collapse
Please be patient, we all have lives outside XDA.
veveve said:
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
Click to expand...
Click to collapse
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
timmaaa said:
Please be patient, we all have lives outside XDA.
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
Click to expand...
Click to collapse
yes, i did it more than once, now it's fixed, but when i mount it to Windows using TWRP, nothing happen, so i can't format it. and the same things when i tried to sideload. But in fastboot mode, it usual.
and i flashed the newest rom in this thread: http://forum.xda-developers.com/showthread.php?t=1868236 ViperXL 4.2 and i didn't check the MD5
back to my previous question, can i fash a custom rom without root?
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
nem1yan said:
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
Click to expand...
Click to collapse
I disagree. I think it's a better idea for him to get his head around the simple operations like flashing ROMs before attempting s-off.
Sent from my Evita
timmaaa said:
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Click to expand...
Click to collapse
Full ROM:
Jelly Bean - Android 4.2.2 / Sense 5
ViperXL 4.2.0
Main Link: http://www.androidfilehost.com/?fid=23134718111254927
Mirror 1: http://goo.im/devs/Turge/ViperXL/ViperXL_4.2.0.zip
Mirror 2: http://d-h.st/z4Q
Click to expand...
Click to collapse
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/showthread.php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Thanks!
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
timmaaa said:
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
Click to expand...
Click to collapse
it is ViperXL_4.2.0.zip
i'll do it next time!
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
veveve said:
it is ViperXL_4.2.0.zip
i'll do it next time!
Click to expand...
Click to collapse
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
You might be onto something.
Sent from my Evita
timmaaa said:
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
You might be onto something.
Sent from my Evita
Click to expand...
Click to collapse
I mean, i didn't do it and i will do it next time
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
thanks, i will try.
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
timmaaa said:
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
but i still have trouble with mounting internal storage using TWRP on windows, should i try the older TWRP?
What version do you have installed?
Sent from my Evita
timmaaa said:
What version do you have installed?
Sent from my Evita
Click to expand...
Click to collapse
here
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/show....php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Click to expand...
Click to collapse
I've been in the samsung family for so long that I didn't realize how different flashing can be. I broke my phone so I bought a Moto G. Rooted it right away with only a little trouble. I installed a Lollipop ROM afterward and couldn't get my phone to boot. Guess who forgot to do a backup of the stock ROM? Yay me... but anyway, I found a stock file and went through all the steps in the screenshot. Each time, I got the okay to move on and I assumed I had the stock file flashed. Upon rebooting, I stay at the "warning, bootloader is unlocked" and phone doesn't go any further. I'm not booting up at all and custom recovery is gone now.
Can anyone help? I'm at my wit's end.
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
That's actually the instructions I used to try to flash back to stock. But when it reboots, it never gets past the warning about bootloader. I can get the TWRP recovery back but from there is there another way to flash the "flashable zip"? With Samsung I could always use ODIN but I don't think it works with Moto G. I can't get the zip to internal storage to flash it.
Thanks for the reply by the way I'm going to try it one more time I think....
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
Click to expand...
Click to collapse
I hate sounding dumb... but how will I flash the zip if I can't get it on my phone?
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Thank you for all your help. I'll give that a shot.
BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
audit13 said:
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
Click to expand...
Click to collapse
The problem is that I didn't make a backup. When I tried flashing back to stock using fastboot everything was wiped. I don't even have the original custom ROM that started the whole mess. The stock file flashed but phone won't boot. I never get passed the boot loader warning screen. I did everything to the tee (following the directions that BBobby posted above. Actually did it twice. Isn't there an ODIN type deal for this phone. Brand new and I've broke it dangit.
Oh and I can't get into the phone to enable us debugging.
There is rsd lite but it may not help. Odin doesn't help if you can't enter download mode too. Usb debugging isn't require to flash a rom or install recovery.
It sounds like your phone is not booting because of the bootloade or the data partition is messed up.
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
stacalicious said:
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
Click to expand...
Click to collapse
I also got similar problem as yours. I have xt1033 dual sim phone and i had flashed lollipop 5.0.2 soak version. When official update was released for xt1033 i got back to kitkat 4.4.4 to download ota. But when i flashed kitkat through fastboot it got stuck on unlocked bootloader screen. Only solution i got still is converting to gpe. Only Gpe firmware boots. Im still finding solution for bootloop
You can get into TWRP? What happens when you use it to flash a custom ROM?
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I've flashed dozens, probably hundreds of ROMs in the past and never ran into such an issue. Custom ROM seemed to take, but got stuck. So I used fastboot and followed the directions to the tee in this link http://forum.xda-developers.com/showthread.php?t=2542219
When the ROM is finished flashing (stock that is) it never gets past the bootloader warning screen. If I could just get a zip onto the phone, I could flash through TWRP but I have no idea how to or if it's even possible.
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
So I got into cwm. I can't mount usb storage, but I have an option to use adb sideload? Can I flash stock from there?
http://teamw.in/project/twrp2/233
Instructions on how to flash via fastboot are there in the same download page
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
stacalicious said:
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
Click to expand...
Click to collapse
The moto g just needs to do a wipe. Advanced wipe is not necessary. Then install the zip from the folder. By the way you can flash from USB otg (USB storage device such as a flash drive)
I fixed it!!!
stacalicious said:
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
Click to expand...
Click to collapse
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
I'd hug your neck right now if I could get to you!!! I flashed cwm, went to adb sideload and installed a stock rom. My phone is back up and money isn't going to be pissed into the wind because I made a mistake. Thanks to everyone for your help.
Q&A for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest)
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 EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest). 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!
billblack said:
Long time lurker. I read and can use Google . Regardless, it failed and scared the crap out of me as it wouldn't boot. Got back into boot loader, fired up EXE again and it seems to have finished the 2nd time. A few more grey hairs, but all is good my friend. Thanks.
Click to expand...
Click to collapse
Same thing happened to me! Failed the first time around, worked the second. Booting now and it appears to be working (Android is upgrading...)
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
EXE/ZIP RUU M8_VZW 5.0.1 Help
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
mbarcus said:
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
Click to expand...
Click to collapse
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
dottat said:
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
Click to expand...
Click to collapse
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
mbarcus said:
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
Click to expand...
Click to collapse
recovery doesnt' weigh in here. You can install it from bootloader using the SD card method.
How do I flash L Hboot? with twrp? do I have to flash it or can I just use the ruu to get to the new 5.0.1 firmware? thanks
So you asked to report our experience ...
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
A_Levis said:
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
Click to expand...
Click to collapse
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
..
dottat said:
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
Click to expand...
Click to collapse
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
A_Levis said:
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
Click to expand...
Click to collapse
Most recoveries will offer to flash su on an unrooted rom. You can either do that or manually flash the newest supersu.zip After you boot up you can install busybox from an app like this... https://play.google.com/store/apps/details?id=stericson.busybox
So what rom/firmware are you currently on?
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
Nickchapstick said:
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
Click to expand...
Click to collapse
After looking for a little bit, it appears I'm having a similar issue.
klw7890 said:
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
After looking for a little bit, it appears I'm having a similar issue.
Click to expand...
Click to collapse
You were able to boot up the OS successfully the first time right?
dottat said:
You were able to boot up the OS successfully the first time right?
Click to expand...
Click to collapse
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
klw7890 said:
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
Click to expand...
Click to collapse
Stock recovery?
dottat said:
Stock recovery?
Click to expand...
Click to collapse
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
klw7890 said:
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
Click to expand...
Click to collapse
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
dottat said:
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
Click to expand...
Click to collapse
"That app" being TWRP Manager?
Hello,
i need your help with my htc u 12+., please (
What happened
While I was happily using the phone a pop up from Magisk manager showed up, asking if I wanted to update. I said ok.
Magisk manager updated. Then it asked to update Magisk itself to 17.1. Checked on XDA if it was stable. It was. I chose the suggested method and tapped ok.
Here's where the nightmare begins. The installation seemed successful but the phone couldn't boot properly. The HTC animation stopped suddenly on the three green dots and the phone didn't react at all. It was not really a bootloop, it was like it couldn't boot any more.
What I did
Tried not to freak out and managed to boot into bootloader and then recovery. Tried to uninstall magisk through the magisk uninstaller, couldn't do it.
I didn't know if I could install Magisk 16.0 over a newer version, and I preferred not to try by luck. So I decided to restore a previous NAND Back up I had made. The NAND backup could restore everything but the /vendor partition.
Now, the phone successfully reboots but:
- I have no root (Magisk is gone)
- when I plug my USB cable, it only charges. No communication between the phone and the PC, unless I boot into bootloader (then the connection is there again and I can use fastboot commands). When I go to Developer options, no matter what communication protocol I choose for USB, it sticks to "Charge". Debug USB is ON, of course.
Tried to install Magisk again through a temporary TWRP, but the issue is still there: I can't mount /vendor partition and it fails.
I've looked for a solution here and there; what I found out is that I should use a treble-enabled TWRP, but my limited knowledge doesn't help me with that.
Please could you help me? It's crazy how messy can be just tapping ok on a notification :crying:
EDIT - FIXED:
To restore the USB communication, flashing the RUU solved the problem.
Using the patched boot.img method to install Magisk could succesfully work around the /vendor issue.
Huge thanks to the guys who helped, that was essential.
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
MNoisy said:
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
Click to expand...
Click to collapse
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Thank you, maybe this one will help me.
Should I check something before trying ? (like CID.. or.. something else?)
And can I launch the RUU when I'm in bootloader mode? It's the only way I have to make the PC recognize the device.
EDIT: trying to launch the RUU, but after a few clicks it closes.. maybe my PC can't find a device, even in bootloader mode, and the software is shut down.
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
[canceled]
sbiricuda said:
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Click to expand...
Click to collapse
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
MNoisy said:
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
Click to expand...
Click to collapse
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
sbiricuda said:
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
Click to expand...
Click to collapse
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
MNoisy said:
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
Click to expand...
Click to collapse
Seems that I have no luck. The provided boot.img in the spreadsheet is for US unlocked variant, while I have the european version. Maybe it's the same, but the point is that when I open the AFH page to download, it says "for HTC U11".
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
The U11 is just a typo, it is the right stuff. You have a couple options since there is no signed stock boot available on the spreadsheet. Simply download the RUU and decrypt the payload using the instructions in the OP of the post I already provided or go to here and find yours (It is there, I checked )
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
sbiricuda said:
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
Click to expand...
Click to collapse
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Flippy498 said:
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Since I was facing USB issues (no communication via USB betwenn the device and the PC), I flashed the whole RUU. I'm now completely stock 1.21.
As I mentioned, the problem is now that I can't root again.
Tachi91 said:
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Click to expand...
Click to collapse
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
sbiricuda said:
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
Click to expand...
Click to collapse
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
Tachi91 said:
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
Click to expand...
Click to collapse
I have installed the RUU through TWRP. I had to use the 1.15 because the 1.21 gave me an error about the CID that was not coincident (but I'm sure I picked the right RUU in the spreadsheet, for my CID, the HTC__034).
So i restored the 1.15, and then installed the OTA update to 1.21. This is my current situation. And yes, I'm S-ON.
What I could do is either:
- I try to decrypt the boot.img from the RUU in the spreadsheet (but using the tool seems sooo complicated, I'm reading the thread over and over not understanding much), or
- I use the .exe version of the 1.21 RUU, from the HTC official website. If I do that, can we be sure that I have a signed boot.img? And can this work around the TWRP limits about partitions?
Oh, something I forgot to mention: I did try the switching trick MNoisy suggested (switching the slots and then switiching back), but it didn't work.