Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Hurders

  • Rank
  1. [Recovery] TWRP 3.0.2-0

    No noticeable problems with the touchscreen in TWRP. Any signs of differing GPS drivers between the AS and EU kernels?
  2. [Recovery] TWRP 3.0.2-0

    Right, so: 1. Replacing /system/build.prop with the EU one didn't work - bootloop reboot. 2. Replacing boot.img with EU one did work and it booted ok. So can we assume hardware differences?
  3. [Recovery] TWRP 3.0.2-0

    Just tested using a repacked EU B08 with files removed and updater-script modified and it booted ok like stock. Must be some variants between the AS and EU hardware then?
  4. [Recovery] TWRP 3.0.2-0

    Well I tried to flash it again but did a factory wipe before, still no good, bootloops, doesn't actually get as far as the animated ZTE splash screen, shows the static ZTE splash screen for a few seconds then reboots and repeats over and over. Looks like I'll have to give it up as a bad job!
  5. [Recovery] TWRP 3.0.2-0

    Yes, does the firmware need repacking in a special way? I assumed it would be ok just to flash the zip through TWRP?
  6. [Recovery] TWRP 3.0.2-0

    I went ahead and flashed the modified zip (after nandroid backup!) which flashed ok but didn't work, phone got stuck in bootloop, restored the nandroid backup ok. I didn't wipe any partitions prior to flashing, should I have done?
  7. [Recovery] TWRP 3.0.2-0

    Ok, really appreaciate the help, got it ready I think, can I just flash my zip file (with files/folders removed and modified updater-script) directly in TWRP? or do I need to make a recovery.img from it? I'm a TWRP newbie, not done much custom rom work since CWM on my original blade 1 way back in the day!
  8. [Recovery] TWRP 3.0.2-0

    Ok got it, so what about the /persist directory. I should get rid of that too? And also the lines in the updater-script referencing it?
  9. [Recovery] TWRP 3.0.2-0

    The stock firmware packages don't seem to have typical bootloader, modem or recovery images contained within. All I see is the boot.img and a splash.img in the root (which I assume is something to do with the boot logo?), there's also a NON-HLOS.bin which I assume is the modem image? and also the folders /system, /meta-inf and /persist. There is also a /recovery folder which I assume contains the recovery image (there's a .sh file inside a /bin folder in there?). Can't see any obvious bootloader images? So, if I were to repackage the rom just containing the boot.img and /system folder (can that easily be done?) would that be flashable in TWRP?
  10. [Recovery] TWRP 3.0.2-0

    Ok good point, but you say if we repack a stock firmware for custom recovery then that would work? My reasons are my S6 (EU B08) has a big issue with the GPS not working (sees plenty of satellites but refuses to lock on to any ever, seems to be widespread issue on some EU S6 handsets), so if there was a way to try and flash the AS B12 firmware then I'd be tempted to give it a try. Possibly a dumb question but would a TWRP backup prior to flashing be a safeguard to revert to if the AS firmware then bricked the phone?
  11. [Recovery] TWRP 3.0.2-0

    So you're saying that we still shouldn't try flashing the AS firmware on EU handsets using TWRP?
  12. [Recovery] TWRP 3.0.2-0

    So AS and EU varients use the same patition layout and same TWRP versions then? I thought they were different and that was wy we couldn't flash AS firmware on EU devices?
  13. Just checking, this firmware won't work on an EU blade? Current firmware on mine is EU B08, my GPS doesn't work at all so want to see if newer firmware will fix but obviously don't want to brick?
  14. Nhede, I tried again, did a full wipe and installed your rom again with latest xposedframework in system/app. Ran/installed xposed, rebooted, installed gravity box (jb) via module downloader, enabled/rebooted. No joy, lockscreen image is still the default jellybean one. If you change the gravitybox settings to use a custom image then that seems to work (but not a proper solution) but if you have the setting as default background it always goes back to the standard jellybean background on the lockscreen rather than whatever you have as your current wallpaper.