So I flash santod's lollipop without upgrading to latest firmware and I am stuck in htc quitely brilliant.
And after that I tried to update my firmware so I go to http://forum.xda-developers.com/showthread.php?t=2485651 and I downloaded "Firmware 6.06.401.1, NO Red Warning"
I followed all the steps and here's what happened :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And after all the desperation I try to relocked to upgrade my firmware and this what happened now:
My get var for more info:
Please. I really need your help as a student, phone is important to me.
Cyber.droid said:
So I flash santod's lollipop without upgrading to latest firmware and I am stuck in htc quitely brilliant.
And after that I tried to update my firmware so I go to http://forum.xda-developers.com/showthread.php?t=2485651 and I downloaded "Firmware 6.06.401.1, NO Red Warning"
I followed all the steps and here's what happened :
And after all the desperation I try to relocked to upgrade my firmware and this what happened now:
My get var for more info:
Please. I really need your help as a student, phone is important to me.
Click to expand...
Click to collapse
Your firmware is very old, most newer roms recommend to be on a 7.xx.xxx.x firmware, you are on a 1.xx.502.xx firmware
You can't flash a no red text firmware on a s-on phone
firmware must be flashed in ruu mode not directly from the bootloader:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootlaoder
Your phone is at&t branded so you can only flash at&t signed firmware on it (x.xx.502.x not other version like x.xx.401.x)
If s-on, bootloader must be locked or relocked before flashing signed firmware or signed ruu.
alray said:
Your firmware is very old, most newer roms recommend to be on a 7.xx.xxx.x firmware, you are on a 1.xx.502.xx firmware
You can't flash a no red text firmware on a s-on phone
firmware must be flashed in ruu mode not directly from the bootloader:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootlaoder
Your phone is at&t branded so you can only flash at&t signed firmware on it (x.xx.502.x not other version like x.xx.401.x)
If s-on, bootloader must be locked or relocked before flashing signed firmware or signed ruu.
Click to expand...
Click to collapse
I am pretty sure I am S-OFF before I follow mike's relocked.
Can you link me specific latest at&t firmware. I don't want to be fckd up again.
Cyber.droid said:
I am pretty sure I am S-OFF before I follow mike's relocked.
Can you link me specific latest at&t firmware. I don't want to be fckd up again.
Click to expand...
Click to collapse
no, your not s-off, you fastboot getvar all quite clearly shows you are s-on------------ (bootloader) security: on
your best bet for now as you are on a very old firmware, in fact one of the first release firmwares, you are on 1xxxxxxxxx everyone else 2 years later is on 7xxxxxxxx, is flash this rom in a TWRP 2.6.3.3 recovery (you may have to use an earlier version of recovery than that) https://www.androidfilehost.com/?w=files&flid=6697
and then try and get s-off using rumrunner http://rumrunner.us/ or you can try this version of moonshine: http://moonshine.io/downloads/getfile.php?file=i3jm4u8412zx or finally try revone: http://forum.xda-developers.com/showthread.php?t=2314582
do not try and flash any lollipop roms, they wont work and you will have all sorts of problems.
if you get s-off, you can then change your cid and mid and update your firmware to the latest version and flash any Lollipop roms you like.
I am depressed right now. Moonshine download page take forever to appear. I can't sideload to put my rom in my phone.
I shouldn't flash lollipop, I have done a biggest and worse problem in my life so far. (
P.s.: I already unlocked my bootloader and my TWRP is 2.6.3.4 is working
EDIT: Flash a new TWRP. Wow it has a USB Mass Storage no more sideload
just a small side note (sorry didnt read the whole thing), but i think that is a patched hboot 1.44 (check the date, if it's June 2013 or later then it's patched) against revone & moonshine, so
either
a) use the att downgrade method ruu
b) use rumrunner
Related
ok my phone is update to this firmware:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im on ARHD 13.4 and tried to apply the RUU update to android 4.3, so i relocked my phone but still no succees (error 155 when applying RUU)
i think this is due to HBOOT RADIO update, but your are the experts
any idea how can successfully update my phone???
PS i need this file "M7 CWM Nandroid Backup / Developer Edition / CID BS_US001 / 1.29.1540.3" the original host is dead
thanks in advance
eltoffer said:
ok my phone is update to this firmware:
im on ARHD 13.4 and tried to apply the RUU update to android 4.3, so i relocked my phone but still no succees (error 155 when applying RUU)
i think this is due to HBOOT RADIO update, but your are the experts
any idea how can successfully update my phone???
PS i need this file "M7 CWM Nandroid Backup / Developer Edition / CID BS_US001 / 1.29.1540.3" the original host is dead
thanks in advance
Click to expand...
Click to collapse
Last time I flashed RUU, I broke the bootloader. It took me more than 20 time to flash RUU to recover the phone. I will not suggest you to flash RUU unless it is really necessary.
If you really need flash RUU...
1. Go back the original hboot if you flashed customized one before
2. Change CID back to original CID if you changed it before
3. Return to S-On
4. Re-lock phone
5. Flash RUU
Also, if you flash 4.3 RUU, the hboot will be upgrade, which means the current S-Off solution will not work. You have to flash RUU without hboot to keep the ability to get S-Off.
yanggame said:
Last time I flashed RUU, I broke the bootloader. It took me more than 20 time to flash RUU to recover the phone. I will not suggest you to flash RUU unless it is really necessary.
If you really need flash RUU...
1. Go back the original hboot if you flashed customized one before
2. Change CID back to original CID if you changed it before
3. Return to S-On
4. Re-lock phone
5. Flash RUU
Also, if you flash 4.3 RUU, the hboot will be upgrade, which means the current S-Off solution will not work. You have to flash RUU without hboot to keep the ability to get S-Off.
Click to expand...
Click to collapse
i think this is the problem, the HBOOT, can i use the files from a ZIP file, (i mean an ORIGINAL ZIP FILE)? if so how can i flash only the HBOOT, radio ETC???
BTW my cid is original, and i just relocked my bootloader
EDIT
just found the original base firmwares thread and i got the files, the question now is, can i DOWNGRADE? im on 1.54 and want to go back to 1.44, please notice im S-OFF, or just flash the base firmware from hboot 1.54?
thanks, im updated, the problems was in the HBOOT, so flashed the original one and then applied the RUU and now im on 4.3
thanks
Here we have the RUU for the Sprint HTC One 4.06.651.4!!! This RUU is for the Sprint One ONLY to restore your phone back to stock. If you are S-ON, you MUST relock your bootloader prior to using this RUU.
HUGE Thanks to the dude who hooked me up, you're awesome!
credit to @-viperboy- for decrypting, thanks!
***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to use:
-Download Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
DEVs, here is the Decrypted version!
Sprint_HTC_One_m7wls_4.06.651.4_RUU_decrypted.zip
These new RUU's now have the system.img split into 3 imgs. You must combine prior to extracting. Copy all 3 to a folder, then...
Use this cmd for Windows:
copy /b system_1.img + system_2.img + system_3.img newsystem.img
Use this cmd for Linux:
cat system_1.img system_2.img system_3.img > newsystem.img
credit to @-viperboy- for the cmds, thanks!
Here is the extracted Firmware:
Full Firmware from RUU (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407568410
Modified Firmware w/ Radio....removed hboot, boot, recovery (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407574146
some basic instructions for flashing the modified firmware....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type Fastboot oem rebootRUU
-when u see the black screen w/ HTC, type Fastboot flash zip firmware.zip
-when it's done, type Fastboot reboot
Here's a nice video from @thoughtlesskyle showing you how to flash the firmware:
Stock Rooted Romz Made From The RUU
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
MD5 5603e630ddffc29a9dd20c96867c1853
Sprint_One_Stock_Rooted_Odex_4.06.651.4.zip
MD5 022aad5e626f08ea6899d7390320324c
Unsecure boot img. init.d support, data/app support
If you get the Side by Side Configuration error while using the RUU you need to install Microsoft Visual C++
Great work gents
Sent from my Nexus 7
If I were to do the Ruu and im s-off with hboot 1.55 will it update me to 1-56 hboot and still have s-off. I read on a thread that by flashimg the Ruu will eliminate my phone not able to update profile and prl. I jhave been having issues in updating my profile with code 1233, currently in Bad Boyz Rom 1.0 4.06
Sent from my HTCONE using xda app-developers app
Thank you for offering this option so soon, it's greatly appreciated and saves so much time!
Sent from my HTCONE using Tapatalk
there have been reports of the RUU not unzipping, I have re-upped... http://www.androidfilehost.com/?fid=23329332407573774
Will come in handy, thanks O.M.J.!
Sent from my HTCONE
This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
Is the RUU different than the OTA?
numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
Are you asking me?
numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
systemshock869 said:
This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
Click to expand...
Click to collapse
Can you confirm the windows 8.1 drivers are installed?
benny3 said:
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
Can you confirm the windows 8.1 drivers are installed?
Click to expand...
Click to collapse
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.
numus said:
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.
Click to expand...
Click to collapse
when u install an OTA, alot of files are "patched", RUU is just cleaner. When I diffed the 4.06 dump against the RUU, most of the files were binary equal but there were 250+ that were not.
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
no more simultaneous voice + LTE
O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
i updated to kit kat and now I don't have simultaneous voice and LTE which I used to have...anyone else notice this? I know that simultaneous voice and 3G was never an option(unlike the EVO 4G LTE) but I always had simultaneous LTE + Voice...this sucks!!
O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
I'm trying to run the RUU but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?
jaybombz said:
This is exactly what I'm trying to do but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?
Click to expand...
Click to collapse
You run this RUU from your PC not fastboot.
BD619 said:
You run this RUU from your PC not fastboot.
Click to expand...
Click to collapse
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!
Unless I am mistaken, you have to relock your bootloader to run the RUU.
jaybombz said:
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!
Click to expand...
Click to collapse
sevarious said:
Unless I am mistaken, you have to relock your bootloader to run the RUU.
Click to expand...
Click to collapse
OP says only if you're S-ON so I thought you didn't have to if you are S-OFF.
Ok, I'm going to try to be as thorough as possible, so bear with me.
Last summer a friend of mine and I both bought ATT M7 64gb's. We pretty much immediately unlocked through HTC Dev and flashed the google edition rom. I decided to S-OFF and SuperCID, he did not.
I sold my M7 when the N5 came out, he was deployed. He just came back and his mic stopped working. He would like to return it to stock, tried, and had no luck, so I'm trying for him.
As mentioned, it's a bootloader unlocked ATT HTC One M7 64gb, now running 4.4.3 Google Edition rom. When I got it, it wouldn't boot, just went to a weird blue screen and did nothing else. Thankfully still had recovery and bootloader. I tried flashing a stock RUU from here:
http://www.htc1guru.com/downloads/ruu-file-downloads/
And got "Remote 99 unknown fail"
HMM
I tried flashing the newest CWM recovery and installing CyanogenMod, just for the hell of it, and got a "status 0" failure.
I tried the same rom with the newest TWRP and got "error executing updater binary"
I finally got the Bigxbie 4.4.3 GPE rom to flash in TWRP, boots fine, everything works (except the mic still of course).
Here's where we are right now:
Current ROM:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader info:
I read that flashing RUU files requires S-OFF, so I tried to do that.
Firewater yielded:
So I figured since it was an older hboot I would try RevOne, which I used a year ago.
That got this:
Here's the CID, I believe the correct one for ATT.
What are my options at this point? I have a booting 4.4.3 GPE rom with a hardware issue and he needs to send it back for repair. Just say screw it and send it in or is there a way to get back to stock from here?
Revone needs to be ran from a sense rom. Try flashing an old version of ARHD 4.2.2. you might need to flash TWRP 2.6.x.x to do so.. Once you have an older sense rom booted, revone should work. At least, that's what worked for me.
Then you will have S-OFF and can flash the RUU.
synt3k said:
Revone needs to be ran from a sense rom. Try flashing an old version of ARHD 4.2.2. you might need to flash TWRP 2.6.x.x to do so.. Once you have an older sense rom booted, revone should work. At least, that's what worked for me.
Then you will have S-OFF and can flash the RUU.
Click to expand...
Click to collapse
Having a hard time finding a 4.2.2 Sense rom, but I'll give it a go, thanks.
MSigler said:
Having a hard time finding a 4.2.2 Sense rom, but I'll give it a go, thanks.
Click to expand...
Click to collapse
Install this ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone
nkk71 said:
Install this ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone
Click to expand...
Click to collapse
If I could hug you over the internet I would. Obviously it worked, thank you very much.
MSigler said:
If I could hug you over the internet I would. Obviously it worked, thank you very much.
Click to expand...
Click to collapse
no problem
and remember, once S-Off do not go S-On again!
Sent from my HTC One using Tapatalk
nkk71 said:
no problem
and remember, once S-Off do not go S-On again!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm not messing with it any more. This should be sufficient for what is very clearly a hardware issue.
Am I safe to flash 4.19.401.11 over 3.62.401.1 and then go to 6.06.401.1 ?
Im currently on 3.62.401.1 custom firmware by sneakyghost and want to upgrade to 6.06.401.1.
From what I read flashing 5.xx.xxx.x over gpe 3.xx.xxx.x results in a bricked One.
There's no real explanation or clarification what's a safe procedure, hence my question.
Logic tells me to gradually flash between "major" versions of fw but don't wan't to risk it..
The x.xx.401.x firmwares are WWE, not GPE right?)
_saiko said:
Am I safe to flash 4.19.401.11 over 3.62.401.1 and then go to 6.06.401.1 ?
Im currently on 3.62.401.1 custom firmware by sneakyghost and want to upgrade to 6.06.401.1.
From what I read flashing 5.xx.xxx.x over gpe 3.xx.xxx.x results in a bricked One.
There's no real explanation or clarification what's a safe procedure, hence my question.
Logic tells me to gradually flash between "major" versions of fw but don't wan't to risk it..
The x.xx.401.x firmwares are WWE, not GPE right?)
Click to expand...
Click to collapse
There were some bricks due to skipping major versions, so I would recomend to flash one at a time. .401 is WWE version
_saiko said:
Am I safe to flash 4.19.401.11 over 3.62.401.1 and then go to 6.06.401.1 ?
Im currently on 3.62.401.1 custom firmware by sneakyghost and want to upgrade to 6.06.401.1.
From what I read flashing 5.xx.xxx.x over gpe 3.xx.xxx.x results in a bricked One.
There's no real explanation or clarification what's a safe procedure, hence my question.
Logic tells me to gradually flash between "major" versions of fw but don't wan't to risk it..
The x.xx.401.x firmwares are WWE, not GPE right?)
Click to expand...
Click to collapse
if you are updating your firmware by flashing firmware.zip from OTA files, you MUST do it incrementally or you WILL brick your phone. Why?
---> firmware.zip packages from OTA are not containing all the firmware files (recovery, sbl, radio, boot, hboot, drivers and much more) but only some of them. if you flash, i.e, a 5.xx.xxx.x over a 3.xx.xxx.x you will brick because the 5.x firmware was designed to work with some existing files of the 4.x firmware that are not included in the 5.x firmware.
---> the only safe way to flash a higher firmware, without doing it incrementally is by using a frimware.zip from a RUU. Fimware.zip from RUU are complete packages containing all firmware files.
see image below, you'll understand what I mean
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=2316726
alray said:
if you are updating your firmware by flashing firmware.zip from OTA files, you MUST do it incrementally or you WILL brick your phone. Why?
---> firmware.zip packages from OTA are not containing all the firmware files (recovery, sbl, radio, boot, hboot, drivers and much more) but only some of them. if you flash, i.e, a 5.xx.xxx.x over a 3.xx.xxx.x you will brick because the 5.x firmware was designed to work with some existing files of the 4.x firmware that are not included in the 5.x firmware.
---> the only safe way to flash a higher firmware, without doing it incrementally is by using a frimware.zip from a RUU. Fimware.zip from RUU are complete packages containing all firmware files.
see image below, you'll understand what I mean
Click to expand...
Click to collapse
Thanks for the clarification!
Im not planning to using OTA partial firmwares but combined firmware zip files from users like Sneakyghost or Vomer which should have all components.
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2316726
In any case ill go 3.xx.xxx.x -> 4.xx.xxx.x -> 5.xx.xxx.x -> 6.xx.xxx.x just to be safe!
Hello guys !! I apologize for my first post be this but I need help to reset my HTC one m7 with OTA updates ect. I want to do not to send to warranty
I have installed one custom ROM 12 with cyanogen version of android 5.1.1
I have also installed TWRP 2.8.6.0 ...
I have unlocked the bootloader also says that this "Tampered" and "S-ON"
My HTC is Portugal's vodafone network and has 4G or LTE i think it's the same thing ...
I know I have to do dowload the RUU file, OTA's and Stock ROM but has a huge list and need help to know what my smartphone need ...
apologize for my bad english and being noob
..
I realy need help... plzzz
No one???
deckard10 said:
No one???
Click to expand...
Click to collapse
post the output of "fastboot getvar all". Remove your IMEI and Serialno before posting.
alray said:
post the output of "fastboot getvar all". Remove your IMEI and Serialno before posting.
Click to expand...
Click to collapse
cant put links on topic.. i send you PM
i try install a stock rom but my device is not started!
so i remember that have a backup in TWRP with my original rom and now i got back my stock ROM with root access and SU with android 4.4.2 and software version 4.19.161.11
now how i got OTA??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
deckard10 said:
i try install a stock rom but my device is not started!
so i remember that have a backup in TWRP with my original rom and now i got back my stock ROM with root access and SU with android 4.4.2 and software version 4.19.161.11
now how i got OTA??
Click to expand...
Click to collapse
You can relock the bootloader, flash the 7.18.206.2 firmware and then the 7.18.206.2 RUU
or
you can relock the bootloader flash the 7.18.206.2 firmware, unlock the bootloader flash twrp recovery and restore the 7.18.206.2 nandroid backup
bootloop
1 guy help me with this and now i got stock rom and stock recovery but when i install OTA's the phone enter in bootloop... what is the problem??
the rom that i installed is Guru_Reset_M7_2.24.161.1 but have to install some apk's manualy
In this process i never relock bootloader
I got the same problem, with all the topics about the perfect fix there is no good one any more, getting really confused since i'm very used to flashing with twrp.
anybody got a fix for this problem ?
alray said:
You can relock the bootloader, flash the 7.18.206.2 firmware and then the 7.18.206.2 RUU
or
you can relock the bootloader flash the 7.18.206.2 firmware, unlock the bootloader flash twrp recovery and restore the 7.18.206.2 nandroid backup
Click to expand...
Click to collapse
@alray i have to put S-OFF?
deckard10 said:
1 guy help me with this and now i got stock rom and stock recovery but when i install OTA's the phone enter in bootloop... what is the problem??
the rom that i installed is Guru_Reset_M7_2.24.161.1 but have to install some apk's manualy
In this process i never relock bootloader
Click to expand...
Click to collapse
You can't use 2.24.161.1 with your actual firmware version, its too old hence why you should use the 7.x version
alray said:
You can't use 2.24.161.1 with your actual firmware version, its too old hence why you should use the 7.x version
Click to expand...
Click to collapse
but i need S-off?? i try the sunshine and said "sunshine require a kernel and rom closer to stock than your pls flash a stock boot.img and rom and try again"
deckard10 said:
where i can find this version?
Click to expand...
Click to collapse
hummm..... post #7 maybe....
alray said:
hummm..... post #7 maybe....
Click to expand...
Click to collapse
y i saw it... but the RUU will not work right? because S-ON?
deckard10 said:
y i saw it... but the RUU will not work right? because S-ON?
Click to expand...
Click to collapse
it should work if its a signed ruu otherwise you can do what said below with the stock firmware, twrp, nandroid backup
@alray i try use 2x rumrunner to put S-OFF but doesnt work... why?
deckard10 said:
@alray i try use 2x rumrunner to put S-OFF but doesnt work... why?
Click to expand...
Click to collapse
if you want to s-off use sunshine or you can restore your phone using the second method even if s-on.
relock the bootloader, flash the firmware, unlock the bootloader, flash twrp, restore the nandroid backup.