yashsingh1/xdaforums huggingface dataset:
[MDA, XDA, 1010 Software Upgrading] abbas:
there is a subfolder named english. The NK lives there.
[MDA, XDA, 1010 Software Upgrading] les:
i found the nbf file i had to extract onto itself

i'm using the bootloader to do flash the new rom to my phone

i'm at the step where the device is suppose to recognize a new rom on my sd card

i copied the nbf file using xdarit

i plugged the card back into the pda

now i start the wallaby bootloader im running v5.15 it supposedly should recognize the new rom well the instructions say to copy the .nb1 file on the card but with the extraction method i could only get a .nbf is that why it's not being recognized

thanks
[MDA, XDA, 1010 Software Upgrading] les:
thanks guys my phone is free .... free as in unlocked

these are the steps i took

someone can do in 30 mn what i did in 1 day

-backed up my rom onto a sd card with wallaby bootloader v5.15

-using the xdarit i downloaded my old rom on my PC

-cooked a new rom with xdaunlock at yorch.net

-couldn't create a .nb1 or .nbf file so i took the .exe rom

-with winzip extracted the newly dowloaded rom onto itself to get the nk.nbf file to be flashed (when i extracted it on a new folder there was no nk file listed, so i went back to the kitchen cooked another rom saved the exe "et voila")

-i couldn't get the newly upgraded rom to be recognized when using the bootloader

-downloaded the xdatools to copy the nk file on sd card (i was unable to pick my sd card reader as a destination -weird stuff) so i did this

-from the english folder Abbas is talking about above i right click the nk file to copy it to SD card and xdatools was launched automatically

-plugged the sd card in the phone and started the bootloader v5.15 and instantly the rom on the sd card was recognized

-press action to download it

-cold reboot ( the battery on/off, erase all)
[MDA, XDA, 1010 Software Upgrading] sena:
Re: thanks guys my phone is free .... free as in unlocked

hi less

i have siemens sx56 too (it arrived just today)

model	: PW10B1

platform : Pocket PC

IMEI	: 350314010468370

ROM v.	: A.30.09 ENG

Radio v. : A.33.02

Protocol v. : 1.3.3

i want to unlock at&t wireless in order to use another provider.

im new here.

can u explain more about how to unlock the sx56. i'm still confused with your explanation. detail?? (like how to backed up your rom onto a sd card with wallaby bootloader v5.15 ... etc)

make astep by step... :) please
[MDA, XDA, 1010 Software Upgrading] les:
here you are

http://xdaforums.com/viewtopic.php?t=3274&highlight=bootloader
[MDA, XDA, 1010 Software Upgrading] sena:
unlock simens sx56

thanks for reply les

i still afraid to try it. is that realy save?

sorry for my bad english :)
[MDA, XDA, 1010 Software Upgrading] cgigate:
All tools in XDA-developers.com cannot unlock SX56 radio A.33.02 or T-mobile 6.25.02

I developed a new tool to unlock them.
[MDA, XDA, 1010 Software Upgrading] abbas:
Maybe they should downgrade their radio, then unlock and then upgrade the radio and rom again. I think that is the new tool cgigate developed!
[RAZR HD General] lesdense:
Ever since getting my Razr Maxx HD (XT926) three months ago I've been trying to get rid of the Navigation Bar on the bottom of the screen. I use Button Savior so I'm fine with having the NavBar controls disappear.

Among the most reliable remedies seemed to be upgrading to 4.1.2, at which point many people said that you could simply add the line "qemu.hw.mainkeys=1" to the end of your build.prop file in /system, reboot, and *poof* the NavBar would be gone. My phone, which I bought used, was running a leaked 4.1.1 so, once root for OTA 4.1.2 was discovered, I downgraded to 4.0.4, did the updates to that, then took the OTA upgrade to 4.1.1 (no problem), then took the OTA upgrade to 4.1.2 (no problem). So now I had the latest JB version offered for Verizon XT926 in the US. I know that I'd wiped data at least once along the way. The SafeStrap installation that I used to have was gone, as I expected. I assumed that my phone was as stock as it could be and thus ready for the build.prop edit.

I used the new procedure to root my XT926. At that point all I did was to download and install Root Explorer (needed to do the build.prop edit) and Button Savior (needed for navigation once NavBar was gone). In Root Explorer I navigated to /system, made it R/W, opened build.prop in the stock text editor, added qemu.hw.mainkeys=1 at the end, saved (which backed up the older version as expected), and rebooted.

The first thing I get when my phone boots up is the "SystemUI has crashed" error message. My NavBar is gone but so is my System Bar (a/k/a Notification Bar), which I need and want to be visible. I've read a TON about this and I'm pretty sure I've followed the instructions. Why is this not working for me?

I am just not smart enough to decompile and edit my framework-res.apk file (or whatever the name is) so I'm stuck trying to make the build.prop edit work. What could I be doing wrong?

(also, if I use one of the apps like FullScreen or BottomBar they produce the EXACT SAME result -- SystemUI crashes, NavBar disappears but so does System Bar).
[RAZR HD General] realpg:
cant help

it works for me as experted
[RAZR HD General] deeje00:
Are you positive you entered it correctly?

Sent from my JokerMATRIX HD MAXX
[RAZR HD General] saloums7:
He also tried an app which writes the line to the build.prop and got same results.

AFAIK I had crashes on ICS but since I'm on JB 4.1.2 I never had any issues...
[RAZR HD General] lesdense:
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
[RAZR HD General] coolloser:
I have had the exact same issue and done the same troubleshooting...sucks!
[RAZR HD General] kilroy1stcav:
did you happen to check file properties after you saved, i remember back in the early days of Android if you edited a file, you had to change the properties back to the defaults, not sure if that is still the case, but worth a look.
[RAZR HD General] progrockguy:
It can't be done on any stock via build.prop only, and framework edits require a deodexed rom.

I recommend you install CM10 or 10.1. If you prefer safestrap over CWM, then you can use CM10, but without a camera. Fullscreen toggle works perfectly, and I'm able to use PDroid : )
[RAZR HD General] lesdense:
I suppose I should be glad that at least *one* other person is having this problem. Means it's slightly less likely that I'm just incompetent.

As for changing file properties, I didn't change any properties to do the edit other than making /system "RW" in order to be able to edit the file. Could someone tell me what the default values are for build.prop? The most recent edit I've made always shows up correctly when I go back into build.prop, by the way, so I know I'm actually changing the file.

If a rooted stock 4.1.2 can't hide the NavBar with a build.prop edit then this is the first I've read about it, and I've read just about everything that I can find on this subject (including translations of non-English discussions, just in case I could get a new lead from them). Not saying that's not true, just not consistent with what I've read so far.

I'd love to install a CM ROM on my XT926. I've admired Cyanogenmod since I first started fiddling with my Nook Color some years ago. Their crew does some spectacular work. But -- no camera? No Bluetooth? Sometimes wifi or phone call problems? That's too much lost functionality for me. If those remaining few obstacles are someday overcome I'll be all over it though.

ONE LAST QUESTION -- I assumed that, if I "scrubbed" my phone down to the lowest level possible (wipe cache, wipe dalvic, wipe data) I would eliminate whatever weird impediment I have to getting the build.prop edit to work. Is there something else I can do to wipe the phone even MORE thoroughly?
[RAZR HD General] coolloser:
The permissions are RW-R-R, I have had the issue with stock and custom roms (running Foot Through the Floor right now). I wasn't surprised when it didn't work with stock (silly Moto) and I was a little surprised when it didn't work with and of the custom roms I tried, I have no doubt it would work in CM. :)
[RAZR HD General] kilroy1stcav:
I tried it out, it works but you need to reboot after edit, I hot booted and nothing changed, full reboot and it works. hope it helps you.
[RAZR HD General] lesdense:
Just in case this makes the difference, can you tell me what distinguishes a "hot boot" from a "full reboot"?
[RAZR HD General] surfmly:
Having issues myself. Have 4.1.2 rooted, RAZR HD. Added the line above to build . prop with "=0" first shutdown, started back up. Then changed to "=1" saved, shutdown and started back up. System UI FC's.

Wonder if it matters what launcher is being used. I am on GO Launcher. I say this since on home screen I see the GO Launcher menu show up just below bottom of my wallpaper but behind it. I can swipe up to bring up full menu but it is weird how it comes up in background on its own.

Anyone get it to work with GO Launcher?

---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------

Oh and does it matter where in build.prop the line goes? I just added to bottom. Thx.

---------- Post added at 11:29 AM ---------- Previous post was at 10:56 AM ----------

I just noticed this (missed it first scan through) that you use Go Launcher as well. I do also and am having same issue. I am going to try switching to Apex, Nova or other to see if that is the culprit. If so, I can most likely get used to another custom launcher to gain the extra space.

BUT if anyone doesn't have issues AND is using Go Launcher, please let us know so we can rule that out.

Thanks
[RAZR HD General] coolloser:
I use nova pro and have the issues.

Sent from a non-apple device.
[RAZR HD General] surfmly:
I just tried Apex Launcher and had same FC issue. So guess it isn't specific to any of the launchers (was a long shot anyway). This is just really weird. Some folks swear they have it running on stock 4.1.2 (OTA update) rooted, but many of us have the same and can't get it to work.

I saw one thread where someone mentioned you needed to make sure everything is stock, meaning using TB to unfreeze anything you had frozen, and then give it a go. Problem is I'll want to refreeze much of that bloatware from VZW so not sure if that helps or not.

So frustrating......
[RAZR HD General] lesdense:
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.

OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
[RAZR HD General] PantsDownJedi:
Root Explorer is what I used.

For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
[RAZR HD General] surfmly:
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).

Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.

Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).

---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------

BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).

Thanks.
[RAZR HD General] PantsDownJedi:
I was kind of just pulling at straws, and trying to answer two posts at the same time, sorry for the confusion. My habit, especially before unlocking the bootloader, is to push things to the sdcard then moving them and setting the right permissions and assingining the correct group and user.

As you've explained things, I don't know why it shouldn't work. Mine is a 4.1.2 OTA. It was originally rooted before upgrading and using Voodoo root keeper but between that and Supersu paid version I was able to reinsert root again after a factory reset, which was a stroke of luck as others lost it. I don't think it would matter which root method is used but I could be wrong; esentially its just allowing us to access the build.prop file to edit at all. I don't remember if I had modified the build.prop before or after the reset. I know that it was working both before and after I unlocked the bootloader though. As for the placement of the line, I put it at the end. I also, out of habit, hit enter for a new line for this type of thing. Afterwards, though, there is now new things that Pimp My Rom has inserted (Some of the tweaks in that package are old and I'd advise people to stick with close to stock as possible when using it unless they know what those lines mean; and there's some build.prop myths still floating around XDA that are not good ones, one of which I know Pimp My Rom uses and looks pretty apealing to select). So, now I have some stuff after it. If there were other things added to your build.prop, then perhaps moving the line to the end of where the default configuration ended... grabbing at straws again with this last sentance but in the lack of information I'm just trying to be helpful

Perhaps if people also with this problem, in addition to answering your question about the root method they used, also posted which carrier branding they had it might reveal something, or rule it out. <-Put that in bold for you :)
[RAZR HD General] majorpay:
I am VZW with Nova Pro, and I get the systemUI FC as well. After much research, I haven't heard of too many people with PHONES that have been successful in this hack, so I tried it on my GTab 2, and same thing.

After spending entirely too much time looking into this, I purchased Full!Screen+, set the apps that I wanted full screen, and I'm set (oddly enough, this didn't work on my GTab, so I also purchased Hide Bar for that device. I prefer FullScreen+ because the truth is, there's only certain apps that I care about being full screen (Netflix, games, youtube...).

The biggest problem with FS+ is that it hides the notifications. Honestly, I don't really care about that either when I'm doing one of these other activities. After all, we have a notification light.
[RAZR HD General] lesdense:
FullScreen+ worked for me too but only if I am willing to hide Notification Bar as well as NavBar (as noted above). I am NOT willing to go without Notification Bar. Clock, signal strength, BT on/off, wifi on/off, messages, battery status -- this is ALL information I want constant assess to. So, for me, the search goes on.

And, by the way, why wouldn't there be something instructive in the comparable coding for Razr/Razr Maxx? I understand that those phones are not quite the same as the HDs but I assume that most of it is the same. The Razr/Razr Maxx have "hard" navigation buttons so they don't need soft NavBar buttons. Surely that difference shows up in the coding to people who can read such things. I, sadly, am not one of those people.
[RAZR HD General] Xioshen03:
its qemu.hw.mainkeys=0
[RAZR HD General] djparent:
Has anyone ever solved this? I stumbled onto this thread and have a feeling that the problem isn't limited to any one device. I have a Samsung Galaxy Tab 3 running 4.1.2 that is giving the same systemui crash after changing qemu.hw.mainkeys. The weird part is that it was previously working for me until I updated the xposed installer on my tab. After the update I can't activate the nav bar anymore even after wiping and reinstalling the factory rom. I thought it may be related to dpi settings but no luck so far. Here is relevant info:

-nova launcher pro

-rooted with supersu

-build.prop edited with build.prop editor by jrummy apps

Sorry for resurrecting an old thread just looking for a solution. :)
[RAZR HD General] jason600:
Use xposed framework with gravity toolbox, there's an option in gravity under display for expanded desktop, select hide navbar option (or hide both), long press power button and select expanded desktop and no more navbar.
[RAZR HD General] lesdense:
For the XT926, most of the latest ROMs (4.2.x and beyond, I believe) have a setting for "Expanded Desktop" (Settings/Interface). The options are Disabled (both Navigation Bar and Status Bar are visible), Status Bar Visible (only Navigation Bar is hidden) and Status Bar Hidden (both Navigation Bar and Status Bar are hidden). I flash a new ROM on my XT926 every couple of weeks and this method (I choose Status Bar Visible) has worked perfectly every time for me. It eliminates the Navigation Bar and it seamlessly resizes everything, wallpaper and every app I've tried, to fit the expanded space. If you're set on staying with a 4.1.2 ROM this won't help, and it may not work for a Galaxy Tab 3, but it solves the NavBar issue on a Razr HD in seconds.
[RAZR HD General] pistacios:
I'm running in the same vicious circle now. Still looking for a fix. I'm running eclipse based on 4.1.2 and can't get the notification bar to stick while hiding the nav bar.

I'd like to stick to stock based ROM only because of HDMI/car dock USB audio functionality.

Tried xposed with gravity box, gmd app, udn app.... nothing to achieve no nav with notifications.

EDIT: ultimate dynamic navbar pro works!!! It also needs it's xposed module loaded. Notification bar visible, navbar hidden and tap trigger area to show navbar when needed.

(I Can't post screenshots thru tapatalk for some reason...?)
[RAZR HD General] six37:
Try this:

Download Total Commander. Go to settings and give it root access. Edit buildprop via TC...
[RAZR HD General] Rodrigolopezguerra:
Hi . No relation with the launcher or whatsoever .

If you properly add the line to build.prop and is not working , check for another build.prop . sometimes located in

VENDOR/BUILD.PROP

or at

DATA/LOCAL/BUILD.PROP

If not that paths , search for another build.prop and you will find it.

BR
[HTC Sensation] anatolpau:
i have a hardware problem with my sensation, i have the bsi and btemp intrerupted somewehe(on the phone board)... if you could help me with a scheme to know where to measure, and to find the problem. Tnx a lot
[HTC Sensation] kien3g_gsm:
see the schematic

you can see the schematic view can help you not
[Galaxy Tab 8.9 General] lien91:
hello...im new in here,,,my tablet wont turn on after i put into download mode,,,is there anyone can help me,,,:crying:

im i had a hardbrick,,,
[Galaxy Tab 8.9 General] jd1639:
Make sure usb is not connected, then press and hold the power button until it vibrates

Sent from my SAMSUNG-SGH-I727
[Galaxy Tab 8.9 General] lien91:
thanks,,,im new with the tab,,,its my fault,,btw thanks for helping,,,;)
[Galaxy Tab 8.9 General] jd1639:
It's it working now?

Sent from my SAMSUNG-SGH-I727
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Frikid:
hi everyone, while i was installing a rom, i think i messed and not i am stuck in a boot loop.

Now whenever i switch it on, it shows the logo then black screen then again logo and then again black screen ,,,

Now please help me =/
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] darkshadow246:
Flash stock rom through Odin and then flash custom rom again

Sent from my

you'll never know
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] sanny5:
Enter cwm

Format everything except sdcwrd

Moynt everything

Wipe delvic and battery stats

Mount everything

Flash ur rom...

=========HOLO-UBUNTU========theme
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Frikid:
i tried this but it is still stuck in the boot loop, i guess i should stick with the stock rom for now.

I tried flashing the stock rom but it didn't work. i think i need to flash it through odin , can anyone link me to its tutorial ?
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] :
I think you are using nemesis rom.

Dont use that rom its going to break it
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] PrtScrSysRq:
Flash The Stock ROM via ODIN

download here

http://xdaforums.com/showpost.php?p=21846620&postcount=1

search rom by region.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] menewtoroot:
Hey hey hey.!!! It can happen to anyone .. Its nt neccasory that he used nemesis or nemesis is the only rom that can brick ur phone..

Jst by editing build.prop can also brick ur phone..

He is a dev too.. Respect him nd his works ..:mad:

** rooting is new for me,

nd i am a noob to root....:D:D**
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] andynroid:
Use the ODIN way so as long you can go to DownLoad mode then you are fine.

Use ODIN and find a ROM (FW) which you can extract it's packages i.e.

Place the CSC package in the CSC folder...Modem in the Phone folder and PDA in the PDA folder...........Under ODIN leave everything as default and flash it............Have a copy of this FW which is meant for Universal, perhaps I may upload a copy here later :laugh:
[Desire HD Themes and Apps] ATMOSF3AR:
[PSD] ░█░ HTC Desire HD PSD by ATMOSF3AR Designs ░█░

This is for showing off your ROM's and themes and Apps for the HTC Desire HD.

I worked really hard on this so a thanks would be great,

if you think i deserve it.

Here's the preview

Please Credit me if you use it

Download : deviantART (free)

Support Me on Facebook : I SUPPORT YOU ;)

​
[Desire HD Themes and Apps] XDA_h3n:
Will use for future designs tnx.
[Desire HD Themes and Apps] ATMOSF3AR:
I'll be glad. :)
[General Questions and Answers] Hagemazu:
Can anyone help me because I have phone motorola fire xt530 and now the conditions is hardbrick.

can be normal again ???

please anyone help me.... :(