yashsingh1/xdaforums huggingface dataset:
[Milestone 2 Android Development] v8star_it:
my notification led is pwned and i didn't press vol down key at right moment: now i'm ok (i've flashed sucessfully standard theme zip). What is not ok is 3g data connection: try to change baseband (from standard HK) to 2.2.2 and 2.2 then to 222 again but data never comes up... (carrier 3 ita)

try to activate from notification toggle and system settings but i'm stuck :crying:

what can i do?

many thanks
[Milestone 2 Android Development] -Danik-:
Hi.

What are your country frequencies?

If you succeed on making calls then you may just have to reconfigure the AP.

:)
[Milestone 2 Android Development] v8star_it:
where no default dun profile selected: now i'm ok with 2.2.2 UK- DE. The phone became slugghish from this morning when i restore some apps with titanium(not able to answer a call). I wipe cache & dalvik from recovery and now seems fine.

Possible reason is flash the new kernel after rom?

BTW the rom is very reactive and game performance are very high compared with cm10/miui: now i can play with blood and glory without big lags :cowboy:

thanks
[Milestone 2 Android Development] -Danik-:
Of Course it does , that is the ROM intention <after all upgrades>

And yes , Flashing the Kernel after first boot with the ROM is suggested to avoid problems that may be.

:)
[Milestone 2 Android Development] Leandro Castro:
No boot after trying to flash StockPlus_r3_Jan_8 Kernel

Hi Daniel,

First of all thank you very much for your effort, I tried your ROM for a few days and it´s amazing.

So amazing now I regret for trying to flash the kernel... Should follow the ancient wisdom "If it´s not broke don´t fix it" :(

Anyway, this is what I did in short:

1- Root the phone like described here: http://xdaforums.com/showthread.php?t=1750277

2- Install CWM Rom manager, copy your latest rom (v2), reboot in recovery, install it, reboot in recovery again, wipe all, reboot

Spent a few days with it... really liked it

3- Installed RSD Lite 6.1.4 and flashed StockPlus_r3_Jan_8.sbf file. Now the phone does not turn on... No motorola logo, no blue light to show when enter the recovery mode, nothing. It´s still recognized by the computer so I can use RSD Lite to flash other stuff.

4- Tried to flash other of your Kernels, stock kernel, stock ROM, 70.13 bootloader... so far nothing worked.

I´ll paste here what RSD Lite shows me on the "Device Properties" window... It´s very weird and it may give you some clue:

IMEI/ESN/MEID: N / A

Technology: N / A

Software Version: N / A

Flex Version: N / A

Bootloader Version: v0x007013

DRM Version: N / A

AP Die ID: 1bb00003c5c35d010000d8ff0100

BP Die ID: 0000000000000000000000000000

AP Public ID: 38fc2e50d6c3af999c699472d2c291d4ca64ae85

BP Public ID: 0000000000000000000000000000000000000000

Do you have any ideas?

Thnaks in advance,

Leandro.
[Milestone 2 Android Development] -Danik-:
Hi.

Thanks for mentioning the APDID..after decryption it seems that you have BL 4 but it is not recognized as 4 though my script for CRC uncheck will not run and continue to boot normally..then..BOOM nothing happens , phone won't even log - on this case the EP runs in it a CRC check and gets a NULL , then the bootloader asks for the returned value from EP - ok , it's NULL , no boot.

Since I managed to put the checking after EP so the values of BL read by EP(3) and the true one (4) , not all the phones will be able to run it.

I'll try to get it working..

Should not be a problem , if you look on your info we can have 2 solutions possible :

- getting the script to increment by 1 the value to it so it won't be NULL - when NULL in your case comes after value mismatch of my integer that reads 28691 instead of 28692 (in Hex : 28691 will be 0x7013 and 28691 will be 0x7014..yes that's it I always said Motorola's locked bootloader wouldn't be that big problem..though downgrading the whole bootloader could be great but we'll do well even without it..)

- next solution is the easiest to do but will boot really slow by changing the code to convert every NULL in the loop to 0x7014 but it loop check for every byte exists - 2 bytes X 2 = like 4 times slower..on every boot..

Read carefully , I'll try to work on first solution of course

:)
[Milestone 2 Android Development] Leandro Castro:
No boot after trying to flash StockPlus_r3_Jan_8 Kernel

Dude, I feel ashamed to say i didn't understand most of what you said... I'm a noob :(

Anyway, I have no rush about it, as I do not use it for phone calls. I just wanted to make you aware of this potential problem.

Thanks for your time and for your prompt answer.
[Milestone 2 Android Development] scumie:
Same issue here, and I was discussing this with Danik yesterday. I'm also on BLv4 (personal argentina firmware R02). Can you confirm you latest stock firmware and company?

In my case, nothing worked either after the phone got stuck on recovery mode. The only thing that worked is to flash stock (personal R02, no other would work) and you have start all over again.

Also on a side note, if you flash kernel 7.12 after stock it does work (however 8.12 and 01.08 after that will result in the same so don't try them).
[Milestone 2 Android Development] -Danik-:
Hi :)

Read the my previous reply as I answered the guy the same.

I checked your problems .. I suggest you really read it..some mismatch between BL and EPROM.

Hope to get it fixed so everyone will be able to use new features <flashing the new kernel>.
[Milestone 2 Android Development] scumie:
Thanks Daniel.

Yes I read your post and understood the problem and possible solutions (I'll be waiting eagerly for the fix, let me know if I can help). I'm just trying to give Leonardo a tip and only thing that worked for me with what we have available: to flash stock and work over rooting and everything back (he can't flash any rom/kernel/fix as they won't work now after flashing 8.12 or 01.08 kernels). if I missed something let me know (I'll give it another read anyway).

By the way, there is no downgrade for BL4 (as I know of), so that's not an option. :(
[Milestone 2 Android Development] Leandro Castro:
No boot after trying to flash StockPlus_r3_Jan_8 Kernel

Hi,

I got the Roms i tried to flash after the incident, with no success, here: and-developers.com/sbf:milestone2

They are both on the "2.3.6 Service Version" section

One is Country=Brazil Provider=Tim Filename=M2L_U6_4.5.2_51-27_SIGNED_US1MILA2GBTIMBRB125LA001.0R_STABLE45LAMILETTIMBR_P009_A020_M001_HWp2a_Service1FF

Other is Country=Brazil Provider=Retail Filename=M2L_U6_4.5.2_51-27_SIGNED_US1MILA2GBRETBRB125LA001.0R_STABLE45LAMILETRETBR_P007_A019_M001_HWp2a_Service1FF

So you are suggesting me to try your "personal R02"... where did you get it?

Thanks and regards,

Leandro.
[Milestone 2 Android Development] scumie:
What is the firmware you had before you tried with these new ones?

If you are coming from Brazil firmware, then no, I don't suggest you go the same route as I did. The one I have is newer (R02) and only thing that changed is they fixed the exploit for rooting so superoneclick does NOT work. You have to use PreInstalameEsta which is different and more difficult (in a way).

Once you go to a R01 firmware there is no going back, and probably you won't be able to flash Brazil until they bring it up to the same level.
[Milestone 2 Android Development] Leandro Castro:
I´m not sure what it was :(

All I know it was a 2.3.6 from Brazil Provider=Vivo and I tested several methods to root it and the only one that worked was PreinstalameEsta.
[Milestone 2 Android Development] morcego.surf:
Hello Guys .

I am using the MS2Ginger 4 v2 and the custom kernel since the first released.

My previous installation was retail Brazil :

M2L_U6_4.5.2_51-27_SIGNED_US1MILA2GBRETBRB125LA001.0R_STABLE45LAMILETRETBR_P007_A019_M001_HWp2a_Service1FF.sbf

Then...

MS2Ginger 4 v2 , custom kernel 07.12 , 08.12 and 8.1 .

Everything is fine on my miles 2 .

Good luck in solving the issues.
[Milestone 2 Android Development] scumie:
If you ever had Vivo, then you are stuck with it as I am. That's a R01 firmware, same as Argentina Personal and Claro and you can't install any other lower version as Retail or TIM (the ones you mentioned), they won't work. The only brazilian firmware that's going to work with you now is Vivo. Try flashing it again over your "dead" ms2 and it should work, then it's back again with PreinstalameEsta. After that's rooted you can flash Danik's 7.12 Kernel (don't try any other for now until he can hack around the newer ones for BL4).

Let me know how it goes.
[Milestone 2 Android Development] -Danik-:
Hello Everybody.

After hard working ... I fixed it !!

Read Changes in OP and in ReadMe file.

Enjoy BL = 4 users :)

<Motorola - I got you one more time..>
[Milestone 2 Android Development] morcego.surf:
Is the new 11.1 kernel only the " HARDMOD Fix for People with Half BL = 4 " ?
[Milestone 2 Android Development] -Danik-:
Yes.

You don't need it :)
[Milestone 2 Android Development] scumie:
Thank you Daniel! testing right now.

So if I understood correctly it's flashing 7.12 and this one on top of it to have the latest right? No need to flash 8.12 or 8.1?
[Milestone 2 Android Development] axl63800:
excuse me but when i try to restore i have a md5 mismatch
[Milestone 2 Android Development] -Danik-:
Yes , Don't use 8.12 and 8.1 versions.

it goes : 7.12 > 11.1 mod > enjoy :)

You may have changed the ROM folder name inside clockworkmod\backup.

<if not , try using CWM versions of a different ROM.>
[Milestone 2 Android Development] -Danik-:
Hi Everybody.

Due to locked bootloader <it isn't really a problem!> we need to "booktype" the kernel info.

everybody flash the latest fix for BL = 4 , you can do it without any harm.

I attach some of my Arduino checks...look how it should be.

In the first picture you can see my checks on the "real" kernel info and the "fake" info which is needed to be in order to boot with locked BL.

COM7 stands for the flasher cables during a connection and USBPORT is just usb while the device is ON. <both ports COM and USB running together and this is the real info you should have seen in the Settings > About.

In the second picture I just compared the bootloaders of the recent fix

from now on , anyone who flashed the fix will be able to get semi tricked the bootloader so that it shows false values for the bootloader itself but the true value is lower.

so,

binary values on 0x16 is the real one.. 70.13

binary values on 0x0AA3B3A is the fake one which lets the phone read 70.14 .

This gives us the option to get more from the kernel without checks.

In the second picture it says that TARGET WILL NOT RUN , but it will , it doesn't know that the values should not be equal.. :)

:)
[Milestone 2 Android Development] gambiarraweb1:
the size of the kernel, correct?

http://www.mediafire.com/?ld9a1var5leuzot

StockPlus_r3_HARDMOD.7z

61.33 KB?

For correct operation I use these files correct?

StockPlus_r3_HARDMOD.7z

+

MS2G4HMv2_01.01.7z

? Excuse my ignorance, because I got confused with some links in the first post!

I'm leaving the CM10, I use MS2Ginger: D
[Milestone 2 Android Development] -Danik-:
Yes.

But before the HARDMOD , flash 7.12 kernel and reboot.

Enjoy :)
[Milestone 2 Android Development] morcego.surf:
I have 8.1 kernel...

...only 7.12 kernel needs the new hardmod?

Enviado de meu A953 usando o Tapatalk 2
[Milestone 2 Android Development] -Danik-:
Yes , that's fine.
[Milestone 2 Android Development] fedee13:
I'm sorry, but it isn't clear for me....If I flash 8.1 version of the kernel, do I need to flash the fix 14.1 after? Thanks! :)
[Milestone 2 Android Development] -Danik-:
No , if you got 8.1 version to work then no.

but the fix is not problematic anymore and it will help in future , but you don't need to flash it.
[Milestone 2 Android Development] fedee13:
I tried to flash the kernel using RSD (version 5.7), but here's the problem: RSD tells me that the process is finished but the phone stays in a black screen, it doesn't reboot, I can't turn it on or even charge it. I had to flash a stock ROM to save it.... :(
[Milestone 2 Android Development] gambiarraweb1:
I did the whole procedure more my Milestone 2 now will not turn on at all or loads!

I do HELP!

already plugged in the USB, but only the led, white, indicating the battery, plus nothing appears on the screen!

has some convenience keys for shortcuts, you can use?

I already know some more infirm is working, thanks!

HELPPPP ...!
[Milestone 2 Android Development] fedee13:
What I did was: take off the battery, put it on again, I open RSD, load the stock sbf and plug the usb to the phone and PC, RSD recognized the phone and flashed the original stock firmware
[Milestone 2 Android Development] gambiarraweb1:
I've solved the problem, I'm now doing update!

I had to charge the battery on a universal charger, so I could connect the phone, oh the RSD, acknowledged the same!

Now I will do update: d
[Milestone 2 Android Development] -Danik-:
Hi.

RSD is tricked so most of the times you try - it will flash.

IF it still messes then flash 7.12 only.
[Milestone 2 Android Development] axl63800:
excuse me but i'm a little lost.

what are the benefits and the risks of using the custom kernel please.

i use my mm2 for a little time and i used many roms (cm7 cm10 miui and now ms2ginger) and the kernel change is new for me.

my bl is 7013 so i suppose the is bl3.

thanks for your help.
[Milestone 2 Android Development] -Danik-:
Hi :)

It's not a problem..

It is really easy to do it and you can't get lost.

As for the Advantages : they're all detailed in the OP , Disadvantages : none.

<Everything is stable as your device will boot - from there it is fine.>
[Milestone 2 Android Development] fedee13:
What version of RSD do you use to flash the kernel?
[Milestone 2 Android Development] gambiarraweb1:
Sorry, but my prolema actually not been resolved, I think the problem is even bigger!

My ms2. nothing appears on the screen, I have done flash (official 2.3.6, 2.3.6 retail) and nothing! using rsd 4.9! have any recommended version to do this?

I also noticed that the only time something appears on the screen when he is doing flash update!

'Flash update'

'progress'

he's a 'Finish' more does not start nothing, not motorola logo appears!

helppp!:crying:

# # # # I have to charge the battery in an external charger, not charging for the taking!

Novo! Clique nas palavras acima para editar e ver traduções alternativas. Dispensar
[Milestone 2 Android Development] fedee13:
Try to use RSD 5.6, that's the one I use and I had no problems so far.
[Milestone 2 Android Development] gambiarraweb1:
flash'm doing right now, so I'll post the finished result!

has no other rom I can do flash!

at the moment I'm trying to flash the rom 2.2 FROYO,

. but I have here with me, the official 2.3.6 rom, what do you recommend?

thank you!
[Milestone 2 Android Development] -Danik-:
Froyo based will not boot without BL = 3 Chinese Kernel <check the thread for "downgrade" GB to Froyo> but that's not the point ,use GB stock ROM.

Use VIVO brasil r1 and then flash 7.12.

Don't get scared from not booting it is due to incompatibility for Kernel and ROM , but the kernel on Motorola also flashes BL sectors..
[Milestone 2 Android Development] gambiarraweb1:
ok, I ask that you please post the links, and step by step I should go,!

I am very angry with this error!

I would like the links or the topic because I do not know what is it 7:12??

and what is the link R1 VIVO Brazil?

thank you!
[Milestone 2 Android Development] -Danik-:
No you can't destroy your phone at once , in addition - you have an external charger - that's good for some cases

so,

7.12 is the first release of the custom kernel I published - download it from first page.

The stock brasil sbf is :

M2L_U6_4.5.2_51-27_SIGNED_US1MILA2GBRETBRB125LA001.0R_STABLE45LAMILETRETBR_P007_A019_M001_HWp2a_Service1FF

from here <open free user if asked> :

http://www.4shared.com/zip/h58gYrZg/M2L_U6_452_51-27_SIGNED_US1MIL.htm
[Milestone 2 Android Development] fedee13:
What I would do is flash the firmware you were using before installing this ROM (if it bootloops you must wipe data and cache using the stock recovery). Root it and install CWM Recovery and the flash this ROM. If you want then you can flash the kernel.
[Milestone 2 Android Development] gambiarraweb1:
I just do flash, this was pray>

FLASH, ROM RETAIL 1 TIM BRAZIL! RSD => FINISH OK!

FLASH, FLASH 2, 7.12 STOCK RSD => FINISH OK!

but does not start the phone, it gets black screen and nothing appears!

Download the ROM awaiting R1 BRAZIL VIVO, to make new flash!

ok, no more shortcuts works, (X + POWER) (VOL -, + CAMERA + POWER) nothing works

the phone just starts to flash mode!

more nothing appears on the screen or print version of my bootloader!

That is strange!
[Milestone 2 Android Development] fedee13:
If it starts in flash mode, flash R1 Vivo and then tell us what happen....and I think that you have to root it with preinstalameesta (it's in this forum or in a spanish forum)
[Milestone 2 Android Development] gambiarraweb1:
good, I just do flash, VIVO r1, the rsd asked to manually restart, I waited and nothing, then restarted the same way straight into flash mode!

7:12 then passed the flash! and continues the same way!

I do not know what to do guys!

I believe it has to get a sbf, a different version whatever, other suggestions??

---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------

some of you can use the TEAMVIEWER, and make remote access to my machine, I allow a good one!

please do it!

ID: 404 785 113

PASSWORD: nkw386

waiting!
[Milestone 2 Android Development] -Danik-:
unplug battery and hold X - then replug battery still holding X , you should get into stock recovery to wipe data and cache partitions.

if it still gets into flashing mode downgrade using the Chinese kernel and flash MIUI GB and try Z+Power to boot MIUI on safe mode. < but try the battery plug trick before>
[Milestone 2 Android Development] gambiarraweb1:
did not work!
[Milestone 2 Android Development] fedee13:
Which was the ROM you were using before this one?
[Milestone 2 Android Development] gambiarraweb1:
for anyone remote access, add a login to get easier,

Login: gambiarraweb1

password:

add me will get easier! thank you!

---------- Post added at 04:47 PM ---------- Previous post was at 04:46 PM ----------

I was using the 2.3.7 rom CM7!

so I decided to use the Stable MS2Ginger 4 2!

I made one more error in CWM, then started giving this problem!

---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------

someone to help me?

the TEAMVIEWER, is there anyone who can access to, and tell me if I'm doing right! thank you!

Add on Skype: gambiarraweb1
[Milestone 2 Android Development] -Danik-:
Hi.

Thank you for the info.

You are on BL =4 so that you can't apply any Custom ROMs .

My ROM works with BL = 4 using init code but you can't boot to logo so that's a problem using it.

If you succeed booting any ROM , flash the HARDMOD fix afterwards.
[Milestone 2 Android Development] fedee13:
I think TIM and RETAIL are BL=3, and VIVO is BL=4 if I'am not mistaken. And with BL=4 you can apply Custom ROMs, I had Movistar Latin America (2.3.6) which is BL=4 and rooted it with "preinstalameesta" and I can flash custom ROMs. :)
[Milestone 2 Android Development] scumie:
Not really. Technically you cannot flash ROMS (through RSD Lite), other than the ones with same BL or newer. You can however restore backups through CWM, posted in the milestone2 forum, just not any kernels.

I had the same issue, phone booting into blank screen after flashing 8.12 kernel. It's actually the phone booting into Bootloader mode (programming) so you can flash it but only with stock (nothing else will work).

To check you can connect the phone to your computer with USB and open RSD Lite. You'll see that it says "connected..." even the screen is completely black.

If this happened you need to reflash the kernel, the only way it worked for me is to flash stock again (has to be the same release you had before or newer), otherwise it will stay locked. Maybe we can prepare a minimal firmware to fix the boot lock, but I'm not been on that route yet.

So if you got to this point:

1) identify the stock rom you had before this (it is 2.3.6 service, but you have to say exactly what version, TIM, VIVO, Movistar, Personal, all have different versions).

2) After you identify the version copy it here so we know your exact steps.

You can find all the possible stock firmwares here: http://and-developers.com/sbf:milestone2

A word of caution: Don't try flashing every firmware, if you flash something newer than you had, then you will be locked into it as there is no way to downgrade the firmware.

In other words:

if you had 2.3.6 Service Version you have 3 possibilities:

1) Brazil TIM and Retail have BL 70.13 version 3, can be rooted with superoneclick

2) Argentina Personal and Claro have 70.13 version 4 (R01), had fix the rooting, so it can only be rooted so far with PreInstalameEsta

3) Brazil Vivo has 70.13 version 5 (R02), mixed results, some reported to be able to root with PreInstalameEsta, some others just can't but should be fixable.

If you tried one version on the 2nd group, you can't go back to 1. Same if you tried on the 3rd, you can't go back to 2 neither 1.

For 70.13 version 3 or earlier you can use any kernel (altough it's not necessary to use this ROM).

For 70.13 version 4 or newer you either don't flash any new kernels from this post and live with it, or if you want the custom kernel flash ONLY 7.12, reboot, wipe cache, check everything working, and later flash HARDMOD FIX 14.1 (StockPlus_r3_HARDMOD.7z). You need to flash BOTH to have a stable system and fast system, although 7.12 will work.

All links are in the first post on this thread.

let me know if it helped.
[Milestone 2 Android Development] infiniteproject:
If I'm running tezet's cm10, it's ok just to restore this rom as a nandroid backup and do a full wipe?

Inviato dal mio A953 con Tapatalk 2
[Milestone 2 Android Development] -Danik-:
That's exactly.

EDIT:

After lots of checks for UVP these are the new summaries:

People who got their phone with BL = 3 or 4 will be able to OC better due to new HW.

So as said really depends on piece..

Arduino Factory tests:

BL = 4 <CG31.smg was 4 > gives 1350/70

BL = 3 gives max 1300/70 if you want 1350 you need 76 that's high and is not recommended <1350/76>

BL = 1/2 fails on 1350 even on high VSEL , however I've tested an MS2 that came with BL = 1 for 1350 with custom kernel it worked like a charm.

Now I'm working on a new stuff for the kernel.

I managed to know where the 1350mhz cap came from.

while looking through OMAP3 codes I found the following line :

core_mret_vl <-this is an address which leads to a Hex value of 546 , yes it 1350 in decimal!

so of course..I put something funny like 1869F <99999> and compiled.

flashed it using RSD ... no success ... locked bootloader led me to get a bootlogo freeze , yes..I can't flash it directly.

flashed it with Arduino cables directly to chip on kernel section.

Phone recently after all booted up!!!

Stable for now are above 1.4Ghz..stupid code limitation , benchmarked it and flawlessly worked.

Now for ULV ... changing the VSEL multiplier in the past still gives great scores : 150/4

So about that...looked over the internet for devices alike..Defy , Droid 2 , R2D2 , Droid X - no one with no rom or kernel could make the phone not freeze with 150mhz on vsel1.

this means double the already doubled hold time :)

the 12C hex code meant 300 , that's the minimum the core can work.

now runs smoothly on 150/4 , working on bringing it into an SBF.

What I say is that it is ok to "lock" the core to prevent any damages , they did lot of tests .. 300 for minimum and 1350 for max were their conclusions , OK.

However why not squeeze out EVERYTHING this core can give us?!

:)