Database Info

Stuck on Booloader Screen *Solution*

After 2 days of messing with this and learning more about flashing ROMS than I ever wanted to it finally worked!!!
If you messed up by not SuperCID(ing) your phone before you flashed it because you didn't follow directions like me, here is a solution that i had to dig up from various forums and threads to get your phone back to WM5.
1. Downloaded the imate wm5 from here:
ftp://ftp.xda-developers.com/smartphones/Tornado/Shipped_Complete_Updates/I-mate
2. Downloaded the Typhoonnbftool...just google it. I used version .4.
3. Find out what your original CID id is by using the Ttermpro. (make sure the Allow USB Connections is unchecked in Activesync...i spent an hour trying to get ttermpro to work)
refer to this thread for more info: http://forum.xda-developers.com/showthread.php?t=319588
4. Now run the typhoonnbf tool. File > Open the .nbf file you downloaded in step 1. (imate wm5)
Tools > Edit Data Header
Change the Operator to match what your SuperCID id is (Step 3) and type in 99.99.99.99 (i'm sure any high number will work here) in the "Image Version" field as well as the "Secondary Version" in the header of the .nbf. (i'm not sure if the Secondary version is necessary, but i did it anyway to be safe)
Sample of what it should look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Save the file under a different name in the same directory. Move the orignal .nbf file to a safe location. Rename the edited version to nk.nbf
6. Run the ROM update utility and it should work
Good Luck and don't give up hope.

Hi All... I didnt notice and i tried to run ((Artemis_Touch_Vanilla_4.02.zip)) this ROM on HTC touch and its got stuck on HTC logo screen and says OS 3.13.0.0 .... Please help me... i have tried to restart and tried what ever possible but nothing is working it comes back to same screen...Please help ...please
the thing is it does not go the three color screen...it straight comes to the HTC logo screen and then in about 3 or 4 seconds comes OS 3.13.0.0 and then thats it its on the screen for ever....I cant click on anything its does not even restart with the power button on top...i can reset or take out the battery to shut down.....what do i do now...please help me

512k nbf
Hi
After I edit the nk.nbf file the resulting file is only 512k so the rom updater won't load it.
What do I do?

try using another version of typhoonnbftools

1. Downloaded the imate wm5 from here:
ftp://ftp.xda-developers.com/smartph...Updates/I-mate
The link doesn't seem to work for me. It poped up "error 503: permission denied".
Does anyone have the same problem. Where else can I get an imate wm5? Thanks a lot

SupremeM said:
1. Downloaded the imate wm5 from here:
ftp://ftp.xda-developers.com/smartph...Updates/I-mate
The link doesn't seem to work for me. It poped up "error 503: permission denied".
Does anyone have the same problem. Where else can I get an imate wm5? Thanks a lot
Click to expand...
Click to collapse
Use ftp://[email protected]
you should be asked for login details, use xda as user + password
then navigate the folders starting with the smartphone then Tornado links, you should be able to find it from there.

New problem
I got another version of Typhoonnbftools and successfully edited the header of the file. Flash seemed to go fine right up until reboot. It restarted and displayed o2 splash screen (which should have been overwritten by the imate rom) and continues to bootloader.
Any more suggestions anyone?

wat i still dnt understand is that wen i run tera term pro i dnt no where to type the info 2
my problem now is how to know my tornado cid pffff

Bricked?

Hi,
I did something, i do not know what but my P6800 bricked /data folder cannot be formatted. ICS was installed. Stuck Samsung screen.
I found some solutions in forums but not worked for me, then i replaced .pit file by Odin and replaced original Honeycomb by Odin.
Then when i restart (without any wipe) i get this screen
Can anyone help me what is the password?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wouldent that be your lockscreen password? Others have had this happen when thay installed a ROM with out removeing
The lockscreen password before installing . Just do a search in the forums here I am sure I read that thay came up
With a solution .

Same **** here
Hey dude, I have the same problem.
Did you solve it in the meantime ?
Thanks in advance

Lipi32 said:
Hey dude, I have the same problem.
Did you solve it in the meantime ?
Thanks in advance
Click to expand...
Click to collapse
This is gonna sound real dumb I know but......has anyone tried entering no password? In other words, just hit Enter? Or maybe using the word "password" as the password?

xseaplus said:
Hi,
I did something, i do not know what but my P6800 bricked /data folder cannot be formatted. ICS was installed. Stuck Samsung screen.
I found some solutions in forums but not worked for me, then i replaced .pit file by Odin and replaced original Honeycomb by Odin.
Then when i restart (without any wipe) i get this screen
Can anyone help me what is the password?
Click to expand...
Click to collapse
No problem...!
This kind of things happen..I am not that expert but can advise on the basis of what i gained from xda website.
If you can go in recovery and download means not much serious thing.
FIRST TRY TO RESTORE YOUR SYSTEM FROM RECOVERY BY USING YOUR OLD BACKED UP .
if not then follow steps below:
1. I would recommend you to download fresh odin3V1.85
2. Download steady honeycomb version of your region from
3. From recovery clear delvic cache/factory reset/ and all stuff.
4. Enter download mode and do all the flashing once again. Make sure your power to usb post is ok. I have observed old laptops or pcs just disconnect for a second or so and again reconnect. If this happens while flashing then you come to this stage.
Hope it will solve your problem.
If not other experts are still out there on XDA developers website.......
Don;t panic.
Enjoy with XDA developer's website.
Ashwin

Hi niceashwin79,
thank you very much for your short tutorial.
!NICE! Ashwin
But I already sent it to Samsungsupport. ( BTW. Couldnt wipe anyway, it always stucked, also tried to flash serial roms)
It was returned yesterday, with 3.2 Open Austria and AUT (Swizz) CSC.
So I flashed 4.0.4 Open Austria and became XEO CSC.
But the return to ATO (Austria, the right CSC) was with CSC Selecter for SG1 SG2 and Note from the Market quite easy.
The third party Samsung support company exchanged the motherboard.
However my UMTS/3G-module is not working anymore. I didnt test it with the 3.2, but I guess, it didnt work, too.
The Tab does not recognize the SIM, no message, nothing.
Besides that I have a full nandroidbackup of 4.0.4 with AUT CSC BEFORE the brick.
(Loading this backup after changing CSC from AUT to ATO probably bricked my Tab.
I would be very pleased and thankfull if anywone is able to help me,
thanks in advance
EDIT: I have a small update for you.
If you go to the tab "security" you can deactivate/change the SIM's password. Both actions register my device in the network. Every reboot is the same, so the problem is not fixed yet but kind of sloved.
Still looking for a perfect solution,
greetings Lipi

[Q] Encryption Unsuccessful & Bootloop - GT-P3100 Tab2 7"

Hey guys! i have an issue here. can anyone help me solve this problem.
before i started getting this error i had, they were working well
- AOKP 4.4.4 custom rom
- Philz touch 6.0 Recovery.
from few days i started getting this error, see image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash stock firmware, i downloaded two firmware of INU region (India)
everytime i get the following error on odin,
(Above pic for reference only. im using odin v3.09 and latest)
I tried flashing with PIT files, it didnt work.
I tried flashing TWRP, CWM it flashes recovery but when i go to recovery then still philz is there.
I searched on many forums and Googled, and i came to know that my /data and /sdcard is corrupted. but i can access the content /sdcard from recovery and i can view my files.
I tried flashing other custom rom. It flashes them without any error but when i reboot my Tab its not flashed. its same.
What to do please help me.

Ok so after doing so mush research on this on xda, gsm-hosting, google, etc....
i came to a conclusion that the emmc is corrupted or right protected (Means It has become read only). which is why we are unable to flash through odin or through recovery. even if the flash is successful then after reboot the TAB returns to the earlier state i.e same rom, bootloop and recovery.
so there are three way you can fix it:
1. change motherboard, which is very costly. on ebay it was 13k (India). dont know about local shops or service center. but im sure it will be more or less same.
2. Change emmc. ask the repair guy to change the buggy emmc to a new one. buy the emmc from alibaba online store or other online stores if you cant find it offline.
3. You can get back the same tab to work by directly flashing the stock rom directly to emmc. This process involves soldering the pins of the tab and flashing directly on to the chip using a box called ATF (Advance turbo flasher). This process is little advance, one can do it if you know what pins to solder (You can get the idea from youtube & gsm hosting), but buying atf box would be costly. costlier than the emmc replacement. now if you want to experiment and learn you can go buy a atf and revive your dead tab (it will be called The walking dead. ).
:)
so i am replying to my own thread so that if any body is comes searching for the same gets to know what happened and what to do next.
BTW Android_Andi has done some great research on this he tried every possible thing but unfortunately it didnt work. Thanks to him for his time and effort.
and if anybody figures out how to fix it without using atf box please do post and let me know. because im keeping my dead tab with me and if someone knows any alternate way i can fix mine too. who knows anything can happen.

[FIXED] !!! S7 SM-G930F Bricked and i'm currently f***ed up with 3 screens only

Hi folks,
I was recently rooting my Samsung Galaxy S7, Model: SM-G930F, and here is the deal:
Root ok, everything fine. After that I dumbly disbled OEM and USB Debugging.
Then I tried to install "Patcher app" ( I'm ****ing hating myself right now ) and the phone froze and restarted with this annoying message: blocked by frp lock
Restarting it and putting it to charge resulted in blocking message... trying VOLUME + POWER + UP after restarting also.
THEN: I saw somewhere that I could try and restore the firmware to deal with it.
Thing is, I think I might have downloaded wrong PDA version ( I don't f***ing know how to find it without entering the phone but the tip is: It was bought in Brazil. If someone have ANY idea... ) + used CSC file instead of HOME_CSC and it ended up screwing more.
The current situation is:
The DOWNLOAD PAGE ( Odin Mode ) shows of but it doesn't load any more firmware files from ODIN and it shows that when not on Odin mode: " ! - An error has occurred while updating (...)" .
Here's what I've already tried since I'm in this situation:
1. Trying to use Smart Switch to restore
- After filling the MODEL - s/n it says that SM-G930 doesn't support initialization.
2. Trying to use KieS... same thing.
3. Trying to use on ODIN
AP: twrp-3.1.1-0-herolte.img.tar
FAILED
Also the folowing:
G930FXXU1DQD7_G930FZTO1DQD7_ZTO
G930FXXU1DQE5_G930FZTO1DQD7_ZTO
G930FXXU1APB4_G930FUUB1APB4_ARO ( random dl )
{ The first and second I know is for Nougat 7.0 as I updated the software myself before this novel }
everyone failed at writing...
I don't know what else to do. I'm literally stuck
Here are the pics of the current possible screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit:
Although it's recognized by ODIN, when I press start nothing happens on the S7 and ODIN stays like this:
Until it fails at writing:
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
And trough Smart Switch:
EDIT (FINAL):
I'm relief and frustrated... I was not able to flash FW because the cable I was using was not the original.
After losing my hole weekend, it at least is Fixed / \
Installing FW went fine, then it rebooted and come back to life.
I found out about it by trying to send just the CSC file in when it returned a weird error message at Odin.
Also I uninstalled Kies, best thing, it didn't help until the end (basically, KIES process keep active backgrounded giving you incompatibility of driver or something like that, messing around Odin when you try to upload anything. Either you kill it or do what I did). BUT serious guys, cable incompatibility is the fist time I experienced myself.... Never though this day would come.
Hope to help anyone with same prob.
See ya!

Nokia 3 stuck in Recovery after a 7.1.1

Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug with the production line of Nokia? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatter file based flashing ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since that's meant to help.
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Note: I cannot access the recovery page with the Android mascots chest open, only the screen posted in the reply below.
EDIT: Downloaded OST (Nokia's desktop flash editor), not much help as I can't seem to find the type of file its asking for. Seems like it could be a problem with a com port on the phone side seeing as I've mucked about with other cables/sockets.
Any help is so so appreciated right now :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Faraheim said:
Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatters ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since thats meant to help but I'm still super lost
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Haven't had a proper phone now for half a week and I'm a little anxious and I just want someone to help me out. Can't wait to finally get into Android!
Any help is so so appreciated right now :victory:
Click to expand...
Click to collapse
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320

redweaver said:
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Click to expand...
Click to collapse
https://imgur.com/sIsqZoo
This is the only thing accessible. Good suggestion though. Seems we have a mystery on our hands.