Develop Bugs

every rom is (bad)!!!

every time i try to flash a rom i get this error: can't open /sdcard/signed_virusROM_R1_KINGSLICK.zip
(bad)
that was the error for that specific rom, but instead of virusrom it would have been bakedsnack or cm6. please i havent had a phone for 3 days i need some help here

25 views no answer? comeone people please help!

sounds like a memory card read issue to me.. Format the memory card and try again.

bullshark_the_real said:
sounds like a memory card read issue to me.. Format the memory card and try again.
Click to expand...
Click to collapse
i will try this, i believe i know how thanks.

i generally just have to restart recovery and it will work i have had the same error a few times and just have to try again once i reboot

kindakrazy said:
i generally just have to restart recovery and it will work i have had the same error a few times and just have to try again once i reboot
Click to expand...
Click to collapse
i cant even reboot. its stuck in a bootloop, will pull itself out, then go back into it after the setup freezes. ive flashed different kernals, different roms newest wimax and radio updates, ive done everything a noob can do after being here for a few weeks. and no one seems to be helping me and more and more threads are popping up with same issues as me

b_allert said:
i cant even reboot. its stuck in a bootloop, will pull itself out, then go back into it after the setup freezes. ive flashed different kernals, different roms newest wimax and radio updates, ive done everything a noob can do after being here for a few weeks. and no one seems to be helping me and more and more threads are popping up with same issues as me
Click to expand...
Click to collapse
What radio r u using
Sent from my PC36100 using XDA App

kris54241 said:
What radio r u using
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ive seemed to have fixed it. i wiped phone like 10 times. reformatted sd card, installed the rom called virus. it went to bootloop. so i let it do its thing. when i woke up today, it was perfect!

b_allert said:
ive seemed to have fixed it. i wiped phone like 10 times. reformatted sd card, installed the rom called virus. it went to bootloop. so i let it do its thing. when i woke up today, it was perfect!
Click to expand...
Click to collapse
thats not working perfect, thats called one f'd up phone.
sounds like a bad memory card and you can wipe and format all day long, the card is still bad.
are you using a different card than the one that came with the phone?
if so put the original back
if not, go get a different card.
if the original is bad take it to the sprnt store and see if they can replace it.

v_lestat said:
thats not working perfect, thats called one f'd up phone.
sounds like a bad memory card and you can wipe and format all day long, the card is still bad.
are you using a different card than the one that came with the phone?
if so put the original back
if not, go get a different card.
if the original is bad take it to the sprnt store and see if they can replace it.
Click to expand...
Click to collapse
haha thanks. its been 8+ hours i havent had a problem using,saving,loading,calling. idk man, still think i should go take it back??
o and yea im using original sd caRD. how do i explain the problem if to them without letting them know it has been rooted?

Just act clueless and be like "I just took it out of my pocket and it was acting weird" if all else fails plead the fifth

[Q] S3 device status detected as "modified" after JB update yesterday night.

[Q] S3 device status detected as "modified" after JB update yesterday night.
First let me say that my Galaxy SIII was not rooted before the update. It's been running full stock rom.
I've done the Jelly Bean update yesterday night through Kies while my phone was connected to my computer.
Update was perfect until I tried the software update app to check if there was anything left to install.
At this moment, I had a message telling me that my phone was modified and updates will not work (I don't remember the exact message).
If I go to Settings, About device, Status... Device Status is "modified".
Again, I don't have anything on my phone to root my device.
So what I tried next... removing my microsd card (64GB Sandisk microSDXC) and reboot my phone. Now, Device status is "Normal".
Put it back again... reboot... and Device status is again "modified".
Format the card... reboot... Device status is Normal.
Put everything back (55GB of music only synched through iSyncr wifi with my Mac)... reboot... Device Status "modified".
So it really looks like that the thing that Samsung uses to detect the "modified" state of the phone is broken in some way because it's detecting my media files (mp3 and m4a) as some sort of modification to the phone... this is completely wrong!!
Am I the only one with this problem?
I will try this week to reduce the amount of music file to see if there is anything that broke the detection system... I will report later if I find anything.
By the way, I found a similar thread with a similar problem... but this thread did not offer any solution and it looks like to be close as I cannot add anything to it.

That's very weird because I was rooted using the method in my sig and my device status showed modified as well. I was able to install the update just fine.

Tony_YYZ said:
That's very weird because I was rooted using the method in my sig and my device status showed modified as well. I was able to install the update just fine.
Click to expand...
Click to collapse
I was also able to install the update... the status was "normal" before the update...
the issue I have now is it says "modified" even if I did not modify anything in my phone.
I did the test again this morning... I removed all the music file on my card... device status is back to normal.
It must be one of my music file that triggers this detection... if it's in fact the case, it means that there is a bug in the detection that Samung have implemented.

zadigre said:
I was also able to install the update... the status was "normal" before the update...
the issue I have now is it says "modified" even if I did not modify anything in my phone.
I did the test again this morning... I removed all the music file on my card... device status is back to normal.
It must be one of my music file that triggers this detection... if it's in fact the case, it means that there is a bug in the detection that Samung have implemented.
Click to expand...
Click to collapse
Yeah, that is very odd. I'd organize all your files on our SD Card into folders and move them to your PC. Then copy one folder at a time over to the SD card and see which one triggers the phone to show a Modified status. Then you can narrow it down from there.

Tony_YYZ said:
Yeah, that is very odd. I'd organize all your files on our SD Card into folders and move them to your PC. Then copy one folder at a time over to the SD card and see which one triggers the phone to show a Modified status. Then you can narrow it down from there.
Click to expand...
Click to collapse
this is exactly what I'm going to do... I will also try to logcat command through adb ... I might be able to find something in the log.
I will let everyone know as soon as I find the cause of this problem.

Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available
Sent from my SGH-I747M using xda premium

thatsupnow said:
Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
This is so weird, after my OTA completed yesterday I tried to check for updates again and it just told me I was on the latest version. Now when I check it gives me the modified error.
Blargh. Ahh well, It's not like we're going to be seeing another update anytime soon, unless it's a patch.

Tony_YYZ said:
This is so weird, after my OTA completed yesterday I tried to check for updates again and it just told me I was on the latest version. Now when I check it gives me the modified error.
Blargh. Ahh well, It's not like we're going to be seeing another update anytime soon, unless it's a patch.
Click to expand...
Click to collapse
are you rooted after updating?
maybe you can do like what I've did (remove microsd card), reboot and see if you still have this "modified" status/message.

zadigre said:
are you rooted after updating?
maybe you can do like what I've did (remove microsd card), reboot and see if you still have this "modified" status/message.
Click to expand...
Click to collapse
I did restore root after updating. I'll have to temporarily remove root, restart and see what it says then. I'll try to do that later.

Tony_YYZ said:
I did restore root after updating. I'll have to temporarily remove root, restart and see what it says then. I'll try to do that later.
Click to expand...
Click to collapse
I suspect that they are checking not just the presence of "rooting" app in the system folder, but also other "rooting" files anywhere else on the phone... I'm sure they do this because just by removing my microsd card, even if the only files present were music and jpg file, the status went from modified to normal.
So a temp unroot might not necessarily fix this problem for you.

zadigre said:
I suspect that they are checking not just the presence of "rooting" app in the system folder, but also other "rooting" files anywhere else on the phone... I'm sure they do this because just by removing my microsd card, even if the only files present were music and jpg file, the status went from modified to normal.
So a temp unroot might not necessarily fix this problem for you.
Click to expand...
Click to collapse
Hmm, hopefully the answer surfaces from one of the devs soon.

I have ROOT but my Device Status is Normal
Sent from my SGH-I747M

yulet said:
I have ROOT but my Device Status is Normal
Sent from my SGH-I747M
Click to expand...
Click to collapse
which su binary are using (supersuser or supersu)?
I think that supersu has an option to hide the root availability... is this the one that you are using?

thatsupnow said:
Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Sam here, as far as I can tell it wasn't as a result of the SD card. It was fine when I had stock unrooted Rogers ALH1, but it changed to modified when I flashed the root injected Rogers ALH1 for the no counter trip thread, and it was in ODIN too.

zadigre said:
which su binary are using (supersuser or supersu)?
I think that supersu has an option to hide the root availability... is this the one that you are using?
Click to expand...
Click to collapse
I'm also rooted on the JB update and status shows normal. I'm using supersu but can't find an option to hide. With rooted ics it always showed modified.
I wasn't sure if it was connected to the flash counter in some way since I'm not at 0 anymore but apparently that's not the case.
Sent from my SGH-I747M using xda app-developers app

acloaf said:
I'm also rooted on the JB update and status shows normal. I'm using supersu but can't find an option to hide. With rooted ics it always showed modified.
I wasn't sure if it was connected to the flash counter in some way since I'm not at 0 anymore but apparently that's not the case.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
It's all based upon files in /system ALSO flash counter.
Modified, meh.
Just if you DO NOT root and updated to JB 4.1 and it now shows modified...that's weird.
Yet most of the time when you flash to a rooted version and it says modified thats cause of /system files and flash counter.

caha2639 said:
It's all based upon files in /system ALSO flash counter.
Modified, meh.
Just if you DO NOT root and updated to JB 4.1 and it now shows modified...that's weird.
Yet most of the time when you flash to a rooted version and it says modified thats cause of /system files and flash counter.
Click to expand...
Click to collapse
My phone has a stock rom and flash counter is 0.
This morning, I had all my music files on my microsd card... Status was modified. I removed all files, reboot... Status normal. Yes this is weird.

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I have the same weird problem too. I bought my phone 4-5 days ago from a famous shop. It was totally new and unused, never rooted, never flashed anything, no simlock, no root required app installed AND no sdcard. These days it is mostly Modified, rarely it turns to Normal after restarting the device...

I don't know what was really going on... I removed one song, got the "Normal" status. I removed some other files, got "modified". ReAdd the first file that was removed, got the "Normal" status again.
What I've decided to do is put my memory card in my MacBook Pro. I got an error that the card wasn't readable. My MacBook is supposed to support SDXC standard with and extFAT formated card... so it looks like that my card had a problem. I decided to reformat the card with FAT32 even if SDXC card are supposed to be extFAT. I put the card back into my phone. I synched all music files.... and I got the "normal" status again. I modified my playing list in iTunes... I synched again... status stil shown as "normal".
So I don't know what was the problem exactly... I suppose that the file system on the card was damaged in some way... but I really do not know what caused this problem at first.
Anyway it works fine now... so this is the most important thing.

For all those fighting with 'Device Status: Modified'

If you have 'Device Status: Modified' and don't know how to fix it, you may be interested in my story.
I bought GN2 in November. Rooted, flashed custom firmwares etc. Beyond being just great phone it seemed to have one big problem: it did lock up cold every once in a while regardless of firmware.
I created some other thread on that and based on responses and some of my own research I started getting to conclusion that my device has a hardware problem.
So I figured that I need to do warranty exchange. So I unrooted, triangle away and flashed completely fresh original tar.md5 package via odin with all blows and whistles. Did factory reset, of course.
I still see 'Device Status: Modified' after some time. Usually after reboot. Bummer!
So I did some research and someone here on xda mentions that using jig from old days helped with it. I had a jig, so I tried it. Rest assured - device status became 'Normal'. Awesome! I am happy and I didn't have to wipe data.
Some time passes. The darn thing is 'Modified' again!. I use jig again - story repeats. So I figured that I use jig to reset status right before I go to AT&T. So I did.
I came to AT&T center and they say 'Hmm - it must be software locking up your device. Lets just flash and clean it all'. Fine - lets do it. So I walk out of the store with wiped clean device having UCALK7 version of firmware.
Obviously, it didn't solve the problem. Device still locking up and it's still modified'.
Now we get to the interesting part.
I use 64Gb Sandisk microsd card. It has may be 40Gb of music and other stuff. I always had .nomedia file in a music folder so album art would not appear in gallery.
I decided to remove .nomedia for some other reasons and so I did.
The phone didn't find my music for couple of days but eventually music did get scanned. And at this point (I think at this point), my jig stopped working and device just remained in 'modified' status. That was bad - I needed to replace device.
So I did more research and some people mentioned some correlation between external sd card and 'modified' status. Something, in effect, that formatting external sd card fixed it for them. I simply took out sd card and rebooted. AND.... status become 'normal'.
Now we get to part III.
I am happy that my status is 'normal', I am not putting sd card back and I use it for a day and than go AT&T. Right before that, while watching YouTube during lunch, my device locks up. I am block away from AT&T center so I just walk to them and show locked up phone.
They say ok and give me a new phone. Awesome! I plugin my sd card and walk out.
I didn't even sign in to Google yet, just walking away from store and I look at my brand new phone and, guess what? 'Device Status: Modified'
So I took out sd card: 'Device Status: Normal'. Card in - modified.
Tonight I will explore my sd card on PC to see what possibly can be on it to cause it. And may be reformat it.
So the moral: external SD seems to cause somehow this device modified status.
And may be this story will help someone.

It definitely appears that Samsung is searching external sd card for artifacts related to rooting. Once I deleted all twrp an titanium backup as well as all flashable stuff like roms etc the status changed to normal. After a while it became modified again so I formatted card and copied back my media.
Now it stays.
So big brother is watching - you can't own any illegal artifacts...
Sent from my SAMSUNG-SGH-I317 using xda premium

Ok. I give up. After a day it became 'modified' again. New phone without any change + formatted sd card.
So just remove the darn card from the phone and reboot before taking it to AT&T or Samsung for warranty. That's provided that this 'modified' status even matters.

Maybe it's the size of the card? Isn't 32 gig the largest officially supported?
Just a thought...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Its not the size of the card...I had a 4gig in mine and had that modified status also...time will tell.
Sent from my SAMSUNG-SGH-I317 using xda premium

LOL
I am NEVER going to understand wtf posses people to play mcgeyver when doing warranty exchage.
:banghead:
First off NOTHING is easier than using sammys firmware tool and it garauntees
A complete stock phone.
If you can get into dl mode youre golden.
Its a one step process and fail/noob proof.
You will need kies, and the most recent usb drivers.
I cannot believe you jigged your n2
All that time wasted unrooting, fladhing "stock rom" checking md5 sum
Waste of time!!
Go to samsung.com and dl kies.
Flash em firmware recovery:done
Like new no modified flag.
I cant tell you how many times I have done this. Bootlooped, bricked, corrupted recovery... if you can get into dl mode and have 20 min to spare...shell be just like new. GL ! :thumbup:

freakboy13 said:
LOL
Go to samsung.com and dl kies.
Flash em firmware recovery:done
Like new no modified flag.
I cant tell you how many times I have done this. Bootlooped, bricked, corrupted recovery... if you can get into dl mode and have 20 min to spare...shell be just like new. GL ! :thumbup:
Click to expand...
Click to collapse
I kind of agree that the easiest is to just flash kies firmware. But the point of this thread is to highlight that SD card may cause it even to brand new unmodified phone.

The real question is...havebyou tried it yet?
I have had the same 32gb samsung sd card in my gs3 and just swaped right into
My n2. And according to your title the thread is about the "modified" flag on your phone.
The em firmware tool garauntees that not to be there. I wasnt trying to hijack your thread or anything. There are tons of fake sd cards that say samsung or kingston.
Do you have any tools to verify the sd cards integrity/ true storage?
Honestly give the em tool a try.
Then (this may be your prob)
Reformat your sd with your phone.
I know pia but it fixes a lot of probs.
When I first got my 32gb I was having issues. Missing/ corrupt files, etc.
Reformated the card with the phone...bingo! Never had an issue since.
Hope it works out for ya!
:beer:

freakboy13 said:
LOL
I am NEVER going to understand wtf posses people to play mcgeyver when doing warranty exchage.
:banghead:
First off NOTHING is easier than using sammys firmware tool and it garauntees
A complete stock phone.
If you can get into dl mode youre golden.
Its a one step process and fail/noob proof.
You will need kies, and the most recent usb drivers.
I cannot believe you jigged your n2
All that time wasted unrooting, fladhing "stock rom" checking md5 sum
Waste of time!!
Go to samsung.com and dl kies.
Flash em firmware recovery:done
Like new no modified flag.
I cant tell you how many times I have done this. Bootlooped, bricked, corrupted recovery... if you can get into dl mode and have 20 min to spare...shell be just like new. GL ! :thumbup:
Click to expand...
Click to collapse
I agree completely!!! Why go through all that when you're just trying to go back to stock for a repair? (plus it's a good "last ditch" troubleshooting tool when a ROM is just giving you too much trouble and re-flashing doesn't seem to help.

ReggieSmith said:
I agree completely!!! Why go through all that when you're just trying to go back to stock for a repair? (plus it's a good "last ditch" troubleshooting tool when a ROM is just giving you too much trouble and re-flashing doesn't seem to help.
Click to expand...
Click to collapse
I'm attempting to restore my phone to complete stock and am having issues getting by binary counter from 1 to 0. Status is Normal and firmware is official Samsung, but the counter remains at 1 after using triangle away. I have done a factory reset as well.
I didn't know you could use Keis to restore to stock and I've look around the software, but can't see how to do it. I see the Emergency Firmware Recovery, but it looks like you can only use that if your phone is in emergency mode.Any help?
---------- Post added at 08:54 PM ---------- Previous post was at 08:25 PM ----------
KinAndTonic said:
I'm attempting to restore my phone to complete stock and am having issues getting by binary counter from 1 to 0. Status is Normal and firmware is official Samsung, but the counter remains at 1 after using triangle away. I have done a factory reset as well.
I didn't know you could use Keis to restore to stock and I've look around the software, but can't see how to do it. I see the Emergency Firmware Recovery, but it looks like you can only use that if your phone is in emergency mode.Any help?
Click to expand...
Click to collapse
Nevermind, I figured it out using Firmware Upgrade and Initialize. Although, it didn't clear the Binary Count. Still shows "yes (1 counts)" when I enter download mode. ugh
---------- Post added at 09:43 PM ---------- Previous post was at 08:54 PM ----------
I did it! lol
Used this (http://rootgalaxys3iii.com/how-to-reset-rooted-galaxy-note-2-flash-counter/) to finally get Triangle Away to work on my phone and then did factory reset. Completely stock now.

Hey grats on that. Judt an fyi you can use the EM tool anytime...doesnt have to be an emergency.
Hmmm im gonna have to try the em tool again and check my count.
It set back to 0 eveytime on my gs3.
Glad it worked out for ya.
:thumbup:

How do you use the EM Recovery via Kies? I click on it and all get is no phone listed in the Emergency Phone section and ask for recovery Code from the other PC or something..Not sure..

Device shows custom after OTA

I had something very odd happen. I got my replacement note and when I took it out of the box and fired it up there was an OTA waiting for me. I installed it right away. Afterwards I went to check to see if there were more updates.. It then told me my device was modified and couldn't update. The status shows "custom" I was able to update via kies and got the latest OTA but it still shows custom. I haven't rooted or modified the device in anyway. In Odin mode it shows warranty flag as 0.
Had this happened to anyone else? No matter what I do it keeps saying custom. In Odin I flashed a full official firmwares.. Still says custom.. It's driving me nuts..
USA wifi model SM-P600
Sent from my Nexus 5 using Tapatalk

Don't know if it will help, did you tried removing the extsdcard and reboot?

was it factory sealed? sounds like you got someone else's returned note. has the Knox flag been tripped?

It was factory sealed. The seal was intact. The odd thing is that it got the first ota but after that it showed modified. I haven't tried removing the ext sd card. Would that really matter?
Sent from my Nexus 5 using Tapatalk

can you boot into dlownload mode and see if knox has been flagged? if it is then this as gotta be some freaky stuff going on and pretty crappy if younare denied a warranty repair bc of a faulty ota.

madsquabbles said:
can you boot into dlownload mode and see if knox has been flagged? if it is then this as gotta be some freaky stuff going on and pretty crappy if younare denied a warranty repair bc of a faulty ota.
Click to expand...
Click to collapse
OP, who's a dev, said in his post KNOX is at "0."
bruce16878 said:
Don't know if it will help, did you tried removing the extsdcard and reboot?
Click to expand...
Click to collapse
I've seen this before on XDA but can't remember where. Here's an offline post referencing it. The issue's never been explained but rebooting the device without the SD card in it corrects the problem.
https://community.optus.com.au/t5/M...eventing-Galaxy-s4-Software-update/td-p/57034

Thanks Barry I will try without the bad card in.. Haven't seen you in a while.. Hope all is well
And yes.. Removing the SD card made it say official again.. Thanks man. Odd that an SD card would make it show modified. I'm going to read that link you posted now.
Sent from my Nexus 5 using Tapatalk

Well, have a nice day.
Sent from my GT-N7105 using xda app-developers app

[Q] Bricked with out custon rom??

So I think my phone is hard bricked. I was on G+ ealier today, clicked on a link that opened Chrome. got through a third of the web page and my phone freezes then the screen goes black... I have tried every troubleshoot trick provided by tmobile and samsung and the phone wont respond in any way. Just a black screen. Is it possible to brick your phone with out trying to flash a custom ROM??? The only thing new I have done in the past week was install "graph ti89" and "aviate." I dont know if this has anything to do with it but tmobile has being try to get me to install the kitkat OTA for the last week and I keep ignoring it.

just update
jcampana28 said:
So I think my phone is hard bricked. I was on G+ ealier today, clicked on a link that opened Chrome. got through a third of the web page and my phone freezes then the screen goes black... I have tried every troubleshoot trick provided by tmobile and samsung and the phone wont respond in any way. Just a black screen. Is it possible to brick your phone with out trying to flash a custom ROM??? The only thing new I have done in the past week was install "graph ti89" and "aviate." I dont know if this has anything to do with it but tmobile has being try to get me to install the kitkat OTA for the last week and I keep ignoring it.
Click to expand...
Click to collapse
Hi,
Do the update or factory reset your phone. You can always use KIES also.
Ms. K

Ms. K said:
Hi,
Do the update or factory reset your phone. You can always use KIES also.
Ms. K
Click to expand...
Click to collapse
Thanks for your input but the phone won't turn on at all. Can'T turn it on to update. Won't go into safe mode by pressing vol. up&home&power. When I plug it into the computer it says it needs drivers for "QHSUSB_BULK." Kies doesn't see it as a connected device...

If you haven't done anything to the phone why not call Tmobile and get a replacement..
Sent from my bad ass Kryon infused Note 3

deeznutz1977 said:
If you haven't done anything to the phone why not call Tmobile and get a replacement..
Sent from my bad ass Kryon infused Note 3
Click to expand...
Click to collapse
because i'd like to recover the data that is on the phone.

jcampana28 said:
because i'd like to recover the data that is on the phone.
Click to expand...
Click to collapse
A few threads down you would have found this... http://forum.xda-developers.com/showthread.php?p=47555043
My recovery image is here: http://www.mediafire.com/view/?6nu61z43y51v3k4
You need a 32 GB sd card and some luck. Also reading is a requirement.
Yours may be a special case though, as you claim nothing was going on besides you clicked a link. Should have absolutely nothing to do with ota, and everyone else who had done this was messing with their phone. This definitely works for 4.3, but no one had reported working on 4.4 (you were on 4.3 anyways). Good luck.
Sent from my SM-G900T using Tapatalk

noobtoob said:
A few threads down you would have found this... http://forum.xda-developers.com/showthread.php?p=47555043
My recovery image is here: http://www.mediafire.com/view/?6nu61z43y51v3k4
You need a 32 GB sd card and some luck. Also reading is a requirement.
Yours may be a special case though, as you claim nothing was going on besides you clicked a link. Should have absolutely nothing to do with ota, and everyone else who had done this was messing with their phone. This definitely works for 4.3, but no one had reported working on 4.4 (you were on 4.3 anyways). Good luck.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Mr Noobtoob, has anyone reported un-bricking a N900t running 4.4.2 (1st release, believe it ends in N94 or similar, NOT NE6)?
If so, did they do anything different?
Be well.

golfcartguy said:
Mr Noobtoob, has anyone reported un-bricking a N900t running 4.4.2 (1st release, believe it ends in N94 or similar, NOT NE6)?
If so, did they do anything different?
Be well.
Click to expand...
Click to collapse
I have not seen a successful report back of the nb4 firmware. Doesn't mean it doesn't work, just don't have confirmation.
Fusionized tweaking tapatalker here...

Thanks for the quick response!
Going to try, and will report back.
To clarify, it must be a Class 10 microsd card, and must be the same size (32gb), 1st formatted to exfat, correct?
Sent using XDA Free mobile app

golfcartguy said:
To clarify, it must be a Class 10 microsd card, and must be the same size (32gb), 1st formatted to exfat, correct?
Click to expand...
Click to collapse
Those are the magic ingredients!
Frank

Frank Westlake said:
Those are the magic ingredients!
Frank
Click to expand...
Click to collapse
Got it! So, to be clear;
1st - Format class 10 card to Exfat file system or structure
2nd - Using Win32Diskmapper, just point to the file (in my case kk900tunbrick image) and write to card. *Nothing special, should I verify Md5 sum, or just leave it as default settings?
3rd, Proceed to attempt to Unbrick (Battery at 100%, Put Sd card in slot, Then Add Battery, Connect cable - some say, some say doesn't matter, to computer, then attempt to boot with button sequence to download mode, or may boot by itself?)
Also, if the 1st image I downloaded does not work, can I reformat or wipe the sd card and start again with the other file (I believe a Pit file??)