need help to root rogers dream, please - G1 Q&A, Help & Troubleshooting
Hi,
I got a rogers dream and i tried several ways to root it, but i cannot so far:
1. follow wiki guide, but i cannot got into recovery mode by holding Home key while power on the phone, it hangs on at rogers screen.
2. try goldcard. cannot update, showing Model ID incorrect, failed. i am not sure it is because my card or something else.
3. i tried flashrc(?), it failed updating img.
4. i tried telnet. remote refused.
if you succeed rooting a rogers dream 1.33.0010, please tell me how.
thanks,
Follow this guide
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
thanks for your swift reply. that is the wiki i followed, but when i tried to install DangerSPL, i cannot go into recovery by holding HOME while power on the phone. it hangs at Rogers screen.
i checked radio and it is correct version. should i flash radio still?
any suggestion?
thanks,
Well you certainly need recovery..
The original steps for that process are here: http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
(as cm wiki sometimes is organized more for maintenance by people who don't use a rogers dream than being user friendly.. and they removed the link to the xda thread with all the q&a on the process)
the error however is either you are flashing the wrong recovery; or the flash of the recovery failed. make sure your flashing one of the '-R' ra-recoverys.
best to take it from the top.. if recovery still fails some people have found re-flashing the e911 rom and trying again helped (see 'Returning to Stock Rogers' on the xda wiki page)
still i cannot go into recovery.
can you tell me how long i have to hold HOME key in order to boot into recovery?
i push HOME and POWER together, and then i can only see ROGERS. it probably stays there forever.
one thing i cannot follow wiki before is LONG HOLD POWER TO TURN OFF PHONE.
thanks,
JaydenCanada said:
still i cannot go into recovery.
can you tell me how long i have to hold HOME key in order to boot into recovery?
i push HOME and POWER together, and then i can only see ROGERS. it probably stays there forever.
one thing i cannot follow wiki before is LONG HOLD POWER TO TURN OFF PHONE.
thanks,
Click to expand...
Click to collapse
If you can boot normally but not recovery (ie you are stuck on the rogers logo and it never changes when you boot holding down home) their is a problem with the recovery you flashed. (We will not move on from this statement unless we find why there is an issue with the recovery or that the incorrect recovery was flashed)
As for long press power or end on the phone that is how you get the shutdown menu in the rogers and other roms.. so I'm not sure what is wrong if that is failing outside user error.
I need you to do the following if you want help:
1) flash (as per the restore stock rogers rom on the xda wiki) the e911 patched rogers nbh file
2) making sure you document every command you run and saving the console output to a text file run the e911 rooting process as per xda wiki
3) if you can't boot recovery post said output here.. however first check it with the sample output
thanks for your patience.
when i say long press power button cannot power off the phone, i mean i cannot turn off the phone by only press it, i have to go through two more windows, one is power down options and another is confirmation.
i will follow the instructions again to see what happen. do you suggest any recovery image? or something else i can do ?
thanks
wait what. power down options?
I don't remember power down options on the stock rom
Sleeepy2 said:
wait what. power down options?
I don't remember power down options on the stock rom
Click to expand...
Click to collapse
Certainly had power off and airplane mode.. probably reboot as well but I forget.
JaydenCanada said:
i will follow the instructions again to see what happen. do you suggest any recovery image? or something else i can do ?
thanks
Click to expand...
Click to collapse
The recovery image with the md5 sum in the instructions is what most people use.
after i run exploid, i can see three files: hotplug, loading, and sim_lock_status were generated, as well rootshell in /system/bin.
i tried to go into recovery, but i cannot, because it hangs on ROGERS screen forever. i have to pull battery out to reboot. then i checked /sqlite_stmt_journals, exploid, loading, hotplug and sim_lock_status were all gone. there were two files there: screen_lock_status and pattern_lock_status.
i don't have sim card in the phone, can it cause the problem?
BTW: i even followed "how to root Droid" to install exploid, using chmod 755 and turn on/off wifi after running exploid.
any suggestion? thanks,
Please don't follow the droidx instructions, and follow the Rogers root instructions.. the root exploit is the same but the hardware and goal is different.
many others hard successfully rooted and some q/a on the process is in this thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638
You have not given the console output to your attempt so as I said earlier I have no additional recommendations than what I have already provided as we do not know what recovery you flashed.
i am very new to this thing. does "console out" mean the screen captures? i will supply tomorrow.
i had tried different recovery image, the results are same. could you send me a known working image for rogers dream?
[email protected]
thanks
please kindly have a look. thanks.
the output shows in the following:
D:\MyDocs\JD\android\adb_1.0.26>adb push spl-signed.zip /sdcard/1_33_2005_spl.zi
p
452 KB/s (0 bytes in 188246.000s)
D:\MyDocs\JD\android\adb_1.0.26>adb push recovery-RA-dream-v1.7.0R-cyan.img /dat
a/local
1159 KB/s (0 bytes in 4712448.003s)
D:\MyDocs\JD\android\adb_1.0.26>adb push exploid /sqlite_stmt_journals
372 KB/s (0 bytes in 11917.000s)
D:\MyDocs\JD\android\adb_1.0.26>adb shell chmod 777 /sqlite_stmt_journals/exploi
d
D:\MyDocs\JD\android\adb_1.0.26>adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
D:\MyDocs\JD\android\adb_1.0.26>adb shell
$ rootshell
rootshell
Password (echoed):secretlol
secretlol
# chmod 666 /dev/mtd/mtd1
chmod 666 /dev/mtd/mtd1
# exit
exit
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
$ exit
exit
D:\MyDocs\JD\android\adb_1.0.26>
this is files under /dev/mtd:
does it have something to do with the "skipping writing"?
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
JaydenCanada said:
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: write error at 0x00120000 (I/O error)
mtd: verification error at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
Click to expand...
Click to collapse
See now we know the error .. well that there was an error anyway.
I'm used to a memory error not the io error. Usually when flash_image fails it skips the block and writes the data in the next block.. if all is well the block is flagged bad and the spl booting the recovery does the same.. seems not all is well in your case.
Before going too crazy. . Lets see if we can make it work.
1) restore the rogers nbh
2) try to boot recovery (hopefully) you will enter stock recovery with the /!\ image.. alt+L will show a short list of options, you may reboot to the rogers rom.. if it fails to boot make a note to inform me in your next reply and reboot into the rogers Tom
3) try the root process again with the 1.6.2R recovery
Amon_RA said:
recovery-RA-dream-v1.6.2R.img (Click here to download from a Mirror) - MD5Sum: b9db12cdd9a1e42b3187425e89c5fbe5
Click to expand...
Click to collapse
3b) if it works you can use fastboot to flash 1.7.0 after installing the 1.33.2005 spl.. I think 1.7.0 will work then..
Report back if it works great. . If not things are a bit more complex. . Particular if the stock recovery also fails.
when you said "rogers nbh", do you mean Bootscreen.nbh?
can i use this: http://forum.xda-developers.com/showthread.php?t=341753
sorry, i am new to this.
really appreciate
JaydenCanada said:
when you said "rogers nbh", do you mean Bootscreen.nbh?
can i use this: http://forum.xda-developers.com/showthread.php?t=341753
sorry, i am new to this.
really appreciate
Click to expand...
Click to collapse
No I mean this: http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
i restore rogers nbh. and i can go into recovery mode. after press alt-L, it shows:
android system recovery utility
there are three options:
reboot system now
apply sdcard:update.zip
wipe date/factory reset
but on the bottom there is warning:
E:Can't open /cache/recovery/command
what i supposed to do next?
thanks,
i tried to go through the instruction. but rootshell won't be generated after run exploid. i can see exploid had run, but in /system/bin there is no rootshell.
i tried
IMMEDIATELY after executing the next step, toggle wifi or bluetooth off and back on
Run "./exploid" and follow directions on screen. Once this completes you'll be back at a shell prompt.
Click to expand...
Click to collapse
rootshell generated. but still i have this:
$ flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
mtd: erase failure at 0x00120000 (I/O error)
mtd: erase failure at 0x00120000 (I/O error)
mtd: skipping write block at 0x00120000
it seemed there is something preventing writing to that block.
thanks
Related
Help! Screwed up recovery somehow.
OK, I have been running recovery-RA-1.5.2 for some time now and I'm using Fresh 1.1. I was trying to update my recovery to 1.6.2 and when I went to flash the recovery it gave me a bunch of errors and now I can't get into recovery at all. My phone boots fine into fresh but I get nothing when I try to boot into recovery either using home+power or adb. I have tried re-flashing the recovery and I even went back and followed the rooting guide from the beginning because I know that worked before. Nothing helped, I'm still getting the read errors. Going back to the old recovery is not working either, although it does show only 1 error instead of the many that 1.6.2 shows. Any ideas? Here are the errors I got: # flash_image recovery recovery-RA-heroc-v1.6.2-blue.img flash_image recovery recovery-RA-heroc-v1.6.2-blue.img mtd: read error at 0x00000000 (Out of memory) mtd: read error at 0x00020000 (Out of memory) mtd: read error at 0x00040000 (Out of memory) mtd: read error at 0x00060000 (Out of memory) mtd: read error at 0x00080000 (Out of memory) mtd: read error at 0x000a0000 (Out of memory) mtd: read error at 0x000c0000 (Out of memory) mtd: read error at 0x000e0000 (Out of memory) mtd: read error at 0x00100000 (Out of memory) mtd: read error at 0x00120000 (Out of memory) mtd: read error at 0x00140000 (Out of memory) mtd: read error at 0x00160000 (Out of memory) mtd: read error at 0x00180000 (Out of memory) mtd: read error at 0x001a0000 (Out of memory) mtd: read error at 0x001c0000 (Out of memory) mtd: read error at 0x001e0000 (Out of memory) mtd: read error at 0x00200000 (Out of memory) mtd: read error at 0x00220000 (Out of memory) mtd: read error at 0x00240000 (Out of memory) mtd: read error at 0x00260000 (Out of memory) mtd: read error at 0x00280000 (Out of memory) mtd: read error at 0x002a0000 (Out of memory) mtd: read error at 0x002c0000 (Out of memory) mtd: read error at 0x002e0000 (Out of memory) mtd: read error at 0x00300000 (Out of memory) mtd: read error at 0x00320000 (Out of memory) mtd: read error at 0x00340000 (Out of memory) mtd: read error at 0x00360000 (Out of memory) mtd: read error at 0x00380000 (Out of memory) mtd: read error at 0x003a0000 (Out of memory) mtd: read error at 0x003c0000 (Out of memory) mtd: read error at 0x003e0000 (Out of memory) mtd: read error at 0x00400000 (Out of memory) mtd: read error at 0x00420000 (Out of memory) mtd: read error at 0x00440000 (Out of memory) mtd: read error at 0x00460000 (Out of memory) mtd: read error at 0x00480000 (Out of memory) mtd: read error at 0x004a0000 (Out of memory) mtd: read error at 0x004c0000 (Out of memory) mtd: read error at 0x004e0000 (Out of memory) mtd: write error at 0x00000000 (Out of memory) mtd: re-read error at 0x00000000 (Out of memory) mtd: write error at 0x00000000 (Out of memory) mtd: re-read error at 0x00000000 (Out of memory) mtd: skipping write block at 0x00000000 mtd: write error at 0x00020000 (Out of memory) mtd: re-read error at 0x00020000 (Out of memory) mtd: write error at 0x00020000 (Out of memory) mtd: re-read error at 0x00020000 (Out of memory) mtd: skipping write block at 0x00020000 mtd: write error at 0x00040000 (Out of memory) mtd: re-read error at 0x00040000 (Out of memory) mtd: write error at 0x00040000 (Out of memory) mtd: re-read error at 0x00040000 (Out of memory) mtd: skipping write block at 0x00040000 mtd: write error at 0x00060000 (Out of memory) mtd: re-read error at 0x00060000 (Out of memory) mtd: write error at 0x00060000 (Out of memory) mtd: re-read error at 0x00060000 (Out of memory) mtd: skipping write block at 0x00060000 mtd: write error at 0x00080000 (Out of memory) mtd: re-read error at 0x00080000 (Out of memory) mtd: write error at 0x00080000 (Out of memory) mtd: re-read error at 0x00080000 (Out of memory) mtd: skipping write block at 0x00080000 mtd: write error at 0x000a0000 (Out of memory) mtd: re-read error at 0x000a0000 (Out of memory) mtd: write error at 0x000a0000 (Out of memory) mtd: re-read error at 0x000a0000 (Out of memory) mtd: skipping write block at 0x000a0000 mtd: write error at 0x000c0000 (Out of memory) mtd: re-read error at 0x000c0000 (Out of memory) mtd: write error at 0x000c0000 (Out of memory)
I remember when I first loaded the recovery image a long time ago that I got tons of errors, but the instructions said to ignore them. I know, I am no help on this one. there is always RUU, root, flash new image, load nandroid backup.
nothing is wrong. reboot and try again. Every now and then you get that error when flashing a recovery. hope you didn't wipe and RUU already.
Had the same issue as above, but mine wouldn't even get past the "htc" screen. Had to pull the battery, do an RUU then re-root using the 1.6.2.img my advice would be to RUU and go back to "real" stock, then root again using the updated .img then load up your ROM again.
heck no DO NOT RUU as this WILL brick your phone. I had the same issue and tried to RUU. Your phone will be bricked. Just looks like you're going to be stuck using that rom for the rest of your phone life... You can take the risk if you want but don't say I didn't warn you. ~Danny
Bielinsk said: there is always RUU, root, flash new image, load nandroid backup. Click to expand... Click to collapse +1 10char
he can't even root, flash new image, or even nandroid as he is only able to turn on his phone and it goes straight to the actual android os .. it does not allow him to goto the ra. Like I said I had to return my phone because I tried RUU after this and it bricked. ~Danny
This happened to me today also. I downloaded better terminal and installed old recovery menu through terminal. It worked perfectly.
Try this: adb shell reboot oem-78 Once the phone shows the HTC logo try this: fastboot devices Make sure your device is listed, then flash the recovery: fastboot flash recovery recovery.img recovery.img should be the latest recovery image.
i got this message a few times but there was nothing wrong with my phone. what i did that i know fixes the problem is this: download a task killer of some sort and kill ALL APPS. as in, ALL currently running apps. try flashing it again. it should work.
justinisyoung said: i got this message a few times but there was nothing wrong with my phone. what i did that i know fixes the problem is this: download a task killer of some sort and kill ALL APPS. as in, ALL currently running apps. try flashing it again. it should work. Click to expand... Click to collapse That's why you should reboot into oem-78 and use fastboot, so nothing else is running
justinisyoung said: i got this message a few times but there was nothing wrong with my phone. what i did that i know fixes the problem is this: download a task killer of some sort and kill ALL APPS. as in, ALL currently running apps. try flashing it again. it should work. Click to expand... Click to collapse EDIT: THAT worked with the old 1.5.2 recovery!!!! Thank you so much!!! I don't know why my phone hated the 1.6.2 recovery. Maybe it just didn't want to be blue.
richse said: This seemed to almost work. The flash finished without any errors but then when I try to boot into recovery it just sits on the HTC screen forever I tried doing the command "adb shell reboot oem-78" and it just returned a "1" and the phone didn't reboot. Any idea? Click to expand... Click to collapse try this Code: adb shell reboot recovery try it without combining it all into one line, like adb shell reboot recovery. i found that that doesn't always work. so just separate it into two lines
justinisyoung said: try this Code: adb shell reboot recovery try it without combining it all into one line, like adb shell reboot recovery. i found that that doesn't always work. so just separate it into two lines Click to expand... Click to collapse It's back to v1.5.2 with the fix using the task manager. Just gonna have to figure out why 1.6.2 is failing now. Thanks!
I got 1.6.2 working using the one with out a color change. Maybe I just downloaded a bad copy of the blue one from the start. I guess this is how we learn. Thanks again for all the help guys!
i had this same issue, exactly... i did the fastboot flash and now im rocking the blue carebear...
Has anyone tried flashing with flashrec when it fails, a la the original recovery loading?
I got those errors on my first attempt at flashing the 1.6.2 recovery image so I just rebooted then used adb and reflashed the 1.5.2 recovery image, rebooted into recovery just fine and then when I was at the recovery screen I followed these instructions: make sure the recovery image is already on your sd card. Code: Connect your Hero via usb to your pc/mac/... (while at the recovery screen) adb shell $su (not required if you have root already) #mount -a (I got an error on this so just ignored it) #flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img everything works great now
navalynt said: Try this: adb shell reboot oem-78 Once the phone shows the HTC logo try this: fastboot devices Make sure your device is listed, then flash the recovery: fastboot flash recovery recovery.img recovery.img should be the latest recovery image. Click to expand... Click to collapse I'm new to this "forum" business, so I don't know how to do this officially... but you, sir, have my thanks. this information was solid. out of curiosity, how'd you know that special mode to tell fastboot to load up?? as a developer I'm always interested in how people find information like this!
If you can Turn on your phone Normally, just Boot your phone... Then once its Turned on, Install Rom Manager and Flash a Recovery through that app! Then at the Bottom of the Rom Manager app you can Select Flash a Alternate Recovery! That should Switch your Recovery back to Amon_RA! But if it Doesn't... You'll still be back up and Running with a Working Recovery! GoodLuck!
Technical Rooting Issue
Trying to Root my first G1. Having some wierd issues. Been searching the net for 2 days with no working solution. Successfully downgraded to RC29, it says so in the settings. Then working with freshly FAT32 formatted SDCARDs (of sizes 4gb, 1gb and 1/2gb), I attempted these two methods: Method 1: Clockwork's Telnet installed From home screen i punch in <enter><enter>telnetd<enter> Launch Telnet, connect to localhost:23 Telnet displays: ??[]??[]?? ??[]?? # From there I type (with no errors): mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system ## is now displayed. I CD into sdcard, LS the contents to confirm I'm there. Seems normal. then... ## flash_image recovery cm-recovery-1.4.img which returns this: mtd: erase failure at 0x00000000 (I/O error) mtd: erase failure at 0x00000000 (I/O error) mtd: skipping write block at 0x00000000 <-----pauses here for a second, then again... mtd: erase failure at 0x00000000 (I/O error) mtd: erase failure at 0x00000000 (I/O error) mtd: skipping write block at 0x00000000 ## Method 2: Recovery Flasher 1.1.3 installed (Previous versions of this APK come up as unsuccessful installations) Note, the "Download Recovery Image" button is grayed from the begining. I type the path/name of the recovery image on the sdcard (Tried both CM's image and RA's image) The button changes from "Download Recovery Image" to "Flash Recovery Image" as soon as I finish typing the path. However... The button remains gray and disabled. No explanation is given. Also as a side note (in case it is relevant), when I hit Backup Recovery Image I get "working do not interrupt", then "Backup FAILED: Image is invalid. This is all going a little outta my league and is getting real frustrating haha. Any help is reeaaally appreciated.
Bump. I can't be the only one with this problem, anyone?
Don't use the mount command when you telnet in. I haven't seen that on a rooting guide before, and it's definitely not part of Cyanogen's instructions. As soon as you've opened the telnet connection, cd into the sdcard and run the flash_image command. There's a link to Cyanogen's installation instructions in his ROM thread. Everything is explicitly spelled out, and easy to follow.
Boring Error No Recovery Cant Root
ok guys i am not a noob i made rooting etc lots of times. now i have a g1 with no recovery menu. when i press home + back it goes tri-color screen i tried to downgrade and root. when i write â—¦flash_image recovery recovery.img command it has an error like : mtd erase failure at 0x00020000 (I/O error) i tried flashrec it has " backup failed: could not run command" error. what should i do now ? how can i root this ?
[Q] Flash Image recovery help
Okay, i did try and search this but seems like nobody asked or its buried under a lot of threads. I thought I saw somebody how to fix it also but cant find it. Anyways, im trying to root my phone but i get after the unrevoked part where i type in: # Flash_image recovery /sdcard/recovery.img I typed it in right and i get a lot of out of memory. Any help from this point? Thx
to be more specific I get this error after typing in # Flash_image recovery /sdcard/recovery.img then i get this mtd: read error at 0x00000000 (out of memory) it repeats it and the 0x00000000 changes to different numbers and letters.
Nvm i restarted my phone then tried again and it fixed the prob.
Need Help Flashing Radio update.
hello, i have a rooted G1 with stock bootloader 0.95.0000, the radio is 1.22.12.29, upgraded to CM 4.2.15.1 DRC83 with amon RA 1.7 no problems downgrading or upgrading to CM4, everything to this point works fine. i tried upgrading the radio after rooting and installing recovery but it didn't go through. i have also tried to install HardSPL and that didnt go through either. Any advice as to why my device will not update radio or SPL?
How did you upgrade the radio and how exactly did it fail?
i tried to upgrade through the recovery. same with HardSPL. it says installing, reboot to complete and it just never actually updates in the system, when i check in the about section same radio, when i boot into bootloader, same old stuff. it gives me some error that says "E: Cant Read MISC" which i have found no useful information about because no one knows what it means. i dont see how that would stop me from updating something, i mean i can fully downgrade/upgrade with no problem its just the Radio and SPL that it will not upgrade.
It means it can't read and probably can't write the misc petition.. If you are in a custom recovery run 'adb shell dump_image misc /tmp/misc.img' then 'adb pull /tmp/misc.img misc.img' Then post your misc.img somewhere if its larger than 0 bytes.. else just tell me its zero bytes.
this is what i get after 'adb shell dump_image misc /tmp/misc.img' the second command you gave gives me a misc.img in my tools folder and it is 0 bytes mtd: ECC errors <0 soft, 1 hard> at 0x00000000 mtd: ECC errors <0 soft, 1 hard> at 0x00020000
hubble99 said: this is what i get after 'adb shell dump_image misc /tmp/misc.img' the second command you gave gives me a misc.img in my tools folder and it is 0 bytes mtd: ECC errors at 0x00000000 mtd: ECC errors at 0x00020000 Click to expand... Click to collapse That is what I feared.. might be fixable but a pain.. OK, lets see if you are willing what we can do (since without misc the engineering spls get stuck in s=on we really need to fix that first ideally) Run 'adb shell cat /proc/cmdline' This will output a bunch of data all I need to know is the value 'androidboot.cid' is set to. If you are confused or don't see it just pm me all the output or 'X' out your serial number and post here