Hello, I have this phone Alcatel OT 918 (without N or D) with android 2.3.6, i don't find nothing in the forums for the root method, I try superoneclick 2.3.3, unlockroot23 and the OT 918D method, and nothing. I can't root it. Somebody can help me? Thank you.
remigereau said:
Hello, I have this phone Alcatel OT 918 (without N or D) with android 2.3.6, i don't find nothing in the forums for the root method, I try superoneclick 2.3.3, unlockroot23 and the OT 918D method, and nothing. I can't root it. Somebody can help me? Thank you.
Click to expand...
Click to collapse
There is someone who already did root the latest Alcatel 918 with the Android v2.3.6. But sadly he won't share it to anybody. I'm still finding the way to root it via adb. And that's what he did by using adb stuffs.
2.3.6 and Rooted...
just want to share, i successfully rooted my OT-918N from SunCellular PH with Android 2.3.6 using the following scatter.txt and recovery.img file.
the procedure i followed was this tutorial by bluerain28 [TUT]Alcatel StockRom for 918D/M/N.
another thing is i set the flashtool to USB Mode instead of scanning to com ports... hope you get the same results as i did.
thanks bluerain28 for the great tutorial..
noxxious said:
just want to share, i successfully rooted my OT-918N from SunCellular PH with Android 2.3.6 using the following scatter.txt and recovery.img file.
the procedure i followed was this tutorial by bluerain28 [TUT]Alcatel StockRom for 918D/M/N.
another thing is i set the flashtool to USB Mode instead of scanning to com ports... hope you get the same results as i did.
thanks bluerain28 for the great tutorial..
Click to expand...
Click to collapse
Thank you sir for the new scatter text file. That's a very big help.
np sir. we are here to share the experience
Gracias
noxxious said:
np sir. we are here to share the experience
Click to expand...
Click to collapse
Hola, gracias, le voy a probar, te cuento después. Un saludo.
hello, anyone can post 2.3.6 firmware which is flashable via recovery or SP flashtool.. TIA..
2.3.6
obcenity said:
hello, anyone can post 2.3.6 firmware which is flashable via recovery or SP flashtool.. TIA..
Click to expand...
Click to collapse
I will try to do it, i never do it before, so it will take a little time, because i have to see how to make a copy of the rom to send it.
well, thanks fot that!
PLease help... Cannot find USB port!
it's the error message i'm getting...
I have an Alcatel OT 918 (not N/D or anything else) running under v 2.3.6.
I tried the easy solutions (SuperOneClick & UnlockRoot) but as expected nothing worked.
I'd like to use the method proposed above, but as my phone is a 918 and not 918N, will the files in the links work, or will I simply brick my phone?
Thanks
hello all, I also I have the same problem, someone found a solution?
Baracuda86 said:
I have an Alcatel OT 918 (not N/D or anything else) running under v 2.3.6.
I tried the easy solutions (SuperOneClick & UnlockRoot) but as expected nothing worked.
I'd like to use the method proposed above, but as my phone is a 918 and not 918N, will the files in the links work, or will I simply brick my phone?
Thanks
Click to expand...
Click to collapse
I bricked my OT-918 Android v2.3.6 when I tried alternative methods...
I guess it's waiting untill another exploit comes
EDIT:
I downloaded the scatter file from noxxious' attachment but because I bricked a phone already I decided to look up what those files actually are.
Microsoft says:
The ARM development tools use scatter files to describe load regions, each of which might contain one or more execution regions
Click to expand...
Click to collapse
Also saying: Wrong scatter file would mean wrong memory is overwritten which will obviously lead to a brick (eg, phone tries to find OS, but because OS is not written in the correct place it cannot load it. Exactly what happened to my phone)
After some searching I discovered that you can easily retrieve the memory regions with ADB.
commandline:
Code:
adb wait-for-device
adb shell "cat proc/*" > device_info.txt
This will give you a nice text file with much information about your device...
Interesting part is this:
Code:
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00080000 00020000 "pro_info"
mtd3: 00300000 00020000 "nvram"
mtd4: 00020000 00020000 "seccnfg"
mtd5: 00060000 00020000 "uboot"
mtd6: 00600000 00020000 "boot"
mtd7: 00600000 00020000 "recovery" <- Seems like we need this region
mtd8: 00120000 00020000 "secstatic"
mtd9: 00060000 00020000 "misc"
mtd10: 00300000 00020000 "logo"
mtd11: 000a0000 00020000 "expdb"
mtd12: 07300000 00020000 "system"
mtd13: 09100000 00020000 "custpack"
mtd14: 03c00000 00020000 "cache"
mtd15: 09fa0000 00020000 "userdata"
If you think logically (and know a little about hexadecimal stuff) there is no space between the regions...
Meaning we can calculate the addresses of all memory pages. For example (we start at 0x0)
PRELOADER = 0x0 (with size 0x00040000) out of this follows that the next region should be at 0x0+0x00040000 = 0x00040000
meaning:
DSP_BL = 0x40000 (size = 0xC0000)
following that PRO_INFO should be located at 0x40000+0xC0000=0x100000
I'm just posting a little of my research... Maybe someone with more experience knows if I can use the same scatter file as noxxious attached...
@others with an OT-918/918N/D/M: Please also try to retrieve the memory regions so we can compare... Maybe those regions are dynamic. I don't know any android developing
Sorry for bumping, but editing the old post failed on android. App doesnt seem to support it either.
Anyways, I calculated the offsets for my device and they match the new scatter file almost perfectly...
The older file, which I used to brick my previous phone did not match!
Please see attached file for more info...
Greetings
Sent from my ALCATEL ONE TOUCH 918 using XDA
I found this video on Youtube, I hope it helps.
http://www.youtube.com/watch?v=RRdgPgI8cbc
YoursTruly98 said:
I found this video on Youtube, I hope it helps.
http://www.youtube.com/watch?v=RRdgPgI8cbc
Click to expand...
Click to collapse
It's actually outdated...
/forum.xda-developers.com/showthread.php?t=747598 <- 2010 post...
Thanks anyways.
I attached the full pack that enables you to root your Alcatel OT-918 Gingerbread v2.3.6
{
"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"
}
Greetings
Solution
remigereau said:
Hello, I have this phone Alcatel OT 918 (without N or D) with android 2.3.6, i don't find nothing in the forums for the root method, I try superoneclick 2.3.3, unlockroot23 and the OT 918D method, and nothing. I can't root it. Somebody can help me? Thank you.
Click to expand...
Click to collapse
Hello, in this post you have the solution...:
http://forum.xda-developers.com/showthread.php?p=27153234
error 8100
Hello mr.exodia
I've the ot918 (without N or D). My relase is 2.3.6 (6573)
Your tuto doesn't work on my phone.
I've download your files.
After 15 second, I have the following error at step 8 :
SP FLASH TOOL ERROR 8100)
Can not find USB port !
I have somme questions :
The phone sould be on or off when I plugg the cable ?
If it is on, the phone ask me to mount the drive. What should I do ?
May be I don't have the good drivers.
Could you help me please...
Ricky
Good question
Ricky074 said:
Hello mr.exodia
I've the ot918 (without N or D). My relase is 2.3.6 (6573)
Your tuto doesn't work on my phone.
I've download your files.
After 15 second, I have the following error at step 8 :
SP FLASH TOOL ERROR 8100)
Can not find USB port !
I have somme questions :
The phone sould be on or off when I plugg the cable ?
If it is on, the phone ask me to mount the drive. What should I do ?
May be I don't have the good drivers.
Could you help me please...
Ricky
Click to expand...
Click to collapse
Hmm,
I think you don't actually have the drivers... I first downloaded the One Touch Upgrade (/alcatelonetouch.com/nl/downloads/otu/one-touch-upgrade-s-1-7-9-setup.exe)
And I think drivers are installed automatically. (I attached the usb_driver directory, direct copy from that tool)
And your phone must be turned off. Just wait until it's fully powered-off and then plugin USB cable. You should get a "Install Driver?" popup... (If you haven't installed a driver already)
Long story short:
- Install Drivers (Download Tool or use attached file)
- Turn off phone
- Plug in to make sure windows 'knows' the device
- Unplug your phone
- Follow steps of flashing custom recovery
ok !
dear mr.exodia
I've installed your driver and it works perfectly !
My phone is root now !
Thanks a lot...
Ricky
Related
So, there hasn't been any solution to unlock bootloaders of 3rd party certificates, other than multiunlock, seetool2 and semc.
I'm pretty new to this thing... but I'll give it a chance, as nobody did anything in several months.
the_laser posted his solution
His script roots the device, exploits qualcom bug to disable MPU, loads mapper.ko, then excecutes his bootloader patch, then flashes his custom loader.sin
what we lack is the bootloader patch
the_laser left this comment:
the_laser said:
ps.
all that other 3rd-pary unlock tool authors need to do -
- sniff my patched s1boot
- replace S1_SL_Root_xxxx with own
- proudly release new version with words "world first user friendly REAL TRUE TOTALLY SAFE ULTIMATE bootloader unlock blablablablabla"
Click to expand...
Click to collapse
So, insterting mapper.ko maps the next devices
Code:
< /dev/mtd/mtd5ro
< /dev/mtd/mtd5
< /dev/mtd/mtd4ro
< /dev/mtd/mtd4
< /dev/block/mtdblock5
< /dev/block/mtdblock4
Code:
adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 0ce00000 00020000 "system"
mtd1: 03200000 00020000 "cache"
mtd2: 00040000 00020000 "appslog"
mtd3: 0d3c0000 00020000 "userdata"
mtd4: 80000000 00020000 "msm_nand"
mtd5: 00040000 00020000 "userdate"
I wasn't able to read "msm_nand".
I don't know what "userdate" contains, but inside is this "S1_SL_Root_xxxx" that repeats two times. Is this partition the S1boot?
respect to the "my7227bootwrite_*SL" of the laser...
Does anybody has its sources?
Androxyde flashtool plugin comes with a third my7227bootwrite_omniusSL. This one restores the bootloader lock of omnius unlocked phones... Who made this one and how did (s)he made it?
Finaly, i tried disassembling "my7227bootwrite_*SL". I wasn't able to find the patch or the nand image inside. the debug/error messeges, state that it sets some mtd partition in raw mode.
So, I'll start comparing the images after and before the_laser patches...
Questions:
Does anybody have a compiled mtd_utils for this device?
How do I enable raw mode nandread for a partition/block?
What is inside mtd5 and mtd4?
Am I near of a mini brick?
skirhir said:
What is inside mtd5 and mtd4?
Am I near of a mini brick?
Click to expand...
Click to collapse
a: Yes...
I was unable to access to de oob area...
And I was unable to find the image inside the patcher binary, so:
Unlocked with my7227bootwrite_setool2
made a "nandump -o" with busibox(I was unable to access de oob area).
edited the dump and replaced S1_SL_Root_xxxx with omnius one...
made a (flash_erase 0 0) with mtd_utils
made a nandwrite (no flags) with mtd_utils (failed to write with the busybox one).
checked that the image was correctly patched. No difference with the original dump.
Reboot...
No boot, no flashmode, no nothing...
If anyone can point the mistake in the flashing process...
Now I'm trying to resurrect my shiny brick (any Ideas to make a test point matrix connector, or the name of that connector?)
Conclussion: do not try this at home.
unlock bootloader
I know this is not the answer that this thread was meant to find, but omnius has updated its omnius for SE, and now supports bl unlock for the mini, they still will ask for a license to do this, but the good news is that right now its free for a promo that lasts till the 9th i think, anyways i unlocked my bootloader free a few minutes ago without purchasing a license and wanted to share with anyone in the same problem of sim unlocked with omnius that couldnt unlock their bl
hello everyone,
I am using a Motorola device XT390(based on MTK 6573),it is nice except for the limited roms and several useless appliciations in the stock rom.I really want to get it rooted and get those appliciations deleted.I have tried many diffierent kinds of ways I found via google,but none is working for me so far.Is anybody else here using this device or XT389,has anybody succeeded rooting it?
I have read some technical topic here regarding the MTK 6573 platform,does that necesarilly mean,if I can install CWMR mean I will be able to root it?How is the system partition mounted during starting,via boot.img? A mess in my mind now.
Any information will be highly appricated,
Thanks
are you successed in XT390 rooting?
i've tried methods from chinese forums (zergRush root vio MT6513_MT6573_ROOT.exe files) - no success.
also i've tried to get bootloader unlock code (info on motosite: hhtp:/ /motorola-global-portal.custhelp.com/ app/ standalone/ bootloader/ unlock-your-device-a/), but fastboot returns nothing (no attached devices in fasboot, but 1 attached in adb).
i dont try to install CWMR through CWMR Touch Installer.
if you have any news about root access on XT390, please let me know!
You can boot in recovery with MTKdroid.
I need root too. Whith root this device can performe much better.
lenzexe said:
You can boot in recovery with MTKdroid.
I need root too. Whith root this device can performe much better.
Click to expand...
Click to collapse
I've found ssomething on redigua.com/how-to-root-motorola-motosmart.html but I'm a noob and I don´t know if makes sense. Can someone with more background take a look?
Thanks
This is an updated method on how to root your Motorola MotoSmart.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your Motorola MotoSmart into development mode by going to Settings->Applications->Development and turn USB debugging on.
Third, connect your Motorola MotoSmart to your computer and set your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers. (You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste, easier!)
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select temp root and wait until its done.
Eighth,go back to command prompt and type:
adb shell
su
If you get a pound(#) sign, that means you have temp root, which just gives you temporary root so we can now install permanent root.
Ninth, lets backup our WiMax 4G RSA just in case we lose it during installation of new ROMs.
Type:
Mkdir /sdcard/nandroid/RSA-PR-BACKUP
Cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
busybox sed -n /BEGIN CERTIFICATE/,$p /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
Tenth, go back to command prompt and type the following:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip and after about 3 minutes ask you if you want to install PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install the new zip file, should take about 10 minutes. Go grabs some coffee and come back.
Eleventh, reboot when its done by hitting the volume up button.
It will reboot into the OS and we dont want that so takes the battery out and puts it back in it. Then go back to the bootloader by hitting the power button while holding down the volume down button.
Choose Bootloader and wait until you get the triangle sign and type:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery &
Go back to your Motorola MotoSmart and you should see green menus.
Choose install zip from sd card and choose unrevoked-forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename PC36IMG-MR.zip to PC36IMG.zip.
Then power off your Motorola MotoSmart, power back on by pressing Power Button while holding down the Volume Down button, this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the Volume Up button.
then reboot your Motorola MotoSmart, your device should now be rooted with Recovery menu then you can flash new ROMs for Motorola MotoSmart.
Click to expand...
Click to collapse
Cris RF said:
I've found ssomething on redigua.com/how-to-root-motorola-motosmart.html but I'm a noob and I don´t know if makes sense. Can someone with more background take a look?
Thanks
Click to expand...
Click to collapse
any success?
mobiclip said:
any success?
Click to expand...
Click to collapse
We will only succeed when we can unlock the bootloader. For that so we need access to the fastboot protocol, witch is bloked (at least in my rom version).
erlyneto said:
We will only succeed when we can unlock the bootloader. For that so we need access to the fastboot protocol, witch is bloked (at least in my rom version).
Click to expand...
Click to collapse
It's good to know it,although it is rather disappointing.Is that possible to modify the binary rom?To do something with the bootloader,or even only to remove the applications not used often to make larger inner storage space,then flash.
Thanks a lot!
mobiclip said:
any success?
Click to expand...
Click to collapse
I failed on step 9,"Seventh, go to your phone and launch Z4Root app. Then select temp root and wait until its done.
Eighth,go back to command prompt and type:
adb shell
su
If you get a pound(#) sign, that means you have temp root, which just gives you temporary root so we can now install permanent root."
When I launch Z4Root app to get temp. root,it never finish.:crying:However, I continued and tried "su" to get temp. root access from adb shell,it is said "permission denied"
Rooted finally,can be one key rooted by a software,but no english version,it is a pity.
Tried on XT390,should be OK for her sister XT 389.:laugh:
http://www.gsmfans.com.br/index.php?topic=313996.0
this method works
lenzexe said:
http://www.gsmfans.com.br/index.php?topic=313996.0
this method works
Click to expand...
Click to collapse
It worked on my XT389 :good:
In order to reader the article i have to registrate on the forum can someone post the method? thank
TheProspi said:
In order to reader the article i have to registrate on the forum can someone post the method? thank
Click to expand...
Click to collapse
Register with a fake email, no activation is needed to login
Sent from my GT-S5830L using xda-developers app
This method works for my XT390
This method works for my XT390. Now I'm rooted
But the question is - i've removed all stock-chinese apps, but internal storage still full (Root Uninstaller free app used).
SOLVED: clear stock-chinese apps data from /data/dalvik-cache.
In order to reader the article i have to registrate on the forum can someone post the method
Click to expand...
Click to collapse
The method is quite simple:
1) install moto drivers for XT390 (i've used official app from motosite - motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/~/drivers)
2) connect phone, active USB debugging. Windows will show your phone at traybar as "android phone".
3) install AppLocale (microsoft utility for launch chinese apps on windows - download.microsoft.com/download/5/6/8/568a8caf-29c4-43ec-a10f-97730f26977e/apploc.msi)
WARNING - here's the video of installaton procees, some tricks detected: youtube.com/watch?v=9t9iZJBwNA0
4) install chinese app for rooting (simple): products.mgyun.com/api/downjump?productcode=romasterlab
5) after installation, you got 2 shortcuts on your desktop (1 - blue, 2 - blue with yellow), rename them to latin names (root1, root2);
6) launch AppLocale, click next, choose root1 shortcut (blue icon) in the dialog, click NEXT, appLocale detects language, NEXT, FINISH.
7) chinese app starts & tries to detect your phone. If everithing ok - it will show XT390 & sync some data (bars in bottom):
shot is here - imgfans.com.br/NR/Abr13/05/02.png
8) click root
shot is here - imgfans.com.br/NR/Abr13/05/03.png
9) process on, phone will reboot 2-3 times, when it boot finally - you're root
10) Try progs, that use root rights.
WARNING - Do not disconnect usb cable while phone is rooting.
work under root on XT390
Hi, guys!
I've made full backup of my phone. Used this tut - http://forum.xda-developers.com/showthread.php?p=26802588. Works great!
Also i've unpacked boot.img & recovery.img, that was saved during backup look this tut for details: http://forum.xda-developers.com/showthread.php?t=1587411
Now i try to flash my phone via preloader. First of all, how i've entered in preloader mode - install moto drivers, switch off phone, push VOLDOWN button, connect USB. Windows will activate Preloader VCOM driver (check at Control Panel, COM port branch).
I'm using this tut: http://forum.xda-developers.com/showthread.php?t=1982587
To use SP Flash you need scatter file. I've created it with this tut: bm-smartphone-reviews.blogspot.pt/2012/04/creating-rom-dump-of-your-mt65x3-device.html
First problem. Cannot to enter in stock recovery utility PWR+VOLUP - no result, PWR+VOLUP+VOLDOWN - no result.
SOLVED:
1) Power UP phone;
2) when china-logo/moto-logo will apear (or after 1-2 secs) press VOLUP+VOLDOWN
3) recovery will launch & u see standard android recovery img (droidtune.com/wp-content/uploads/2012/07/20684-nexus_one_android_hard_reset_3-150x150.jpg)
4) use VOLUP & VOLDOWN to browse recovery menu, PWR for choise.
5) here's the video, that helps me to enter recovery: www.youtube.com/watch?v=cwHWILMlctI
Second problem - SP Flash Utility couldnot connect to device. I try to run memory tests & save some roms from phone - no result. Tried 2 versions: v2.1134.00 & v3.1224.01
I'm planning to flash CWMR.
My flash map is:
$ su
# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00040000 "preloader"
mtd1: 00180000 00040000 "dsp_bl"
mtd2: 00300000 00040000 "nvram"
mtd3: 00040000 00040000 "seccnfg"
mtd4: 00080000 00040000 "uboot"
mtd5: 00600000 00040000 "boot"
mtd6: 00600000 00040000 "recovery"
mtd7: 00140000 00040000 "secstatic"
mtd8: 00080000 00040000 "misc"
mtd9: 00040000 00040000 "logo"
mtd10: 00a00000 00040000 "flex"
mtd11: 000c0000 00040000 "expdb"
mtd12: 00280000 00040000 "nrstdata"
mtd13: 101c0000 00040000 "system"
mtd14: 03c00000 00040000 "cache"
mtd15: 096c0000 00040000 "userdata"
in Terminal Emulator:
$ su
dd if=/sdcard/recovery.img of=/dev/mtd/mtd6
I'm planning to flash repacked CWMR for mtk6573 (port CWMR for any mtk6573 - http://forum.xda-developers.com/showthread.php?t=1825722), there is link to: mediafire.com/view/?1zc473vx18g69bn
So final question - could i brick my phone via recovery flashing (flash through TE)?
UPDATE. dd fails with "Invalid argument".
Any ideas?
cenzored said:
Hi, guys!
I've made full backup of my phone. Used this tut - http://forum.xda-developers.com/showthread.php?p=26802588. Works great!
Also i've unpacked boot.img & recovery.img, that was saved during backup look this tut for details: http://forum.xda-developers.com/showthread.php?t=1587411
Now i try to flash my phone via preloader. First of all, how i've entered in preloader mode - install moto drivers, switch off phone, push VOLDOWN button, connect USB. Windows will activate Preloader VCOM driver (check at Control Panel, COM port branch).
I'm using this tut: http://forum.xda-developers.com/showthread.php?t=1982587
To use SP Flash you need scatter file. I've created it with this tut: bm-smartphone-reviews.blogspot.pt/2012/04/creating-rom-dump-of-your-mt65x3-device.html
First problem. Cannot to enter in stock recovery utility PWR+VOLUP - no result, PWR+VOLUP+VOLDOWN - no result.
SOLVED:
1) Power UP phone;
2) when china-logo/moto-logo will apear (or after 1-2 secs) press VOLUP+VOLDOWN
3) recovery will launch & u see standard android recovery img (droidtune.com/wp-content/uploads/2012/07/20684-nexus_one_android_hard_reset_3-150x150.jpg)
4) use VOLUP & VOLDOWN to browse recovery menu, PWR for choise.
5) here's the video, that helps me to enter recovery: www.youtube.com/watch?v=cwHWILMlctI
Second problem - SP Flash Utility couldnot connect to device. I try to run memory tests & save some roms from phone - no result. Tried 2 versions: v2.1134.00 & v3.1224.01
I'm planning to flash CWMR.
My flash map is:
$ su
# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00040000 "preloader"
mtd1: 00180000 00040000 "dsp_bl"
mtd2: 00300000 00040000 "nvram"
mtd3: 00040000 00040000 "seccnfg"
mtd4: 00080000 00040000 "uboot"
mtd5: 00600000 00040000 "boot"
mtd6: 00600000 00040000 "recovery"
mtd7: 00140000 00040000 "secstatic"
mtd8: 00080000 00040000 "misc"
mtd9: 00040000 00040000 "logo"
mtd10: 00a00000 00040000 "flex"
mtd11: 000c0000 00040000 "expdb"
mtd12: 00280000 00040000 "nrstdata"
mtd13: 101c0000 00040000 "system"
mtd14: 03c00000 00040000 "cache"
mtd15: 096c0000 00040000 "userdata"
in Terminal Emulator:
$ su
dd if=/sdcard/recovery.img of=/dev/mtd/mtd6
I'm planning to flash repacked CWMR for mtk6573 (port CWMR for any mtk6573 - http://forum.xda-developers.com/showthread.php?t=1825722), there is link to: mediafire.com/view/?1zc473vx18g69bn
So final question - could i brick my phone via recovery flashing (flash through TE)?
UPDATE. dd fails with "Invalid argument".
Any ideas?
Click to expand...
Click to collapse
The chinese method works just fine.Just follow the steps described above> Ive rooted the xt389, factory reset, then always on for the developer option.Apps in root can be uninstaled, but do this before the full reset, or you can encounter some errors when you install some apps.
The Romaster Lab program also works in a Spreadtrum SP6820 :victory:
Hi All,
I have this rather exotic MediaTeK MT6575 device, called the 尼彩 epade S7, running android 2.3.6.
Specs are:
Hardware : MT6575
Model : epade S7
Build number : X300_N09_T08
Build date UTC : 20120905-031644
Android v : 2.3.6
Baseband v: MAUI.11AMD.W11.50.SP.V14.P2, 2012/07/14 11:46
Kernel v : 2.6.35.7 ([email protected]) (gcc version 4.4.3 (GCC) )
I have three issues with this device
1. To root this device I would like to do an update, using an update.zip file which I install through the recovery mode. The strangest thing is that in recovery mode. I can't select update from sdcard. I can enter recovery mode by holding volume up and the power button. In the recovery mode I can let the menu appear and disappear with the home button, I can navigate the menu with volume up and volume down, but I cannot select any options. The only way out is to remove the battery. Do any other phones suffer from this issue with the recovery mode?
2. I have extracted my whole ROM using SP flash tool, which looks like:
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00300000 00020000 "nvram"
mtd3: 00020000 00020000 "seccnfg"
mtd4: 00060000 00020000 "uboot"
mtd5: 00500000 00020000 "boot"
mtd6: 00500000 00020000 "recovery"
mtd7: 00120000 00020000 "secstatic"
mtd8: 00060000 00020000 "misc"
mtd9: 00300000 00020000 "logo"
mtd10: 000a0000 00020000 "expdb"
mtd11: 0d000000 00020000 "system"
mtd12: 03c00000 00020000 "cache"
mtd13: 0d620000 00020000 "userdata"
This is different from the GooPhone Y5 and the Thunderbird 4S phones. I tried to flash a custom recovery for a Goophone Y5 through the SP flash tool, but that failed and resulted in the error:
BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054)
[EMI]obtain DRAM Failed!
[HINT]lease check your load matches to your target which is to be download.
I guess the GooPhone recovery is smaller (4836 kB) than my recovery and that is why this error pops up. Does anybody have experience with this kind of errors? The strange thing is that even when I try to flash my own recovery.img (5120kB) I get this error.
3. Is it possible to flash a CWM or any custom recovery image on this MT6575 phone? I have no experience with android kitchen, but other threads report success.
I have included my recovery.img in this post.
Any help is appreciated.
Try this...
www[dot]droidextra[dot]org/2012/10/17/install-clockworkmod-on-micromax-a52-aisha[dot]html
I own a Micromax A52 with the same config... This worked for me. Also remember to use the scatter file of your phone... Search around you'll get it. Or try the attachment!
u can select an option in recovery by using the menu key
sunny624 said:
u can select an option in recovery by using the menu key
Click to expand...
Click to collapse
Nope, I cannot select with the menu key. No physical key seems to work.
ash1794 said:
Try this...
www[dot]droidextra[dot]org/2012/10/17/install-clockworkmod-on-micromax-a52-aisha[dot]html
I own a Micromax A52 with the same config... This worked for me. Also remember to use the scatter file of your phone... Search around you'll get it. Or try the attachment!
Click to expand...
Click to collapse
Thanks, I have tried this, but my phone won't flash anything. After I start the download with F9, the process starts (red bar) but then it stops and replies BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054). I tried holding the download start (volume down) button all the way, but that won't work either.
Has anyone seen this error before?
e-lime said:
Thanks, I have tried this, but my phone won't flash anything. After I start the download with F9, the process starts (red bar) but then it stops and replies BROM ERROR:S_DL_GET_DRAM_SETTING_FAIL(5054). I tried holding the download start (volume down) button all the way, but that won't work either.
Has anyone seen this error before?
Click to expand...
Click to collapse
yes. the phone is probably locked.
google for engineering points, for example for the candy mt6575 phone.
You either need to prep a cable, or open up the phone and connect two points to get it to switch to flashable mode.
I did not find a cable mod, I opened my Daxian G20 up and soldered wires to the 6 points under the battery.
Check china-phone.ru if your model is there. It might be added any time with instructions.
If you do find a way, please post back and hit thanks if it helped .
Hi there, long time reader, first time contributor.
[Edit: Sorry I just read this should go in Q&A and I do apologise. Can a moderator please move if appropriate?]
I'm hoping some of you on this forum can help me with a Rockchip 3066 TV Box I am working with. The situation is thus:
I have a number of these boxes, 12 in my possession currently with more on the way
I have successfully rooted the boxes through ADB, none of the one click or other methods worked, but rooting through ADB did.
I have tried using rkdump but unfortunately it cannot find the update.img which I assume to mean it doesn't have one.
What I would like to do is setup a box exactly how I want and then image this off and copy the image to the others
As I mentioned, even though it's a Rockhip based chipset, there's no way I can identify to extract any kind of update.img from it. I have seen through other postings that some of the 3066 based boards no longer use the same cramfs file header/structure the previous 2xxx chipset used so this is probably why.
The big thing is, I just want to mirror the setup to other hardware of exactly the same pedigree.
Here is the MTD/partition map:
Code:
1|[email protected]:/dev # cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 6ac00000 00004000 "user"
My thoughts are I could just dd off the partition to the sd card, and dd this back onto the other devices. I could write a shell script easy enough that could do all this, but obviously trial and error could be an expensive process if I start bricking boxes.
So a couple of questions:
Would the DD thing work?
If so which MTD partition(s) should I dd off
any ideas on what the precise format of the copy to and from commands should be assuming this is the way to go about it?
Is this the wrong way to go about it? Are there better suggestions / ways of achieving this i.e. mirroring devices?
There's a number of applications that ship on the box by default too I need to remove as root, and I'd like to automate everything, hence the idea of imaging as opposed to stepping through all the tasks manually.
Use rkdump to dump kernel, boot and recovery (use /dev/block/mtdblock# as an argument), dd'ing system partition should work, but i wouldn't suggest it because it can be modified during creating dump, and this may corrupts image , so its better to copy all files from system using adb and then create ext4 image using make_ext4fs.
After you done use RKAndroidTool to flash dumped images to your device
lolet said:
Use rkdump to dump kernel, boot and recovery (use /dev/block/mtdblock# as an argument), dd'ing system partition should work, but i wouldn't suggest it because it can be modified during creating dump, and this may corrupts image , so its better to copy all files from system using adb and then create ext4 image using make_ext4fs.
After you done use RKAndroidTool to flash dumped images to your device
Click to expand...
Click to collapse
Thanks very much for your reply, unfortunately rkdump cannot find the boot and recovery.img in any of the mtdblocks, only kernel.img. I had read this is because of the FS Rk3066 uses for some images.
Hence the DD route.... but as you said, there is a possibility of corruption.
DoctorDbx said:
Thanks very much for your reply, unfortunately rkdump cannot find the boot and recovery.img in any of the mtdblocks, only kernel.img. I had read this is because of the FS Rk3066 uses for some images.
Hence the DD route.... but as you said, there is a possibility of corruption.
Click to expand...
Click to collapse
You can dd boot & recovery image safely, then strip 0xFF in hex editor from end if you need lower size of images. Try my tool I attached.Type:
"dump.bat info", to get partition structure you will need later to flash the images, then
"dump.bat recovery o",
"dump.bat kernel",
"dump.bat boot o",
"dump.bat system"
Good luck.
Hi
these are my random online notes. Being sometimes dis-organised, I need to focus on some things which in hindsight may be trivia but better to put them out there so others can add knowledge if they are free to do so.
Please note this is not a post to specifically answer questions but general research and observations of what I think I know. And I may be wrong
I may also ramble on about some of my intentions
#######################
Stock tablet ROM but rooted.
Kernel size reported on unpack follows/// md5 second bit
3673028 kernel // 947125799e8124bddcb9737a347e98ec kernel
TWRP kernel details are
3676160 kernel // e421c8e09888728b6a43aa7a63288074 kernel
########################
I think I will use the boot image kernel
#######################
In stock normal boot, AFAIK usb-otg works as expected.
in TWRP, so far I can't get it to work.
In comparing the init commands and some files and modules in stock I am leaning this way
stock has 2 modules that begin with the string rk as per image
{
"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"
}
research suggests the first one, ipp is useful for screen stuff and may resolve some upside down issues so I may inject that into any TWRP mod
The second module apparently is required for usb-otg. however this is the current config lines
on early-init
insmod /rk29xxnand_ko.ko.3.0.8+
insmod /rk29xxnand_ko.ko.2.6.32.27
write /sys/bus/platform/drivers/usb20_otg/force_usb_mode 2
write /sys/devices/virtual/display/HDMI/scale 80
Click to expand...
Click to collapse
Checking other init lines I see a trend that before we write any configs we turn off a service and re-enable, restart it at the end of the config as per these type entries
write /sys/class/android_usb/android0/enable 0
blah blah
write /sys/class/android_usb/android0/enable 1
now I consider otg as a USB style function and most usb entries have above formula but I may be wrong.
Testing it may prove something but unfortunately I believe I should make only small changes so I can trouble shoot my own brain .....giggles.....
thanks for reading.
Feel free to add any notes for mediapad
You do realize you can run Abdul's recovery for RK2918 tablets? I use that and it seems much better than the one made here for the Mediapad 7 lite specifically. I'm not sure about USB OTG working (haven't tested) and IIRC I also changed the partition sizes as well to eliminate the useless cust partition and I love it!
To change sizes you gotta edit some addresses in misc before flashing and you must make sure to edit fstab accordingly.
Oh and to get the recovery running - the device has an unified image with kernel and recovery like most standard Android devices (RK2918 usually has it separate).
Simply take the recovery image for the RK2918 (TWRP by abdul), take its ramdisk, put the stock zimage and make the final recovery.img with mkbootimage for rockchip. (This is coming all from my memory atm)
It was a while ago since I modded this tablet, so I am a bit rusty with it, but I got it again just yesterday so I will start hacking the thing again.
If in any case you want me to, I can dd the tablet and send images away (except big files due to upload speed).
@xan1242 this is great news... Hope you guys can make cm rom for this tablet
There already are ports for RK2918 done numerous times (namely by CrewRKtablets, props to them!) and I almost did make it to run on the Mediapad 7 Lite, but it got stuck at the part where after it caches the programs it just holds at "Starting applications". This has all been done, of course, with the stock kernel image.
I couldn't compile from the sources for some reason, it didn't want to boot. Also yes, Huawei released the kernel sources specifically for Mediapad 7 Lite. It doesn't matter if it's the w or u variant as they're compatible. I can confirm that since I am running a modified stock ROM of the S7-931u on my S7-931w. I'm not sure which kernel it is, but, nevertheless, it can be configured which variant you've got during compilation anyway.
As far as CM11 goes, I tried porting CWM recovery off of the main branch as well, but the display didn't work with the stock kernel.
OOH goody I should keep quiet but I have just rememebered while I had stock recovery I had downloaded firmware from here
http://consumer.huawei.com/en/support/downloads/
unfortunately when I unzip it, its not like a traditional official zip containing mulitiple images like boot and system but only one big file called update.app.
Anyhows that might explain why my kernel differs from our TWRP.
######################################
xan1242 in post 4 you mention you almost had a new ROM running.
forgive me for mentioning it, but you did flash both the boot image and the kernel area?
I know you may have changed your fstab but for a stock rom, kernel is sitting at mtd1
also known as /dev/mtd/mtd1 as per mtd outputs hidden here
OR try /dev/block/mtd/by-name/kernel
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 00400000 00004000 "backup"
mtd5: 00c00000 00004000 "oeminfo"
mtd6: 00800000 00004000 "vrcb"
mtd7: 01000000 00004000 "reserved"
mtd8: 20000000 00004000 "cust"
mtd9: 1cc00000 00004000 "system"
mtd10: 10000000 00004000 "cache"
mtd11: 01000000 00004000 "userdata"
mtd12: 00400000 00004000 "kpanic"
mtd13: 9a800000 00004000 "user"
Click to expand...
Click to collapse
aus9 said:
xan1242 in post 4 you mention you almost had a new ROM running.
forgive me for mentioning it, but you did flash both the boot image and the kernel area?
I know you may have changed your fstab but for a stock rom, kernel is sitting at mtd1
also known as /dev/mtd/mtd1 as per mtd outputs hidden here
OR try /dev/block/mtd/by-name/kernel
Click to expand...
Click to collapse
The listing you got there is the default partition table indeed which can be changed as per one single text file which has got a specific name I can't remember (located in the folder with the images for the Rockchip flash tool), but you'd usually flash it in the "misc" partition, hence it being the partition 0.
Here is the thing with the kernel - as I said, with this device the images are unified just like on normal Android devices (only on Mediapads as far as Rockchips go) which means - the kernel is inside "boot" and "recovery" partitions respectively.
The "kernel" partition you see there seems to be nothing more than either a fallback or a leftover for the flash tool so it could still work. I believe it still may be necessary for the device to start up, but it may just be a dummy to which you can put anything. (zImage only goes here)
So when you boot normally it boots the "boot" partition, so if you need to change the kernel, change it like you would for any other device. IIRC the regular mkbootimg works fine!
When you go to recovery (hold vol up + vol down), it'll boot the "recovery" partition and its own kernel and everything so the recovery is treated entirely as its own part.
So yeah, I changed the boot partition by separating the zImage from the stock boot dump, modifying the ramdisk as necessary and then remaking the boot image with mkbootimg with some special addresses (I think, don't take my word for the address part, I don't remember exactly as of yet, will have to do things again since I deleted most of the stuff)
let me take the opportunity to mention I have edit top post to encourage anyone to add more notes on mediapad.
your information is very valuable, but I do have some issues so have not tested what you have said on the kernel or remodding my own partition table.
I would agree tho, that its not very efficient to rely on a kernel from boot image and some other flash storage.
As a side note, I have been attempted to flash various re-modded TWRPS, and at this stage with no luck, so the kernel is a bit of fixation for me at the moment.
That and keeping aussie beach babes from smothering me.....giggles
I have still not converted my boot image to insecure mode, and yes I know how to
instead I am using an apk to give me insecure mode called .......adbd insecure by Chainfire
in order to overwrite, I use a simple read-write script I made executable sitting on removeable sdcard = /sdcard2 with contents
#!/system/bin/sh
mount -o remount,rw /system
mount | busybox grep system
Click to expand...
Click to collapse
make it executable with a rooted device by commands
Code:
su
busybox chmod +x /sdcard2/rw.sh
result of actioning script is showing in image
Notice that we are looking for rw against /system and anything else is bad.
the balance of the output of mount for system has been cut from image as its irrelevant to discussion
hope that helps someone
mtd1 the kernel......
just took an image of it using formula
dd if=/dev/mtd/mtd1 of=/sdcard2/kernel.img
2) tried to unpack it using Linux executable imgrepackerrk.......gives me error unknown format detected
3) so tried Linux command strings against it with the following result for any interested?
Code:
strings kernel.img
RKOEM10
RKOEM10
[email protected]:~/Downloads$file kernel.img
kernel.img: data
[email protected]:~/Downloads$ ls -al
total 8280
drwxr-xr-x 2 gordon gordon 4096 Jan 31 13:29 .
drwxr-xr-x 21 gordon gordon 4096 Jan 31 13:12 ..
-rwxrwxr-x 1 gordon gordon 74456 Feb 17 2014 imgrepackerrk
-rw-rw-r-- 1 gordon gordon 131 Jan 31 13:29 imgrepackerrk.ini
-rw-r--r-- 1 gordon gordon 8388608 Jan 31 2015 kernel.img
It does nothing for me......but hey I am just the messenger
You should dd using the ones in "by-name" since it's kind of broken or just use TWRP.
Besides, it seems it's just the addresses there for the kernel, the rest is padding.
Code:
http://puu.sh/fhpXv/45b3326285.7z
Check this file out and tell me if it differs from yours. If it does in any case, then there are the addresses for the kernels in the other two partitions. If not, then it's something else I don't know about. I don't think I've ever touched this file even.
By the way, the ROM I'm using is this one:
Code:
http://4pda.ru/forum/index.php?showtopic=395683&st=840#entry23349533
It's based off of the stock one and it's basically just a cleaned up ROM. Only thing is you'd need to survive through is the Russian. To fix that you just need to get MoreLocale and change the languages.
There you can find some info about flashing 'n' other stuff.
I just looked into the images from the ROM as well - misc is just random padding again, kernel is the same thing I got and the partition table is defined in a single file called parameter. You can edit that file with any text editor.
There you will find the CMDLINE where the partition table is defined as well under mtdparts.
parameter
Code:
FIRMWARE_VER:0.2.3
MACHINE_MODEL:MediaPad 7 Lite
MACHINE_ID:007
MANUFACTURER:HUAWEI
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 2929
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
COMBINATION_KEY: 0,6,A,1,0
CMDLINE: quiet console=ttyS1,115200n8n androidboot.console=ttyS1 init=/init initrd=0x62000000,0x800000 mtdparts=rk29xxnand:[email protected](misc),[email protected](kernel),[email protected](boot),[email protected](recovery),[email protected](backup),[email protected](oeminfo),[email protected](vrcb),[email protected](reserved),[email protected](cust),[email protected](system),[email protected](cache),[email protected](userdata),[email protected](kpanic),[email protected](user)
Format is
Code:
[email protected]
xan1242
You should dd using the ones in "by-name" since it's kind of broken or just use TWRP
Click to expand...
Click to collapse
I wish I knew this early as I had made a number of flashing with modified TWRPS, all not booting and always thought it was just me not being good enough to know what I am doing with a Rockchip.
So I plan to redo one of my better efforts just to see if it boots later.
2) I downloaded and inspected your file here
Code:
md5sum kernel.img
c497d0e079117e8a08c3e3894237811d kernel.img
[email protected]:~/Downloads$ ls -al
total 8208
drwxr-xr-x 2 gordon gordon 4096 Feb 1 06:53 .
drwxr-xr-x 21 gordon gordon 4096 Feb 1 06:45 ..
-rw-rw-r-- 1 gordon gordon 5529 Feb 1 06:53 kernel.7z
-rw-rw-r-- 1 gordon gordon 8388608 Jan 31 23:10 kernel.img
strings kernel.img gives me
RKOEM10
RKOEM10
That size looks to me to be padded already. As the size/ erase size from stock mtd output is
mtd1: 00800000 00004000 "kernel"
Click to expand...
Click to collapse
the 8 number I believe means 8 megs or 8 x 1024 x 1024 = 8388608 bytes and so we agree
the rest is padding.
Click to expand...
Click to collapse
but it does not help me know if we have same kernel or not sorry. Can you at least tell me what kernel version the Russian ROM is please?
I use Linux tool imgrepackerrk from here
http://forum.xda-developers.com/showthread.php?t=2257331
ignore my next bit.....its just a whine by me.....after I pull my fist out of the monitor
I have found 3 main methods.....ignoring adb....to flash recovery from within normal bootup
dd if=newimagename of=/dev/mtd/md3
dd if=newimagename of=/dev/block/mtd/by-name/recovery
dd if=newimagename of=/dev/block/mtdblock3
I have also apppended those lines with bs=512 count=32768, giving a total of 6 commands
all of them show output of records in matching records out
but I am not getting recovery on boot up for any of them, consistenly so sorry if that looks bad.
2) it may be that I have been long pressing to turn off on failure and other pressing buttons.......that my device is spanking me for treating it without respect
b) but then if what I just said is true, this device is unreliable. I mean no great disrespect here either as it only costs A$50 in australia
end of grumble
ok so had modest success on a TWRP mod and flash using mtd3 method
the working bits are in images hidden, the really bad bits I am too shy to show but mount is not getting access to my fstab entries such as for system which in showing as 0 MB to backup
Yes.....thats not good.
Also I added some more flags to show more options in the mount area of TWRP but inserting usb-otg after boot or on reboot.....does not allow me to CHECK the box and mount it.
In first image, removeable sdcard means the microsd card you push into slot and the bottom entry is for OTG, I might amend the flags later but only when I resolve the fstab to mount issue.
working fstab entry is
/sdcard2 vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 flags=display="removeable sdcard";wipeingui;storage;removable;backup=0
OTG failure line is currently
/usb-otg vfat /dev/block/sda1 flags=display="USB Storage";storage;wipeingui;removable
and yes I must make that auto instead of vfat
system faulure line is attempt to use block style and yes I must try by name
/system ext4 /dev/block/mtdblock9 flags=display=system;wipeingui;backup=1
Drat I should I think remove wipingui for sdcards
#######################
heck I think I just found a gremlin?
in normal boot up the command
Code:
cat /proc/mtd
gives me the mtd list including this line
mtd9: 1cc00000 00004000 "system"
looks good but we know that our current TWRP has this entry for its fstab line
/system ext4 /dev/block/mtdblock10
WT?
well I know and am fairly sure pogs24ever has done a TWRP backup and restore so mtd10 must be for system and not mt9
only way to confirm is for me to try a new image with corrected fstab
well well well
lets go and have a peek at the current TWRP backup log created when doing a backup. I backed up only boot, data and system
Q If anyone thinks I should back up more, please say so.
############
now let me focus on mtd.....which I know scant about.....in normal boot up......recovery is mtd3
in twrp log its not the same!!
and others also have changed. so frustrated I am with this blinkin mtd system I thought I would share a link to my log and maybe some kind soul can tell me where to go.....LOL
https://www.dropbox.com/s/xa6uy8f4akauffo/twrp-current-recovery.txt?dl=0
if not thanks for reading.
Just to repeat ......this is the current TWRP not my mod as my mod contains more errors than current.
Hi Guys...
You can check my conversation with abdul on his page... here's the first page........ http://www.freaktab.com/showthread.php?10466-Unofficial-TWRP-2-7-0-0-for-Rockchip-s/page4
pog2rever
I can see your recovery log from that other site.......so in case it helps others let me take a snip from yours that our friend also saw at post 95, page 5
I:Actual command is: 'cd "/" && cat proc/mtd 2>&1'
dev: size erasesize name
mtd0: 00400000 00004000 "parameter"
mtd1: 00400000 00004000 "misc"
mtd2: 00800000 00004000 "kernel"
mtd3: 01000000 00004000 "boot"
mtd4: 01000000 00004000 "recovery"
mtd5: 00400000 00004000 "backup"
mtd6: 00c00000 00004000 "oeminfo"
mtd7: 00800000 00004000 "vrcb"
mtd8: 01000000 00004000 "reserved"
mtd9: 20000000 00004000 "cust"
mtd10: 1cc00000 00004000 "system"
mtd11: 10000000 00004000 "cache"
mtd12: 01000000 00004000 "userdata"
mtd13: 00400000 00004000 "kpanic"
mtd14: 18880000 00004000 "user"
Click to expand...
Click to collapse
now from our post 5.....with a normal boot up, I used cat /proc/mtd giving us
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 00400000 00004000 "backup"
mtd5: 00c00000 00004000 "oeminfo"
mtd6: 00800000 00004000 "vrcb"
mtd7: 01000000 00004000 "reserved"
mtd8: 20000000 00004000 "cust"
mtd9: 1cc00000 00004000 "system"
mtd10: 10000000 00004000 "cache"
mtd11: 01000000 00004000 "userdata"
mtd12: 00400000 00004000 "kpanic"
mtd13: 9a800000 00004000 "user"
Click to expand...
Click to collapse
I still have no idea why a twrp boot up uses different numbers from our normal boot up.
I am now forced to use a "by-name" etc/recovery.fstab, but have yet to resolve USB-OTG
################
adbul_pt discusses some of this issue at post 100,
at post 126 it is claimed TWRP does not support fuse........I can see on normal boot /dev/fuse so will have to check that out later.
thanks for reading
hi
Having read 60 odd pages at freaktab I have a new test, for USB-OTG
boot current TWRP, insert usb stick into hub and hub into OTG cable into device
check mount and try to check the box for usb storage.....fails
choose right hand side, it names a storage device and changes to a dialog box........usb storage shows as 0 Mb......result ......fails
Altho this is no better than my earlier report, until someone says they have succeeded with OTG storage..............I think I have done enough testing of this and my brain hurts (joke)
Sorry for not replying, been a bit busy. ;V
I'll upload the recovery dump now. I have some files on my computer too (ramdisk and other stuff) so if you want those too I'll send em too.
EDIT: Link
Code:
http://puu.sh/fsBNP/4789c249eb.zip
This is the recovery I use. It really wasn't too hard to make. I even think I took the one for RK3xxx. Only bad things are - no internal SD and it's upside down lol
i tried a CWM and found it upside down
repacked with this string in default.prop
ro.sf.hwrotation=180
still upside down.....have not had a chance to look at your recovery but assume its based on the generic rk2918?
cheers
aus9 said:
still upside down.....have not had a chance to look at your recovery but assume its based on the generic rk2918?
cheers
Click to expand...
Click to collapse
My pack is based on abdul's RK292x recovery since there wasn't any 2918 based with 1024x600 resolution.
On another note - I think the etna_viv driver can be ported to the Mediapad 7 Lite as the developer himself has a RK2918 based tablet. I think it's better than the regular Vivante driver. Apparently it handles things horribly and you can see it in games such as Table Top Racing or some games/3D apps not running at all such as Epic Citadel, which is quite disappointing. Besides games and apps, I think it can benefit the latest of CWM recoveries since the framebuffer didn't get updated at all when I ran it (and I'm not sure even if it ran since I need serial pins for that, I do own a RS232 interface though).
EDIT: I actually found the original image file I used. Instead of the link above (which has the extra unnecessary padding) use this one;
Code:
http://puu.sh/fta8X/824844a344.img