Jelly 2E not able to get back to stock after bootloop

[yona-h]

When trying to flash my Jelly 2E with lineageOS I came across an error after the Flash Boot Image step (I did the unlocking and rooting steps before, it was already Android 12). The phone would get stuck in a bootloop saying it's in orange state, booting, rebooting again.

To get back to stock rom, I tried using SPFlash tool and the stock ROM following this guide:
https://romprovider.com/unihertz-jelly-2e-firmware-stock-rom/
Afterwards I found the (official?) firmware and Flashtool from Unihertz at
https://drive.google.com/drive/folders/0By1nhWOmuw2KdDhTUlFOZHpXQjg?resourcekey=0-KHJPIYVPw2iHL--cceWyaw
There is also a pdf there explaining downloads, drivers and flashing.

I tried all 5 stock rom images (one from romprovider, 4 "official" ones), using SPflash and Unihertz' SPFlash. But whatever I try, it always seems to successfully flash the image, but when I start the Jelly2E, the screens keeps being black, with just a hint of the backlight. When I then plug it into my PC, the screens goes partially white with a vignetting "effect" and blinks that way, sometimes reversing the colors. I also get vabration feedback when touching the on/off or the home-button.
No Fastboot or any text appears anymore.

Did someone have similar issues or even a solution to unbrick it? Thanks in advance!

[rumplestilzken]

Use http://rumplestilzken.com:14005/Unihertz/StockResources this spflashtool dont use the software provided by unihertz. Do you have tee or eea device? I have roms for both. Orange state indicates you have an unlocked phone.

…

On Sun, Jul 21, 2024, 10:11 AM yona-h ***@***.***> wrote: When trying to flash my Jelly 2E with lineageOS I came across an error after the Flash Boot Image step (I did the unlocking and rooting steps before, it was already Android 12). The phone would get stuck in a bootloop saying it's in orange state, booting, rebooting again. To get back to stock rom, I tried using SPFlash tool and the stock ROM following this guide: https://romprovider.com/unihertz-jelly-2e-firmware-stock-rom/ Afterwards I found the (official?) firmware and Flashtool from Unihertz at https://drive.google.com/drive/folders/0By1nhWOmuw2KdDhTUlFOZHpXQjg?resourcekey=0-KHJPIYVPw2iHL--cceWyaw There is also a pdf there explaining downloads, drivers and flashing. I tried all 5 stock rom images (one from romprovider, 4 "official" ones), using SPflash and Unihertz' SPFlash. But whatever I try, it always seems to successfully flash the image, but when I start the Jelly2E, the screens keeps being black, with just a hint of the backlight. When I then plug it into my PC, the screens goes partially white with a vignetting "effect" and blinks that way, sometimes reversing the colors. I also get vabration feedback when touching the on/off or the home-button. No Fastboot or any text appears anymore. Did someone have similar issues or even a solution to unbrick it? Thanks in advance! — Reply to this email directly, view it on GitHub <#55>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA27YVRCS3CIQK4BWZVP6FTZNO6SBAVCNFSM6AAAAABLG4TLV6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDCNBSGMZDIMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[rumplestilzken]

Are you using windows or linux?

[rumplestilzken]

Use my rom and spflashtool version with 'firmware upgrade' selected. This will additionally lock your boot loader, but should get you out of bootloop.

[yona-h]

oh good, didn't see that one. It should be EEA, I'm on Windows.
To be clear: the jelly is not in a bootloop anymore, as it boots just once, but without any splashscreen or further information, only a blank (black) screen.

Thanks, I'll try that!

[yona-h]

so, the process was the same to what I did before, just with another Flash Tool-Version and your provided ROM. It didn't change the outcome though.
In the guide you say something about if the DA doesn't load automatically. In my case, it always chooses the MTK_AllInOne_DA.bin from the FlashTool directory, even before connecting my phone. Should it choose another one from the device after connecting?

[rumplestilzken]

You only need a special da if they provide one in a folder called da in stock rom.

…

On Mon, Jul 22, 2024, 5:45 AM yona-h ***@***.***> wrote: so, the process was the same to what I did before, just with another Flash Tool-Version and your provided ROM. It didn't change the outcome though. In the guide you say something about if the DA doesn't load automatically. In my case, it always chooses the MTK_AllInOne_DA.bin from the FlashTool directory, even before connecting my phone. Should it choose another one from the device after connecting? — Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA27YVWKA7TK26GBQ3M4CSTZNTIEZAVCNFSM6AAAAABLG4TLV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBSGUZTSMRQGI> . You are receiving this because you commented.Message ID: ***@***.***>

[rumplestilzken]

so, the process was the same to what I did before, just with another Flash Tool-Version and your provided ROM. It didn't change the outcome though. In the guide you say something about if the DA doesn't load automatically. In my case, it always chooses the MTK_AllInOne_DA.bin from the FlashTool directory, even before connecting my phone. Should it choose another one from the device after connecting?

I think what i was getting at is if DA doesnt load you need to load udev rules in linux or install drivers for windows.

[yona-h]

ok thanks a lot. I'll keep trying this method. If I don't get it to work, can I donate the jelly somewhere? Would you be interested in it?