yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] THE LEGEND L:
coming soon ROM THE LEGEND 3.1
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AndroidSlave:
What in the world are you talking about
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
May be he's making a new rom for us. ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AndroidSlave:
OK you test it and let Me know...lol
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
sure may be when he has at least 100 posts
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] THE LEGEND L:
thank you all guys:good::good::good:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AndroidSlave:
This guy is funny...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Haints:
He's a legend!

As to the poster who wouldn't try his ROM until he hit 100 posts ... don't worry. That should be any second now.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AndroidSlave:
Lol he will be at 500 posts by the end of today.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jokus09:
Hey guys.

I am not cooking any new rom. I am a newbie with custom roms. What i was trying to explain was like cm9.1 is there any cm10 stable one available for GTN7000? In get.cm quincytmo have a stabke version which shows gtn7000 tmus(supposed to be T-Mobile US.)

Hope u guys got it.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
It was not about you. Legendary
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Haints:
Grab the new Asylum rom from the forum. Stripped down CM10. Stable and ultra fast.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jokus09:
Ok. Cool. Mistaken. ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] rollingdices:
I can recommend JellyBam, as it is very smooth and has a lot of setting options. But as some already mentioned, it's completely up to your taste...
[Samsung Galaxy W I8150] zezadas:
so, already compiled some times GB kernel, easy, just command make and everything works fine

but i'm interested in compiling jb kernel.

already git clone kernel 2.3.6, git checkout jb 2.3.6

but i cant compile, already sudo sh extract-files and setup-makefile, the only thing that it does is pushing the files from adb to a dir.

also, itt new guide for compile kernel

any help in compiling the kernel from source.

any help would be appreciated

regards
[Samsung Galaxy W I8150] hadidjapri:
i use thishttp://xdaforums.com/showthread.php?t=1966751 as my guide for building the kernel also this one http://xdaforums.com/showthread.php?t=

Sent from my GT-I8150
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] njfuller:
I suspect I will get some jip for this - but I have hurt my Ace from trying to install an IOS5 ROM. I will detail process and attempted fixes below. Please be assured I have spent 3 hours crawling Google before darkening your doorstep with my problems...:crying:

Advice would be hugely appreciated as it's my wife's phone and, well, I'm in trouble,....

1. Installed ROM for IOS5 Black - SGA, via Recovery mode, wipe and install from SD ([ade.htp.ac.id/?p=524[/url]) (also rooted - assuming it worked)

2. Rebooted, the device showed the Samsung logo, an X-Ray hand (I guess it's the programmers logo) and then hung on ANDROID. I left for 25 mins, tried rebooting a few times, tried re-wiping and reinstalling - nothing worked.

3. Read up a bit, downloaded Odin and cooper_v1.0.ops and latest samsung firmware from sammobile

4. Launched Odin, entered Download mode, connected successfully, loaded cooper and firmware as 1 package

5. Checks are okay

6. Start - and it hangs on MIBIB, no progress at all for 30 mins

7. Already tried - redownloading ROM and a new cooper file - no luck. Tried running without Protect Ops - no luck, tried different USB port - no luck

8. The device now does not boot at all and opens straight to an icon of a mobile connecting to a PC. I can enter download mode, and can reconnect to Odin - but the same problem occurs.

9. I did make a backup of my original SD if that's any use, and I have an SD reader/writer to access SD if that is any good to me.

So - gentlemen, how pooped am I?

Ideally I'd liked to boot back to a standard firmware, factory default or equivalent (and then try again with some adhoc ROMS)

System: Windows 8

Phone: S5830

Odin versions: I've tried 4.38 and a couple of older versions.

The only thing I haven't tried is installing XP to run it from there - doubt there's any merit in it but it came up in one article I read.

Help would be warmly received. I'm hoping you all role your eyes and abuse me for not finding the obvious answer elsewhere.... :D
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Prawesome:
You are completely messed up.. No idea what's with your phone, try flashing a full package file with Odin on Windows 7 instead of Win8..
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] side_effect:
Rename cooper_v1.0.ops to cooper.ops and try.

BTW googling

Samsung galaxy ace stuck on mbibi brings first result so I am having a slight doubt on ur 3 hr claim
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] SnowPluralism:
Theres already post with ace stucked on mbib.... Just search its an easy fix :)
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] njfuller:
Hi

I am installing W7 and will try both. More like 4 hrs now - I don't BS. However, was searching under model number rather than Ace, will give that a try when new W is working.

Thanks for your help

NJ
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] njfuller:
Thanks - back on W7 now. Could I just confirm what you mean by a full package file? Is the 1-package file I got from sammobile going to be okay?

Cheers

NJ
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] njfuller:
Hi,

I'm having no luck. Have tried renaming cooper, also got another new version of it just in case and also tried ClockWorkMod 4.0.0.9 mentioned in another forum. But Odin never get's passed MIBIB.

Have attached a screenshot.

Are there any other methods to completely reset / reboot a bricked Ace?

Help much much appreciated

NJ
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Venomous Viper 119:
Go here& try for one final luck.

www.themythace.com/flash-stock-rom.html. Be sure to install the mobile device driver before & keep kies shut while flashing. I've tried it & has worked perfectly fine with me & by the way, even my phone was stuck on the screen that showed phone connected to pc on boot :) So, if followed correctly, nothing should go wrong.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] side_effect:
Where there is Odin multi downloader (Android) written,it should start showing Odin multi downloader (GT-S5830) after choosing cooper.ops.

So try getting S5830XEKPH or S5830XXKPH from sammobile or angeeks
[Samsung Galaxy Player 4.0, 5.0] AzWizzard:
I am looking for a car charger for my daughters Galaxy Player 4.2.

I currently have a Motorola one which works fine for my Galaxy SII and my wife's HTC EVO, but for some reason it does not work on my daughters Player 4.2.

Anyone have a Car Charger that works on the 4.2 Player?
[Samsung Galaxy Player 4.0, 5.0] aznflawless:
It maybe that you need a charger with more voltage.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
More amperage, not voltage. USB voltage is ALWAYS 5 volts, but these players need like 700mA (.7A) or atleast the 4.0 needs .7A

Just make sure when looking at car chargers that each port on the charger outputs 1A
[Samsung Galaxy Player 4.0, 5.0] AzWizzard:
Thanks, I was just surprised it wouldn't work on her Player.. It charges my S2, my wife's Evo and even my Nexus 7.. I will see what I can find on Amazon.
[HTC Droid DNA] WilliamStern:
I was just reading in another thread about how some are just not happy with the camera quality that this phone has to offer. Well, I'm here to tell you that the camera is not the issue at all.

I was one of those that thought the stock camera was just not cutting it for me, and was a tad upset about it as well. Yesterday I thought I'd give Camera 360 from the app store a shot, as I already used it before with my Gnex, and it produced better looking images. To my surprise, the app completely kicked ass, and now I will never use the stock camera again on this phone for any reason, period!

Not only is it a fantastic app, but it comes loaded with some amazing features, and filters that make taking photos with this phone a pure joy.

Below are a few samples of images I took today while hanging out with my daughter. Take note that edits were done from within the app itself, and are straight out of camera without any processing using Photoshop, or Lightroom.

Hope this helps many of you out that were on the fence about the camera.
[Nexus 4 General] efrant:
How to return to stock if your USB port is broken

I am adding this how-to in case people need it, for return their device to Google, etc.

This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.

Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.

1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;

2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;

3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;

4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.

5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.

6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;

5) Turn off your device and reboot into the bootloader;

6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.

7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.

8) Done. Now you are fully stock JDQ39 with a locked bootloader.
[Nexus 4 General] efrant:
Reserved.
[Nexus 4 General] El Daddy:
Awesome! Thanks again efrant!
[Nexus 4 General] tomedic:
Ok...

So I consider myself fairly good at this stuff. I've been rooting and doing custom stuff since the N1. I have messed up somewhere...

So initially I used the "1-click" script method (I know) to unlock/root/BB/etc... It worked, but then I decided to go into recovery and wipe everything (inlcluding /format system) in CWR.

That ended up being unable to get passed the Google screen.

I then used your method, which appeared to work...

First time through it got to the "X" and just sat there for 5+ minutes (I unplugged the USB about a minute after it rebooted). I then attempted to restart and nothing.

I tried a second time and instead of it going to the "X" then screen just went black. The device is now recognized as a Nexus 4 under USB devices on my computer, but the screen is off and I can't turn it on. I just unplugged it and now nothing! It can't turn on!

Ummmm... ****! I even rooted the Desire HD back when you had to do a bunch of weird terminal stuff. What happened? Little help?

EDIT - Ummm I managed to get it turned on. I tried in bootloader and eventually it turned on. However it went staright to the Google screen with these weird graphical glitches, now it's on the "X" but I can still see "google" behind it. I'll leave it for a bit and see what happens....

Jesus...
[Nexus 4 General] efrant:
Yeah, you know I personally don't recommend that ;)

If you wipe system, there's nothing to boot to, so it certainly won't get past the Google screen.

Boot back into CWM, wipe data, then boot into the bootloader, and re-flash the boot and system images, and erase the cache. Then reboot, and wait a good 5-10 mins for it to start.
[Nexus 4 General] tomedic:
Ya, I did the format system out of habit because I usually did that when flashing ROM's.

So I'm still staring at the X. The graphically glitches have cleared up, but it's been 10+ minutes. I restarted into bootloader, went to recovery and have the andoid showing with a red exclamation mark!

I turned the phone off. I await your guidance...
[Nexus 4 General] efrant:
The android with the red exclamation mark is the main screen of the stock recovery. (I'm assuming you flash it if you followed the guide in post 1. You need to re-flash CWM if you want CWM.) As an aside: if you want to see the menu, hold power and press volume up.

Ok, do you have data on your device you want to keep?

If not, do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot, system and userdata, and then erase the cache partition as per the first post.

If yes, then do this: reboot into the bootloader and flash the following images as per the instructions in the first post: boot and system. Then flash CWM. Then boot into CWM, and wipe data, and wipe cache. Then reboot.
[Nexus 4 General] tomedic:
I don't want to keep data. I chose that option (but didn't reboot the bootloader after boot.img because you said not too). It just went to the "X". I'll wait...

---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------

Still nothing. Just the "X" animation. No graphical glitches though. It's been 15 minutes.

Any other suggestions? Your stuff works, it's just not booting...
[Nexus 4 General] efrant:
Strange. All the images flashed fine (without errors) and it won't boot?

Can't think of anything else to try at the moment.
[Nexus 4 General] evaradar:
Question, is there a reason to flash stock image at all if we get the phone brand new? Or is this only if we are coming from a custom ROM? Reason I ask, its not the question of build versions like the Galaxy Nexus - yakjux, and then flashing to yakju/takju, etc.

Just verifying that's all.
[Nexus 4 General] tomedic:
No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...

I will try your method from the beginning again tomorrow.

I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...
[Nexus 4 General] efrant:
No, no reason to flash a stock image on a brand new phone. Only if you want to go back to stock following a custom ROM.
[Nexus 4 General] Maverick1707:
It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...

Hope it works for you too.
[Nexus 4 General] efrant:
This is indeed strange, as steps D10 and D13 do exactly that: factory reset and wipe cache.

In any case, I will make a note of it in the first post.
[Nexus 4 General] evaradar:
Gotcha. By the way when I rooted the Nexus 4 even before this guide, I know how to do it but I had one slight issue after flashing TWRP's latest recovery. When I tried to enter Recovery mode on the phone I got the Red Triangular Exclamation mark, even after flashing the stock recovery back. To get it working I had to type in fastboot erase cache to get it working then rebooted the bootloader to test it out and it was fine.

Then after installing SuperSu using TWRP, it got stuck on the Nexus logo, even after pressing down on the Power Key for 10 seconds or slightly longer same thing. Then I resolved the problem by clearing cache and dalvik cache using TWRP and it solved the problem.

So just a heads up if anyone runs into this problem.
[Nexus 4 General] tomedic:
It worked! Thanks man!

And thank you efrant. Now to switch recoveries and get root! :laugh:

---------- Post added at 10:55 AM ---------- Previous post was at 10:40 AM ----------

Yup, I just rooted and had to do the same thing.

I assume if I wanted to keep the custom recovery I would just have to: fastboot flash recovery customrecovery.img ?

Thanks again all. These little hiccups make it interesting!
[Nexus 4 General] efrant:
As I mentioned before, the "Red Triangular Exclamation mark" is the stock recovery. It gets flashed on every re-boot if you updated you stock ROM via an OTA update. More details on this in this thread.

Again, interesting. Not sure why this is.

Correct.
[Nexus 4 General] jimmyz:
I'm assuming that like the GN we need to rename the recovery-from-boot.p file if we want our custom recovery to survive a reboot?

EDIT- never mind I just looked through your 101 thread and answered my own question- thanks!!
[Nexus 4 General] spaceman860:
Thank you for making this thread over here. Glad to have you as a moderator. I hope every noob reads all of your threads.

Sent from my BAKED N7
[Nexus 4 General] Jake-CT:
I just did unlock and root from stock and it required a cache wipe to reboot. Weirdly I didn't lose my apps/data - I was under the impression that this would happen (glad it didn't)... I have root access and unlocked bootloader... Everything seems to be working great. Thanks!
[Nexus 4 General] efrant:
What you did was fine. No need for anything else.

Yeah, unlocking the bootloader should have wiped. Not sure why it didn't, but all the better!
[Nexus 4 General] Kameel:
Thank you!

So I ran across a issue where I was unable to boot into my device ( Soft-Bricked ) I'm 14 and thought it was all over for my device but using you extremly well written guide I managed to fix all the issues, I dont know how I can repay you, THANKS SOO MUCH!
[Nexus 4 General] Postal Psycho:
thank you efrant i learned some stuff from this. I too, couldnt get past the X, so i had to boot to stock recovery and factory reset wipe cache as per your instructions. I previously used toolkits to root and unlock all my recent phones but i think i am going to do the manual way next time just to know that i can. Your efforts are appreciated. Thank you again.
[Nexus 4 General] Jake-CT:
I agree great guide. Just wanted to add that I only had to wipe cache when stuck at the colored X - might be worth trying first to save your data.
[Nexus 4 General] efrant:
Thanks. I'll make a note of that in the OP.
[Nexus 4 General] xameius:
How does one go about unrooting, reflashing stock recovery, and relocking the bootloader with a bad USB port on the phone? I need to send it back as part of the RMA and would like it to be stock if possible...
[Nexus 4 General] efrant:
Yes, there is a way.

EDIT: Moved (and refined) instructions to post #2.
[Nexus 4 General] xameius:
Thank you very much! Thought I was S.O.L. Wireless charger is barely keeping my phone from draining itself, bad USB port, not sure what happened.. AirDroid and BootUnlocker are lifesavers. I have the stock 4.2 image but it isn't in a flash-able format and not sure how to get it into a CWM zip. Since the version you're uploading seems to be newer (at least, the recovery is) I'll just wait for that. Thanks again!!!!
[Nexus 4 General] efrant:
Link posted.
[Nexus 4 General] xameius:
Followed your instructions and I am now 100% stock, unrooted, and locked bootloader. Ready for Google RMA. Thanks again!
[Nexus 4 General] efrant:
Glad it worked for you. Thanks for the feedback.
[Nexus 4 General] jakeman66:
Thanks for putting this together, worked well.
[Nexus 4 General] DDeleted:
Does this unroot the phone? :confused:

(My USB port is broken and I need to send my phone to Samsung to repair).

EDIT: this is Nexus 4... I need files for Galaxy Nexus...
[Nexus 4 General] efrant:
Added additional info in post #2.
[Nexus 4 General] kyokeun1234:
Glad to see you in Nexus 4 forum :)

Loved your work since galaxy nexus days!!!
[Nexus 4 General] clpw:
Hi there. I am trying to do flash the stock ROM to my soft bricked nexus 4 but i'm on a mac and my computer does not seem to recognize my device. when i type in fastboot devices i get command not found. Please help! Thank you!
[Nexus 4 General] muz4:
I feel this should be in the OP.

---------- Post added at 05:37 PM ---------- Previous post was at 05:36 PM ----------

use "./fastboot-mac" (unquote) instead.
[Nexus 4 General] clpw:
Ah yes, thank you. SLAPS SELF.

I'm now stuck at the nexus logo, will give it 10 minutes before freaking out again. It should work, right?

Edit/

I did it. I actually did it. THANK YOU SO MUCH FOR THIS POST. THANK YOU THANK YOU THANK YOU X A MILLION.
[Nexus 4 General] efrant:
What should be in the OP? Everything you quoted is there.

Glad you got it working.

You will come to realize that in most cases, you shouldn't have to worry because there is very little you can do to brick your device. Most of the time, all you have to do is flash the factory images, and you are back to out-of-box condition.

I'm sure you learned a lot in the process (which is the goal of this thread) and hopefully you've gain some confidence with respect to flashing.
[Nexus 4 General] Rushing:
To all with troubles, In windows (10) simply double click the

flash-all

file.. you need to unzip everything into the same folder. the script did it did it better than I could have --faster and real easy. those with linux.. try the falsh-all.sh or bat golf clubs are amazing!

here is a look at the flashing order .

ps sorry if this has been posted 1002 times I admit i only read about three pages the OP and the following quotes as well as the last couple pages of ten or thirty posts so dont double click clack me..

[HIDE]sending 'bootloader' (2264 KB)...
OKAY [ 0.080s]
writing 'bootloader'...
OKAY [ 0.294s]
finished. total time: 0.378s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.529s]
writing 'radio'...
OKAY [ 2.533s]
finished. total time: 4.064s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 0067bf6019ce51c3
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (6448 KB)...
OKAY [ 0.221s]
writing 'boot'...
OKAY [ 0.346s]
sending 'recovery' (7008 KB)...
OKAY [ 0.267s]
writing 'recovery'...
OKAY [ 0.401s]
erasing 'system'...
OKAY [ 0.082s]
sending 'system' (834934 KB)...
OKAY [ 32.265s]
writing 'system'...
OKAY [ 47.516s]
erasing 'userdata'...
OKAY [ 0.643s]
sending 'userdata' (137438 KB)...
OKAY [ 5.289s]
writing 'userdata'...
OKAY [ 7.362s]
erasing 'cache'...
OKAY [ 0.032s]
sending 'cache' (10984 KB)...
OKAY [ 0.429s]
writing 'cache'...
OKAY [ 0.629s]
rebooting...

finished. total time: 95.524s
Press any key to exit...[/HIDE]