Rooting the Alcatel Ideal 4060A & Replacing Kingroot With SuperSU - Android Q&A, Help & Troubleshooting

I have about 30 of these phones and people have been asking me how I get SuperSU on them:
https://youtu.be/qkik4q5ERaU

NitroKoS said:
I have about 30 of these phones and people have been asking me how I get SuperSU on them:
https://youtu.be/qkik4q5ERaU
Click to expand...
Click to collapse
In the video, you said Kingroot 4.5
There is new:
Kingroot V5.0.4 should I get it instead?

Handsome Jack said:
In the video, you said Kingroot 4.5
There is new:
Kingroot V5.0.4 should I get it instead?
Click to expand...
Click to collapse
Successfully rooted the Alcatel Streak with KingRoot. But my cell phone won't boot after I applied the KingRoot/SuperSu replacement.
Here is thread on requesting ROM to recover from the issue. Obviously another person had same issue as I did:
https://forum.xda-developers.com/android/help/requesting-alcatel-4060-o-cricket-stock-t3578896

I have uploaded all the partition dd image at mediafire.com excepect /system witch is big file and i have low bandwidth
Note, the recovery image is compressed zip us unzip before dd back

kdm6389 said:
I have uploaded all the partition dd image at mediafire excepect /system witch is big file and i have low bandwidth
Note, the recovery image is compressed zip us unzip before dd back
Click to expand...
Click to collapse
I see many dd files with one particular zip file in mediafire. How can I use these files to flash my Alcatel Streak ROM? I have never done this before and I am newbie here.
Thanks,

jxzz said:
I see many dd files with one particular zip file in mediafire. How can I use these files to flash my Alcatel Streak ROM? I have never done this before and I am newbie here.
Thanks,
Click to expand...
Click to collapse
You need "adb"
use following cmd to replace using,
adb shell
su
dd if=/sdcard/backup/pationno.img of=/the/pation/where/you/want/to/restore
beware!
dd is very lethal in wrong hand, I recommend not use until you are knowing what are you doing, we dont have any TWRP so to save your device.

kdm6389 said:
You need "adb"
use following cmd to replace using,
adb shell
su
dd if=/sdcard/backup/pationno.img of=/the/pation/where/you/want/to/restore
beware!
dd is very lethal in wrong hand, I recommend not use until you are knowing what are you doing, we dont have any TWRP so to save your device.
Click to expand...
Click to collapse
I am quite comfortable handling linux command line shells. However, since my Alcatel Streak phone is stuck at boot, not sure how I can get the adb shell?
After several rounds of factory reset, cache reset, no mater what, the phone simply won't boot and it is stuck with "google " or "android" welcome picture.
I noticed a a guideline of using cygwin in windows PC to run dd for backing up the phone partition image. Is it possible that I copy all your dd files into a cygwin in window 10 PC, then use USB cable to move the files into the phone or flash the phone?

jxzz said:
I am quite comfortable handling linux command line shells. However, since my Alcatel Streak phone is stuck at boot, not sure how I can get the adb shell?
After several rounds of factory reset, cache reset, no mater what, the phone simply won't boot and it is stuck with "google " or "android" welcome picture.
I noticed a a guideline of using cygwin in windows PC to run dd for backing up the phone partition image. Is it possible that I copy all your dd files into a cygwin in window 10 PC, then use USB cable to move the files into the phone or flash the phone?
Click to expand...
Click to collapse
nothing will work unless u have /system image, or working ROM.zip,
Since you have corrupted /system, and your model is different then mine is pop445
i did not uploaded /system bc its wqy more size then recovery

kdm6389 said:
nothing will work unless u have /system image, or working ROM.zip,
Since you have corrupted /system, and your model is different then mine is pop445
i did not uploaded /system bc its wqy more size then recovery
Click to expand...
Click to collapse
Thanks for the information. I searched the web and found many stock ROM for download for many Alcatel models except this model.
Alcatel Streak (model 40600) is dedicated for Cricket and it appears that neither Cricket nor Alcatel releases the ROM for this model.

jxzz said:
Thanks for the information. I searched the web and found many stock ROM for download for many Alcatel models except this model.
Alcatel Streak (model 40600) is dedicated for Cricket and it appears that neither Cricket nor Alcatel releases the ROM for this model.
Click to expand...
Click to collapse
share the stock ROM

I have figured out a way to root easier, I have flashed twrp (with some graphical issues... Working on it) flashed Xposed framework on it, and got native tethering working.

This thread is obsolete now,
for rooting read https://forum.xda-developers.com/android/general/super-guide-alcatel-one-touch-4060a-t3621525

Latest Stock ROM we have | https://forum.xda-developers.com/showpost.php?p=74529924&postcount=205

Related

[Q] screwed up custom recovery - bricked? :(

Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App

[CWM] Nexus Q Factory Image

For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem

Why not Rom Manager?

I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
eastwood1 said:
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
Click to expand...
Click to collapse
Someone with more knowledge will need to chime in, but I I'd bet the build we are using isn't official, and probably can't be installed through Rom Manager. Give it some time, eventually things will work as normal
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Click to expand...
Click to collapse
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
eastwood1 said:
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
Click to expand...
Click to collapse
To all,
I couldn't be bothered with learning ADB, but wanted a custom recovery on my SIII ... maybe you can relate?
Here's the easiest way to do it -- and you don't even need a computer!!! You do, however, already need to be rooted before you can use this method ...
Download your recovery of choice (.. as of this writing, I think there are two: CWM and TWRP ..) and make sure you place a copy in the root drive of your sdcard. Rename it recovery.img, if you want to follow the terminal directions listed below ...
Then, download a terminal emulator onto your device (I use Better Terminal Emulator Pro, which is a paid app) and fire it up.
Once in the terminal emulator, type the following commands one line at a time, waiting after each line for the appropriate prompt:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Your device should then boot into the custom recovery, which serves as immediate confirmation that you did things correctly.
I just used this method to install birdman's twrp8.img to my SIII and it worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1764398
I dont think that will work. Notice the command says sdcard.
The internal memory on the sgsiii is labeled sdcard for whatever reason. The external sdcard slot is under mnt/extsdcard in root explorer if that helps.
Sent from my SGH-T999 using xda premium
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
You need to be rooted and have a "su" command. Typical "rooted" roms include supersu , or equivalent, and busybox (which provides the basic Linux commands). I would install super super and busybox from Google play and try again.
You need the SU command to switch to root user in the shell to have the rights to use dd to overwrite the recovery partition.
I can confirm that the dd command works as that is how I loaded cwm on my s3.
Sent from my SGH-I747M using xda app-developers app
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
See if this helps.
http://forum.xda-developers.com/showthread.php?t=1739426
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Pompsy said:
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Click to expand...
Click to collapse
There's no official CWM Recovery for any US versions of the GS3, Sprint included. The only official GS3 recovery available is for the international version. The one we're all using right now (I believe) was built by Team Epic. They're historically Sprint devs and so they built it for the Sprint version; however, as you know it works on more than just the Sprint version. Eventually, I'm sure there will be official recoveries direct from Koush.
Personally, I prefer TWRP (bettery touch control layout and options such as compression to save space), but that too is a work in progress.

[Q] MTK6573 custom recovery and backups / Stock Boot, Recovery + Scatter included

Phone is a Star X19i
Now I'm looking at getting a system to allow me to back up the rom and re-flash if needed.
Post 4 has attachments of my boot, recovery and scatter files.
Old issue: (Solved)
Stupid thing I did I renamed the mtklockscreen.odex to mtklockscreen.odex1 just as a test in a half asleep phase to see if I would get the stock lockscreen loading.
Suffice to say the phone no longer boots.
Really don't think I can get into ADB and rename the file to get the phone booting again unless anyone knows a way.
Android was 2.3.6 and I asked the seller if it was possible to get the rom incase anything like happened which they didn't.
So anyone have any ideas?
I have attached the stock recovery and boot images made with cat and a scatter file I made to post 4.
As I have no idea about modifying these for hard root can anyone take a look?
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
dxppxd said:
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
Click to expand...
Click to collapse
I got into built in Factory mode and can see the file I renamed through ADB and android commander but cannot rename it back due to not having hard root access.
I also have a copy of the boot and recovery partitions 5 and 6 respectively I made in the adb shell yesterday as I was half looking at getting hard root access.
ren mtklockscreen.odex1 mtklockscreen.odex
ren: permission denied
I read you can do a custom recovery with root using SP Tools still so can anyone help me do this?
I know about system root etc and stuff and have flashed roms before on other tablets and have been a PC I.T tech (wouldn't think it due to the stupid mistake) but this recovery and scatter files etc is kinda new to me.
I have a scatter file now I just made if anyone is interested in helping me.
Yes I have a MTK6573 but the scatter file came from the MT6516 Rom Studio which I read works the same for the 6573.
Attached is also my stock boot and recovery partitions I made with cat yesterday if there usable to anyone to help.
Well I got it working and fixed.
I had to go into adb shell and su and mount the file system as writable, as I have used linux before I didn't know about android and what needed to be done and permission locks etc.
The stock boot, recovery and scatter files will remain on this thread if anyone wants to help create or find a recovery which can allow me to create backups and flash custom roms.
I may be able to provide a dump of android 2.3.6 for those that want it once I'm provided with a backup solution as I have read a few people wanting this updated android rom.
This got too close to what I would like liked with bricking this phone.
And I'm not comfortable unless I have a rom backup of this.
Rooting Advice: For anyone with a MTK6573 on Android 2.3.6 trying to root but having issues with super one click make sure you only turn on USB debugging after Android has loaded and just before you plug the usb cable in to run super one click.
I have seen a few thread and posters here about not being able to root the phone and this is the cause that debug needs to be switched on right before you connect and try to root.
Original seller has agreed to send the firmware and flashing stuff on cd for me so I can upload it for you all.
This is a win for MTK6573 Star X19i owners as I'll have the updated 2.3.6 Gingerbread firmware to release for you all root modify etc in a week or so.
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
cybermaus said:
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
Click to expand...
Click to collapse
That's what I read and did to get my scatter as I used cat then used the program linked in that thread to generate the scatter.

[STOCK ROM][QMobile Z8][L5510][WIKO RIDGE 4G|Blu Life One(2015)] Lollipop5.0.2 ROOTED

NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I have created this flashable zip myself and tried this on QMobile Z8 only. It's similar to Wiko Ridge 4G and Blu Life One (2015) in hardware specifications.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing.
NOTE-2:
This flashable zip flashes SYSTEM and BOOT partitions only. If you face ROM abnormal behavior like signals issue, charging problem, device heat up etc. you may flash other partitions as explained here.
Read here more about partitions.
REQUIREMENTS
To flash zip, CUSTOM RECOVERY must be installed. If you don't have one, get here.
If your device is bricked and doesn't boot, try flashing factory firmware as explained here. Even if Download Mode isn't accessible, get official support for your device and pray for it.
STEPS
Download QMobile Z8 Stock ROM Lollipop 5.0.2 Rooted flashable unsigned zip and place it on SD Card or Internal Memory (if you don't going to wipe it).
Reboot into Recovery.
Install ROM zip.
Wipe DALVIK-CACHE, CACHE & DATA.
Reboot. Ignore "No OS Installed" warning (if it comes).
Enjoy!
Thanks for Your Post
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
sadiq1 said:
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
Click to expand...
Click to collapse
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
sadiq1 said:
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
Click to expand...
Click to collapse
dd is a command on UNIX-like operating systems including Linux and Android to copy / dump data. https://www.computerhope.com/unix/dd.htm
Put both img files on internal sd card. Boot in recovery and run these commands from built-in terminal or adb shell:
Code:
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
Make sure "/dev/block/mmcblk0p23" and "/dev/block/mmcblk0p24" are correct partitions to flash or you may overwrite wrong partitions.
Don't forget to make a backup before making experiments.
mirfatif said:
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
Click to expand...
Click to collapse
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
x.ak**** said:
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
Click to expand...
Click to collapse
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
mirfatif said:
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
Click to expand...
Click to collapse
Exactly that's why I prefer them and recommend them.
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------
mirfAtif
where can i write this command
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
I have TWRP this is a GUI program , where can i write command there?
---------- Post added at 06:35 PM ---------- Previous post was at 05:44 PM ----------
I found the terminal to write the command
Let me know where should i keep the files after unzip them
---------- Post added at 06:46 PM ---------- Previous post was at 06:35 PM ----------
Sorry mirfatif
You told me every thing in ur first post , i didnt read it properly,
Thanks ,
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
sadiq1 said:
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
Click to expand...
Click to collapse
Execute these commands:
Code:
ls -l /dev/block/bootdevice/by-name/boot
ls -l /dev/block/bootdevice/by-name/system
sadiq1 said:
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
Click to expand...
Click to collapse
Flash QMobile factory firmware, not Wiko's. If that doesn't fix, there must be hardware problem.
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
sadiq1 said:
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
Click to expand...
Click to collapse
You must be flashing wrong partition. Or try changing different dd binary e.g. from latest busybox version.
Or if you can loop mount system.img with ext4 filesystem, simple copy files to /system partition along with file permissions.
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
sadiq1 said:
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
Click to expand...
Click to collapse
Then other firmware partitions from Wiko must be incompatible with QMobile ROM. Simple is to use a flasher which flashes all partitions. But replace the recovery image with custom recovery like TWRP. After that you may flash this rooted ROM if needed.
yar mujhe app se bat kerni he 03343210716/03028484502
I downloaded some firemware for qmobile , using QFile application
every thing was ready when i click on download there was error "download fail:sahara failvalue canot be null"
sadiq1 said:
yar mujhe app se bat kerni he 03343210716/03028484502
Click to expand...
Click to collapse
English please, it's international forum.
PM me for personal assistance.
mirfatif said:
English please, it's international forum.
PM me for personal assistance.
Click to expand...
Click to collapse
He's saying he wants to have a word with you and he has given his number.
x.ak**** said:
He's saying he wants to have a word with you and he has given his number.
Click to expand...
Click to collapse
I know I'm Urdu speaking :laugh:
Just asking to follow the rules.

Categories

Resources