Develop Bugs

Stuck in bootloop, can't flash

Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance

Bump in hopes of a solution

And another bump, any help would be greatly appreciated

I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.

bumping because I'm having the same issue, coming back to stock after having CM12.1

As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working

I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.

Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.

KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk

ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.

KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...

Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?

Really Bricked m9... Please Pro help required.

My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff

nobody?? :'(

Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.

computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1

Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?

Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.

Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up

Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).

Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!

im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?

logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.

Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work

Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk

I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution

Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...

bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"

Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.

copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse

bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU

So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip

[Optus M9] Need 3.50.710.1 RUU or the latest radio.img My SIM has vanished.

Hi guys,
I hope this is in the right forum. While the Ressurection Remix ROM broke my radio, my goal is to flash to stock so I can start again with a functioning radio and try something else.
The install went well: unlocked and installed TWRP just fine. The new ROM installed without a hitch but when it started I noticed that there was no SIM detected.
I found an RUU that looks to be the one I need: (0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_AUS_1.32.710.16_Radio_01.01_U11440261_56.02.50306G_2_F_release_427214_signed ) and extracted the radio.img and used the scripts here to create an installable zip. But, then I read that I need S-Off and Sunshine says that my ROM is not stock enough to get S-Off... So I can not patch the radios in.
But when I try to install the RUU (relocked etc) it also fails as do the TWRP stock backups here
What am I missing?

Try restoring a stock nandroid backup from flippys thread and then get s off
ICE M9

Roobwz said:
Try restoring a stock nandroid backup from flippys thread and then get s off
ICE M9
Click to expand...
Click to collapse
Thanks, I'll give it a go in a couple hours and let you know how it goes.

ghostcorps said:
Thanks, I'll give it a go in a couple hours and let you know how it goes.
Click to expand...
Click to collapse
Do you mean the TWRP Stock Backups?
TWRP Restore can't see the zips and I can not extract them to the phone because the system images' are larger than 4gb. As far as I know, I can not flash a backup image over usb, if I could I would have much less trouble for sure.
Also, fastboot shows the version as:
Code:
#fastboot getvar version-main
version-main: 3.50.710.1

ghostcorps said:
Do you mean the TWRP Stock Backups?
TWRP Restore can't see the zips and I can not extract them to the phone because the system images' are larger than 4gb. As far as I know, I can not flash a backup image over usb, if I could I would have much less trouble for sure.
Also, fastboot shows the version as:
Code:
#fastboot getvar version-main
version-main: 3.50.710.1
Click to expand...
Click to collapse
Yes i meant stock nandroid backups. You can find them in flippys thread in the general forums
ICE M9

Roobwz said:
Yes i meant stock nandroid backups. You can find them in flippys thread in the general forums
ICE M9
Click to expand...
Click to collapse
Thanks for clarifying
Are there any Nandroid backups with a smaller system image? 4gb+ seems to render them useless for me
Now that I am at my PC I can show you some more logs:
(ROM.zip = 0PJAIMG_HIMA_UHL_L51_SENSE70_MR_hTC_Asia_AUS_2.9.710.5_Radio_01.04_U11440601_71.02.50709G_F_release_452741_signed.zip)
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
OKAY [ 1.008s]
writing 'zip' 1/1...
(bootloader) HOSD CL#761596
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_t
(bootloader) KTVsG
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.044s
I assume this is because the current software version (3.50.710.1) is newer than the RUU (2.9.710.5)?

ghostcorps said:
Thanks for clarifying
Are there any Nandroid backups with a smaller system image? 4gb+ seems to render them useless for me
Now that I am at my PC I can show you some more logs:
(ROM.zip = 0PJAIMG_HIMA_UHL_L51_SENSE70_MR_hTC_Asia_AUS_2.9.710.5_Radio_01.04_U11440601_71.02.50709G_F_release_452741_signed.zip)
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2317440227 is not a multiple of the block size 4096
OKAY [ 1.008s]
writing 'zip' 1/1...
(bootloader) HOSD CL#761596
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_t
(bootloader) KTVsG
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.044s
I assume this is because the current software version (3.50.710.1) is newer than the RUU (2.9.710.5)?
Click to expand...
Click to collapse
Correct, you cannot downgrade with a stock backup. You need s off and a RUU/firmware.zip.
You gotta find a backup that matches your firmware 100%
ICE M9

Roobwz said:
Correct, you cannot downgrade with a stock backup. You need s off and a RUU/firmware.zip.
You gotta find a backup that matches your firmware 100%
ICE M9
Click to expand...
Click to collapse
How do I get S-Off without a stock OS? Or can I possibly install the radio.img with S-On?
Otherwise I am pretty much screwed yeh?

ghostcorps said:
How do I get S-Off without a stock OS? Or can I possibly install the radio.img with S-On?
Otherwise I am pretty much screwed yeh?
Click to expand...
Click to collapse
Bro I'm not that into firmwares that aren't popular... but it cant make things worse to try to flash a custom sense Rom as leedroid or Ice. It's enough to just boot it to get soff. Either that or just stay on that rom.
ghostcorps said:
How do I get S-Off without a stock OS? Or can I possibly install the radio.img with S-On?
Otherwise I am pretty much screwed yeh?
Click to expand...
Click to collapse
ICE M9

Roobwz said:
Bro I'm not that into firmwares that aren't popular... but it cant make things worse to try to flash a custom sense Rom as leedroid or Ice. It's enough to just boot it to get soff. Either that or just stay on that rom.
ICE M9
Click to expand...
Click to collapse
I would stay on the ROM if I could get the radio.img installed. It works fine otherwise.
But you make a lot of sense. I will try some other ROMs and see if they work better with Sunshine.

Sunshines S-Off seems to like Ice more than Ressurection Remix but after shelling out $25US the app has been 'Unlocking' the phone for 15 minutes The progress bar is moving but it just starts again when it gets to the end.
I am going to work now so will just leave it and hope that it is done when I get home.

ghostcorps said:
Sunshines S-Off seems to like Ice more than Ressurection Remix but after shelling out $25US the app has been 'Unlocking' the phone for 15 minutes The progress bar is moving but it just starts again when it gets to the end.
I am going to work now so will just leave it and hope that it is done when I get home.
Click to expand...
Click to collapse
If it doesnt work, try viper. Read somewhere that their ROMs always works with sunshine.
Skickat från min HTC One M9 via Tapatalk

Sunshines S-Off worked with Ice
Now to see if the radio.img will actually fix my problem...

Nope.
I am going to do some more research on installing the radio.img, hopefully I am doing something wrong there.
If anyone can supply me with the latest Optus radio.img file, I would be eternally grateful

I had the same issue trying to flash Leedroid from the same firmware. After some research I installed thicklizards Minimillistic kernel from here:
http://forum.xda-developers.com/sprint-one-m9/development/kernel-minimillistic-t3321416
After it installed it fixed all my problems, still on Leedroid and radios working again. Just make sure you download the RC2 version and not the RC3.

cwf124 said:
I had the same issue trying to flash Leedroid from the same firmware. After some research I installed thicklizards Minimillistic kernel from here:
http://forum.xda-developers.com/sprint-one-m9/development/kernel-minimillistic-t3321416
After it installed it fixed all my problems, still on Leedroid and radios working again. Just make sure you download the RC2 version and not the RC3.
Click to expand...
Click to collapse
Thanks!
I have just finished updating it to the latest stock version so I can get a backup this time but, that sounds like a very promising solution
Why not RC3? I can't seem to find RC2.

ghostcorps said:
Thanks!
I have just finished updating it to the latest stock version so I can get a backup this time but, that sounds like a very promising solution
Why not RC3? I can't seem to find RC2.
Click to expand...
Click to collapse
In the end, I am back on stock and looking for something else to try. The root of the problem is that for whatever reason, and CM13 based mods seem to break my radio and only stock RUUs seem to fix it. I am going to try installing Ice over the stock ROM and seeing what happens.

Issue trying to go stock (S-On)

Hi guys!
My HTC one M9 was rooted, running Android 5.0.2 and i had Twrp recovery set up.
Since i was S-On and i'm a total noob/asshat i never tried to load any rom or mods onto my system =)
Now i wanted to try and get back to stock, so i could receive OTA updates, and after getting Nougat (even if i had to wait a long time for it), then i'd just root again and enjoy the lack of bloatware.
In this order i:
-Unrooted through the SuperSu
-Checked to see if it was unrooted using rootchecker
-Found my stock recovery mode here: http://forum.xda-developers.com/one...collection-t3132698/post61286815#post61286815
-Went to ADB, opened the command prompt
-Went to download mode
-entered fastboot flash recovery HIMA_UHL_Stock_Recovery_1.32.401.15.img
From there, i took my phone and on the phone itself tried to go to recovery mode to check..
The screen went black, it went to (the stock!!!) recovery mode, but now the system can't reboot.
I've seen the same question asked, but not for S-On phone or done in about the same way i did..
My info:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
There are recovery logs on my phone but they are very long and i honestly don't know how or if i can retrieve them through ADB, if any of you should think it necessary and can tell me what command to put in, i'll bring them up right away!
thanks alot for your time, i'm very sorry to bother you with this
Edit: after encountering the issue, i tried wiping the cache partition and factory reset options but to no avail.
flashed twrp recovery back in, no change.

So, you found the correct stock recovery in my thread and didn't read the warning above the download links? Since I'm currently revamping the thread, it would be nice if you could tell me why you didn't read it. Was it to small? Was the colour unreadable? (This is a serious question. I'm not making fun of you. I really need to know that for being able to improve the thread.)
Flash a 401 RUU. Instructions and download links can be found in the same thread.
Sent from my HTC One M9 using XDA Labs

*made mistake, please ignore*

Flippy498 said:
So, you found the correct stock recovery in my thread and didn't read the warning above the download links? Since I'm currently revamping the thread, it would be nice if you could tell me why you didn't read it. Was it to small? Was the colour unreadable? (This is a serious question. I'm not making fun of you. I really need to know that for being able to improve the thread.)
Flash a 401 RUU. Instructions and download links can be found in the same thread.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Sorry man.
You can see from the time it was between 3 and 4 AM =D
I read all your info, i just read it all again, but for some reason i didn't pay attention to
"Read the Backup or the RUU tab of my google sheet if you want to be able to receive and install OTAs, again.
Simply unrooting your device and reflashing the Stock Recovery is not enough due to the block-based OTAs."
I honestly have no *cursing* idea why that didn't register in my brain.
My apologies in any case. Your thread is fine, it's the most helpful i've come across for my phone in days.
I never flashed anything before, and i knew absolutely **** (not that i know alot right now =D but at least i'm learning). Without your thread, i'd probably still be looking.
i flashed the stock recovery (HIMA_UHL_Stock_Recovery_1.32.401.15) back on, got 1.32.401.15 Ruu from your thread
unfortunatly i don't have an SD card.
I tried flashing from platform tools the 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip file
but got this message:
C:\Users\pc\Desktop\platform-tools>fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SENSE
70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_4268
91_signed.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
OKAY [ 1.053s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.076s
i think the guy here http://forum.xda-developers.com/one-m9/help/urgent-help-bricked-htc-one-m9-t3138987
had the same issue so i'm trying to solve from here, and if not i'll go out and buy an SD card, though i don't know if that'll work, my computer doesn't see my phone at the moment

As written in my thread you can't flash M9 RUUs with fastboot. You need HTC_fastboot.
Sent from my HTC One S using XDA Labs

Flippy498 said:
As written in my thread you can't flash M9 RUUs with fastboot. You need HTC_fastboot.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So i tried, i changed adb fastboot to the htc_fastboot.exe and now i get this:
C:\Users\pc\Desktop\platform-tools>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_L50_S
ENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_
426891_signed.zip
sending 'zip'... (101066 KB) OKAY
sending time = 7.986 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 9(s)
Okay! edit: i'm an idiot. i put things back in order, downloaded htc_fastboot from here: http://d-h.st/6LC (thanks brandon gunderson) and tried again.
Unfortunatly now i get this:
C:\Users\pc\Desktop\htc_fastboot>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SEN
SE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_42
6891_signed.zip
htc_fastboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
(it means: htc_fastboot is not recognized as an internal or external command, program or batch file)
still an idiot. No idea what's wrong
you said in the thread:
Important Notes:
I won't support flashing RUU.exe files or flashing RUU.zip files via HTC_fastboot in this thread. There have been too many reports of people having problems with these methods. Trying to find the reason for the problems can be quite frustrating and time-consuming. The SD card method on the other hand is much easier and less time-consuming than searching for user errors if the other methods fail.
If you only have a RUU.exe at hand you can extract the *.zip file using these instructions. Although they're a bit older they can still be used with M9 RUUs.
so i went to that other thread to find out how i could do it

Yeah, I wrote that part because of all the problems that arise most of the times if people try to flash RUUs via fastboot and all the risks that are connected with this method. As you can see your try isn't an exception.
The bootloader needs to be locked or re-locked if you use the HTC_fastboot method. However, I don't recommend doing so if you aren't 100% sure that you can flash the RUU without any issues afterwards. If your phone isn't completely stock your phone won't boot anymore after it got (re-)locked. That is a security feature that prevents the phone from getting bricked if anything is modified. You can't even enter TWRP, anymore, in that situation if it's installed. In addition it's impossible to re-unlock the bootloader if your phone is S-ON and the option "OEM Unlock" isn't activated in the developer options. (Sidenote: The option got introduced with firmware 2.x. So in your current situation re-locking is safe. However, as soon as you updated your phone to a higher firmware version you shouldn't do it unless you know that you have a working RUU at hand and you know that you are able to flash it.)

Flippy498 said:
Yeah, I wrote that part because of all the problems that arise most of the times if people try to flash RUUs via fastboot and all the risks that are connected with this method. As you can see your try isn't an exception.
The bootloader needs to be locked or re-locked if you use the HTC_fastboot method. However, I don't recommend doing so if you aren't 100% sure that you can flash the RUU without any issues afterwards. If your phone isn't completely stock your phone won't boot anymore after it got (re-)locked. That is a security feature that prevents the phone from getting bricked if anything is modified. You can't even enter TWRP, anymore, in that situation if it's installed. In addition it's impossible to re-unlock the bootloader if your phone is S-ON and the option "OEM Unlock" isn't activated in the developer options. (Sidenote: The option got introduced with firmware 2.x. So in your current situation re-locking is safe. However, as soon as you updated your phone to a higher firmware version you shouldn't do it unless you know that you have a working RUU at hand and you know that you are able to flash it.)
Click to expand...
Click to collapse
thank you very much man.
i know questions like this must annoy you, and i'm very sorry for bothering you. I'm learning though =)
At this point, after the failed attempts to flash, is it still possible for me to use an SD card? If so i'm going to get one right away.
My worry is, though, that since my phone doesn't register on my computer, how i'll get the file on the SD card... I'm thinking i'll pass by a friend, put it in his phone, load the file on the SD card, put the card in my phone again, change recovery back to twrp and try to flash from there?

Please read the instructions for the SD card method. Chances are high that it's not possible to copy the RUU onto the SD card while it's put into the phone. You probably need a SD card reader.
The SD card method is completely independent of the fastboot method. And as long as the fastboot method fails completely (as in your situation) chances are high that you can still recover your phone with the other method.
Sent from my HTC One S using XDA Labs

Flippy498 said:
Please read the instructions for the SD card method. Chances are high that it's not possible to copy the RUU onto the SD card while it's put into the phone. You probably need a SD card reader.
The SD card method is completely independent of the fastboot method. And as long as the fastboot method fails completely (as in your situation) chances are high that you can still recover your phone with the other method.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
things aren't going well for me today.
I have an SD adapter for micro SD that i can plug into my laptop. I renamed the Ruu zipfile "0PJAIMG.zip", that is the name (in the name i included .zip, that's supposed to be like that, no?)
I put off my phone, put the card in, rebooted to download mode.... Nothing.
tried to boot, it failed (of course), then i got the following menu:
Reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
i tried the "apply from sd card" option but it says:
fail to open file: /sys/devices/platform/android_usb/host mode
Wrtie host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
E: Find no match PARTITION for package path /sdcard/ptt.zip
E: unknown volume for path
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package...
E: failed to map file
i tried flasing from the twrp recovery (install, from SD card-. Received the following:
Updating partition details....
.... done
Full SELinux support is present.
Installing '/external_sd/0PJAIMG.zip.zip"...
Checking for MD5 file....
Skipping MD5 check: no MD5 file found
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/0PJAIMG.zip.zip'
Updating partition details...
... done
FAILED
the SD card is a 32GB Samsung SD card (MB-MC32D model), and it's FAT32
any idea what went wrong? (also, i seem to have hit my max "thank you!" 's i can give out today, i'll be sure to thank any replies that are left tomorrow!)

Fatimiyye said:
things aren't going well for me today.
I have an SD adapter for micro SD that i can plug into my laptop. I renamed the Ruu zipfile "0PJAIMG.zip", that is the name (in the name i included .zip, that's supposed to be like that, no?)
I put off my phone, put the card in, rebooted to download mode.... Nothing.
tried to boot, it failed (of course), then i got the following menu:
Reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
i tried the "apply from sd card" option but it says:
fail to open file: /sys/devices/platform/android_usb/host mode
Wrtie host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
E: Find no match PARTITION for package path /sdcard/ptt.zip
E: unknown volume for path
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package...
E: failed to map file
i tried flasing from the twrp recovery (install, from SD card-. Received the following:
Updating partition details....
.... done
Full SELinux support is present.
Installing '/external_sd/0PJAIMG.zip.zip"...
Checking for MD5 file....
Skipping MD5 check: no MD5 file found
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/0PJAIMG.zip.zip'
Updating partition details...
... done
FAILED
the SD card is a 32GB Samsung SD card (MB-MC32D model), and it's FAT32
any idea what went wrong? (also, i seem to have hit my max "thank you!" 's i can give out today, i'll be sure to thank any replies that are left tomorrow!)
Click to expand...
Click to collapse
so yeah. I'm an idiot. thought i wasn't, but i am.
named it 0PJAIMG without the '.zip' at the back and worked fine. Hope i can install OTA's now

Fatimiyye said:
so yeah. I'm an idiot. thought i wasn't, but i am.
named it 0PJAIMG without the '.zip' at the back and worked fine. Hope i can install OTA's now
Click to expand...
Click to collapse
Yes, OTAs shouldn't be a problem now.
Well, we all make mistakes. You live and learn.

Flippy498 said:
Yes, OTAs shouldn't be a problem now.
Well, we all make mistakes. You live and learn.
Click to expand...
Click to collapse
Thank you very much for your help man =)
The whole thing is stock now, took hours to update it all but i'm on the latest update available here for marshmallow, so i'm quite pleased.
from what i've gathered it's not possible for me to flash Nougat without S-OFF so i'll very likely keep notes on how i did this, and either wait for nougat before re-rooting, or get S-OFF and hurt my (and maybe your) head again trying to get my phone the way i want it xD
cheers man! <3

HTC 10 UK Version

Hi, i have HTC 10 UK Version. OS 2.41.91.31 Rooted S-ON. i accidentally delted my internal storage and Rom in TWRP. I have backup in SD CARD but it is not workin when i restore it just stuck on HTC logo then reboot and in a loop.
Any help?

Em.. How you can accidentally click internal storage and System?
Nevermind. If you restored system successfully and it's stuck in htc logo then... I think you deleted something else too and the best option is restore full system image or RUU. It's my opinion and i can be wrong. I have only oreo images unfortunately and with .401. so i can't help you maybe someone else have backups of nougat rom.

Hi, thanks for responding. I amnot very expert in Roms etc. You can give me oreo image that wiill be fine. I can't find any RUU for this model. I just want it to get it work again.
HTC Dev website nly has kernals for EE UK HTC 10. There isn'ta anything else on whole internet. In XDA i found a stock recovery for this model EVE__XXX. Which caused this issue.

imDCStar said:
Hi, thanks for responding. I amnot very expert in Roms etc. You can give me oreo image that wiill be fine. I can't find any RUU for this model. I just want it to get it work again.
HTC Dev website nly has kernals for EE UK HTC 10. There isn'ta anything else on whole internet. In XDA i found a stock recovery for this model EVE__XXX. Which caused this issue.
Click to expand...
Click to collapse
That stock recovery didn't caused this issue. You yourself caused this issue.
You need a RUU 2.41.91 or a higher one (example) 3.16.91. I know firmware gem flash (website) holds many RUU's..... have a look there and pray they have it.

Mr Hofs said:
That stock recovery didn't caused this issue. You yourself caused this issue.
You need a RUU 2.41.91 or a higher one (example) 3.16.91. I know firmware gem flash (website) holds many RUU's..... have a look there and pray they have it.
Click to expand...
Click to collapse
You mean this. Will this RUU work. https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2035

imDCStar said:
You mean this. Will this RUU work. https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2035
Click to expand...
Click to collapse
No 2.41.91. I don't see any. 2.41.91 in any of those files, please read well. No idea how you came up with those. When i type your OS number i get a instant hit.
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51637

Mr Hofs said:
No 2.41.91. I don't see any. 2.41.91 in any of those files, please read well. No idea how you came up with those. When i type your OS number i get a instant hit.
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51637
Click to expand...
Click to collapse
Got it. I cant make payment using my Credit Card as there is no option there. Can you help. I do not have paypal.

imDCStar said:
Got it. I cant make payment using my Credit Card as there is no option there. Can you help. I do not have paypal.
Click to expand...
Click to collapse
Sorry no, i am never giving support on people's payment options. I'm drawing the line at giving support here and if i have the files i will share but i don't have an account at that website.
I checked the website, continue with PayPal and you see the option to pay via creditcard. Problem solved

Mr Hofs said:
Sorry no, i am never giving support on people's payment options. I'm drawing the line at giving support here and if i have the files i will share but i don't have an account at that website.
I checked the website, continue with PayPal and you see the option to pay via creditcard. Problem solved
Click to expand...
Click to collapse
Downloaded the firmware flashing in downloadmode using SDCARD. Getting 22 RU_HEADER_ERROR :crying:

Try download again, check md5 of that file. It can be something wrong with that downloaded zip.

Mr Hofs said:
Sorry no, i am never giving support on people's payment options. I'm drawing the line at giving support here and if i have the files i will share but i don't have an account at that website.
I checked the website, continue with PayPal and you see the option to pay via creditcard. Problem solved
Click to expand...
Click to collapse
ShadoV90 said:
Try download again, check md5 of that file. It can be something wrong with that downloaded zip.
Click to expand...
Click to collapse
Ok checking and re downloading.

I was trying to flash using ADB Fastboot getting this error.
JUST TO MAKE SURE
DEVICE: HTC 10 UK EE VERSION
SYSTEM MODIFIED, S- ON - Bootload UNLOCKED.
OS: 2.41.91.31
Problems:
- Htc logo reboot loop even from stock TWRP Restore.
- Cant flash any rom successfuly.
ADB Log
C:\adb>fastboot flash zip 2PS6IMG.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
OKAY [ 1.023s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_l
(bootloader) 3gExy
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.346s

imDCStar said:
I was trying to flash using ADB Fastboot getting this error.
JUST TO MAKE SURE
DEVICE: HTC 10 UK EE VERSION
SYSTEM MODIFIED, S- ON - Bootload UNLOCKED.
OS: 2.41.91.31
Problems:
- Htc logo reboot loop even from stock TWRP Restore.
- Cant flash any rom successfuly.
ADB Log
C:\adb>fastboot flash zip 2PS6IMG.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1966691128 is not a multiple of the block size 4096
OKAY [ 1.023s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_l
(bootloader) 3gExy
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.346s
Click to expand...
Click to collapse
No idea why it's not working, the ruu should be fine. Did you download the full RUU right ? Not the firmware.....those are 2 different things.
If you want your phone up and running at least i have a custom rom that will work. At least for now so at least you can use your device again.
https://www.androidfilehost.com/?fid=1322778262903991031
Flash that with TWRP and your phone should boot up. I'm brainstorming when i have more time. But the full RUU 2.41.91 (around 2 gig) should do the trick.

Mr Hofs said:
No idea why it's not working, the ruu should be fine. Did you download the full RUU right ? Not the firmware.....those are 2 different things.
If you want your phone up and running at least i have a custom rom that will work. At least for now so at least you can use your device again.
https://www.androidfilehost.com/?fid=1322778262903991031b
Flash that with TWRP and your phone should boot up. I'm brainstorming when i have more time. But the full RUU 2.41.91 (around 2 gig) should do the trick.
Click to expand...
Click to collapse
Yeah i downloaded the RUU. It a zip with some zips inside it. around 1..8gigs there are two RUUs on https://firmware.gem-flash.com/index.php?a=search&b=2.41.91.31 I downloaded the first one.
The link you provided is showing 404 error.

"99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues."
"For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!"
So... maybe try to go into download mode and flash that from SD card, but in my opinion it can be, because that zip can be somewhat modified
I saw link by MrHofs (previous, earlier, not current), and i see in name of that file "combined_signed" it means it can be flashed only when your phone is at S-OFF state... i think.

ShadoV90 said:
"99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues."
"For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!"
So... maybe try to go into download mode and flash that from SD card, but in my opinion it can be, because that zip can be somewhat modified
I saw link by MrHofs (previous, earlier, not current), and i see in name of that file "combined_signed" it means it can be flashed only when your phone is at S-OFF state... i think.
Click to expand...
Click to collapse
I see the combined signed and the signed indeed, i did offer somebody else here at xda some assistance and sent that user to gem flash too and he flashed a combined signed version to its S-ON unlocked device so i assumed this would be appropriate too now.........but then again assumption is the mother of all f ups........
In my humble opinion signed is signed, combined or not. So that would not be the issue here. I had another case lately where the absolute correct RUU didn't flash and up to today i still don't know why
---------- Post added at 08:20 PM ---------- Previous post was at 08:18 PM ----------
imDCStar said:
Yeah i downloaded the RUU. It a zip with some zips inside it. around 1..8gigs there are two RUUs on https://firmware.gem-flash.com/index.php?a=search&b=2.41.91.31 I downloaded the first one.
The link you provided is showing 404 error.
Click to expand...
Click to collapse
My apologies, link is fixed......was a typo

ShadoV90 said:
"99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues."
"For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definetely this means the ZIP is not signed - get an unmodified zip!"
So... maybe try to go into download mode and flash that from SD card, but in my opinion it can be, because that zip can be somewhat modified
I saw link by MrHofs (previous, earlier, not current), and i see in name of that file "combined_signed" it means it can be flashed only when your phone is at S-OFF state... i think.
Click to expand...
Click to collapse
I redownloaded and checked MD5 for both files. It is same. Can you please guide how to S-OFF

I understand. You are more experienced than me, so probably you are right.
But don't hurt trying:
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51635
Maybe this just signed file will be good...
EDIT: In order to be S-OFF you need working system, and sunshine app (and 25$ because S-OFF is paid feature), so it's AFAIK impossible for you at this time.
I am trying to figure out solution for this situation... if just signed file won't work.

ShadoV90 said:
I understand. You are more experienced than me, so probably you are right.
But don't hurt trying:
https://firmware.gem-flash.com/index.php?a=browse&b=file-info&id=51635
Maybe this just signed file will be good...
EDIT: In order to be S-OFF you need working system, and sunshine app (and 25$ because S-OFF is paid feature), so it's AFAIK impossible for you at this time.
I am trying to figure out solution for this situation... if just signed file won't work.
Click to expand...
Click to collapse
Already gave a link to a working (custom) rom. Sunshine should work with it. If not we will find another stock like rom to enable sunshine.

Mr Hofs said:
Already gave a link to a working (custom) rom. Sunshine should work with it. If not we will find another stock like rom to enable sunshine.
Click to expand...
Click to collapse
Downloading rom. I hope this one works. I tried another custom OREO rom. It installed but same loop on boot logo. After i cant flash anything even cant restore backup using TWRP. (Backup used to restore fine earlier but loop on boot logo)
This device is getting worse and worse. I hope this Rom works. Lets see. Thanks for helping out. I will give feedback after flashing it.