Venue Rooting Android 2.2 & 2.3.3 In Under 2 Min, Backup ROM, Udating to Gingerbread
DISCLAIMER
Do this at your own risk. Always have a backup. If you Break your phone, don't blame me. There is a chance that your Andriod device will be made into a paper weight. This post is my adventures of my phone and if you follow do so at your own risk.
Requirements:
Dell Venue:
My dell was oem unlocked, so it should be region 00
Oem Ver: GTOUB1A130730
Baseband Ver: GTOUB1A130730-AWS
Quick Root instructions:
1: Enable Debug USB
2: Download SuperOneClickv1.5.4-ShortFuse to your desktop
3: Download Fastboot with ADB to your c:\ Drive
3: Open SuperOneClick as Administrator under the dir Win32
4: Click "Shell Root" in the GUI of SuperOneClick, then wait untill a popup says "Reboot to remove Superuser" Click "OK"
5: Go to the Fastboot with ADB Dir using Windows Command Prompt.
6: Type: adb shell (You should see # insted of $)
You should have temp root until you reboot the device.
Permanent root instructions: (Optional)
(Get the system mtd path)
Type: cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00600000 00020000 "recovery"
mtd2: 00600000 00020000 "recovery_bak"
mtd3: 00040000 00020000 "LogFilter"
mtd4: 00300000 00020000 "oem_log"
mtd5: 10400000 00020000 "system"
mtd6: 22600000 00020000 "userdata"
mtd7: 06600000 00020000 "cache"
(do the following as root, #)
1: Type: mount -t rfs -o remount,rw /dev/block/mtd5 /system
2: Type: cd /system/xbin
3: Type: cat /system/bin/su > su
4: Type: chmod 4755 su
5: Type: exit
6: Type: adb install Superuser.apk (Only do this if missing from device)
7: Test, Reboot, GoTo ADB Win dir
Type: adb shell (you should see $) Type: Su (Push Yes When your Android App SuperUser asks you to accept)
Backup Android ROM:
Type: cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00600000 00020000 "recovery"
mtd2: 00600000 00020000 "recovery_bak"
mtd3: 00040000 00020000 "LogFilter"
mtd4: 00300000 00020000 "oem_log"
mtd5: 10400000 00020000 "system"
mtd6: 22600000 00020000 "userdata"
mtd7: 06600000 00020000 "cache"
(do the following as root, #)
Type: cat /dev/mtd/mtd0 > /sdcard/boot.img
Type: cat /dev/mtd/mtd1 > /sdcard/recovery.img
Type: cat /dev/mtd/mtd2 > /sdcard/recovery_bak.img
Type: cat /dev/mtd/mtd3 > /sdcard/LogFilter.img
Type: cat /dev/mtd/mtd4 > /sdcard/oem_log.img
Type: cat /dev/mtd/mtd5 > /sdcard/system.img
Type: cat /dev/mtd/mtd6 > /sdcard/userdata.img
Type: cat /dev/mtd/mtd7 > /sdcard/cache.img
Type: exit
Type: adb pull /sdcard/boot.img
Type: adb pull /sdcard/recovery.img
Type: adb pull /sdcard/recovery_bak.img
Type: adb pull /sdcard/LogFilter.img
Type: adb pull /sdcard/oem_log.img
Type: adb pull /sdcard/system.img
Type: adb pull /sdcard/userdata.img
Type: adb pull /sdcard/cache.img
Udating to Android 2.3.3 Gingerbread:
Be warned, remember to backup your phone before these next septs.
1. Goto the dell venue wiki (http://forum.xda-developers.com/wiki/Dell_Venue) and download these 2 files from Version 408
a. Thunder_408_20707_14.pkg
b. recovery.img (make sure its the version 408)
2. Download Thunder_408_20707_14.pkg and rename it update.pkg
3. type: adb push update.pkg /sdcard/update.pkg
4. Reboot and go into fastboot recovery, conect the usb and you should see yellow fastboot recovery mode 2
5. type: fastboot flash recovery recovery.img (remember this is version 408)
6. Reboot and enter recovery mode, there you should see an option (update using update.pkg), select it with the camera button
You should see another screen in blue saying doing emergency update..................
Your phone will reboot and another update screen will appear saying Updating..... and a Android logo animation
Your phone should reboot one last time this time slowly be patient and you should see Android 2.3.3 Gingerbread welcome screen.
Rooting Android 2.3.3 Gingerbread:
1. Download Superuser.zip and rename it to update.zip (http://mirror2.streakdroid.com/manii/Tools/Superuser.zip)
2. Download ClockWorkMod rename it to recovery.img (http://mirror2.streakdroid.com/manii/misc/ClockWorkMod/V-5.5.0.4.img)
3. Type: adb push update.zip /sdcard/update.zip
4. Remember to remove update.pkg from /sdcard/update.pkg
5. Reboot to Fastboot_Mode 2 again
6. Type: fastboot flash recovery recovery.img (remember this is ClockWorkMod)
7. Reboot into recovery mode and select "update.pkg" option again to go into Rom Manager
8. Once in Rom Manager select (update.zip) option
You should see Rom Manager saying "update completed you have root now".
9. Reboot and test with adb shell with the command su.
10. Upon reboot Rom Manager will be remove and 408 recovery.img will be on your system.
DO NOT INSTALL "Rom Mamager" AGAIN ON 2.33, BACKUP DOES NOT WORK AND FILLS YOUR /CACHE/RECOVERY/ WITH LOG FILES
thx share,but this not work on 2.3 rom
Thank You
Best easy way....use gingerbreak.apk...frm ur cell only u cn root ur phn
Sent from my Dell Venue using xda premium
1. Goto the dell venue wiki (http://forum.xda-developers.com/wiki/Dell_Venue) and download these 2 files from Version 408
a. Thunder_408_20707_14.pkg
b. recovery.img (make sure its the version 408)
2. Download Thunder_408_20707_14.pkg and rename it update.pkg
3. type: adb push update.pkg /sdcard/update.pkg
4. Reboot and go into fastboot recovery, conect the usb and you should see yellow fastboot recovery mode 2
5. type: fastboot flash recovery recovery.img (remember this is version 408)
6. Reboot and enter recovery mode, there you should see an option (update using update.pkg), select it with the camera button
You should see another screen in blue saying doing emergency update..................
Your phone will reboot and another update screen will appear saying Updating..... and a Android logo animation
Your phone should reboot one last time this time slowly be patient and you should see Android 2.3.3 Gingerbread welcome screen.
3. type: adb push update.pkg /sdcard/update.pkg where i type ?? have tool ?? i used windows 7
thank
masirvan said:
1. Goto the dell venue wiki (http://forum.xda-developers.com/wiki/Dell_Venue) and download these 2 files from Version 408
a. Thunder_408_20707_14.pkg
b. recovery.img (make sure its the version 408)
2. Download Thunder_408_20707_14.pkg and rename it update.pkg
3. type: adb push update.pkg /sdcard/update.pkg
4. Reboot and go into fastboot recovery, conect the usb and you should see yellow fastboot recovery mode 2
5. type: fastboot flash recovery recovery.img (remember this is version 408)
6. Reboot and enter recovery mode, there you should see an option (update using update.pkg), select it with the camera button
You should see another screen in blue saying doing emergency update..................
Your phone will reboot and another update screen will appear saying Updating..... and a Android logo animation
Your phone should reboot one last time this time slowly be patient and you should see Android 2.3.3 Gingerbread welcome screen.
3. type: adb push update.pkg /sdcard/update.pkg where i type ?? have tool ?? i used windows 7
thank
Click to expand...
Click to collapse
Follow this thread:
Link
Its for downgrade , but you can upgrade in similar manner
I have one big problem after update to 2.3.3(408):
I can't run USSD codes on my device. This is very annoying - I can't chcek value of my account, put money into account and many others...
checking of IMEI is working...
Re: Venue Rooting Android 2.2 & 2.3.3 In Under 2 Min, Backup ROM, Udating to Gingerbr
Tomaszu87 said:
I have one big problem after update to 2.3.3(408):
I can't run USSD codes on my device. This is very annoying - I can't chcek value id my account, put money into account and many others...
checking of IMEI is working...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1558331
Flash this file using CWM or TWRP
USSD codes will work
Sent from my Dell Venue using xda app-developers app
terminal17 said:
Flash this file using CWM or TWRP
Click to expand...
Click to collapse
Thanks for your reply!
One more question: Where can I get CWM in proper version - all of the links on forum are dead or are for the devices, not fot PC...
Re: Venue Rooting Android 2.2 & 2.3.3 In Under 2 Min, Backup ROM, Udating to Gingerbr
I don't know for pc...but they are available only for fones in this forum...chk for dell venue CWM Or TWRP
Sent from my Dell Venue using xda app-developers app
terminal17 said:
I don't know for pc...but they are available only for fones in this forum...chk for dell venue CWM Or TWRP
Click to expand...
Click to collapse
Everything well done!
My earlier questions born of my low level of knowledge on android.
Read a lot of posts, users answers and everything becomes easier...
Thanks XDA!
Related
Can we add a new section for the LG Optimus One P500?
Thank You
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
I agree!
Bye
Franco
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
Yes, please create a forum for the LG Optimus P500.
giacor
came on men
create this section for LG Optimus one with Google!
thanks
Yes!!! You know you want it!
Thanks!
yes please, can you add this section?
yes please, can you add this section?
Add it.
Thanks!
Please, Add it
rotorto said:
Can we add a new section for the LG Optimus One P500?
Thank You
Click to expand...
Click to collapse
Yes I think it would be useful
Proud owner of a LG P500 Optimus One since 2 days, great device, please open a section for it! It deserves that!
I'm seeking a rom dump from the P500 to aid in porting froyo to the LG VS740. I'll also try to make a custom recovery for you as I have done ones for the lg ally and htc incredible as a thank you for dumping the files.
It should be able to be rooted with universal androot or else use the rageagainstthecage-arm5.bin method.
Once rooted from adb shell or terminal app type:
Code:
su
cat proc/mtd
note the mtd partition # of boot & recovery.
then in the dd parts use the mtd number of your boot and recovery partitons
for example if boot is mtd3 on P500 do dd if=/dev/mtd/mtd3 of=/sdcard/boot-dump.img bs=4096
then type
Code:
cd /system
tar zcvf /sdcard/system-dump.tar.gz *
dd if=/dev/mtd/mtd1 of=/sdcard/boot-dump.img bs=4096
dd if=/dev/mtd/mtd0 of=/sdcard/recovery-dump.img bs=4096
Please someone upload these 3 files from p500:
system-dump.tar.gz
boot-dump.img
recovery-dump.img
Thanks again.
Also, in case anyone is worried there is no personal user data in /system thats all in the /data partition.
I agree we need a Optimus One P500 forum.
IMHO it's one of the most interesting middle class Android phones: better screen resolution than HTC Wildfire or Samsung Galaxy 3. An alternative to HTC Aria/Gratia
I have rooted my P500 and i have found this :
cat proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
but when i tried to TAR files the system told me
tar: not found
I have WIN XP Pro and maybe TAR is for linux or i'm wrong in something ...
if you could help me we can make it.
bye and sorry for my english.
Get busybox for phone and do it on phone with terminal eumulator. Optionally do adb pull of your entire system folder and zip it up if all else fails. Need boot and recovery too.
I'd like a section for Optimus One ...
Have someone installed Flash Lite for default browser?
Ok I just downloaded a dump thanks fughy. I am looking at pics and don't see a navigational pad. Can someone confirm it has one or it not & what it uses other than touch screen for navigation as thats needed for recovery. Please list all hardware buttons/keys also please.
I have a custom amon ra recovery that needs to be tested. Please PM if interested. Md5 is below to check against after download.
MD5sum b15d0d4a6588b28b58ee16cf9470ab5f recovery-thunderg_test.img
drellisdee said:
Ok I just downloaded a dump thanks fughy. I am looking at pics and don't see a navigational pad. Can someone confirm it has one or it not & what it uses other than touch screen for navigation as thats needed for recovery. Please list all hardware buttons/keys also please.
I have a custom amon ra recovery that needs to be tested. Please PM if interested. Md5 is below to check against after download.
MD5sum b15d0d4a6588b28b58ee16cf9470ab5f recovery-thunderg_test.img
Click to expand...
Click to collapse
The P500 has no touchpad or something else for navigation. The only keys are:
- Power button on top
- Volume Up/Down on right side
- Menu, Home, Back, Search on front
I would love to create my own custom rom for this device but I'm quite new to this. Is there somewhere a good tutorial on how to create a custom rom based on an original rom?
This LG Optimus is the number ONE
As promised here is a beta amon ra style recovery for opt1 thunderg.
Its untested as I don't have one to test it on.
Key mapping is up/down = vol-up and vol-down
select = power
backup = search
If the keys aren't right use the key code debugger under "other" menu and give me the key code outputs.
Fastboot IF enabled on optimus one can be accessed by "adb reboot bootloader".
The best way to test this if you have fastboot is to do
Code:
fastboot boot recovery-thunderg_test1.img
if done this way it will boot from ram and will be lost upon reboot. IE. its temporary if it needs some changes instead of actually flashing it.
If you need help setting up fastboot/adb drivers reference my post here for the Lg Ally
http://androidforums.com/ally-all-things-root/146564-ally-recovery-img-here-custom-roms.html
It should either be 618e or 618f for adb.
If you don't have fastboot on device this will flash it:
Do this from a su (root) adb shell (preferred) or terminal on phone after you have copied recovery-thunderg_test1.img & flash_image to root of your sdcard. Flash_image is attached to the post linked above.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-thunderg_test1.img
Also if you have a file named install-recovery.sh in system/etc you will need to rename it to install-recovery.sh.bak prior to flashing a recovery.
Download at:
http://www.mediafire.com/file/atz2309jc5d5zqc/recovery-thunderg_test1.img
MD5 = 954c6249e400c0b779b8f47cdb79d87c
This is a simple little guide that'll show you how to back up the phone without the famous nandroid. So as we can use it to get fastboot to work and restore the phone back without nandroid.
adb shell //enter the device native shell
$ su //enter the secure shell (make sure your screen is unlocked when you run this command, then click allow when the window pops up on the phone's screen)
# cat /proc/mtd //show device partitions
Here's an example output. Note: not all phones are like this, some have different partitions. This just happens to be the structure of the my old LS670.
cat /proc/mtd
dev: size erasesize name
mtd0: 00700000 00020000 "boot"
mtd1: 07c20000 00020000 "cache"
mtd2: 00700000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 09e80000 00020000 "system"
mtd6: 0a4e0000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
Then we will back them up to the SD card
# cat /dev/mtd/mtd0 > /sdcard/boot.img
# cat /dev/mtd/mtd1 > /sdcard/cache.img
# cat /dev/mtd/mtd2 > /sdcard/recovery.img
# cat /dev/mtd/mtd3 > /sdcard/splash.img
# cat /dev/mtd/mtd4 > /sdcard/FOTA_STO.img
# cat /dev/mtd/mtd5 > /sdcard/system.img
# cat /dev/mtd/mtd6 > /sdcard/userdata.img
# cat /dev/mtd/mtd7 > /sdcard/misc.img
# cat /dev/mtd/mtd8 > /sdcard/persist.img
Similiarly for the others..
To restore your phone to it's previous state, you'll need fastboot which should come with the SDK.
# exit //exit the secure shell
$ exit //exit the device native shell
fastboot flash boot /sdcard/boot.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash cache /sdcard/cache.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash recovery /sdcard/recovery.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash splash /sdcard/splash.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash FOTA_STO /sdcard/FOTA_STO.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash system /sdcard/system.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash userdata /sdcard/userdata.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash userdata /sdcard/misc.img //wait for 'sending...OKAY / writing...OKAY'
fastboot flash persist /sdcard/persist.img //wait for 'sending...OKAY / writing...OKAY'
fastboot reboot //reboot the device
After that, you can zip all of the img files and upload it for us.
This will be really appreciated.
Update me if you need any help
Please Dell Venue Users, help us restore our bricked devices
Thank you
Clarification...
Let me make sure I understand this correctly...
All I need to do to create an update.zip to restore the phone is:
Take these 9 image files from the phone, zip them, name the zipped folder "update.zip"?
Will doing this potentially fix all the "bricked" dell vunes?
If so... Can that "update.zip" folder be flashed from fastboot?
This HOWTO is only useful for people who have NOT yet installed a stock recovery or who have lost the custom recovery after KDZ or LGMDP flash.
Why I posted it? Since I have had enough of complaints about screwed phones via ROM Manager, also there is some broken rf.sh script I have heard of.
Step 1:
- Download (see attachment) the flash_image.zip
- unzip it
- and put the flash_image binary on the root of your SD card (via USB cable).
Step 2:
- Dowload a recovery of your choice (CWM or AmonRA) from this thread.
- Unzip it on your local box and find the recovery.img file.
- Put the recovery.img to the root of your SD Card (via USB cable)
Step 3a - via terminal emulator
- Run terminal emulator on your phone (download one from market if you do not have it yet, duh!)
- type these command exactly: $ denotes a normal user, # denotes root. This character should NOT be typed into terminal emulator!
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
or
Step 3b:
- Install Android SDK (EXE installer recommended for Windows users.)
- run command prompt (cmd.exe) on your Windows box, or run the following from shell on your Linux box:
Code:
> adb shell
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# exit
$ exit
> adb reboot recovery
Step 4:
Now you should find yourself in your shiny new custom recovery. Do whatever you need there.
Q: Is not there an easier way? This seems like a lot of typing? It sucks - I have heard about ROM Manager!
A: ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Q: I already have custom recovery. Do I need to do this if I want to switch from CWM to AmonRA or vice versa?
A: No. This thread has recovery ZIPs when can be flashed from recovery itself.
Q: HELP!!! I screwed and now my phone is stuck in fastboot mode! What should I do?!?!
A: You are officially lame, very lame person. Now go here to fix it.
Q: But my phone is not rooted (no su binary) - the above does not work! I tried to root it via z4root, GingerBreak, SuperOneClick but everything failed! What should I do? Am I stuck with stock ROM?
A: No! See the LGMDP method below.
Nice guide
This way newbies won't be confused where to search.
BTW, a little mistake: in the adb codes it's flash_image recovery /sdcard/recovery.img
Alternative method: Flashing custom recovery via LGMDP.exe
Tried to root it via z4root, GingerBreak, SuperOneClick but everything failed? No problem! Flash the recovery via LGMDP.
Step 1:
Download P500-CWM-3.1.0.0.zip (CWM 3.1.0.0 included, if you want something else, replace recovery.img with whatever you want) and unzip it.
Step 2:
- Browse to the folder where you unpacked the ZIP and run LGMDP-v1.5.exe
- Click Download in menu
- Select Port
- Choose your phone, click Connect
- Click Image Folder button, browse to the directory where you unpacked this
- Click OK about 3 times on the warnings
- Close the window
- Click Download button
- Let it do the job. It will backup your IMEI and MACs to .NV2 file, reboot your phone, flash recovery and restore the NV2 backup. Do NOT interrupt it or disconnect your phone until it says "Download complete"! Do NOT delete the NV2 backup!
Step 3:
Done! Now when you press Home + Volume Down + Power, you should find yourself in your shiny new custom recovery. Now you can flash a rooted ROM via flash zip menu.
Q: I am a moron and have interrupted the process. Now I get a black screen with some weird fastboot text, what to do? HELP!!!!
A: Yes, you are a moron. See [HOWTO] Revive a bricked P500 on fastboot mode (the SHORT way) thread.
Q: Can I just quickly root my stock ROM after flashing recovery? I do not want a custom ROM.
A: Yes. Download su-2.3.6.3-efgh-signed.zip and flash it from recovery. Reboot, download Busybox Installer from the market, run and install busybox on your phone.
--- reserved ---
Thx doktor, it helps some of my friend who lost their recovery while upgrading to official GB...
+1
Nice one man, really useful and funny text.
Yo,added this to the N00B repo.
"Q: Can I just quickly root my stock ROM after flashing recovery? I do not want a custom ROM.
A: Yes. Download su-2.3.6.3-efgh-signed.zip and flash it from recovery. Reboot, download Busybox Installer from the market, run and install busybox on your phone."
In reference to the above words, cud i use this as a method to root my stock GB 2.3.3??? cos nothing else seems to root it and installing sdk and adb and all tat, seems too complex!
Of course.
nice guide TS
but this guide also can use for thunderg recovery right ???
and i not quite understanding ur step 3a
which is this :
type these command exactly: $ denotes a normal user, # denotes root. This character should NOT be typed into terminal emulator!
Click to expand...
Click to collapse
but in my mind just type EXACTLY what the below quote write
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Click to expand...
Click to collapse
but you say the things in 1st post make me confuse
so just follow and type the word exactly ???
No comment, everything I wanted to say has been censored
get what you meaning already
When I type
flash_image recovery /sdcard/recovery.img
I take the error message
mtd: not writing bad block at 0x00440000
error writing recovery : No space left on device
But I have at least 60MB on my phone's memory...
edit:
OK,that error bricked my phone again...
evripidis said:
error writing recovery : No space left on device
But I have at least 60MB on my phone's memory...
Click to expand...
Click to collapse
Has nothing to do with the space for /recovery on a separate partition.
evripidis said:
edit:
OK,that error bricked my phone again...
Click to expand...
Click to collapse
Congrats.
doktornotor said:
Has nothing to do with the space for /recovery on a separate partition.
Click to expand...
Click to collapse
KDZ is always saving me always!
How can I fix that about /recovery?
Because I don't understand, I don't have a partition for recovery?
If is that, why after KDZ update, original recovery works properly?
I am worried about bad block that error message said...
evripidis said:
I am worried about bad block that error message said...
Click to expand...
Click to collapse
Yeah, am I worried too, should not report any bad sectors (at least not on this phone).
Code:
> adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
I get this
Code:
>adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
In google I found this http://android.modaco.com/content-p...kmod-recovery-for-zte-blade-oled-tft/page/20/
He gets the error at the same point.
And this http://androidforums.com/647576-post25.html
I did everything as I was meant to, but when I get to the point to insert the text, both on pc or on phone I get an error message...What's wrong?
celtic-paolino said:
I did everything as I was meant to, but when I get to the point to insert the text, both on pc or on phone I get an error message...What's wrong?
Click to expand...
Click to collapse
Eh... Insert what text? Where? What error message?
When I have to write the codes in the terminal emulator or in cmd.exe, I get these messages:
TE: su: permission denied
and the rest doesn't obviously work
CMD: doesn't work at all even if I installed the program you said...
Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
xorkrus said:
Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
Click to expand...
Click to collapse
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Sent from my SCH-I535 using xda premium
shimp208 said:
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Click to expand...
Click to collapse
View attachment mounts.txt
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
xorkrus said:
View attachment 1395857
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
Click to expand...
Click to collapse
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
Code:
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0ba00000 00020000 "system"
mtd5: 03f00000 00020000 "cache"
mtd6: 0a0a0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
mtd8: 01400000 00020000 "cust"
From here you should be able to tell which ones is boot, recovery, etc.
shimp208 said:
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
From here you should be able to tell which ones is boot, recovery, etc.
Click to expand...
Click to collapse
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
xorkrus said:
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
Click to expand...
Click to collapse
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
kuisma said:
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
Click to expand...
Click to collapse
View attachment fdisk.txt
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
xorkrus said:
View attachment 1409237
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
Click to expand...
Click to collapse
You already know system, cache and data. Also, root and boot lives in the same partition.
Good day XDA-Developers
Is there Any Root for This Device
its a Rebrand Product of GFIVE G95..
Heres some Infos
Cherry Mobile Cruize specs:
• Dual-SIM
• 1GHz single-core CPU
• 512MB RAM
• 4GB internal storage with microSD card slot up to 32GB
• 5.2-inch WVGA display (800 x 480 resolution)
• 5-megapixel rear camera with LED flash
• VGA front camera
• 2500mAh battery
• Android Ice Cream Sandwich
GFive G95 - Bravo
Dimension 149.5 x 83 x 10.9mm
Weight 211 g
Battery Talk time Up to 5 h 30 m, Stand-by Up to 350h
OS Android OS, v4.0.3 (Ice cream Sandwich)
Memory 2.4GB built-in, 4GB ROM, 512 MB RAM + microSD Card (supports up to 32GB)
Processor 1Ghz, CORTEX A9 (MTK6575) + PowerVR SGX531 GPU
Connectivity Bluetooth v3.0 with A2DP + EDR, USB, WLAN (Wi-Fi 802.11 b/g/n + Wi-Fi hotspot),GPRS, EDGE, 3G (HSDPA 14.4 Mbps, HSUPA 5.76 Mbps)
Display Size WVGA, 5.3 inches
Display Colour TFT LCD, 262K colors
Operating
Frequency / Band GSM 850 / 900 / 1800 /1900
Browser HTML (Adobe Flash)
Colors Black / White
Entertainment Stereo FM radio with RDS, SNS integration, MP3/eAAC+/WAV/WMA player, XviD/MP4/H.264/H.263/WMV player, 3.5mm jack, YouTube, Google Talk, Skype Video Calling, Picasa, Games, G’Five Market & Reading.
Camera 8MP, HD, autofocus 2048x1536 Pixels, Geo-tagging, face detection, Video
Other Features Project mode, Skype Video calling, Speakerphone, G-Cloud
i TRIED Different ROOT Software Like this
MTK DRIODTOOL
Super One Click
Binary ROOT
Failed
Still
The ADB Drivers are already installed.. even the device is on DEBUGGING Mode Already..
I think the Device is not recognize by those program or the Computer..
Well appreciated any IDEAS and INFORMATIONS
Thanks and More Power..
:crying::crying::crying::crying::crying:
follow-up
up for this thread
check this out
http://www.techbloggerzone.com/2013/05/how-to-root-cherry-mobile-cruize.html
Hello,
I'm using the same phone, a rebranded version of cherry mobile cruize. I have successfully rooted my phone. But when trying to install cwm, i have accidently overwritten the /dev/block/mmcblk0p16 block. Can you please take a backup of your mmcblk0p16 block and upload it ? it'd be great help.
The process would be,
adb shell
su
dd if=/dev/block/mmcblk0p16 of=/data/local/tmp/block16.img
now the adb shell exit
adb pull /data/local/tmp/block16.img ./
now please upload the block16.img to the web.
sarimkhan said:
Hello,
I'm using the same phone, a rebranded version of cherry mobile cruize. I have successfully rooted my phone. But when trying to install cwm, i have accidently overwritten the /dev/block/mmcblk0p16 block. Can you please take a backup of your mmcblk0p16 block and upload it ? it'd be great help.
The process would be,
adb shell
su
dd if=/dev/block/mmcblk0p16 of=/data/local/tmp/block16.img
now the adb shell exit
adb pull /data/local/tmp/block16.img ./
now please upload the block16.img to the web.
Click to expand...
Click to collapse
I have the same problem too.. I rooted my phone and accidentally pushed wrong img file. Then I messed with files in /dev/block/ .. Now my phone won't turn on at all, no charge etc. Please help
can anybody upload the stock rom for this phone, in zip format, that can be installed/updated using the stock recovery? thanks.
Root for Cherry Mobile Cruize/GFive Bravo G95
I spent alot of time searching on google then i finally found out how to root this phone.
Download and extract the Cruize ADB.zip file to a separate folder.
Hold shift and right click on an empty space in the folder. Click on open command window here.
Type “adb devices” if you will see a command prompt list ”cruize device”. If not, try installing the PDANET drivers attached.
Type these commands one by one. Press enter after each command.
adb push pwn /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 pwn
./pwn
The exploit will run and this may take a few minutes. If “Bus error” comes up then repeat the last command “./pwn” if the display appeared “success." then continue.
Then enter these Commands
adb kill-server
adb devices
adb shell
You should see a hashtag (#) to show that you are temporarily rooted. Then enter these commands.
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
After the phone reboots, install superuser. You can download it at Play Store.
ORYou can install using adb. Type this command.
adb install Superuser.apk
Try And Reply
Cheers
P.S. I also found CWM for this phone. Tell me if you need it.
Pardon me, Credits to JemPuno member djkyjem, as the article was originally posted by him/her or whatever.
noob.droid said:
I spent alot of time searching on google then i finally found out how to root this phone.
Download and extract the Cruize ADB.zip file to a separate folder.
Hold shift and right click on an empty space in the folder. Click on open command window here.
Type “adb devices” if you will see a command prompt list ”cruize device”. If not, try installing the PDANET drivers attached.
Type these commands one by one. Press enter after each command.
adb push pwn /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 pwn
./pwn
The exploit will run and this may take a few minutes. If “Bus error” comes up then repeat the last command “./pwn” if the display appeared “success." then continue.
Then enter these Commands
adb kill-server
adb devices
adb shell
You should see a hashtag (#) to show that you are temporarily rooted. Then enter these commands.
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
After the phone reboots, install superuser. You can download it at Play Store.
ORYou can install using adb. Type this command.
adb install Superuser.apk
Try And Reply
Cheers
P.S. I also found CWM for this phone. Tell me if you need it.
Click to expand...
Click to collapse
Is it required to install CWM ???
Not Really.
CWM is not required but it is optional. With that you can create nandroid backups and install roms (if they become available ).
If you are not a CWM fan, I can port TWRP for your phone. .
BTW, Please report if the root worked for you, if not, then I have found another way to root it from Chinese and Russian forums.
noob.droid said:
CWM is not required but it is optional. With that you can create nandroid backups and install roms (if they become available ).
If you are not a CWM fan, I can port TWRP for your phone. .
BTW, Please report if the root worked for you, if not, then I have found another way to root it from Chinese and Russian forums.
Click to expand...
Click to collapse
Yes please. Can I ask for a ported TWRP for this phone?
TWRP 2.4.4.0
Dear edp0gi,
I will need the stock recovery's .img. To get that, follow these instructions,
If you are using ADB, connect your device to your computer via USB, launch a command prompt window on your computer and enter the following command:
Code:
adb shell
If you are using Terminal Emulator instead, just launch it on your Android phone and enter the following command and agree to grant any permissions you’re prompted for:
Code:
su
The remaining process will be the same for both ADB and Terminal Emulator.
Enter the following command:
Code:
cat proc/mtd
You will get an output similar to this. Note that your result may differ from this one and you must proceed according to the output that you get, rather than the example that you see here.
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 0fa00000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 093a0000 00020000 "userdata"
To dump the recovery image to your SD card, make note of the first word of the line which says “recovery” in the end. It is ‘mtd1’ in case of this example but may be another entry for you. Now use this command, replacing ‘mtd1’ with the term that applies in your case, if different:
Code:
dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
Attach the recovery.img in your reply.
P.S. My cousin told me about the adb method, and i haven't tried it so I wont recommend that, although I did it using Android Terminal Emulator(free app in Play Store by developer Jack Palevich)
Try it and Report.
Sure but CWm required
noob.droid said:
dear edp0gi,
i will need the stock recovery's .img. To get that, follow these instructions,
if you are using adb, connect your device to your computer via usb, launch a command prompt window on your computer and enter the following command:
Code:
adb shell
if you are using terminal emulator instead, just launch it on your android phone and enter the following command and agree to grant any permissions you’re prompted for:
Code:
su
the remaining process will be the same for both adb and terminal emulator.
Enter the following command:
Code:
cat proc/mtd
you will get an output similar to this. Note that your result may differ from this one and you must proceed according to the output that you get, rather than the example that you see here.
Dev: Size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 0fa00000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 093a0000 00020000 "userdata"
to dump the recovery image to your sd card, make note of the first word of the line which says “recovery” in the end. It is ‘mtd1’ in case of this example but may be another entry for you. Now use this command, replacing ‘mtd1’ with the term that applies in your case, if different:
Code:
dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
attach the recovery.img in your reply.
P.s. My cousin told me about the adb method, and i haven't tried it so i wont recommend that, although i did it using android terminal emulator(free app in play store by developer jack palevich)
try it and report.
Click to expand...
Click to collapse
ok i will give you my recovery but please give me your cwm also. I need it.
HELP(
Hi everyone!please help me,can anyone upload a copy of systemui.apk from GFIVE G95 or Cherry Mobile Cruize. Because i accidentally deleted mine.
Thanks in advance
CWM
@barbakadabra, Please tell me which rom you are on.
@mtayyabali, CWM is attached. To install use su command and get superuser permissions for terminal emulator then type:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p19
To reboot into CWM
Code:
reboot recovery
P.S. recovery.img is only required for TWRP.
For some reason, I couldn't add an attachment. So here's a Dropbox link to the file.
www(dot)dropbox(dot)com/s/htcbn60rfwa6qm3/recovery(dot)img
I hope i don't get banned for this.
boot loop problem
pls help me about my cherry mobile cruize, it got boot loop..i dont know wht to do.. and what are the necessary files...pls help..is the firmware of g'five g95 is the same with cherry mobile cruize?
hot to root cruize !!!! 100% working my phone is cruize w280 rooted
THE EASIEST WAY how to root CRUIZE W280 IS
>download PdaNet on your pc then it will ask kung anong phone yung iyong device the click the 4th word
>then connect your Cruize w280 and then click ok or install
>w8 for a few seconds
>after install your phone will have a PdaNet
>then download the KINGO ROOT
>install it
>connect your phone using PdaNet
>enable usb debugging
>open PdaNet app on your pc
>the if connected
>open kingo Root
>then click root device
>w8 for a few minutes
>after it reboot your device
>now your phone is rooted
ENJoy
sorry i dont have a direct link of the application
@elvon08
You can find official stock rom along with instructions to flash on http://www.needrom.com/mobile/gfive-g95/
@splitknotz
PdaNet does not work with all devices. It didn't work on my phone along with a dozen other chinese rooting programs. Some worked but the root was only temporary.
Thanks and plz.
noob.droid said:
I spent alot of time searching on google then i finally found out how to root this phone.
Download and extract the Cruize ADB.zip file to a separate folder.
Hold shift and right click on an empty space in the folder. Click on open command window here.
Type “adb devices” if you will see a command prompt list ”cruize device”. If not, try installing the PDANET drivers attached.
Type these commands one by one. Press enter after each command.
adb push pwn /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 pwn
./pwn
The exploit will run and this may take a few minutes. If “Bus error” comes up then repeat the last command “./pwn” if the display appeared “success." then continue.
Then enter these Commands
adb kill-server
adb devices
adb shell
You should see a hashtag (#) to show that you are temporarily rooted. Then enter these commands.
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
After the phone reboots, install superuser. You can download it at Play Store.
ORYou can install using adb. Type this command.
adb install Superuser.apk
Try And Reply
Cheers
P.S. I also found CWM for this phone. Tell me if you need it.
Pardon me, Credits to JemPuno member djkyjem, as the article was originally posted by him/her or whatever.
Click to expand...
Click to collapse
Thank u soo much , I'll give it a try but canu plz help me with Cwm and also some good custom roms for this phone ??
@ali.arsd
Cwm recovery and instructions are in post #14
Unfortunately there is no custom rom yet and probably not for some time. I don't own this phone anymore so I can't help anymore. Sorry. Though, Google is your friend. Sorry again.
Sent from my SM-G900H using XDA Free mobile app
Solved Root issue + CWM Recovery G95
kazutokirito said:
Good day XDA-Developers
Is there Any Root for This Device
its a Rebrand Product of GFIVE G95..
Heres some Infos
Cherry Mobile Cruize specs:
• Dual-SIM
• 1GHz single-core CPU
• 512MB RAM
• 4GB internal storage with microSD card slot up to 32GB
• 5.2-inch WVGA display (800 x 480 resolution)
• 5-megapixel rear camera with LED flash
• VGA front camera
• 2500mAh battery
• Android Ice Cream Sandwich
GFive G95 - Bravo
Dimension 149.5 x 83 x 10.9mm
Weight 211 g
Battery Talk time Up to 5 h 30 m, Stand-by Up to 350h
OS Android OS, v4.0.3 (Ice cream Sandwich)
Memory 2.4GB built-in, 4GB ROM, 512 MB RAM + microSD Card (supports up to 32GB)
Processor 1Ghz, CORTEX A9 (MTK6575) + PowerVR SGX531 GPU
Connectivity Bluetooth v3.0 with A2DP + EDR, USB, WLAN (Wi-Fi 802.11 b/g/n + Wi-Fi hotspot),GPRS, EDGE, 3G (HSDPA 14.4 Mbps, HSUPA 5.76 Mbps)
Display Size WVGA, 5.3 inches
Display Colour TFT LCD, 262K colors
Operating
Frequency / Band GSM 850 / 900 / 1800 /1900
Browser HTML (Adobe Flash)
Colors Black / White
Entertainment Stereo FM radio with RDS, SNS integration, MP3/eAAC+/WAV/WMA player, XviD/MP4/H.264/H.263/WMV player, 3.5mm jack, YouTube, Google Talk, Skype Video Calling, Picasa, Games, G’Five Market & Reading.
Camera 8MP, HD, autofocus 2048x1536 Pixels, Geo-tagging, face detection, Video
Other Features Project mode, Skype Video calling, Speakerphone, G-Cloud
i TRIED Different ROOT Software Like this
MTK DRIODTOOL
Super One Click
Binary ROOT
Failed
Still
The ADB Drivers are already installed.. even the device is on DEBUGGING Mode Already..
I think the Device is not recognize by those program or the Computer..
Well appreciated any IDEAS and INFORMATIONS
Thanks and More Power..
:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Root the set with Root master app,
The app is in chinese but don't worry all you have to do is run it click on root and follow accordingly and a red box will appear click on that. Your set will be rooted. a super user app will be required as the app installed from root master will be in chinese .
To add CWM (Clock work mode) recovery you will need to install Mobile Uncle tools(Available from Playstore)
Flash recovery using the option in the app and there you go. CWM recovery for GFive Bravo G95 / Cherry mobile cruize w820.
See ya....