{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
After months of research and development, both hardware and software... I'm happy to announce UnBrickable Mod is a matter of modifing your phone once, with a single small wire. From that point on, you can click a button to unbrick. This can even be applied to a phone which is already bricked.
This is an example from the Captivate. The procedure is the same on the Vibrant.
Instructions
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
Unbricking:
1. Apply UnBrickable Mod to your device:http://forum.xda-developers.com/showthread.php?t=1273083
2. Run UnBrickable Resurrector: Get it from THIS POST: http://forum.xda-developers.com/showthread.php?p=17135277#post17135277 This will only work on linux currently. Install Linux or dual boot if you have windows.
3. Run Heimdall One-Click http://forum.xda-developers.com/showthread.php?t=1278683
4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
conclusion
You've unbricked the unbrickable captivate... This should not have been difficult. If it was, you should learn teh computer better... Really. And with that said, I'm happy to announce that you no longer have to flash with a fear of bricking.
HIBL
The HIBL is the key to resurrecting a S5PC110 based processor. I'm going to let Rebellos explain the inner workings of the Hummingbird Interceptor Bootloader. It's really quite amazing. While my work is more hardware and high level tasks like making things into one-clicks, Rebellos' work involves reverse software engineering, assembly language, and more...
Rebellos said:
Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
Code:
�������������������������������������������������� ����������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.
Click to expand...
Click to collapse
Tools
Windows32 command line app and drivers http://forum.xda-developers.com/attachment.php?attachmentid=709292&d=1315091521 (doesn't work very well... just want you to know this)
Linux one-click Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=712232&d=1315349672
Wow. i mark it! thank you for your great work!
I just resurrected a Vibrant today using the method above. This tested great. No problems to note at all.
Here's a picture of my work http://forum.xda-developers.com/showthread.php?p=17896376#post17896376
This is slightly more difficult then a captivate because there is no room to work around the resistors.
thanks to you i finally got my vibrant unbricked thanks a lot for this .....................
Aneez1990 said:
thanks to you i finally got my vibrant unbricked thanks a lot for this .....................
Click to expand...
Click to collapse
You're welcome. Glad this helped.
Very sexy work... its nice to have this as a backup and itll be Very nice once people develop ffirmware to work with the unbrickable mod, like nexus s bootloaders or wp7 or iOs or whatever... thanks again
Sent from a cell tower to the XDA server to you.
younix258 said:
Very sexy work... its nice to have this as a backup and itll be Very nice once people develop ffirmware to work with the unbrickable mod, like nexus s bootloaders or wp7 or iOs or whatever... thanks again
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
I'd like to see Ubuntu. Turn these devices into a lamp server or security/web cam orsomething when were done with them.
I would also like to see work on Ubuntu. is there any work being done for that? I'm still thinking about getting the UB mod sometime soon.
Hey guys Im having a problem with step #2. It says to download Unbrickable Resurector but this post is the HIBL post with no "Unbrickable resurector" download link. Is that just an error or do I just download the file listed on the previous post called "UltimateUnbrickResurector.zip"? Thanks for any clarification...
Also, when I launch the resurector on the previous post I get the following error smdk-usbdl: not found. Do I need to have Heimdall running prior to launching the resurector? Thanks again...
Code:
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Building command list
Building command list
Requesting Permission to access device/tmp/skorpnHeimdallOneClick51336EBC/Script.sh: 3: /tmp/skorpnHeimdallOneClick51336EBC/UnBrickPack/smdk-usbdl: not found
Moved this post to the "Mod" thread.
The Resurrector is not working, either because the mod was done incorrectly, or my Ubuntu machine has been setup wrong. The Resurrector keeps giving me the smdk-usbdl: not found error, but the file exists. My best guess is that the Mod was done incorrectly, either that or my Linux box is being a pain... Also noticed adb not working as well.
EDIT: Im going to go out on a limb and say this error is telling me the "usb device" has not been found, which would mean my mod did not take.
edit never mind found the answer was just wondering if it were possible to learn the wielding part of the guide on the internet and such also what type of tools would i need please and thank you
dohandrew said:
edit never mind found the answer was just wondering if it were possible to learn the wielding part of the guide on the internet and such also what type of tools would i need please and thank you
Click to expand...
Click to collapse
If you're asking, you will want to find someone more experienced.
i see where would u suggest going to ? im located in california i dont really know of a place that does welding on phones
Adam will do it for $30 + shipping, PM him.
Atleast thats what hes said (correct me if im wrong)
Adam, did you say you can do this mod for $30 + s&h?
Also, Im wondering if you upgraded to Ubuntu 11.10 yet? I just decided to upgrade before even thinking about it possibly effecting the mode detect, heimdal one click or the resurrector. You think the upgrade can break these apps any?
SkOrPn said:
Adam, did you say you can do this mod for $30 + s&h?
Also, Im wondering if you upgraded to Ubuntu 11.10 yet? I just decided to upgrade before even thinking about it possibly effecting the mode detect, heimdal one click or the resurrector. You think the upgrade can break these apps any?
Click to expand...
Click to collapse
Yes I do. No it doesn't.
AdamOutler said:
Yes I do. No it doesn't.
Click to expand...
Click to collapse
Excellent Im on 11.10, and thanks for the info...
I was able to remove the resistor and replace it with another resistor from an old samsung phone. I used a circuit writer pen from radio shack, it lays down a conductive polymer, which I used to adhere the new resistor onto the bottom spot on the board. "the resistors are so small I could not imagine being able to do this with a soldering iron. I would have probably shorted something out because the amount of solder that needs to be laid down might not even fit on an ants back (seriously!)"
Another note: when using resurector, my phone only went into download mode if I pressed on "only" the volume down button.-I hope this helps someone out there with a brick like the one I had.
Does that mean after applying this mod the vibrant will never brick at any cause ???
galaxyfitftw said:
Does that mean after applying this mod the vibrant will never brick at any cause ???
Click to expand...
Click to collapse
yes that is the meaning of this mod....is just awesome
Related
Alright I have been reading and trying to root this device for days with no avail, now let me tell you what i did. Before I turned off the phone, you have to literally turn off every wireless connection anything that you connected to at all. Dont turn on air plane mode, just turn off every connection you can. Then What I did was click in the sd card after doing the adb reboot recovery. This worked like a charm. I also edited the drivers of the usb driver file called winusb.inf located at c:\sdk\usb_driver
if you dont have that folder that means you have not installed the usb driver which you can do by opening setup.exe clicking on usb drivers install.
you have to edit the file by including the lines under google nt 86 at end of section
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
also then put the exact same lines under [Google.NTamd64] at end of section.
Next your going to want to save the file. Then go under device manager, update the drivers that you already have with that file located at c:\sdk\usb_drivers.
Restart if it says you have to.
Then next step use the windows application
hxxp://incredible.groove2.net/IncredibleRooter.zip
mdawg made This. extract put file in location under "c:\sdk\tools".
Then boot into recovery mode.
run loop.bat and begin clicking in and out of the sd card until it changes the error from device not found to that great error. then exit out of loop.bat with ctrl+c. and finish with the application by pushing files and updating zip. This is the hardest card to do. But it worked very first time after i tried updating drivers! I got wireless Tether working and sending this from there .
I used windows xp sp3
This method will work with any windows machine.
New!!! Load USB drivers from http://tether.com/a/setup.exe
Make sure you update your drivers in Device Manager and restart if needed. These are same drivers I used first time, I just forgot that I downloaded tether before hand.
If you need help you can locate me on IRC
irc://irc.freenode.net:6667/rootmyincredible
This doesn't help if you cant get the phone into the adb recovery status...
This will help you get the phone into recovery status
Please read and try directions instead of thumbing your nose at me. I have put a lot of time into this and im trying to help. I would like to know if my instructions have helped people so we can try and figure out what exactly it is that helps the device. This helped mine and is considered one of the hardest cards to get working. But please at least try this before I get responses like "this wont help". Your not going to ever get rooted with that attitude.
Re: How to root any htc incredible phone with any SD Card. Full proof instructions!
Thanks for the tips, but I think you need to be more careful about using definite statements like 'any card' and 'any PC'. We know from the unRevoked guys that radios and cards play a role, so you're right there.
-------------------------------------
Sent via the XDA Tapatalk App
I believe that SD card does not matter
Let me tell you, The Unrevoked team is a great team. i give them all credit for actually rooting the device. There is still some bugs, im trying to fix those bugs, and provide help how to do that. And I do believe any card can be done on any pc. If your experiencing problems, i might be able to help. Recovery status is easy to achieve if you follow directions. They are wrong about SD cards playing a role though, this is a misguided conception. As my card is one of the hardest cards to get working and practically no one has it.
blue45 said:
Please read and try directions instead of thumbing your nose at me. I have put a lot of time into this and im trying to help. I would like to know if my instructions have helped people so we can try and figure out what exactly it is that helps the device. This helped mine and is considered one of the hardest cards to get working. But please at least try this before I get responses like "this wont help". Your not going to ever get rooted with that attitude.
Click to expand...
Click to collapse
I've already tried this exact method of getting into adb recovery for like past 2 days, my phone just will not co-operate with me.
The root method with the program is awesome, I told mDawg this in TRC the other night... All i'm saying is it doesn't help people who cant get into adb recovery.
I have all the correct drivers installed, because i can use adb shell and android screen monitor to take screen shots fine when the phone is on.
But my phone will not go into adb recovery no matter what i try, I have tried using 2 different sd cards, 8GB Kingston Class 4 and the 2GB that came with the phone, tried formating in FAT, FAT32, and even filling the cards up with junk.
I'm not shutting you down in anyway, trust me, I would love for this to work for me, but It will not let me into adb recovery no matter what i try, I'm on windows Vista Home 32 and just not having any luck, so you saying this will work every time with any card just isn't true.
Anyways, i hope this does help people.
Sorry to post on both forums, but I'm registered on both just like you, so just put it on both.
No disregards at all honest.
blue45 said:
Let me tell you, The Unrevoked team is a great team. i give them all credit for actually rooting the device. There is still some bugs, im trying to fix those bugs, and provide help how to do that. And I do believe any card can be done on any pc. If your experiencing problems, i might be able to help. Recovery status is easy to achieve if you follow directions. They are wrong about SD cards playing a role though, this is a misguided conception. As my card is one of the hardest cards to get working and practically no one has it.
Click to expand...
Click to collapse
Basically you just got lucky I think, it's happened to others, there is defo something conflicting the results.
might want to change the title of the thread to "Fool Proof" instead of "Full Proof"... otherwise you may be considered a fool for more than one reason.
It is full proof and I will be happy to help anyone who needs it and has windows
please come to irc://irc.freenode.net:6667/rootmyincredible
That is my channel and I will help you!
blue45 said:
They are wrong about SD cards playing a role though, this is a misguided conception. As my card is one of the hardest cards to get working and practically no one has it.
Click to expand...
Click to collapse
There's only one way I will believe this: make a video of you getting shell and rooting without an sdcard in your Incredible.
blue45 said:
please come to irc://irc.freenode.net:6667/rootmyincredible
That is my channel and I will help you!
Click to expand...
Click to collapse
I can on via http://www.droidirc.com/ using your channel, and no one was there, is there another way of getting in, I don't have an IRC client installed atm.
sorry it didn't work for me...the only thing that came close was formatting my card to ext4 but the I had permission issues in linux trying to push the files. That was once and now I can't get into recovery shell again.
pozer69 said:
sorry it didn't work for me...the only thing that came close was formatting my card to ext4 but the I had permission issues in linux trying to push the files. That was once and now I can't get into recovery shell again.
Click to expand...
Click to collapse
Permissions? Writing to SD shouldn't require elevated permissions. Anyhow, set up two partitions on the SDcard: ext4 (or another linux partition, shouldn't matter--try something crazy like XFS or reiserFS , followed by a FAT32 partition. I believe the linux partition should give you the 5s race window you're looking for, then you'll have a mounted FAT32 to put the decoy update.zip which recovery will read from when payload is pushed.
What OS are you using to make ext4? PM me if you have more questions, or my gtalk is rynosaur74. Anyone who has questions can contact me: I was a 5-day headache person until yesterday
FYI Sorry to say it is NOT that easy for me. My sdcards will only work if I leave them out until after I start recovery and insert at the sound. I have tried you method and I don't think I'd call if "Full Proof". I know I have the correct driver and the updated lines in the .inf file, because I have rooted my phone. Unfortunatly, I have to use the card insert method, which is a little tricky.
Nice try but I gotta tell you, I think your title is a little misleading.
immjg said:
FYI Sorry to say it is NOT that easy for me. My sdcards will only work if I leave them out until after I start recovery and insert at the sound. I have tried you method and I don't think I'd call if "Full Proof". I know I have the correct driver and the updated lines in the .inf file, because I have rooted my phone. Unfortunatly, I have to use the card insert method, which is a little tricky.
Nice try but I gotta tell you, I think your title is a little misleading.
Click to expand...
Click to collapse
It's like calling the Titantic an unsinkable ship
I appreciate you taking the time to post, but this method didn't work for me (though none of the others have either). I really do wish there was a fool-proof, non-sd card dependent method
Ive discovered something
Ive found out with most of the people that ive helped in the chat room of mine, that you guys have your drivers wrong installed. See when I go into device manager on my computer it says Android USB Devices- My HTC
Make sure your computer has those drivers just like that.
here is what you should have your computer looks like!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No one was in the chat room when I was i there...
im there now
im there now
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.
UPDATE
http://forum.xda-developers.com/showthread.php?p=33043197#post33043197
An app removing WiFi/BT from your Atrix, stopping the reboots. El Noob friendly.
Click to expand...
Click to collapse
Howzit stalkers
There is a serious hardware flaw on our Atrix's (Atrices?) - the WiFi and Bluetooth module from Broadcom goes bust after a while - irrespective of which ROM you are using (even stock is not free from this problem).
You get random reboots, you only get "Error" when trying to connect to WiFi, and if you try again - it reboots. Same with Bluetooth.
That prompted me to make this build. It is CM9 with the WiFi and BT disabled. No more random reboots. This is a stop-gap measure until we can figure out what is causing this (most fingers point to the little battery on the CPU mainboard). This ROM just makes your phone usable again as a, you know, phone. HSPA also works. You can reverse tether with a USB cable to use your PC's internet - if you are interested and you are using Ubuntu I can give you an app I made for this purpose.
Please, keep the discussion on this forum on the topic of FINDING OUT WHAT IS CAUSING THIS.
There is a plethora of other forums with other users also experiencing this problem - no "me too" nonsense, please. It is a recognized problem. The pet protection agency will be forced to euthenize a little fluffy baby kitten if you post a "me too" post.
UPDATE - How to make it work in other ROMS
Some adb shell commands - you should be able to use / know what adb is (I'm no good at clockwork zip scripts - yet - so this will do):
adb shell
su bash
mount
//Then, look for something like "/dev/block/mmcblk0p12 /system ext4" - key is the /system part
mount -o rw,remount /dev/block/mmcblk0p12 /system/
cd /system/lib/modules
mv dhd.ko dhd.ko2
That's it - confirmed to work with Jokersax's 0.6 release and Turl's. Will probably work on older systems as well, seeming that all use the same archaic Froyo f-ing kernel.
Click to expand...
Click to collapse
WHAT IS DISABLED
WiFi
Bluetooth
What doesn't work
Camera (will try to fix this in the next release)
Video Camera
Fingerprint sensor (usual CM9)
Webtop (usual CM9)
Link
http://depositfiles.com/files/o9jyr61a2
http://ifolder.ru/30516689
Reserverd by OP
[ 31.028143] sdhci_tegra_wlan_detect Detecting WLAN
[ 31.028164] mot_wifi_set_carddetect: Nobody to notify
[ 31.029391]
[ 31.029395] Dongle Host Driver, version 4.218.248.32
[ 31.029400] Compiled in /tank/jokersax/cm9/kernel/moto/olympus/wifi-module/wlan/osrc/open-src/src/dhd/linux/../.. on May 7 2012 at 11:40:09
[ 31.328158] mmc1: error -110 whilst initialising SDIO card
WARNING: at /tank/jokersax/cm9/kernel/moto/olympus/lib/kobject.c:595 kobject_put+0x50/0x60()
[ 214.627572] kobject: '<NULL>' (0003da74): is not initialized, yet kobject_put() is being called.
[ 214.627581] Modules linked in: dhd(+)
[ 214.627591] Backtrace:
[ 214.627612] [<c0040010>] (dump_backtrace+0x0/0x10c) from [<c05b68c8>] (dump_stack+0x18/0x1c)
[ 214.627622] r7:c031c6c4 r6:c071fb48 r5:00000253 r4:e83a1e98
[ 214.627647] [<c05b68b0>] (dump_stack+0x0/0x1c) from [<c00bc5b8>] (warn_slowpath_common+0x50/0x68)
[ 214.627663] [<c00bc568>] (warn_slowpath_common+0x0/0x68) from [<c00bc61c>] (warn_slowpath_fmt+0x30/0x38)
[ 214.627673] r7:bf081000 r6:00000000 r5:bf076570 r4:0003da74
[ 214.627692] [<c00bc5ec>] (warn_slowpath_fmt+0x0/0x38) from [<c031c6c4>] (kobject_put+0x50/0x60)
[ 214.627701] r3:00000000 r2:c071fb80
[ 214.627720] [<c031c674>] (kobject_put+0x0/0x60) from [<c03787f0>] (put_driver+0x14/0x18)
[ 214.627729] r4:e98390c0
[ 214.627742] [<c03787dc>] (put_driver+0x0/0x18) from [<c0378938>] (driver_register+0x144/0x164)
[ 214.627757] [<c03787f4>] (driver_register+0x0/0x164) from [<c037994c>] (platform_driver_register+0x4c/0x60)
[ 214.627767] r9:00000000 r8:00000000 r7:bf081000 r6:00000000 r5:e83a0000
[ 214.627782] r4:bf078890
[ 214.627826] [<c0379900>] (platform_driver_register+0x0/0x60) from [<bf049fa4>] (wifi_add_dev+0x24/0x40 [dhd])
[ 214.627870] [<bf049f80>] (wifi_add_dev+0x0/0x40 [dhd]) from [<bf0810bc>] (init_module+0xbc/0x238 [dhd])
[ 214.627902] [<bf081000>] (init_module+0x0/0x238 [dhd]) from [<c003b5c8>] (do_one_initcall+0x40/0x1bc)
[ 214.627912] r5:e83a0000 r4:c07e0c00
[ 214.627932] [<c003b588>] (do_one_initcall+0x0/0x1bc) from [<c00f3880>] (sys_init_module+0xcc/0x200)
[ 214.627941] r9:e83a0000 r8:c003c364 r7:00046bd8 r6:00000000 r5:bf076748
[ 214.627957] r4:5c126008
[ 214.627970] [<c00f37b4>] (sys_init_module+0x0/0x200) from <c003c1e0>] (ret_fast_syscall+0x0/0x2c)
[ 214.627979] r7:00000080 r6:5e0fdb34 r5:5c126008 r4:405ad0f0
[ 214.627995] ---[ end trace 2416c978061dd5a5 ]---
[ 214.628002] Error: Driver 'bcm4329_wlan' is already registered, aborting...
Now I had some experience with WiFi kernel driver development (iMx51 + CSR based WiFi/BT combo chip).
The startup sequence on kernel level will probably go like this:
1) Kernel startup
2) ARM CPU specifics startup
3) Platform specific device setup (setup clocks)
3) Platform driver dependency registration (like, on SDIO 1 there is a WiFI chip that needs driver X to work)
4) Sub-platform driver startup (SPI, SDIO, UART, I2C)
I think this is where we fail first - Error -110 means timeout. Each MMC / SDIO chip has a MMC specific startup sequence, then depending what was given on number 3, it jumps over to SDIO (SDIO is a superset of MMC).
When our BT/WiFi chip is put into SDIO mode, the SDIO commands fail with a time out.
Possible reasons for it failing:
1) Incorrect voltages
2) Skewed clock
3) Busted chip.
4) We talk to it too fast
5) Kernel is messed up
Now, seeing that (through weird loops, check my previous post) I could get the unit running two more times, I do not think it is 3.
Why it could be 1:
Voltage rails needs to start up at the correct sequence for some chips. Like some chips will specify an operating range of between 1.8V and 3.3V. That means if it finds 5V on it, it will shut itself off. Sometimes some chips needs an initial 3V, then after 10 seconds it can be put into 1.8V (in-chip startup). Sometimes, it needs 10seconds to stabilize before you can talk to it (in our case via SDIO).
Why it isn't 1:
I've tried a lot of other kernels. It is all based of the ATT code, and they do the voltage rail setup correctly. I've even reverted back to stock code - no dice.
Why it could be 2
By removing the small cell battery, the drain on the battery was lifted. It could then store up enough current to put itself into the correct clock rate when it was put back.
Why it isn't 2
? Don't know. More needs to be known of the function of this battery. Obviously it is driving some RTC (real time clock). RTC's normally work at 32MHz, (32768, easilly divideable by 2, 4, 8 etc).
Does the Broadcom chip need this RTC? Isn't its clock lines driven by the Tegra2?
Why it could be 4
If the RTC is compromised (number 2) then init will suffer. If the Tegra's clock is not derived from the battery and the Broadcom's is, then there will be a disparity between the 2 units chatting together, as SDIO communication is clock based and not latch based (like SPI). If I'm chatting to you at 32MHz and you are 5% off, then we will not be communicating (if you are an SDIO master and I'm an SDIO slave).
Why it isn't
No idea.
Why it could be 5
Bunch of kernel errors stating un-inited modules pointing to null.
Why it isn't 5
Stock kernels also have the same problem
So, sorry folks, this issue points to a hardware problem.
Our biggest answer will be at the following:
1) What does that battery do?
2) Why is the SDIO subsystem having timeouts?
mirror1
So you deleted two files? A more efficient method would be to make a zip that deletes those files so it could be used with future releases and with turls as well.
Sent from my MB855 using XDA
Can't you just keep wifi and bluetooth off?
jokersax11 said:
So you deleted two files? A more efficient method would be to make a zip that deletes those files so it could be used with future releases and with turls as well.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
No, I've changed the kernel. On arch/arm/mach-tegra/ I've changed board-mot.c to not do wifi init and also removed board-mot-wlan.c from the Makefile. This keeps the SDIO card from being init-ed and is sufficient for the driver not to be registered.
Yes, having an update that is more frugal than having a 125MB update will probably work. But I don't have the inclination to do that now, as making my own custom kernel + ensuring it working with turl's base + a custom update script is not in the depth I want to waddle in now. Unless someone wants to help me with it. It is really a 2 line patch stretching on these 2 files.
As from "just switching off wifi and bluetooth" - there are SDIO interrupts being enabled from the GPIO and (subsequently) on the SDIO card (the Broadcom 4329). That means, even if you disable these 2, IRQ interrupts will still happen = the phone will still reboot.
mvniekerk said:
No, I've changed the kernel. On arch/arm/mach-tegra/ I've changed board-mot.c to not do wifi init and also removed board-mot-wlan.c from the Makefile. This keeps the SDIO card from being init-ed and is sufficient for the driver not to be registered.
Yes, having an update that is more frugal than having a 125MB update will probably work. But I don't have the inclination to do that now, as making my own custom kernel + ensuring it working with turl's base + a custom update script is not in the depth I want to waddle in now. Unless someone wants to help me with it. It is really a 2 line patch stretching on these 2 files.
As from "just switching off wifi and bluetooth" - there are SDIO interrupts being enabled from the GPIO and (subsequently) on the SDIO card (the Broadcom 4329). That means, even if you disable these 2, IRQ interrupts will still happen = the phone will still reboot.
Click to expand...
Click to collapse
If customized kernel, I can make a flash zip for it....really easy. Literally take me like 2 minutes.
Th3Bill said:
If customized kernel, I can make a flash zip for it....really easy. Literally take me like 2 minutes.
Click to expand...
Click to collapse
K, please explain how?
mvniekerk said:
K, please explain how?
Click to expand...
Click to collapse
NP. Assuming you did a boot.img edit, all you would need to do is download a copy of one of Joker's working kernels from Jokersax.com. Overwrite the boot.img and modules with the ones from your "tweaks" and mod name to (no wifi).
Will have a look at it tomorrow. Thanks!
mvniekerk said:
Will have a look at it tomorrow. Thanks!
Click to expand...
Click to collapse
No problemo. I did the same thing once when I had to make an edit to get adb to work my MIUI builds
Is there a way to replicate this issue? I'm curious because I have had no problems with my wifi or bt with any roms I have flashed.
Sent from my MB860 using Tapatalk 2
maulich said:
Is there a way to replicate this issue? I'm curious because I have had no problems with my wifi or bt with any roms I have flashed.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
I don't think it's a guaranteed issue. It seems to be something that happens with some devices over time. At least that's what I gather to be the issue. If you have working wifi and bt, then I wouldn't worry about it at this time
I soo hope this never happens to my atrix!!
Th3Bill, is it possible to create a Generic .zip that can be applied to any cm9 based rom ay any time? Sounds like something I may want kickin around just incase, lol.
Do the reboots happen while the phone is first trying to boot up? Or after wifi or bt is turned on, random reboots start occuring?
Just wanna know what signs I should look out for because I would be hopeless trying to syphon through lines of script. I may as well try reading Japanese lol
ATRIXXIRTA said:
I soo hope this never happens to my atrix!!
Th3Bill, is it possible to create a Generic .zip that can be applied to any cm9 based rom ay any time? Sounds like something I may want kickin around just incase, lol.
Do the reboots happen while the phone is first trying to boot up? Or after wifi or bt is turned on, random reboots start occuring?
Just wanna know what signs I should look out for because I would be hopeless trying to syphon through lines of script. I may as well try reading Japanese lol
Click to expand...
Click to collapse
When you say generic zip, you mean a flash zip that you can just add some files to and use to flash your phone? I have one already made. Only issue...you need to make sure you set the permissions when you use it....so it's not the most user-friendly thing. I will try to make it a bit more user friendly and then up it tonight
By generic I just mean one that can be applied to any rom that's cm9 based (cna,aokp,gummy etc..)
Joker recommended creating a fix to be applied to an existing rom, rather then creating a whole new one with some removed files, scripts, or whatever this rom is missing that removes bt and wifi.
And you said you could possible help create a zip fix.
I was just curious if it would be a fix that can be applied to multiple roms, or would each one need its own specific fix?
Also, where the hell is a good place to start learning the basics of android development.
Seems like the more I try to learn, the more I realize there are othere things I need to know, or should at least have some knowledge of first. Like java, *nix based OS's, and all kinds of other stuff, its pretty overwhelming considering I've had no interest in computers or technology until January when I started working for Rogers, lol.
A good starting point would be awesome. I know google, xda and these forums are good places, but there are soo many abbreviations (html, ttps, http, ip,) that I still don't know, that I end up at least a little confused. lol.
Tryin to read this op is a good example. There like 14 different abbreviations I have no clue about, lol.
Thanks
I just flashed this ROM on my Atrix and so far so good. I have only been running it for an hour now, but usually by now it would have rebooted once or twice. I'll report back tomorrow.
my coworker's sister designed the Atrix antenna and she said that the RTC battery has nothing to do with the wifi module. just my 2 cents.
also, i've had this error for about a month; my solution was to wipe fresh and install CM9 (5.1 jokersax), and NEVER EVER EVER touch the wifi/BT toggles. so far (one month) not a single reboot error. of course, now my data plan is choking pushing towards 3GB in 28 days, but whatever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So far so good! Not a single reboot with some light to moderate usage. Thank you again for the modified ROM and kernel! Brought my phone back to life.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This utility will help you recover your IMEI / MEID from a bad flash.
WARNING:
This software only allows you to write to the device if the IMEI / MEID is zero'd out or does not contain anything.
DO NOT WRITE SOMETHING YOU DON'T WANT. IF YOU WRITE THE WRONG IMEI / MEID YOU ARE SCREWED.
I do not condone changing / modifying / tampering with the serial IT IS ILLEGAL. It is however legal to recover the original one, that is what this software will allow you to do.
I will not answer PM's because you typed the wrong serial number or because you tried something you shouldn't have. This is a fair warning. Make sure you type your original serial number in correctly the first time. Both boxes must match.
[How To Use]
1.) Plug device into computer.
2.) Select Internet Connection Mode, select Modem.
3.) Open device manager to see what COM your device is on.
4.) Open software and select the COM, there is two the device will connect on, you only need to write the information to one of them.
5.) Click on Connect.
6.) Type/Paste you're MEID/IMEI, verify it before you click Repair.
7.) Verify again.
8.) Click repair, wait for software to reboot your device.
9.) If the phone doesn't reboot after 1 Min, go ahead and reboot your device.
10.) Enjoy your ICS rom on your working VS920 device.
[Problems]
Q.) What do I need in order to run the software?
A.) Just dotnet 4.0
Q.) Where do I get my IMEI/MEID ?
A.) Remove the back, then remove the battery. There is a white sticker that say's IMEI. Type the whole string in the top box ignoring the last number its a checksum, you will see the last number being calculated on the IMEI field. Make sure it all matches up.
Q.) I didn't listen/read what you wrote about the 1 time write.
A.) I can't do anything for you.
Q.) The application is throwing an error.
A.) Please take a screen shot, and copy the error then paste here.
Q.) The application just randomly quites.
A.) Stop trying to log what the application is doing, quit any debuggers and try to open the app again.
Q.) My antivirus is picking this up a a virus/torjan why?
A.) Most antivirus suck anyway, they scan on the pe header of the file. If its unable to process it, it will automatically flag the program as a virus. I assure you there is no virus. All my software gets protected low level to prevent tampering with.
Q.) Was the license agreement really needed, its annoying!
A.) No it probably wasn't but to protect me, FTT, and XDA-Developers then yes. I put that there you are fully aware that it is an as is software and you are agreeing not to reverse engineer the software as well as agreeing that you are doing this at your own risk.
Video
How it works
Now while I tested this over and over on my two test devices and they work fine. This doesn't mean that it works fine on every machine. I built the app in less then a day. I have added as many checks as I can so it wont mess anything up.
DotNet Framework 4.0 Is needed.
Download Here
VS920 MEID Repair Utility 1.0
MD5 Sum
Exe: 142882a5de3ae3204704626933522fdc
Rar: 48dd4ab56710ce901af9e2e067d11e1f
DO NOT REPOST THIS ON ANY OTHER FORUMS, DO NOT LINK TO THIS FROM OUT SIDE OF XDA. I MONITOR ALL TRAFFIC ON THIS SITE. I WILL PULL THE FILES IF I HAVE TO.
Reserved for later use if i need it.
I'm getting a 404 on that link.
Link is fixed.
I would love for some success or fail stories, some feed back as well. Hopefully all success stories , but I know that never happens lol.
If I have helped you at all please don't forget to say thanks.
The rar file tested ok with 7Z.
I tried to download dotnet 4.0 and my Win7 64 bit machine asked if I wanted to re install it.
The program crashes before it opens.
A popup askes to check the web for a fix.
EDIT:
You sure that was Internet Modem, or Ethernet?
EDIT:
Fail either way.
Same results here. Also what language was this built in?
Hmm can you post a screen shot of the crash. Ill have to check it out. I have another machine ill run it on right now.
Wow I'm an idiot
No wonder it crashed.
dotNet 4.5 ughh...
You can try to install 4.5 if you want or ill have to recompile later tonight.
Application Crash
Code:
Faulting application name: VS920 MEID Repair Utility.exe, version: 1.0.0.0, time stamp: 0x4fc6f0df
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x2224
Faulting application start time: 0x01cd3eef4903a23f
Faulting application path: C:\Users\Blake\Desktop\VS920 MEID Repair Utility.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 874a351a-aae2-11e1-9249-f1c420cf0b5b
And the .Net crash
Code:
Application: VS920 MEID Repair Utility.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeLoadException
Stack:
at System.ModuleHandle.ResolveMethod(System.Reflection.RuntimeModule, Int32, IntPtr*, Int32, IntPtr*, Int32)
at System.ModuleHandle.ResolveMethodHandleInternalCore(System.Reflection.RuntimeModule, Int32, IntPtr[], Int32, IntPtr[], Int32)
at System.ModuleHandle.ResolveMethodHandleInternal(System.Reflection.RuntimeModule, Int32, System.RuntimeTypeHandle[], System.RuntimeTypeHandle[])
at System.Reflection.CustomAttributeData..ctor(System.Reflection.RuntimeModule, System.Reflection.CustomAttributeRecord)
at System.Reflection.CustomAttributeData.GetCustomAttributes(System.Reflection.RuntimeModule, Int32)
at System.Reflection.CustomAttributeData.GetCustomAttributesInternal(System.Reflection.RuntimeAssembly)
at System.Reflection.RuntimeAssembly.GetCustomAttributesData()
at System.Reflection.CustomAttributeData.GetCustomAttributes(System.Reflection.Assembly)
at System.Resources.ManifestBasedResourceGroveler.GetNeutralResourcesLanguage(System.Reflection.Assembly, System.Resources.UltimateResourceFallbackLocation ByRef)
at System.Resources.ResourceManager.CommonSatelliteAssemblyInit()
at System.Resources.ResourceManager..ctor(System.Type)
at System.ComponentModel.ComponentResourceManager..ctor(System.Type)
at ?1?.?3?.?28?()
at ?1?.?3?..ctor()
at ?1?.?7?.?67?()
amoamare said:
Hmm can you post a screen shot of the crash. Ill have to check it out. I have another machine ill run it on right now.
Click to expand...
Click to collapse
I used 7z to test the archive before I tried to run it.
TypeLoadException is thrown when the common language runtime cannot find the assembly, the type within the assembly, or cannot load the type.
My visual studio decided to default 4.5 framework. So until I can recompile, might just need to install dotNet 4.5
Dotnet 4.5 Beta Download link
EEEW a beta? Just kidding.
No problem, thank you for working so hard at this...
No problem.
4.5 is actually pretty stable for being a beta. I've been running it for months now with no issues that I noticed. Then again i'm on my dev machine and it hardly has issues :S except for it doesn't like wireless keyboards and mouse's ha.
Well it looks like it would do the trick.
It ran through all the motions.
Except I haven't tried the ICS update.
I was thinkin of waiting for a .bin file instead of trying to figure out where the hell the Phone Booth could be found.
I have little doubt that this will work for those that wave gotten stuck with the peek a boo IMEI.
Now if you had the time to work out something for my poor LG Fathom.
It got a case of amnesia or something.
cac2us,
If you wan't to try the ICS update, I can team view with you and show you how to use LGNPST in order to flash the .tot. Its pretty simple once you see it the first time.
People that are having Google Play Store issues and no 4G and Intermittent 3G is because there IMEI is zero'd out. I can log into the play store fine, use my internet fine etc, but when I zero'd my IMEI and MEID out it wouldn't download my e-mails or anything, I couldn't log into the play store it would just freeze.
Whats wrong with your Fathom?
Thanks, but if the only way is to use download mode, that's what killed my fathom's MEID.
So,... aw what the hell.
If I put it in download mode then the .tot file should get accepted?
And where the hell is that Phone Booth folder that I read about?
Fahthom got flashed too many times.
And in download mode. Then I spoofed at to be an HTC 6800, and now it won't change back.
I might have to pay the $99.00 for the newer Workshop to write it back.
Maybe if I send it to you along with a bucket of cash, and the box it came in you could maybe fix it?
That Google play store issue makes sense, just like my fathom won't activate without an MEID or an IMEI.
You don't need to flash in download mode.
Connect the phone to the computer, select internet for the connect and then select modem.
Make sure you have registered the dll regsrv32 "Path to dll";
After that open LGNPST you should see that it shows the model VS920. Click on the Phone settings button, then click read. Make sure it reads everything correctly. Close out of phone settings.
The Port will flash to say its done click on it to reactive the port.
Select upgrade and click browse.
Now in the window that pops up, down at the bottom where you can select a file. Don't worry about what it says. The box above it where you can type the location enter in *.* then click enter.
This will display all files. Now select the .tot file. "You can also rename .tot to .bin" once you select the file, click on upgrade. The flash should succeed fine now..
The reason people have crashing issues is because they would go to "Phonebook" section in the software and use that. The phonebook backup/restore is not used for upgrading the phone.
Also to answer your question, yes I could most likely repair it for you. No cost, just pay for shipping here and back.
OK, I'm ready to do it.
The only part "Make sure you have registered the dll regsrv32 "Path to dll";"
Isn't that file in the Windows\System32 folder?
How do I register it. I allready did the right click thing for the 920.dll while it sits in the Models folder of LGNPST folder.
I will PM you with the details of the Fathom.. Thanks..
Yes if your using the right click register, and you right clicked and registered and it returned with succeeded then the dll is registerd and your are good to go.
Hi all,
I have been going on xdadevelopers a lot and have received so much helpful information. Now, I decided to give in my contribution to the forum. This is my first tutorial so there might be some mistakes...please be easy on me.
The reason I write this tutorial is because I have not found a good one yet on the internet. Although this thread "Just rooted my remix mini" provided some information, but I feel like a more detailed tutorial would be appropriate. So here we go!
Success screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits: all credits goes to these two links and authors:
http://forum.xda-developers.com/remix/remix-mini/rooted-remix-mini-t3311736
http://23pin.logdown.com/posts/435610-root-remix-mini
Requirements:
- Difficult level: Medium
- Tools:
+ Small screw driver
+ Scissors
+ A USB flash drive.
+ Thin metal wire.
+ Serial Converter (I bought on Amazon.com)
- Software:
+ Appropriate driver for the serial converter. Mine is CP2102 driver. Download here. If your serial converter use PL2303 then download this driver. You can google for your specific driver as well.
+ CoolTerm. Download here
+ SuperSU. Download here
- A lot of patience.
Steps:
1. As you can see, I stripped the wire and cut it in small pieces. As long as it is metal wire, that's okay.
2. Open up the Remix Mini with a screw driver.
2a. Flip it up side down, and rip the rubber ring out. It's okay, it will still adhere to the case afterward. Once you ripped it out, you will see two screws holding the remix mini. Proceed unscrew them and gently take the case apart.
2b. Gently take the case apart:
3. Connecting the serial converter to the board.
3a. Plug the 3 metal wires into RX, TX, and GND cable endings of the serial converter.
3b. Connect the other ends of 3 mental wires into RX, TX, and GND of the board.
3c. Make sure connection as such: RX to TX, TX to RX, and GND to GND. This part took me a lot of patience because the wires kept falling off. So please try to keep them in place.
4. Install appropriate serial converter driver.
5. Plug the serial converter into PC.
6. Extract and open CoolTerm.
6a. Click Options -> Serial Port -> Hit "Re-Scan Serial Ports" so it detects the appropriate port for serial converter. Mine is COM3.
- To find out, go to Device Manager -> Ports
6b. Select the right port. Then change the setting as in the picture:
Baudrate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Click to expand...
Click to collapse
6c. Go to tab Terminal -> Select Line Mode.
6d. Hit OK.
7. Power Remix mini up (make sure this happens or you will get serial 103 or 104 error code)
8. Hit Connect button in CoolTerm.
8a. If you have done everything correctly until here, texts will appear in CoolTerm as your Remix Mini booting up.
8b. The texts will keep flowing up. Wait until you only see CPU readings. Then proceed to next step.
9. Download the UPDATE-SuperSU-v2.46.zip file. (Please double check the zip's file name. In my case, I am using SuperSU version 2.46)
9a. Copy UPDATE-SuperSU-v2.46.zip file onto flash drive.
9b. Extract the downloaded "UPDATE-SuperSU-v2.46.zip", from the extracted, go to META-INF/com/google/android/update-binary, copy "update-binary" file onto flash drive.
9c. Make sure you have 2 files, UPDATE-SuperSU-v2.46.zip AND update-binary, on the flash drive.
9d. Plug the flash drive to Remix Mini.
10. Commands: (copy each line and paste into CoolTerm)
Code:
/dev/tty.usbserial 115200
mount -o rw,remount /
mount -o rw,remount /system
mkdir /tmp
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-v2.46.zip /data/local/tmp [COLOR="Red"]<- Double check zip's file name and try Storage02 if Storage01 does not work because it depends on which usb port you plug the flash drive in. [/COLOR]
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
cd /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip
reboot
11. Success. :victory::good:
11a. Wait for Remix Mini booting up, optimizing app..and DONE! CONGRATS! You have now voided your Remix Mini's warranty and cannot receive OTA system update anymore.
I have not figured out how to update manually but please hit me up if anyone knows how.
11b. Download Root checker to verify.
GOOD LUCK!!!!!! :good:
I'm gonna wait for an easier way..
This has got to be a joke.
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far.
Note: first boot takes longer than factory. Be patient. Jide will know it has been hacked so no support for updates but the opportunity to customize was worth it for me.
robot_head said:
Bro, have you tried kingroot, I'm not crazy about it but it works 99℅of the time
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
I tried everything..even Baidu Root...nothing works...I am happy that I can do so many things with the Remix Mini now...rooting it was a genius decision lol
Major kudos, this is a true root method for all the hardware hackers out there. You've never truly "hacked" until you've tapped into a UART console. Very exciting!
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
bullet25 said:
So when I try this the remix mini just sits at the splash screen and coolterm just keeps saysing
Code:
/dev/block/mmcblk0p12fs_mgr: exec: pid 1667 exited with return code 1: Unknown error 256fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p12fs_mgr: finish format to ext4:
while counting up on the pid number. Any idea why that might be?
Click to expand...
Click to collapse
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
unloseking2500 said:
I have not seen that before. May I ask at which step that this occurred? This looked like the device was formatting ext4 itself...it's weird.. can you double check and try everything again carefully?
Click to expand...
Click to collapse
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Sounds like a software issue. Someone else had a recovery partitionfrom Jide search maybe they could upload it.
bullet25 said:
I happens at step 8. I think the mini might actually be dead because even closed up it doesn't boot.
Click to expand...
Click to collapse
Interesting...yeah, try oncouch1's method..try to recover from a partition..see if it helps?!
oncouch1 said:
No it is not a joke, no it will not get easier. Jide made it clear they will not support rooting. The amount of support available is minimal so this is the way. Difficult not if you have done stuff like this before ( FTA satellite. Etc.) kingoroot and all other software has been proven NOT to work. Hardware hacking is the only way so far..
Click to expand...
Click to collapse
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Yoswin said:
I also believe so. Grats on your success tho.
I have a question:-
I have a Tronsmart Vega S95 Telos with Remix OS firmware (Amlogic S905/Mali-450mp5/2 Gb Samsung DDR3/16 Gb Samsung KLMAG2WEMB-B031 eMMC/Realtek RTL8211F Ethernet/Ampak AP6335 Wifi+BT 4.0/Genesis GL850G USB 2.0 hub/JMicron JM20329 USB 2.0 to SATA bridge).
I opened up the TV box and saw the pin holes for PL2303 interface. I tried connect my PL2303 cable with its driver on Mac OS. The connection was succesful, I saw the response in my terminal in the form of message feed. But, I can't go any further. I'm still new to PL2303 use and I don't know how to go from the message feed to issue some commands. Then I see your thread and I think now I got some hope.
My question (again) is:- Do you think I can use your method to root my Tronsmart S95 Telos (with Remix OS flashed and working)?
Many thanks in advance.
PS. Here is the link to a photo of the S95 Telos board showing the PL2303 interface. The photo is not mine. I linked it from a guy tutoring the teardown, but my board looks exactly the same.
(I'm a new XDA user so I can't attach a photo from outside link, sorry for inconvenience)
www,cnx-software.com/wp-content/uploads/2015/12/Tronsmart_Vega_S95_Telos_Board_Large,jpg
Click to expand...
Click to collapse
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
...
oncouch1 said:
Hi honestly I had never heard of your box. I am not sure if you can use the same software etc. If you could communicate with the box you should be able to hack it. That being said depending on cost you may want to leave it to someone with experience! Remix was 50 bucks so no big risk for me.
Click to expand...
Click to collapse
Thanks for reply. I don't think the method can hard brick my device any way. The box itself can be flashed via a PC program made by CPU manufacturer (Amlogic here) and I have both stock firmware and Remix OS firmware images. So I think it's gonna worth a try. Thanks any way for your comment.
Keep us posted, may need one of those!?
Okay got my remix replaced. New remix updated to latest update then did root. It started boot looping. Had to run these commands in coolterm turing a boot loop.
Code:
mount -o rw,remount /system
dd of=/dev/block/by-name/system if=/data/local/tmp/system_image
Don't know if that was the latest update to cause that or what but its all working now. Also was able to easily install the google play services again and get playstore.
Of course I once again broke the power button because that wire is hanging on by a thread.
Apologies for the noob question but what does a root on the Remix Mini allow someone to do with regards to OS options and what are the other advantages?
vinicioh23 said:
I'm gonna wait for an easier way..
Click to expand...
Click to collapse
Please see this: https://secure.avaaz.org/en/petitio...tters_Users_need_root_access_to_remix_mini_1/
Just wanted to give a thanks it worked perfect for me...Just want to add that if you happen to use a built in serial port on an older pc or laptop don't forget to put a ttl converter on your port, or your console screen will be garbage printing out