In order to install custom firmware on the Viewpad 7 and equivalent devices (Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600) you must use an alternative recovery partition. There are several methods to accomplish this, but in this thread I will document what I use personally.
For starters ALWAYS create a backup of your original 'stock' firmware.
Rooting:
1. Download version 1.7 of Super One Click. Some users have reported issues with the latest version, but previous versions can be found in the thread.
2. Place your Android device into debugging mode, and connect to computer.
3. Right-click the Super One Click executable and select 'Run As Administrator'.
4. At program launch select 'rageagainstthecage' exploit method, then select 'Root'.
5. If there is no activity for more than 30 seconds and the terminal display is stuck at 'Running rageagainstthecage....' remove the USB plug momentarily and plug back in.
6. You should get the message “***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***” followed by an ADB reset, waiting for device, and finally a successful rooting message. (Apparently the looping issue is a known bug).
7. Once this process is complete your prompted to test the root condition. Follow the steps to verify.
Stock Backup:
1. Open up ADB shell within a terminal.
2. Get the list of partitions:
cat /proc/mtd
3. Pull each original partition from the device onto the SD card:
cat /dev/mtd/mtd3 > /sdcard/recovery.img (example...change for each partition)
Install Alternative Recovery Partition:
1. Copy the flash_image and clockwork recovery image to your SD Card (Find Attached Below).
2. Open a terminal (via computer or terminal emulator). Enter ADB shell.
3. Within ADB shell enter the following to change permissions for the flash_image:
chmod 755 /system/bin/flash_image
4. Replace the original stock recovery image by copying the clockwork image in it's place:
flash_image recovery /sdcard/cwrecovery.img
Installing Custom Firmware:
1. Copy the custom firmware of your choice to the SD card.
2. Power down your device.
3. Depress both volume keys simultaneously followed by holding in the power switch for a few seconds.
4. Upon power up you will see the birds logo and 'enter recovery' text in the top left corner of the screen.
5. Use the volume keys to step through the menu.
6. Select 'Backup & Restore' followed by 'Backup' to make a 'NANDROID' backup of the current firmware. The backed up ROM should be located in: /sdcard/clockworkmod/backup/date&time/
7. Once the backup process completes you will be back at the main recovery menu.
8. Select 'apply sdcard: update.zip.
9. Once complete select 'reboot device'.
DISCLAIMER: I cannot be held liable for anything you do to your Viewpad 7 (or equivalent device). Make sure you are comfortable with recovery tools, such as ClockworkMod, before proceeding.
[Reserved for Extras]
Installed, working ok. but the UP/DOWN button always jump 2 steps.
same. rooted. 2 spot jump on recovery menu. looks like pressing down moves one and then releasing the button goes another.
what custom rom works with the ViewPad7?
getting installation error Status (0) when I try tnt lite 4.4
Smilez said:
same. rooted. 2 spot jump on recovery menu. looks like pressing down moves one and then releasing the button goes another.
what custom rom works with the ViewPad7?
getting installation error Status (0) when I try tnt lite 4.4
Click to expand...
Click to collapse
TNT Lite is for the gTab.....NOT the Viewpad...therefore it will not work. There are only a couple modified ROMs available at this time for the Viewpad 7. I made a mod to stock ROM which can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1008673
I believe there is someone else working on a Gingerbread ROM (as am I), but I don't know any details of they're progress.
As for the recovery menu navigation problem (moves two spaces instead of one), I think it came that way from the manufacturer (FIH). Not sure how to remedy it at this point.
Viewpad HELP!
Did the volume down + power by mistake
Now I have a message:
Power on with pressing VOLUME_DOWN keys to leave Auto-FTM
and then
Wrong Project!!!!!
Please Select project name:
FA0
FA1...
FST
Cant reboot... cant do anything...
Cant adb in
HELP !
Schilack said:
Did the volume down + power by mistake
Cant reboot... cant do anything...
HELP !
Click to expand...
Click to collapse
Hold down both volume keys and the power button, and then push in the reset button. Keep holding all the keys until you see 'Enter Recovery Mode'.
Smilez said:
same. rooted. 2 spot jump on recovery menu. looks like pressing down moves one and then releasing the button goes another.
what custom rom works with the ViewPad7?
getting installation error Status (0) when I try tnt lite 4.4
Click to expand...
Click to collapse
This is so far what I can find for CUSTOM ROM of VIEWPAD7.
http://forum.xda-developers.com/showthread.php?t=1008673
RC3.
James
May want to update the OP to reflect that one should be downloading SuperOneClick version 1.7, not 1.8. The latter doesn't include the RageAgainstTheCage exploit method and will not root the device.
Took me a few tries to get my new Viewpad 7 rooted, but it finally is.
second that...
chicknlil said:
May want to update the OP to reflect that one should be downloading SuperOneClick version 1.7, not 1.8. The latter doesn't include the RageAgainstTheCage exploit method and will not root the device.
Took me a few tries to get my new Viewpad 7 rooted, but it finally is.
Click to expand...
Click to collapse
I second that, took me a few tries also... Used SOC 1.7 and it was a bit confusing on my Win Xp (xp-home SP3) machine about VP7 drivers and its USB Mass storage state (should remove SD card in VP7 if you have it installed).
It finally worked when the " Synchronation Tool " was also installed and running off of the virtual "CD-Rom" that was installed when the VP7 is plugged in...
Anyways keep up the good work!!! Hope to see more updates/ROMs/mods/etc... for the VP7, I personally think its a solid device with the exception of the small internal storage it has...
Can anyone please help me? /system/bin/flash_image does not excist on my viewpad 7...
chicknlil said:
May want to update the OP to reflect that one should be downloading SuperOneClick version 1.7, not 1.8. The latter doesn't include the RageAgainstTheCage exploit method and will not root the device.
Took me a few tries to get my new Viewpad 7 rooted, but it finally is.
Click to expand...
Click to collapse
Thanks for pointing that out. At the time of writing the latest was 1.7. I will make the correction.
I have all the IMGs on sd card, how do i restore them to get the viewpad back to full stock
dazcox5181 said:
I have all the IMGs on sd card, how do i restore them to get the viewpad back to full stock
Click to expand...
Click to collapse
Have you installed an alternative recovery (like clockwork)? If so you will need to copy the original recovery partition over, and then copy the remaining original partitions over. You can perform these tasks using ADB shell, and by using flash_image for the recovery partitions. You can find more information on this with a quick search.
So...this might be answered in another thread, but since there's no subforum for this device, it's hard to tell, but I digress...
How do I get around the "jump 2 spots" issue when in recovery? I've got clockwork in there just fine now, but I want to back up my system before I do any more serious "playing" and since I can't ever get it to land on "backup and recovery", I'm not sure how to proceed. Thoughts?
chicknlil said:
So...this might be answered in another thread, but since there's no subforum for this device, it's hard to tell, but I digress...
How do I get around the "jump 2 spots" issue when in recovery? I've got clockwork in there just fine now, but I want to back up my system before I do any more serious "playing" and since I can't ever get it to land on "backup and recovery", I'm not sure how to proceed. Thoughts?
Click to expand...
Click to collapse
This double-step issue when navigating the recovery menu is definitely an annoyance. To get around it and only move one selection just keep the applicable volume key pressed down, and then hit the power button to choose the selection.
Sweet...got the backup going. Now just need to figure out how to partition the SD card and get link2sd working. Appreciate your help!
Sent from my SAMSUNG-SGH-I897 using XDA App
JRShield said:
Can anyone please help me? /system/bin/flash_image does not exist on my viewpad 7...
Click to expand...
Click to collapse
I have the same problem as well. Can anyone shed some light here? Please? I'm using CSL Droidpad Mi700 (essentially the same as Viewpad 7).
edit: just got through it. thanks. Now I flashed with CWM v2.5.1.2, but I can't navigate using the volume keys. The power button only give me blank screen... Help...
kuntilanak said:
I have the same problem as well. Can anyone shed some light here? Please? I'm using CSL Droidpad Mi700 (essentially the same as Viewpad 7).
Click to expand...
Click to collapse
You have to download the flash_image file from this thread (look in the first post), and copy it to your device.
This is what I'm getting:
Unable to chmod /system/bin/flash_image: No such file or directory
I'm stuck on this step.
Related
Android System Recovery <3e> after using Odin3 v1.00
All:
I used Odin3 v100 to load Android 2.2 ROM
I followed the following steps
i9000XXJP2 Instructions
1. Remove the battery from your phone
2. Remove the SIM Card and MicroSD Card from your phone
3. Place the battery back on the phone
4. Hold down the HOME button, Volume Down button, and Power On button
5. You should now see a Download screen
6. Open Odin 3 v1.0
7. Click on the button “PIT” and load the “s1_odin_20100512.pit” file
8. Click on the button “PDA” and load the “I9000XXJP2-REV03-PDA-CL464213.tar” inside of the firmware download’s .rar file.
9. Click on the button “Phone” and load the “MODEM_I9000XXJP2.tar” inside of the firmware download’s .rar file.
10. Click on the button “CSC” and load the “GT-I9000-CSC-MULTI-OXAJP2.tar” inside of the firmware download’s .rar file.
11. Click the checkbox next to: “Re-Partition”
12. Your settings should now look like Figure #2
13. Plug your phone into your computer with USB Debugging on
14. Look at the gallery below to see if everything is going right
15. Once done, your phone will boot up
And now the phone Rebooted and I get the following message “update media, plase waite E:Cant mount /dev/block/mmcblk0p1 (invaild argument) E: copy_dbdata_media:Can't mount SDCARD: you storage not prepared yet. plase use UI menu for format and reboot actions. copy default media contenr failed.”
I have tried in vain to boot in the “Download Mode” to try and re flash the device and no luck.
I have tried using the following commands in SDK “C:\android-sdk_r06-windows\android-sdk-windows\tools\adb reboot-bootloader” and no luck
Am I hosed?
It seems to me that I need to reformat the internal SD Card but I cannot select any of the options in the Android System Recovery <3e>
The options I have are
Enter: OK Key, Select : Vol UP /Vol Down
Reboot system now
Applysdcard:update.zip
Wipe date/factory reset
Wipe cache partition
Format internal sd-card
The Volume rocket works to move between the above options but I can use the “OK” key nor any other to select an action
Anyone else run into this issue any thoughts?
I was going to try and see if I move the files to my extra SD card and see if this works but as I cannot select an action I am lost.
I have looked at the recovery (factory recovery option but as I mentioned I can not get to the Download mode.
Thanks in advance
Deadred
Try "adb reboot download".
You do know that flashing an i9000 froyo ROM makes your phone brick if you try to come back to a stock ROM, right? I see that you're looking at JP2, which might be early enough to avoid that, but I thought I should mention it. In the dev section, Eugene posted a non-bricking version.
thanks I will try this and let you know if it works
ttabbal said:
Try "adb reboot download".
You do know that flashing an i9000 froyo ROM makes your phone brick if you try to come back to a stock ROM, right? I see that you're looking at JP2, which might be early enough to avoid that, but I thought I should mention it. In the dev section, Eugene posted a non-bricking version.
Click to expand...
Click to collapse
I am having the same problem. The OK key is not OK cause does not work. Nothing in the world can make the device enter in download mode. And, of course, the adb can not work because the device is not recognized by windows.
I had the same issue, if you boot your phone w/ usb plugged in, you can go into adb shell, however, that's as far as I can get, is there any chance I can fix my vibrant by exploit the unrooted shell?
I had a similar issue and fixed it.
This thread has the solution: http://forum.xda-developers.com/showthread.php?t=788850
The best explanation is on the first post of page 3.
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Don't use Odin 1.0 Some of the newer roms state only use Odin 1.3 or above........... Use Odin 1.7
I'm new to Android, my first step was to research hardware and functionality. The choice, you guest it, gtab!
Now of to the good stuff. I ultimately want to root and update my Rom to vegan5.1. So far I have downloaded cwv08, upload downgrade and vegan. The problem is that when I try to restart using power + volume +, I do see the open box screen but then it just loads tnt and resumes boot. There has to be a step I must be missing here. Like I said I'm new to grab and android. Where do I start?
To my understanding, power with volume + without cwm install will run the command file in recovery folder. Preharps u are missing the file, preharps u are not naming the file correctly; too little details provided to tell..
try reading : http://forum.xda-developers.com/showthread.php?t=865245
same box with green arrow
I too have installed clockwork. Downgrade the bootloader then try to reboot into clockwork using the + and power. The tab acts like it is going to enter recovery says "Detect recover key press
Booting to recovery image"
Then it goes to that screen with he box with a green down arrow coming out of it and a progress bar. When it finishes it reboots. Still at stock rom, no joy at all.
A couple things I have tried. Copying a new update.zip to the root of the internal memory and the sd card, reboot with and without the sdcard inserted, rebooting normal then trying to get reboot recovery with + and power, copying the cwm update and recovery folder into root. No joy each time it it is the update box. I have not tried holding the recovery keys down in the dark while chanting xda but I think I missed my chance for that working last Friday.... when is the next Friday the 13th?
Thanks for any help or insight anyone can give us.
Bednab,I could not have explained any better. This is exactly what happens with mine. Today I encountered another challenge. My gtab will not connect to my-fy on open iphone. I have to figure this out before my road trip next month.
and there was much rejoicing
I kept at this and finally found a solution. A post pointed me to the answer on androidforums about the command file getting deleted out of the recovery folder after a successful update. I opened the recovery folter on the g tab and it was empty so I opened the one from cwm and edited it to this:
--update_package=SDCARD2:/update.zip
This way it points to my external card where I had a few custom roms. Copied it to the recovery folder in the root of the gtab, reboot into recovery mode and much joy!
So i have been stuck at the black screen for days. Searching online for answers and no luck. I am on the brink of just returning but i won't give up yet. So i got the new lg optimus v on black friday and rooted it. I installed busybox and superuser and clockwordmod. I put recovery from clockwordmod. Then being dumb at the time, i clicked factory reset. Now, i get black screen after the lg logo pops up. I look online and use androidscreencast. I use that to find out that i have recovery, but i can't see it because of those hittachi drivers. So, what i do is these instructions
Nandroid Instructions:
1) Extract the "BCDS-20110203-0357" file into the "nandroid" folder, under the "mem=477M" subfolder.
1a) For Clockwork Recovery, place the "BCDS-20110203-0357" file in /sdcard/clockworkmod/backup
2) Boot into recovery
3) Go into the "Backup/Restore" menu, and select "Nand Restore"
4) Allow it to restore
5) Reboot! System should be stock
6) Go below and flash stock recovery
Recovery Instructions:
1) Download flash_image and the stock recovery and nandroid back up
2) Extract stock recovery.img and flash_image to the root of your sdcard
3) Open up an adb shell, or terminal emulator on your phone
4) Enter the following codes:
flash_image recovery /sdcard/recovery.img
reboot recovery
right so now it worked. i then flashed a new rom i think. reboot and it works right? WRong. It loads up but I CAN"T SEE IT. I can hear the virgin mobile saying and androidscreencast shows me the android logo before crashing on me.
So i find out that i can do everything on it but can't see it. SO i go back to recovery with the 3 finger method. home + volume down + power. So then i decide to flash a new recovery.
So i go to adb. I type adb devices. IT shows my device and says its in recovery. Now i can't see it. So i try to use androidscreencast and it comes with an error.
Error attachment at the bottom for androidscreencast.
So i skip that and go back to adb. I try my last hope and try adb shell. Now that comes up with an error.
Error attachment at the bottom for adb shell issue.
Please if anyone could help with good detailed instructions. I don't want a link, some of those are super confusing. I need a good step by step instructions because i may be missing something and i don't know if that is the case.
EDIT: So i started with clockworkmod recovery menu some werid version. Then i put the recovery i was given here . Then after that i flashed this stock optimus v. The new recovery i flashed did not get rid of the black screen, i was still using android screencast. So, now when i boot up into "recovery" i don't know what to press or do and since android screencast + adb aren't there for me. I will have to do it blindly, but i need help.
Sorry to bump, but anyone help me?
To see if the recovery flashed right but isn't visible, boot into recovery, wait about one minute, press camera, then menu, then home. Depending on which recovery those are the select keys.
if the phone reboots after pressing those keys, the recovery works. Otherwise it didn't install right.
You can try
adb remount
Before
adb shell
to maybe get /system mounted for a shell prompt if recovery is broken.
Problems: the stock backup and recovery you flashed are for older ov's with a different screen driver, and stock recovery isn't rooted. Adb remount may not work unless you flashed the right stock zip.
bigsupersquid said:
To see if the recovery flashed right but isn't visible, boot into recovery, wait about one minute, press camera, then menu, then home. Depending on which recovery those are the select keys.
if the phone reboots after pressing those keys, the recovery works. Otherwise it didn't install right.
Click to expand...
Click to collapse
Ok i booted into recovery with the volume down + home + power button and let go when the lg logo popped up. I waited for 1 minute. I pressed the camera button first. No go , nothing happened. Then i pressed the home button (The button with the house on it). It then rebooted into android with the virgin mobile saying (I could hear it) So, recap I pressed home button and booted into black screen android couldn't see anything. Going to try adb when i get home.
TheRookie16 said:
Ok i booted into recovery with the volume down + home + power button and let go when the lg logo popped up. I waited for 1 minute. I pressed the camera button first. No go , nothing happened. Then i pressed the home button (The button with the house on it). It then rebooted into android with the virgin mobile saying (I could hear it) So, recap I pressed home button and booted into black screen android couldn't see anything. Going to try adb when i get home.
Click to expand...
Click to collapse
if it's stock recovery, adb will not work. if it's xionia recovery (might be, with the home instead of menu being select) you'll be ok with adb probably in recovery. if it won't work it'll say 'device not present' or 'connection refused.'
you'll probably have to turn on usb debugging blind in the blacked-out rom install to use adb to fix the recovery. Someone I helped with this some time back used a youtube video (here's the post) to find the right places to press on the screen to do that, then he was able to use android screencast to see recovery on his pc and fix it that way. if you can get debugging on, you can also use adb to fix it.
UPDATE: I did it. I turned on usb debugging with the black screen. I got android screencast and ddms. I can see the screen through android screencast. Now i have no root. So .
1. Root i want a good root for Lg Optimus V (New Screen Hittachi Screen)
2. How to flash working recovery that i can see . I want direct link to the recovery so i don't screw up.
3. How to flash working rom that i can see. Same thing direct link i ain't screwing up now.
4. How to flash a working stock Lg Optimus V New screen rom that i can use.
5. Do i need a new kernal or just working recovery???
nicely done.
you'll have to use screencast several times, then it'll get easier.
you'll need a few apps from market.
oi file manager to install apps from card.
flash_image gui to flash recovery
you need to check "allow install of non-market apps" under settings>applications
download gingerbreak 1.20.apk from here
copy it to your sd card. find it with oi file manager. click it and select install.
then run gingerbreak.
if you're lucky it'll work first try.
some people have had better luck using gingerbreak with the phone plugged into a pc.
it might take many tries if your phone is stubborn.
after it reboots, you can use flash_image gui to install this recovery
it's up-to-date and made to handle new or old screens.
then go to the iho thread herefor a gingerbread 2.3.7 rom, or Harmonia here
for froyo 2.2 rom.
both work without tweaking on your new screen.
both have install instructions in the linked threads.
after flash_image gui does it's thing you can turn off the phone and reboot into recovery
hold home+volume down, then hold power too, until after the silver lg logo goes away.
you could make a backup, it's normally advised.
use camera button to select.
good luck!
Thank you Very MUCH!!!!
One question about flashing the recovery. Can i use adb or some other method of flashing that recovery. Like say adb. I saw this somewhere wondered can i use this instead of flash_gui apk.
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Just wondering, it would be easier for me.
Yes, definitely.
you'll need flash_image copied to the card like the recovery for that.
just change "recovery.img" to the actual recovery filename, or rename the recovery itself to recovery.img first.
Thank You agian very much! I got everything working and i am running CM 7.2. Very happy that i don't have get another phone. Very very helpful.
There is no fofum for my phone, does anyone know of a guide on how to get root on the M Style? The universal Samsung root for flashing in stock recovery doesnt work, super one click doesnt work, and xray say my device is immune to the known exploits. Im willing to root the hard way if I have too, just need steps so I dont brick my phone. Must... Delete... Bloat...
Edit- M340K, sorry.
Bump... Anyone know how to root this thing?
One more bump in case anyone else needs this, I found this finally.
http://auv.me/Galaxy-M-Style-SHW-M340K-root-rom
Its a standard Odin flash, all the odin files and pre-rooted rom are linked here. You can flash it as an update and keep everything, no need to wipe. It does install some carrier bloat (so I had two sets of bloat) but its rooted, so you can get rid of all of it.
nifterific said:
One more bump in case anyone else needs this, I found this finally.
http://auv.me/Galaxy-M-Style-SHW-M340K-root-rom
Its a standard Odin flash, all the odin files and pre-rooted rom are linked here. You can flash it as an update and keep everything, no need to wipe. It does install some carrier bloat (so I had two sets of bloat) but its rooted, so you can get rid of all of it.
Click to expand...
Click to collapse
Hi, will this work on a Korean Galaxy M Style M340S? Please let me know!! :laugh:
domenicostorino said:
Hi, will this work on a Korean Galaxy M Style M340S? Please let me know!! :laugh:
Click to expand...
Click to collapse
It should. My phone says its an M340S now in settings but everything still works so it should work on both models.
Hi. Im using the same phone. But the link is in korean text i think. Help
Sent from my SHW-M340S using xda app-developers app
I just recently rooted my Samsung M Style SHW-M340S phone.
[GUIDE]
1. Download the attachment that I uploaded.
2. Transfer the zip file to the root of your sdcard either by connecting your phone to your computer or wirelessly (Do not unzip the file).
3. Turn off your phone.
4. Go into Recovery Mode by holding down the home button, volume up button, volume down button, and the power button at the same time. Once you see the SAMSUNG logo show up, release the power button and you should see the recovery menu. Select "apply update from sdcard". Use the volume up and down buttons to scroll up and down the menu. Press the home button to select your option.
5. Use the volume up and down buttons and choose the zip file.
6. After the update is complete, choose the option to "reboot system now".
7. After the phone finishes restarting, you now have a rooted phone.
Note: I'm not sure if this will work on a M340K/L phone as I don't have those phones to test out.
m340s
I used several methods to root my m340s. but non of them worked.
After following ur proceeedure when i run terminal emulator it shows $ mark. but when i run the code "su" (without quotes) there it was turned to # instead of $ and it allowed to run that code. I think its rooted now.
Thanks a lot..
I dont know what to do next. im serching the web..
ImAhNoBoDy said:
I just recently rooted my Samsung M Style SHW-M340S phone.
[GUIDE]
1. Download the attachment that I uploaded.
2. Transfer the zip file to the root of your sdcard either by connecting your phone to your computer or wirelessly (Do not unzip the file).
3. Turn off your phone.
4. Go into Recovery Mode by holding down the home button, volume up button, volume down button, and the power button at the same time. Once you see the SAMSUNG logo show up, release the power button and you should see the recovery menu. Select "apply update from sdcard". Use the volume up and down buttons to scroll up and down the menu. Press the home button to select your option.
5. Use the volume up and down buttons and choose the zip file.
6. After the update is complete, choose the option to "reboot system now".
7. After the phone finishes restarting, you now have a rooted phone.
Note: I'm not sure if this will work on a M340K/L phone as I don't have those phones to test out.
Click to expand...
Click to collapse
Hi, Thanks for pointing me the root, do you know rom for m340s?
M340s said:
I used several methods to root my m340s. but non of them worked.
After following ur proceeedure when i run terminal emulator it shows $ mark. but when i run the code "su" (without quotes) there it was turned to # instead of $ and it allowed to run that code. I think its rooted now.
Thanks a lot..
I dont know what to do next. im serching the web..
Click to expand...
Click to collapse
Yea...I'm not sure about how to root the phone through terminal emulator, so I'm not sure what you need.
nguyenhongquan said:
Hi, Thanks for pointing me the root, do you know rom for m340s?
Click to expand...
Click to collapse
I can't link anything here as I don't have 10 posts yet. You can look up "home_m340s.fh27" on google and you should be able to download it. Most will be from Korean sites though.
nifterific said:
It should. My phone says its an M340S now in settings but everything still works so it should work on both models.
Click to expand...
Click to collapse
Mine is M340s. I am about to flash my phone following your thread. Pls, any one confirm that the rom support English laguage. Thanks
ImAhNoBoDy said:
Yea...I'm not sure about how to root the phone through terminal emulator, so I'm not sure what you need.
I can't link anything here as I don't have 10 posts yet. You can look up "home_m340s.fh27" on google and you should be able to download it. Most will be from Korean sites though.
Click to expand...
Click to collapse
sir can you link it to me cause i'm having problem in my phone m340s i cant send any messages. i need it as soon as possible thanks sir
I would like to give credit to everyone who has worked on the android roms, and other guides. I have taken some of the info for this guide from the WIKI
It seemed we were due for a friendly how to guide on how to load a NAND rom on a RHOD device. I decided to write a step by step guide to help people out. This guide does provide a very basic ADB setup, but it is just enough to get you up and running. If you want to do advanced things you should get the full ADB, and learn more about it.
This guide is written for a RHOD400, Android GBX0*+3.4.26 rom, and a Win7 pc, but should be almost identical for the rest of the RHOD family, other versions of Windows, and most other roms.
It is assumed that you have unlocked your phone for custom rom loading in the past at some point. This is not the same as unlocking the sim card. This is 100% required. Please read here and/or here, and/or here if you need help with unlocking your phone.
This guide assumes that you know what a command prompt is, how to load windows drivers for a device, and can open zip files. If these things are not within your skill sets I would recommend that you find someone who understands these things to assist you.
Things you need.
1. A RHOD phone.
2. A micro SD card that is at least 512mb in size.
Tip: I suggest a sd card that is less than 4gb in size. There tends to be less compatibility issues with non SDHC cards. SDHC cards usually work, but if you have trouble this is a good thing to change. The SD card does have to be less than 64gb in size as the phone can not read cards larger than 32gb.
3. A usb based micro sd card reader. A usb based card reader is need to be compatible with the HP format tool. Some built in ones are usb based others are not. If you have one, you can try it and see if it works. It is not recommended to use your phone's sd card reader for prep work.
4. A usb cable that is known to work. Test it in WM first. On rare occasion I have seen cables that did work with WM and not Android. If you have issues, this is also something good to swap out during trouble shooting.
5. A windows based pc. *DO NOT USE USB 3.0 PORTS* Many reports about have come in about them causing issues.
The procedure.
1. Back up anything you want to keep from your phone. Everything on the phone will be wiped during this process.
2. Put the micro sd card into your USB card reader and format with the HP format tool. It needs to be a full fat32 format. Windows format is known to have issues on occasion, and this step is a work around for that problem. It is not 100% required, but if you have trouble it is 100% required during trouble shooting.
3. While this is formatting you can download the recovery (recovery_cwr_6.0.1.3.img) ***It has been found that the 6.0.1.3 recovery does not make backups correctly, resulting in md5 errors. You may use it if you are not planning on using the backup feature, or the older one by acl works fine. You can rename it to use the included scripts if you wish.***, rom (GBX0*+3.4.26 Full) , the boot loader, the needed usb android drivers, and the adb files.Gapps is optional.
4. Make sure your battery is at least 50% charged. I recommend a 100% charge. A dead battery in the middle of flashing can brick your phone.
5. Copy the RHODIMG.NBH, rom (GBX0*+3.4.26 Full), and the gapps (optional) files to the sd card and put it in your phone with the phone turned off.
6. Press the hold down the volume down button while pressing the power button. This will bring up the tri colored screen. It will then automatically go to the white rom update screen.
7. Follow the directions (press the power button on the RHOD400) to start the update. This should take less than 1min.
Troubleshooting tip:
If the phone sits at loading 0%, and never moves after 10 min you may not have unlocked your phone or there is an issue with your RHODIMG file. Verify that you have unlocked your phone (you can try loading a WM custom rom), format the SD card, re-download the RHODIMG file, and try again. Also try another SD card and SD card reader.
8. If the phone reboots automatically, that is fine. Otherwise when the phone says Update Success you can pull the battery to shut it off.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
11. Install the USB/fastboot driver for the phone. On Win 7 the phone showed initially as android device under other folder in the device manager. After the driver is installed it should be called My HTC.
12. Open the ADB Tools zip file, and put the platform-tools folder on c:\
13. Open a command prompt and go to c:\platform-tools\.
Once there type:
Code:
fastboot devices
You should get a response similar to this:
C:\platform-tools>fastboot devices
HT04TM300704 fastboot
If this is not working stop now and troubleshoot.
14. Now to wipe the phone in prep for loading (or reloading) the android rom.
There is a wipe.bat file I have included. You may run it, or you may type the following commands.
Code:
Fastboot erase recovery
Fastboot erase boot
Fastboot erase misc
Fastboot erase system
Fastboot erase userdata
Fastboot erase cache
15. Place the recovery (recovery_cwr_6.0.1.3.img) file into c:\platform-tools.
16. Now load the recovery image. If it is named recovery_cwr_6.0.1.3.img you may use the reload_recovery.bat or type:
Code:
fastboot flash recovery recovery_cwr_6.0.1.3.img
to load the recovery image then
Code:
fastboot boot recovery_cwr_6.0.1.3.img
to boot the recovery image.
17. Install the rom.
Using the volume keys highlight 'Install zip from sdcard' then press the call button to select it.
Highlight 'choose zip from sdcard' and press the call button to select it.
Highlight the rom file (GBX_3.4.26_Full.zip) and press the call button to select it.
Highlight yes and press the call button to select it.
The rom will now install. This will take a few minutes.
18. (optional) Install Gapps.
Using the volume keys highlight 'Install zip from sdcard' then press the call button to select it.
Highlight 'choose zip from sdcard' and press the call button to select it.
Highlight the gapps file (probably gapps-gb-20110828-signed.zip) and press the call button to select it.
Highlight yes and press the call button to select it.
Gapps will now install. This will take a few minutes.
19. Press the back arrow, and select reboot system now.
The phone should reboot into the Android rom now. It will take about 10min the first time. If you have waited more than 30 something has gone wrong. You should troubleshoot and try again.
At this point you have the basics all in place, and can start using your phone.
If you want to do basic ADB tasks (along the lines of installing apps remotely/side loading or pushing/pulling files) you will need to install the adb windows driver.
20. Press the thanks button if you liked this guide.
P.S.
If you have issues getting adb to work later, download and use USBDeview.exe to remove the HTC driver entries and then install pdanet for android to get the correct adb drivers installed.
So is my RHOD500 not supported by this Rom ?
denva said:
So is my RHOD500 not supported by this Rom ?
Click to expand...
Click to collapse
This is a guide, not a rom...
wizardknight said:
This is a guide, not a rom...
Click to expand...
Click to collapse
I know Is a guide . But need to know why my device keeps restarting at startup :crying:
denva said:
I know Is a guide .
Click to expand...
Click to collapse
Then why ask if your phone is supported by this rom?
denva said:
But need to know why my device keeps restarting at startup :crying:
Click to expand...
Click to collapse
Well if you have not listed all your trouble shooting steps, you will not get help from anyone. Our physic abilities are lacking these days.
Also posting specific questions in the thread about the rom you are trying to install will have a higher chance of getting useful feedback.
wizardknight said:
Then why ask if your phone is supported by this rom?
Well if you have not listed all your trouble shooting steps, you will not get help from anyone. Our physic abilities are lacking these days.
Also posting specific questions in the thread about the rom you are trying to install will have a higher chance of getting useful feedback.
Click to expand...
Click to collapse
Am refering you to this thread HERE av done all necessary things but still i get my device rebooting
http://forum.xda-developers.com/showthread.php?t=870081
denva said:
Am refering you to this thread HERE av done all necessary things but still i get my device rebooting
http://forum.xda-developers.com/showthread.php?t=870081
Click to expand...
Click to collapse
Well if you have done all necessary things, then your phone must not be compabtiable.
Maybe if you provided a list of your troubleshooting steps we might be of more help... Otherwise we have no choice, but to bow to your knowlage of having done all necessary things.
wizardknight said:
Well if you have done all necessary things, then your phone must not be compabtiable.
Maybe if you provided a list of your troubleshooting steps we might be of more help... Otherwise we have no choice, but to bow to your knowlage of having done all necessary things.
Click to expand...
Click to collapse
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
denva said:
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
Click to expand...
Click to collapse
Ok. I see the standard steps outlined in the guide that you have done. Now what troubleshooting have you done?
denva said:
Thank you WizardKnight for replying me.
This is the steps i use to do.
1. I use RhodiumWUnlocker to unlock my rhod500 , to get any rom loaded with it
2. I copy RHODIMG.NBH, GBX_3.4.24_Full, recovery_cwr_6.0.1.3 all to my 4gb SDard
3. Vol- + PWR and phone turns to the tri color screen, then the phone started to load the image files
4. I press PWR butt to start the update, within a couple of seconds the phone update successfully
I press resest button for the phone to boot up to see if it will go to the fast boot screen.
But i was unlucky always the phone restart itself within some seconds.
This is my Prb
Click to expand...
Click to collapse
Sounds like you just need to flash CWM... the CWM recovery image doesn't go on your SD card, you flash that from your computer using the "fastboot flash" command...
You can also try "fastboot boot <recovery.img>" - w/o the < >. Remember, this is done on your computer. That's why you need the fastboot drivers...
arrrghhh said:
Sounds like you just need to flash CWM... the CWM recovery image doesn't go on your SD card, you flash that from your computer using the "fastboot flash" command...
You can also try "fastboot boot <recovery.img>" - w/o the < >. Remember, this is done on your computer. That's why you need the fastboot drivers...
Click to expand...
Click to collapse
Ok Can you guide me how to do this on the P.C. ?
denva said:
Ok Can you guide me how to do this on the P.C. ?
Click to expand...
Click to collapse
It's in the guide, is it not...? Please read the guide. It walks you through everything necessary...
Edit - following the guide, you should be on step 9 at this point. Please continue with the guide.
arrrghhh said:
It's in the guide, is it not...? Please read the guide. It walks you through everything necessary...
Edit - following the guide, you should be on step 9 at this point. Please continue with the guide.
Click to expand...
Click to collapse
You Mean This .
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
My Phone doesn't bring this window
denva said:
You Mean This .
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
My Phone doesn't bring this window
Click to expand...
Click to collapse
You described this screen (scrolling text, blue background?) I remember you said you got it to fastboot, no?
Where is your phone getting to?
edit: nevermind fiddled with it, dont know what i did but it worked
I have a rhod400. I have been messing with OMGB as my daily phone OS since July 2012 and just installed this one about a week ago.
I have two questions/issues
1) Every time I try to reboot, it freezes. When I try to power off, it sometimes freezes, but usually reboots.
2) I can't seem to make persistent changes to the hosts file. After every reboot, it's set to the same old generic "127.0.0.1 localhost"
During boot, does the OS unpack a .img or something with the hosts file packed inside it? If so, where is it?
Thanks, guys. Other than these 2 issues, this flavor of android for rhodium is pretty solid. i like it.
jdoggsc said:
I have a rhod400. I have been messing with OMGB as my daily phone OS since July 2012 and just installed this one about a week ago.
I have two questions/issues
1) Every time I try to reboot, it freezes. When I try to power off, it sometimes freezes, but usually reboots.
2) I can't seem to make persistent changes to the hosts file. After every reboot, it's set to the same old generic "127.0.0.1 localhost"
During boot, does the OS unpack a .img or something with the hosts file packed inside it? If so, where is it?
Thanks, guys. Other than these 2 issues, this flavor of android for rhodium is pretty solid. i like it.
Click to expand...
Click to collapse
Please put rom specific questions in that rom's thread.
If you are running a newer than.27 kernel the reboot and power off functions do not work properly in any rom.
I believe that the host file is overwritten by the ram disk/boot.img on boot every time. Any changes will not stick.
There is a chance these issues may be fixed on the next release of GBX, but no promises.
arrrghhh said:
You described this screen (scrolling text, blue background?) I remember you said you got it to fastboot, no?
Where is your phone getting to?
Click to expand...
Click to collapse
My Device always restarting after passing through all the tutorials
denva said:
My Device always restarting after passing through all the tutorials
Click to expand...
Click to collapse
This isn't enough information to help you.
If you're not going to provide detailed information on what is happening, no one will be able to help you.
Perhaps NAND is not for your device. Flash back to WinMo.
arrrghhh said:
This isn't enough information to help you.
If you're not going to provide detailed information on what is happening, no one will be able to help you.
Perhaps NAND is not for your device. Flash back to WinMo.
Click to expand...
Click to collapse
Yeah sir i think so , bcz av search all ova the net only rhod400 is ok
Unlucky for rhod500 am waiting maybe nxt update
anyway thank you arrrghh and wizardknight for your help :good: