After some days work, I had edited most of the special device drivers and build rule files for cliq2 now.
I had succeed to build all the source for cliq2, and got target files, then I try to flash the update.zip to my cliq2, but my phone didn't boot, I was sad T_T.
My phone stack at the boot screen, I can access into the bootmenu screen, but can't access the normal UI.
Now, I want to know, is there any methods to help me debug in booting? Or, dose anyone konw , what is wrong about my phone( or my cm porting)? I want to use the adb to help me cat the log files, but the cliq2 doesn't have the adb services in booting, anyone can help me to run the adb services in booting?
Maybe I can use the 2nd-init in bootmenu to start adb, but I don't know how to edit the init.rc file to start the adb services properly.
My English is poor*_*, I post this thread, I want to get some suggestion or help in porting, not ask how to fix my phone
Any suggestion?
Related
Sorry for the extreme 'newbiness' of this question but I needs some help here. I just got a Google ION (32B) which I am currently trying to simply Root.
I have gone through all types of instructions and everyone leads to the same steps of applying the Recovery image through Fastboot, but when I do the steps listed after I put the phone in Fastboot, plugged it in, and run:
fastboot boot recovery-new.img
Nothing happens. I get no such file or directory. I check ADB and the phone reads just fine. I have tried on both a Windows machine - which I was able to install the proper drivers for, and in OSX, but neither will read: $fastboot devices.
What could I be missing or doing wrong. I have referred to the Wiki, Essential reading and Newbie resource
Any insight would be greatly appreciated.
Thanks
http://forum.xda-developers.com/showthread.php?t=529062
http://android-dls.com/wiki/index.php?title=Magic_Rooting
fastboot
You will have to download it seperatly.. try here:
http://android-roms.googlecode.com/files/fastboot-win32.zip
Try enable USB debugging and fastboot devices should work.
If not, your drivers may be loaded incorrectly. Installing HTC Sync usually fixes the drivers I've found.
Download recovery-new.img
Put it in the TOOLS directory of the ANDROID SDK and retry your commando.
Yeah I have actually tried all of those things. I am following the root process to a T but still no luck. Perhaps I am doing some wrong in the command line?
have you set the $PATH variable? you get this:
"I get no such file or directory."
Click to expand...
Click to collapse
error-message. my best guess is that you have forgotten to added the path to where your fastboot tool is located.
try changing the directory to where your fastboot tool is located.
*Fixed*
I really appreciate the help guys, I redownloaded the fastboot.exe, and it read the phone right away. Now to start loading ROMs
Does anyone have access to an *unrooted* Wind phone with the original software installed? I have an idea how to assemble the original sbf for it: a fastboot recovery.
Basically, my idea is:
1) enable adb
2) use adb to reboot into fastboot
3) fastboot boot a custom recovery that will dump the relevant code groups to sdcard
4) use the pieces from the sdcard to assemble the original sbf
So, to try this I need someone that's somewhat technically comfortable (i.e. able to use adb and fastboot). I can walk someone through it on linux. I haven't made the recovery yet, it's sort of still a brainstorming mode. If anyone bites we can work the details out.
Basically, I'll implement it first for my phone and then post instructions. The phone will be left untouched by doing this (except for files written to the /sdcard).
I will look for it tomorrow why do you want it.
Ok
Sent from my Milestone XT720 using xda premium
We've never had the wind sbf.
it'll be hard to find Windmobile has discontinued the phone
of the existing users, not many are aware of XDA, and i've been spreading word of it on Winds forum
More than happy to help you
Mioze7Ae Your one of my hero that make that xt720 livable. I have 7 of those xt720 at work. I root them all and install custom roms exept one that I keep original to make a nandroid or SBF. If you help me, I have a chance for sucsess. I love all the linux distribution that are base on Debian, I dump Ubuntu becose I can not stand unity. now I am running mint on most of my computers. I am not a programmer but I am a hardware expert. I look forward to work with you.
sorry for my english I am french Canadian.
Stéphan
Great! Give me a few days to get some instructions/needed files put together.
Any luck with that? I have access to unrooted Wind XT720 if you still want it.
Ok, here goes:
Step 1: prepare sdcard (root of sdcard is /sdcard)
Download OpenRecovery-XT720-01.zip (http://android.fjfalcon.com/Files/Tools/OpenRecovery-XT720-01.zip)
Extract onto root of sdcard (creates /sdcard/OpenRecovery directory and OpenRecovery.zip)
Download attached dump-partitions-02.zip and put in /sdcard/OpenRecovery/updates
Create empty folder on root of sdcard called dump (/sdcard/dump)
Step 2: fastboot and dump (you need a computer that has both adb and fastboot working)
On PC: Download attached openrecovery-fastboot.img
On Phone: Enable ADB debugging
Plug phone into PC via usb
On PC: Run "adb reboot bootloader" on the PC
Phone will boot to "Fastboot bootloader"
On PC: Run "fastboot boot openrecovery-fastboot.img" (may require sudo)
Phone will boot into OpenRecoveryXT720
On Phone: select "Apply update" > "dump-partitions-02.zip"
Wait for dump to complete
Reboot phone
This will fill the /sdcard/dump folder with these files:
boot.img boot.md5
bpsw.img bpsw.md5
cdrom.img cdrom.md5
cdt.img cdt.md5
cust.img cust.md5
devtree.img devtree.md5
lbl.img lbl.md5
logo.img logo.md5
recovery.img recovery.md5
system.img system.md5
zip up the /sdcard/dump directory and send it to me and I will attempt to assemble an sbf. I don't think any of these partitions contain personal/sensitive data, but I can't be 100% certain so PM is completely fine or you can gmail them to me ([email protected]). Actually, it's possible that kpanic.img might have private/sensitive data (I think it's where crashed kernels get dumped so it could contain anything that was in memory at the time of a crash) and I doubt I need that partition anyway. So don't send that one if you're concerned about that.
Edit: just a moment -- removing kpanic from dump script
Edit: attached dump-partitions-02.zip which doesn't dump kpanic
Not sure if you're still needing this or if you got this, but a google search for this will give you what you need:
XT720_WIND__STR_U2_05.1F.2__USASHLSTAB14P2XAPCNWND03B.0R_1FF.sbf
I would link you but I'm new so I can't post a link
Use the droid developers link
403d said:
Not sure if you're still needing this or if you got this, but a google search for this will give you what you need:
XT720_WIND__STR_U2_05.1F.2__USASHLSTAB14P2XAPCNWND03B.0R_1FF.sbf
I would link you but I'm new so I can't post a link
Use the droid developers link
Click to expand...
Click to collapse
Another link, http://www.pda-planet.com/forum/forum386/thread233.html.
I'm trying my hand at porting a ROM and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Does adb not work at this point in the boot process or am I doing something else wrong? If I can't use adb to check logs, what can I use to debug?
I'm pretty sure you can only communicate with Adb while the phone is fully booted or while in recovery
If that's the case, how would I go about figuring out why the phone's stuck at the bootscreen? Can I add a line in an init.d script or elsewhere to write a log to the sdcard during boot?
edit: Found this on StackExchange: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
p011i3 said:
Phone: Alcatel One touch POP 5036x
PC OS: Windows 8.1
Hello, I am Nick from Holland and I am 13 years old. My first post is a request for help, for which I apologize.
I recently bought my second mobile phone, which is my first smartphone/android device.
Quickly after I purchased it, I decided to root the apparatus and got into sudo-ing and that kind of stuff.
Now my phone is in a boot loop and I am unable to recover from it.
I have been searching and reading this forum for days now, and I just cannot figure out what to do.
I' m having trouble finding the right files ( Stock image, CWM and such ) for my particular model.
What happened before this mess:
I installed an anti-theft program called ' Prey'
To see how this worked, I flagged my device as missing. Nothing happened though, so I reverted its status to OK.
Later on I decided to delete some bloatware, and eventually I accidentally erased a file called ' Android System' or something like that.
I am not 100% sure about this particular name though, but I do know it sounded important.
My phone froze during the deletion process and I decided to take the battery out and do a reset.
Phone OFF
Power + Volume up
wipe cache partition
wipe data/factory reset
After which I ended up[ in this boot loop.
The phone boots past the android logo, and restarts during the blue Alcatel POP-C5 animation.
To make things worse, I looked in the ' Prey Control panel, and noticed my phone was still flagged as missing.
I remember I read something, somewhere about a security measure that involves being unable to simply remove Prey
by resetting the phone to its factory defaults.
My current status:
I installed the necessary USB drivers on my Windows 8.1 machine, and I am able to connect to my phone using ADB.
I am able to reboot into fastboot. (
Code:
ADB reboot-bootloader
)
I am able to transfer files and such using ADB
I have collected and properly configured the paths within windows to use the command line and downloaded (I think) all the necessary software. like Flash Tool, MTK Droid, the Android SDK, etc.
Code:
fastboot devices
resolves mt6572v1_phone fastboot
Some discrepancies:
Code:
adb devices
resolves the following data:
List of devices attached
0123456789ABCDEF sideload
Notice 1-to-9 and A-to-F. This seems weird to me.
Code:
get-state
and
Code:
get-devseria
l both resolve 'unknown'
Is there anyone willing/able to help me resolve my issues?
In return I can eventually make a new tutorial or Alcatel OT-5036x recovery thread.
I will try pulling the debug info and produce a logfile later on and upload them to my Google Drive.
Regards,
Click to expand...
Click to collapse
You mention cwm.
Don't you have a backup?
Try google translating this thread: http://www.phonandroid.com/forum/carliv-recovery-cwm-6-0-4-4-pop-c5-et-x-pop-t81752.html
Lgrootnoob;50489116]You mention cwm.
Don't you have a backup?
Try google translating this thread: *link removed due restrictions*
Click to expand...
Click to collapse
I thank you for your kind answer.
No, I do not have a backup prior to my problem.
I have one now though, before things get worse.
I actually made some progress - I managed to correctly install and boot CWM.
I already stumbled upon and downloaded the files mentioned in your link.
The teXt translates as:
-put mobileuncle tools and recovery on your SD
mobileuncle-install and granted him the rights superSU
-click recovery update
-then recovery.img
clicked OK
-then it will ask to restart a recovery click OK
I downloaded the file called ' recovery.img' but I am unsure how to transfer it to my device and implement it.
Also, how do I install and run mobileuncle without being able to boot?
Regards,
EDIT:
Code:
C:\Users\Maya\Desktop>fastboot flash recovery recovery.img
sending 'recovery' (5522 KB)...
OKAY [ 0.217s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.242s
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
DeathNotice said:
Install stock firmware anf stock rom and ur phone via Odin.... and ur phone will start as it was when u purchased it...
Click to expand...
Click to collapse
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Lgrootnoob said:
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
p011i3 said:
Were do I find these for my Alcatel 5036x?
I searched for like four days without any definitive result.
Click to expand...
Click to collapse
Search it on www.SamMobile.com......U may get ur stock rom and firmware on it
Lgrootnoob said:
Either try:
Code:
fastboot oem unlock
Or talk to the manufacturer.
They should actually provide source code since it is an android/linux OS.
Once you try these things we will move forward.
Click to expand...
Click to collapse
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
DeathNotice said:
Search it on SamMobile.com......U may get ur stock rom and firmware on it
Click to expand...
Click to collapse
I searched for ' 5036x' : " No entries found."
p011i3 said:
Code:
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> adb start-server
PS C:\Windows\system32> adb reboot-bootloader
PS C:\Windows\system32> fastboot oem unlock
...
And it just hangs there. (Tried 3 times and waited ~10minutes each.)
The cause of this is that I made things worse - yesterday I formatted the /system partition using CWM.
I did make a backup using Android Toolkiot first though, but again I am unsure how to recover it.
Also, I downloaded the files mentioned in the French I briefly discussed above.
I consists of almost all files listed in Flash Tool, except MOBILE_INFO, CACHE and USERDATA
The Alcatel Source code is hosted at Sourceforge under project name ' Alcatel'
You are probably right. However, Alcatel actually does provide source code. See the ' Open Source' link at the bottom of the Alcatel website.
It is hosted at Sourceforge. Project name:: ' Alcatel'
I downloaded the the tar.gz archive earlier this week and extracted it, but I have no idea how to use this.
I am somewhat familiar with Linux though. I could set something up if I need to.
I searched for ' 5036x' : " No entries found."
Click to expand...
Click to collapse
I did look at it and it is the part of the source code for the kernel and that's it
Bat cave One
zelendel said:
This is wrong. They are not required to provide the source code for the OS. Only the kernel is licensed under the gpl. The rest is closed sourced.
You will need to track down the default software for the device. Which maybe hard if not impossible as clone devices/MTK devices are based out of China and few if any have any after market support.
Click to expand...
Click to collapse
The kernel should be good enough though. (With modules)
---------- Post added at 10:41 AM ---------- Previous post was at 10:36 AM ----------
@p011i3 Hey, what version of android do you have.
YOu might be able to make a flashable zip if you have a working system img.
Or we could make a false cwm backup and just restore system only from that.
I managed to fully recover my Alcatel One Touch POP C5 5036X without having a backup for my own. I did this by formatting the entire device using Flash Tool and downloading the files from the French Website discussed earlier in this thread.
I'll post a 5036X recovery topic including all files later this weekend.
Again, I thank everyone for their kind help.
After having a really good tester @mrbtree98 I was convinced that everyone is really that good but after seeing some people on #twrp and some close friends telling their situations of their tester , and believe me its not good
So this read would explain a bunch of including :
[*]Attitude
[*]Basic Stuff
[*]Debugging
[*]Talking skills
[*]Patience
Lets start with attitude
Attitude
People may hear your words
But people feel your attitude
Click to expand...
Click to collapse
Attitude while talking to developer is very important it even sometimes decides your respect on a forum !
People on very forums highly respect the devs even if he is new to the forums , same applies to xda
IF you show your attitude then things will absolutely go wrong
What do I include when I talk about attitude ?
You throw sarcasm or even bad abuse him ! becuase his program messed anything with or phone or anything
You say you are tired of this testing stuff
You try to tell him that he is slow and inferior to other devs
I know this may seem hypothetical but its true , this does happens !
When Talking to dev always keep your temp down remember that he is doing all the work for you all guys and he wants your satisfaction
Basic Stuff
lets Boil down to basic stuff that you need to learn before testing anything in android
Adb
Adb :
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device.
In order to use adb with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
On some devices, the Developer options screen may be located or named differently.
Note: When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
Click to expand...
Click to collapse
fastboot : fastboot is a small tool that comes with the Android SDK (software developer kit) that can be used to re-flash partitions on your device. It is an alternative to the recovery mode for doing installations and updates.
Kernel :
A kernel is critical component of the Android and all operating systems. It can be seen as a sort of bridge between the applications and the actual hardware of a device. Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software. So basically if any instruction is given to mobile it first gives the command to kernel for the particular task execution.
Flashing a kernel :
adb reboot bootloader
fastboot flash boot boot.img
Bootloader :
The bootloader is code that is executed before any Operating System starts to run. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. Think of the bootloader as a security checkpoint for all those partitions. Because if you’re able to swap out what’s on those partitions, you’re able to break things if you don’t know what you’re doing. So basically it commands the kernel of your device to Boot the Device properly without any issues.
Flash a kernel :
adb reboot bootloader
fastboot flash boot boot.img
Recovery :
Recovery is defined in simple terms as a source of backup. Whenever your phone firmware is corrupted, the recovery does the job in helping you to restore or repair your faulty or buggy firmware into working condition. It is also used for flashing the Rom’s , kernel and many more things.
Flash a recovery :
adb reboot bootloader
fastboot flash boot recovery.img
Radio
The lowest part of software layer is the radio: this is the very first thing that runs, just before the bootloader. It control all wireless communication like GSM Antenna, GPS etc.
taken by @jackeagle
You should know this basic stuff :good:
Debugging
Developer dont breath oxygen they breath logs
When he says recovery.log
If in normal mode (in the Operating System)
Using the phone itself :
Open a file manager app or textviwer
Navigate to /sdcard
Open the recovery.log
copy its content
paste it to paste.omnirom.og
Give him the link
If in the recovery itself :
Open up cmd or Terminal
Navigate to where adb is installed (Only windows )
Type
Code:
adb pull /tmp/recovery.log
The file would be at your folder where u navigated earlier or if on linux it would in the /home/{user}/recovery.log (if you didnt cd)
open it using a text viwer
Copy and Paste on paste.omnirom.org
Give him the link
[/INDENT
When he says last_kmsg
Open cmd
Type
Code:
adb pull /proc/last_kmsg
The file would be at your folder where u navigated earlier or if on linux it would in the /home/{user}/last_kmsg
(if you didnt cd)
open it using a text viwer
Copy and Paste on paste.omnirom.org
Give him the link
Talking skills
Dont ever give your thoughts !
Yes thats true the dev doesnt needs to know what he needs to do or not
But always report even a small change
My tester @mrbtree98 always tells me whether when booting the light is dimming or not he is getting the connect sound or not tell everything
Always talk with respect !
Patience
A rom build takes around 2 hours [highly approx , diff for everyone]
A boot.img takes me 20 mins [highly approx , diff for everyone]
So always be Patience
Even when you submit a log wait
A kmsg is around 5000 lines he / she needs to carefully see it to reach a conclusion so be patient
WIP
Flash a recovery :
adb reboot bootloader
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Shouldn't there be "fastboot flash recovery recovery.img"?