yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] JohnCorleone:
I have been in NYC a few times over the past couple of weeks. Its crazy there. You go from 4g to 3g to 1x within 2 blocks. The buildings and mass of people make for an interesting time on Sprint. Now I am 15 minutes away from the city and seeing over 2Mbps on 3g. I am in a fringe 4g area coming from my 7-10Mbps 4g in SoCal but having real Wi Fi for the first time more than makes up for it. I saw the 1x icon for the 2nd time ever in the city. The one encouraging thing was I was at Port Authority 2 levels underground and still had service and had service all the way through the Lincoln Tunnel. I have said it before... with Sprint its all about location and how congested the network is
[Samsung Epic 4G Touch] masbret:
I also very often see faster upload speeds than download. In my area, if I get 10-30kbps in download over 3G, I'm lucky.
[Samsung Epic 4G Touch] gedster314:
Thats about what I get during nights and weekends. Oxnard, SoCal
[EVO 4G General] rblochmn:
So, I am a new user to XDA, but am by no means a newbie developer. PHP, PERL, C+, .net, powershell, you name it.

I wanted to give thanks to Mazwoz, as that poor soul has received the most ridiculous amount of trash talk for no reason. Also, a thank-you for his service (assuming he is enlisted and not a contractor).

Anyways, thanks to MazWoz for your work, and I hope that this silly 10 post minimum garbage goes away.

Otherwise, I guess I'll just post 10 more threads about how silly this is.

(Actually, I won't, but it made me feel better to say so.)

Mazwoz, if you happen so see this, I wanted to get you some information about a gallery issue I am having, I might have fixed it in a reproducible way.
[EVO 4G General] AFschizoid:
I agree, even though he came out of nowhere with a rom, it turned out to be remarkably smooth for a first run ICS rom. Keep up the good work, man!
[EVO 4G General] sobaked2921:
people like to ***** and moan because their real life sucks an on here they feel godly
[EVO 4G General] mazwoz:
Thanks bro. I am enlisted btw. E-5 in the AF

Sent from my evo running MazWoz-EVO
[EVO 4G General] mazwoz:
hehehehe +1
[EVO 4G General] edlokien:
Good work on the rom......a little glichy on my phone, but still non the less good rom....

Keep up the good work and thanks for still serving! I got 2 years ago and I still miss it to this day

605 till the day I die!
[EVO 4G General] mazwoz:
I hear you bro. Almost got out but re-enlisted.

Sent from my evo running MazWoz-EVO
[EVO 4G General] skannan1:
My first post here..but a long time reader and follower of many ROMs.

Thankyou MazWoz. Installed it and works awesome so far..Battery life is 30 hours and counting (on regular battery), and I am power user. Excellent work.!!

Waiting for your HW acceleration and Chrome fix.
[EVO 4G General] KalEl>Zod:
Also would like to give big thanks to mazwoz... I've been using his ROMs for a few weeks now and they have been great daily drivers. I don't ever use 4g because for my experience its unreliable at best. Thanks for a great ICS rom and keep up the great work.
[EVO 4G General] bigazzjeep:
Just like the first one, I've been reading, reviewing and testing long before I decided to join. A lot of appreciation to any and all developers, I am running MazWoz 4.7...props sir!
[EVO 4G General] mightypixel:
+1 here! Been using this ROM since its stormy beginnings!

4.7 is the best yet!

Question for other 4.7 users, Google music suddenly incompatable?
[EVO 4G General] evol4g:
+1 so many people are under appreciated when i first read all that trash on the first page of the roms op I was sooo hesitant to join xda, the only reason i'm here is because the best MIUI roms are on xda..
[EVO 4G General] te45a:
+1

I been testing this since start, running 4.7 now and one thing i noticed is Apex makes this ROM really fly...
[EVO 4G General] savoca:
People seem to forget what open source is. I'm glad I didn't run into something like you when throwing DerpXL out of nowhere but it seems to be all behind you now
[EVO 4G General] dbo_texas:
I'll throw in a thanks to Mazwoz as well. Seems like a genuinely good guy (you can tell by his responses to the garbage some people have posted) and he takes the time to help you out.
[EVO 4G General] Papa Smurf151:
Moved to general as I see no questions in here. Oh and you do realize this tgread was 8 months old

XDA Moderator
[EVO 4G General] HipKat:
Truth! MazWoz is the man!!

BTW, got out of the Army as an E-5..... WAY too many years ago....
[EVO 4G General] dwr3ck3d:
Not a fan of the 10 post minimum either, but I do understand the reasoning behind it. Just started tinkering with roms, but MazWoz-Evo JB 4.1.2 is the best one I've seen so far. So I thought I'd throw my thanks into the pile too. Look for my comments on the rom page soon... Thanks Maz!
[EVO 4G General] NegativeCool:
MazWoz JB B3

I wanted to post a comment to the official development thread, but I couldn't. I have so far only been lurking in the shadows and not participating in the conversation so I'm nowhere close to the ten post minimum, even though I've been frequenting those pages for years!

I've been flashing my phone ever since my first Droid Eris had 1.6, and I've been running Maz's Jelly Bean ROMs since B1. This most recent release is (obviously) the most stable and fastest I've seen yet, and that goes for ANY JB ROM. I've tried a few, but Maz is the best. So the real reason I wanted to post was...

I want to thank MazWoz for spending so much time working on this. You have managed to breathe new life into my old-ass phone (not to be confused with my old ass-phone). Google Now is amazing, I love the new alarm clock, and the SPEED, man! Blistering!!

With B2, I was having a lot of issues when I'd open an app and it would freeze and reboot, but so far that seems to have been resolved. This ROM is so much smoother and faster in general, I don't even know where to begin singing your praises. If I could ask one favor, please include the option to center the clock in the status bar in your next release! I know you're already working on fixing the camera screen, so in summary:

KEEP UP THE GOOD WORK, AND THANK YOU!!! [cue applause]
[EVO 4G General] evol4g:
Wow I remember when this thread was first started loll
[Optimus One, P500, V General] ljubisa_sk:
So the problem is this.

I wanted to update my old baseband v10c on my P500, and like safest option I took the LGMobile update tool.

I started LGMobile update and it said that I got new update for may phone etc.etc. it took me to the "emergency mode" and it stopped there.

But after a 10 minute stop I have decided to restart the phone and everything was just like it was, my old rom (#void) which I used for 7 mounts was ok, I got signal from my carrier etc.etc. Then I flashed NightlyFourE ROM from the OLD BASEBAND and I was not getting a signal. I restored my previous rom back and I got No Signal Error. now I flashed a new baseband (v20g) using this tutorial and again i got the same error (NO SERVICE) NO SIM CARD... :(

So PLESE if someone know how to fix this problem respond me now thank u...

I also read some lg forum user were complaing about this problem on lg forum
[Optimus One, P500, V General] Arjen:
So flashing new baseband following that thread worked? Do you still have the nv2 backup?

Which Rom do you have installed now?

Did you try a full wipe before flashing another Rom?
[Optimus One, P500, V General] ljubisa_sk:
Now I got LG stock 2.3.3 rom which I flashed from the new baseband (v20g) using KDZ the phone is functional at all except "No Sim Card" error.

I have tried full wipe and batt\stats\ using ClockWork 5.0.2.0

I dont know what else can I do\???
[Optimus One, P500, V General] ljubisa_sk:
And if nv2 file is about 179kb large yes I got it
[Optimus One, P500, V General] Arjen:
Can you check in the folder where you have the lgmdp-tool if there is a folder which name contains only numbers?

Edit:

see you have it ;)

guess you allready re-inserted your sim-card?

Don't think it's the cause, but you never know...
[Optimus One, P500, V General] ljubisa_sk:
I got the folder presuming the name of the folder is my IMEI so can this be flashed back into phone?
[Optimus One, P500, V General] Arjen:
It could be the cause of your problem, so just try.
[Optimus One, P500, V General] ljubisa_sk:
I just restored nv2 file using LGMDP-v1.5 and no luck :(
[Optimus One, P500, V General] Arjen:
What baseband info does your rom give? You can find it in About phone.
[Optimus One, P500, V General] ljubisa_sk:
Sorry for slow respond

model number

lgp500

android version

2.3.3

Kernel version

2.6.35.10-perf

lg-electronics@INFABA00091#1

Build number

GRI40

Software version

LG-P500-V20g
[Optimus One, P500, V General] :
I've heard so many times that using kdz is risky business...if I want to switch BB's I just use LGMDP 1.5 and go from there,I know this is of no use...maybe I'm wrong Arjen knows more about this than I do
[Optimus One, P500, V General] laz3r69:
no info

no baseband info here..

---------- Post added at 10:19 AM ---------- Previous post was at 10:15 AM ----------

Check out here and DONT MISS ANY STEPS.

http://xdaforums.com/showthread.php?t=1149530

Its risky.Stick to the steps.otherwise u will have a TOY PHONE for your baby!!

:p

I too had this problem.I did it again and it just worked.

things may not be same for u.....

also please dont complain to LG about this...

in other words just dont get into LION's DEN by yourself... LOL
[Optimus One, P500, V General] ljubisa_sk:
I have tried this now and yesterday like 10 times or more but got no luck I think Lg service should take this in their hands couse there is no way that I can make it work thanks guys.

And yes every time when I tried this the nv2 file was backed up successfully and was restored successfully, and "download complete" was present every time :( but "No Signal" is still here
[Optimus One, P500, V General] ethan24:
Hi,

may be you can try to shift your SIM inside the phone to any other phone and try out - whether your SIM have signal in other phone?

and later just try to shift back your SIM card into this P500 phone.

can give it a try... no harm..

just 2 cents input.
[Optimus One, P500, V General] ljubisa_sk:
I gave the phone to a local service center today and he said that he'll make new nv2 file for my phone and see if it works... I'll report here tomorrow the result.
[Xoom General] iammodo:
What are peoples xooms getting?

Cm9 wifi

Sent from my Xoom
[Xoom General] Sardo Numspa:
Just ran it. On cm9 kang at 1.7 performance
[Xoom General] Elysian893:
Got the same score on my Xyboard I got from before it supposedly supported multicore. Either it doesn't support it very well or it has always supported it. I'm going with the latter.
[Xoom General] maxmiz:
You have some great scores. Me with the "Stock 4.0.3" my score is only 1956.
[Xoom General] iammodo:
We are overclocked does help

Sent from my Xoom
[Xoom General] UnholyX:
3926 at 1,6ghz
[Nook Color General] 12paq:
I am having an issue where my Nook Color will only boot to recovery.

What happened that possibly caused this: While booting up CM9 on emcc, I held the N button down to go into fattire's u-boot menu, I accidentally chose to Alternate boot and I have no alternate boot. The u-boot menu froze for several minutes. I then forced a hard power off by holding the power button. Since then the device will only boot to recovery regardless of the u-boot menu choices.

I have never dual booted and never ran any dual boot scripts. All of the attempts to fix this result in the Nook booting only to recovery. My Nook *will* boot from a bootable CW usd, that I have used for repair attempts of my emcc. I used the most updated CWR version possible. Additionally booting to a "Nookie Froyo" (remember that?) bootable card for repair attempts.

So to be clearer; I can boot to a bootable usd card, but all attempts to boot from emcc result in a boot into recovery.

I have tried:

Full wipe, reflash CM9, clear caches fix permissions.. etc. several times.

Full wipe reflash Cm7, then CM9 respectively.

Manually via adb, removing and installing CWR. (Results in boot to u-boot screen, all menu options lead to boot to blank screen)

Flashed back to stock. (Results in booting to stock recovery, and then fails)

Repartioned boot via flashable zip.

Restore to stock via flashable zip.

Recreated stock boot partitions manually via ADB, fdisk, dd etc..

Recreated all partitions via ADB, and checked the contents and the format structures and sectors.

From stock 8 failed boots, fails.

From stock adb 8 failed boot count. (**All results to revert to stock results in booting to stock recovery and then fails to update**)

Made sure the bootable usd I was useing was latest ver CWR

Tried an eyeballer CWR zip to fix exiting CW.

Installed latest experimental CM9 CWR to emcc and tried all above, and still only boots to recovery.

Made sure no encore or update zips were on the root of my sdcard.

Flashed several iterations of fattire's u-boot.bin, even tho I know it is installed with any encore update.zip

Tried all of the above several times and all the standard tricks to recover that I have learned over the past year.

**All of the above results in a Nook that wants to boot to recovery, any recovery, weather recovery is present or not.**

This leads me to consider the 2nd (rom) partition that can contains 2 (or more?) private files that can control boot that will look for recovery only. I belive BCB and another boot count file I cannot recall..

I would like to reset theses files, if indeed this is the problem, and bring back my Nooks emcc normal boot. Being private files they do not seem to be accessible via normal ADB comands and this is where I start to get over my head.

This is no longer my primary tablet, this is my Android learning device and it continues to be fun. However this issue has me stymied.

So.., If anyone with a deeper understanding of this issue could help me, that would be nice.

Thanks.

12
[Nook Color General] fattire:
Try this from recovery... we'll use /data as a mount point but you'll really be mounting /rom (p2). First make sure that /data isn't aready mounted, then try this:

mount /dev/block/mmcblk0p2 /data

cd /data

ls

(make sure that this is in fact rom with the bcb and bootcnt so forth)

mv BootCnt BootCnt.bak

mv BCB BCB.bak

dd if=/dev/zero of=/data/BootCnt bs=1 count=4

dd if=/dev/zero of=/data/BCB bs=1 count=1088

reboot

Hope something like this works and doesn't make it worse, but maybe it's worth trying. If it doesn't work, you can always move the backup files back...
[Nook Color General] mateorod:
Okay, I have seen this sitting here and puzzled on it awhile. I have a couple links for you.

This first is someone who seems to have the same problem you do. They burst into internet-tears after everyone who was trying to help them got pissy and left. He was unfairly lashing out, but they were being kinda condescending.

http://forum.cyanogenmod.com/topic/...ry-boot-after-cm7-install-cant-get-to-the-os/

I only include it so you could see if the problems line up. This guy was about to give up, and this finally worked. There is a second pagebof posts, that is where I found what appears to be a solution..

The zip at this link (from XDA, of course. I don't know xawen but it is his/her work).

This will repair the B&N bootloader.

http://xdaforums.com/showthread.php?t=958748

I hope this works. I crow to my old lady about how this device is basically unbrickable, and it would dash my hopes to see your emmc unrecoverable...

Edit: Note the clockwork version! You may have to enter into your device through the sd card and first flash the correct CWM versiin
[Nook Color General] 12paq:
Thanks for your time!

ok when I:

C:\android-sdk-windows\platform-tools>adb shell

~ # mount /dev/block/mmcblk0p2 /data

mount /dev/block/mmcblk0p2 /data

~ # cd /data

cd /data

/data # ls

ls

BCB

/data #

ut oh.

No other files show up.

I am wondering since this is not a restore to stock adventure, which of those missing files do I really need?

EDIT:

I'm to going to back up & reset bcb file and see how far that gets me.

C:\android-sdk-windows\platform-tools>adb shell

~ # mount /dev/block/mmcblk0p2 /data

mount /dev/block/mmcblk0p2 /data

~ # cd /data

cd /data

/data # ls

ls

BCB

/data # mv BCB BCB.bak

mv BCB BCB.bak

/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088

dd if=/dev/zero of=/data/BCB bs=1 count=1088

1088+0 records in

1088+0 records out

1088 bytes (1.1KB) copied, 0.078582 seconds, 13.5KB/s

/data #
[Nook Color General] 12paq:
yeah, with backing up and resetting BCB as ^^ above, I still can only boot into recovery.

Edit:

I guess I need a Bootcnt file.
[Nook Color General] mateorod:
No dice on the recoveryfix zips? They are meant to repair issues where people cannot boot into recovery, but I believe it may replace the boot files you are looking for. Maybe not, but a couple threads I found had people with your exact problem, trying everything they could, and this turned out to work. I spent a little minute looking into it.

Edit: well, I downloaded and looked into thebzips, and it is the uboot.bin and the recImages which I guess you tried. If you know exact missing file (I located the mmcblkOp2 file, although it breaks down no further in root explorer) could i just pull it out of my device and email/pm it to you?
[Nook Color General] 12paq:
mateorod-

Yeah, thanks man. I did try all those links and zips before but, thanks for the effort.

I am actually very close to getting this done thru ADB. I have all the files needed. It's just not a simple push from ADB to get them there.

The good news is I am entrenched deep in new stuff and learning and having fun.

I'll keep you posted. Thanks again.
[Nook Color General] mateorod:
Yeah, I'm interested for sure. Good luck and tell us how you did it.
[Nook Color General] 12paq:
Fattire-

This what I achieved tonight:

~ # mount /dev/block/mmcblk0p2 /data

mount /dev/block/mmcblk0p2 /data

~ # cd /data

cd /data

/data # ls

ls

BCB BCB.bak BootCnt

/data # mv BootCnt BootCnt.bak

mv BootCnt BootCnt.bak

/data # dd if=/dev/zero of=/data/BootCnt bs=1 count=4

dd if=/dev/zero of=/data/BootCnt bs=1 count=4

4+0 records in

4+0 records out

4 bytes (4B) copied, 0.004242 seconds, 942B/s

/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088

dd if=/dev/zero of=/data/BCB bs=1 count=1088

1088+0 records in

1088+0 records out

1088 bytes (1.1KB) copied, 0.018737 seconds, 56.7KB/s

/data # reboot

reboot

reboot returned

/data # exit

exit

C:\android-sdk-windows\platform-tools>adb reboot

I still can't boot normaly from emcc, it roles right into CWR.

Any other ideas?

Thanks for your time!
[Nook Color General] 12paq:
ran everything again as seen here:

C:\android-sdk-windows\platform-tools>adb devices

List of devices attached

0000000000000000 recovery

C:\android-sdk-windows\platform-tools>adb shell

~ # mount /dev/block/mmcblk0p2 /data

mount /dev/block/mmcblk0p2 /data

~ # cd /data

cd /data

/data # ls

ls

BCB BCB.bak BootCnt BootCnt.bak tombstones

/data # dd if=/dev/zero of=/data/BootCnt bs=1 count=4

dd if=/dev/zero of=/data/BootCnt bs=1 count=4

4+0 records in

4+0 records out

4 bytes (4B) copied, 0.000702 seconds, 5.6KB/s

/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088

dd if=/dev/zero of=/data/BCB bs=1 count=1088

1088+0 records in

1088+0 records out

1088 bytes (1.1KB) copied, 0.016968 seconds, 62.6KB/s

/data # reboot

reboot

reboot returned

/data # exit

exit

C:\android-sdk-windows\platform-tools>adb reboot

I still cannot get the devices to boot into anything but recovery.

Any help would be greatly appreciated.
[Nook Color General] halrulez:
Ok so this same exact thing happened to me as well. What I did to fix it was make a bootable sd recovery then slapped cm7 on it. Doesn't matter what one. Slapped meaning the flashable zip, after the sd was made to be a bootable recovery. Then wend though an formated everything but the emmc and then installed cm7 and bam it worked again. No problems still.
[Nook Color General] halrulez:
This all happened fro.m some thing that went wrong during a cm9 install? That's what caused mine.
[Nook Color General] halrulez:
Pm me if you need further instruction
[Nook Color General] 12paq:
Thanks, but I am guessing you did not read my op, I have tried that multiple times and ways. But thanks anyway.
[Nook Color General] halrulez:
Sorry I forgot to not that I used TWRP2.0 to do all this. Cwm has never seemed to format anything correctly. So make it a bootable sd recovery of twrp I tried cwm and it didn't work.
[Nook Color General] 12paq:
Mmm.. well that's worth a try, at this point. I did use Neimath's experimental CWR that's more likely to not have problems with 2nd or Rom partition boot count files, but no go.

So, thanks. :)
[Nook Color General] 12paq:
Doh!

Double post.
[Nook Color General] halrulez:
I hope it works for you.
[Nook Color General] halrulez:
Any word on your nookie?
[Nook Color General] 12paq:
so to be clear, so no one will fubar their boot partition, when you say, "format everything but emcc" you meant everything but boot and emcc, right? ;)
[Nook Color General] mateorod:
I was wondering about that when I read the above as well. That is at the root of why I AK so confused about your problem. I don't know the solutions bybrote, but I knowbthat people come back from accidentally formatting boot. I have seen someone a couplenweeks ago successfully struggle through a corrupt ROM and an erased factory partition. There always seems to be a way.

Now all the stuff recommended by fattire is above my head and all that. I just know that these boot partitions and drivers are repairable and/or replaceable. I've kept looking around at this, but the cases I've found off of XDA, the posters advising the OP were as flummoxed as I was, and just kept frustrating the OP with repeated newbie advice. You were wise to so clearly state all your attempts at resolution.

So, what is am getting at here, after all that: I wouldn't format boot at first blush, but since that is where your problem lies, those files probably havento be overwritten or modified at some point, right?

To be clear, I am NOT recommending you just go blithely format boot. You seem like you are being considerate about your steps, but I don't want this to be construed as a vote. I don't know what to do.
[Nook Color General] halrulez:
I formated everything but my emmc
[Nook Color General] 12paq:
Yeah, I get it. There's no format boot option in Twrp.

Edit:

Well, I tried that and no go. But thanks for your efforts. :)
[Nook Color General] 12paq:
Yeah, as you can see in the op, I have successfully reformatted and rebuilt my boot partition multiple times from both flashable repair .zips and manually via ADB.

But thank you for your input. :)

**So I speculate the crux of the matter seems to be my 2nd "rom" partition that has private files for boot counts and records and some personal info like device serial# etc. Normal flashing of zips does not touch these files so the standard repair boot methods do not work.**

When I mount my 2nd partition to data and the command to see the contents of the partition, I only have these 3 files: BCB, BootCnt, and Tombstones.. I have followed fattires's suggestions on how to reset the counts but I have had no success.

So I believe I need a greater understanding of what these files do and what the Nook needs to boot normally.
[Nook Color General] 12paq:
Does anyone have any other ideas?
[Nook Color General] DizzyDen:
if you mount /dev/block/mmcblk0p3 (backup) does it still have rombackup.zip on it?

If it does, you can restore /dev/block/mmcblk0p2 (ROM) files from there.

If it doesn't, I have images of all the partitions, but some of the ROM files will have to be edited to match your device.