Recent content by DTronix

  1. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    I just followed Stethix guide on unbricking () System wipe failed (I think it's bc I already did that before) I deleted the saves he said, like you said except there was no file that ended in 21, only d1, maybe that's what you meant ? Anyway it didn't work. still a black screen...
  2. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Ok I have a Samsung, i'll go with a v4, thanks !
  3. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    I know but my friend forgot to tell me the serial before I ordered the chip... How can I rebuild a nand if my backup is already corrupted ?
  4. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Ok I will buy one... Everyone told me that Pico was better... I usually only do OLEDs and I thought V1 and V2 were easier ! I will try rebuilding the NAND by removing the chip and using the RCM fusée gelée exploit and we'll see where it leads...
  5. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    How should I fix it ? I'm trying the Nand rebuild method but with a FW17 thats been downloaded from internet... Hope it works...
  6. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Damn.. I should have known that... After installing the chip and before any SD prep I tried vol+ and Vol- on the NO SD screen to boot HOS but the issue started there... So my first nand back up is already corrupted if you are right... I must rebuild it from scratch I think.
  7. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Correct.
  8. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    I would agree with you but the fact that Hekate can read it and i can dump it makes me think that the Nand is fine, and the problem should be the data inside that’s corrupted... Is there a way to rebuild a nand from scratch ? The guide I followed made me dump the firmware from the Nand, so if...
  9. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Same result, I had the same entry that I already tried, but mine had the stock=1 before the package3 so i put them in the same order as yours just in case but no, same result. It sits on my desk, black screen and the backplate is warm to the touch.
  10. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    That is the issue : no way to boot neither HOS or AMS, bypassing the chip by holding vol + and Vol - give the same result : black screen. The only thing the console does is Hekate…
  11. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    I attached the pic of the battery menu in Hekate, You will see everything seems normal except for the capacity full and design which are at 1000 mah and the design showing an error.
  12. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    So I can only replace the battery ? Or is there a way to reset calibration data ? I saw a homebrew app and it needs a system to run on so… Not a solution…
  13. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Yes everything is up to date, I wanted to be sure so I remade my whole SD pack from scratch but nothing changed…
  14. D

    Hardware Unpatched V1 can only boot payloads after Picofly install

    Hi ! TLDR : Hekate works, any payloads works, HOS doesn’t work and AMS neither. I’ve searched internet and the few people who got the same issue didn’t post a solution… So I installed a Picofly on an unpatched V1 (the person wanted a modchip and I don’t have any RCM chip atm) So I update...
See more