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:
Related
Obviously there are reasons for wrong doing but after soft bricking my vibrant (not really doing anything just started force closing upon a morning reboot and now i'm stuck) I'm wondering why this happens? I've seen a lot of posts saying that from "flashing too many ROMS" but i flashed a boatload of roms on my g1 and as long as I did it correctly it was fine because it should be wiping all data and replacing it with a whole new ROM but yet when I flash the exact zip files that have worked before they all result in a black screen, i'm currently trying to find a solution to get to stock ( i have a mac ) but I mean, I want to go back to bionix fusion but not if I know that after every couple flashes the phone will go black on me and ill have to start all over at stock again. Sorry, I just want more of a specific reason than "flashing too many roms"
joe.kerwin said:
Obviously there are reasons for wrong doing but after soft bricking my vibrant (not really doing anything just started force closing upon a morning reboot and now i'm stuck) I'm wondering why this happens? I've seen a lot of posts saying that from "flashing too many ROMS" but i flashed a boatload of roms on my g1 and as long as I did it correctly it was fine because it should be wiping all data and replacing it with a whole new ROM but yet when I flash the exact zip files that have worked before they all result in a black screen, i'm currently trying to find a solution to get to stock ( i have a mac ) but I mean, I want to go back to bionix fusion but not if I know that after every couple flashes the phone will go black on me and ill have to start all over at stock again. Sorry, I just want more of a specific reason than "flashing too many roms"
Click to expand...
Click to collapse
Step 3: Flash Bionix Fusion
This is the final step of the installation. This presumes you are already rooted and ready to go. If you are not, then you will need to root and install rom manager first.
1. Download the rom of your choice and place the file onto the root of your internal sdcard.
2. Reboot into Clockwork Recovery.
- From Rom Manager app, select 'boot into clockwork recovery'
- From ADB, type 'adb reboot recovery'.
3. From the main clockwork recovery menu, use the 'down' volume control to scroll to 'install zip from sdcard'. Press the power button. this will take you to a second menu screen.
4. From thet second menu screen, scroll to 'choose zip from sdcard' and select with the power button.
5. Scroll to the file name of the rom you downloaded and press the power button. It will ask you to confirm your choice, select 'yes' and the rom will begin to flash. DO NOT TURN OFF YOUR PHONE DURING THIS PROCESS!
6. Once the flash is complete, select 'go back'. Now select 'reboot' from this menu.
7. Allow your phone to reboot completely. The first boot will take a few minutes, please be patient.
8. Once booted into the home screen, please allow your phone to sit for 5-10 minutes to allow all boot procedures to take place. Keep in mind, you've just heavily modified your device, it needs time to adjust to the new changes.
9. Wait roughly 15 minutes after the first initial boot and then restart your phone one time. You may do this by holding the 'power button' and selecting either shut down or reboot.
chichu_9 said:
Step 3: Flash Bionix Fusion
This is the final step of the installation. This presumes you are already rooted and ready to go. If you are not, then you will need to root and install rom manager first.
1. Download the rom of your choice and place the file onto the root of your internal sdcard.
2. Reboot into Clockwork Recovery.
- From Rom Manager app, select 'boot into clockwork recovery'
- From ADB, type 'adb reboot recovery'.
3. From the main clockwork recovery menu, use the 'down' volume control to scroll to 'install zip from sdcard'. Press the power button. this will take you to a second menu screen.
4. From thet second menu screen, scroll to 'choose zip from sdcard' and select with the power button.
5. Scroll to the file name of the rom you downloaded and press the power button. It will ask you to confirm your choice, select 'yes' and the rom will begin to flash. DO NOT TURN OFF YOUR PHONE DURING THIS PROCESS!
6. Once the flash is complete, select 'go back'. Now select 'reboot' from this menu.
7. Allow your phone to reboot completely. The first boot will take a few minutes, please be patient.
8. Once booted into the home screen, please allow your phone to sit for 5-10 minutes to allow all boot procedures to take place. Keep in mind, you've just heavily modified your device, it needs time to adjust to the new changes.
9. Wait roughly 15 minutes after the first initial boot and then restart your phone one time. You may do this by holding the 'power button' and selecting either shut down or reboot.
Click to expand...
Click to collapse
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
joe.kerwin said:
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
Click to expand...
Click to collapse
Well, if you follow the instructions mentioned in the fusion post it should clean wipe your phone and give you a stable phone, give it a try without tweaking the kernel or anything to make sure you are not getting any black screens.
1 question though did you overclock your phone?
I would take 1 step at a time, first get your phone to stabilize. The reason I referenced Fusion is because, Fusion is much more stable than the Stock Samsung JFD.
joe.kerwin said:
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
Click to expand...
Click to collapse
Did you flash anything over Voodoo?
i've never used voodoo and no i wasn't overclocking even though i had an OC capable kernel. My problem was my phone doesn't turn on, and i dont have a PC to use ODIN also I mentioned that no matter what ROM I flash my phone wont turn on, flashing fusion would not fix it. Anyways I went to tmobile and just told them "my phone doesn't work" and this really cool guy just swapped it for me no questions asked even though i'm well beyond that two week grace period.
Bricks don't happen from flashing too many roms. I've been flashing roms constantly for the last couple weeks, and I've yet to brick my phone. Bricks are usually caused by people not carefully following instructions, or by flashing incompatible rom/kernel combinations. If you play it safe and are careful, you won't brick your phone.
joe.kerwin said:
i've never used voodoo and no i wasn't overclocking even though i had an OC capable kernel. My problem was my phone doesn't turn on, and i dont have a PC to use ODIN also I mentioned that no matter what ROM I flash my phone wont turn on, flashing fusion would not fix it. Anyways I went to tmobile and just told them "my phone doesn't work" and this really cool guy just swapped it for me no questions asked even though i'm well beyond that two week grace period.
Click to expand...
Click to collapse
Most probably the oc/uv kernel, some phones cannot handle undervolting.
Sent from my bionix powered Vibrant
My phone is pretty new... I only had it unlocked and rooted.
It just soft bricked on me this morning after listening to music... Not exactly sure why.....
i've been stuck here for some time trying to find a solution to this. rooted fin but when i tried every time i try to do a factory wipe it aborts and when i try to install a zip/rom through clockwork it just says "E:can't find MISC" i've looked around and haven't been able to find something that helps, this may be due to me being to to android. can someone help or just give me directions to start all over again.
I get that as well, but it doesn't seem to make any difference. But what do I know, it all seems like a black art!
I have the same problem, just flash Streakmod recovery, not clockwork.
never heard of Streakmod recovery i gotta find it and give it a try tonight. ty
http://forum.xda-developers.com/showthread.php?t=840326
You could have use search and not open a new thread but oh well everyone does whatever in this forum.
@edrill i saw that but i dont know what "fastboot -i 0x413c" is. i only ever flashed using the install-recovery-windows.bat. don't know how to flash just the img by itself.
now i'm stuck on the dell logo. tried Stock Android 1.6 Package but my streak isnt in a good mood anymore
Try this link.
http://forum.xda-developers.com/showthread.php?t=776883
Has everything you need to know about fasboot, etc.
i'll print that out tonight and read through it. i work nights so its sleep time now. i'll let you know how it goes thanks for your help
captaingohan said:
i've been stuck here for some time trying to find a solution to this. rooted fin but when i tried every time i try to do a factory wipe it aborts and when i try to install a zip/rom through clockwork it just says "E:can't find MISC" i've looked around and haven't been able to find something that helps, this may be due to me being to to android. can someone help or just give me directions to start all over again.
Click to expand...
Click to collapse
Not Android Development
Please post in the correct Sections
Moving to Q&A
got it working now got an Os splash screen but it works this is how i did it
HOW TO RESTORE YOUR STREAK BACK TO FACTORY CONDITION:
Option 1.
1. Download the stock recovery ROM HERE (http://hotfile.com/dl/61659279/506ac...stock.img.html) and the stock official Dell ROM HERE (http://hotfile.com/dl/61663686/7d7e5...99_21.pkg.html).
2. Rename the stock official Dell ROM 'Update.pkg' and put it in the root directory on your SD card.
3. Boot Streak in fast boot mode (hold camera button when turning on), press 'Fast boot Mode' button, wait 10 seconds then connect to your PC (must have Dell PC suite installed).
4. Open a command prompt, navigate to the folder where your 'fast boot-windows.exe' is stored.
5. Type 'fastboot-windows.exe -i 0x413c flash recovery c:\recovery.stock.img' . Make sure the .img file is in c:\ directory. The program will now update the recovery image on your Streak.
6. Once the phone reads 'Recovery Done', remove the battery and insert it again.
7. Boot Streak in Recovery mode (hold down vol up and vol down when turning on) and select option 2.
5. Wait till it installs and it'll boot into Android....DONE!
Option 2
Place update.pkg on SD card root folder
Power up streak whilst holding both volume buttons
Select option 2 - "software upgrade via Update.pkg on SD card" by pressing camera button
Press camera button again Job done
i think later tonight i'll try to upgrade to 2.2 wish me luck and thanks for all your help EDRILL
i spend a whole night now to get android work on my hd2. had the same error message...
now i know why it didn't work and the solution was dead easy i had to beat myself...
sd card has to be FAT not FAT32
after formatting the card this way, everything works fine ^^
Are you sure it has to be FAT? I have heard there are restrictions on this format that would make it impracticle to use on a 16gb microsd.
Also how you format to fat? my computer only has 2 options to format: Fat32 and exfat.
FAT can only allocate up to 2 gigabytes of storage so there is something dodgy about that explanation.
I'll happily admit that I'm a noob and I never should have done this. After having a couple of android fanatics puffing their chest out about how easy it was to toss Froyo on a phone, I tried it and now I'm stuck.
I have a Samsung Fascinate on Verizon's network. I follow the instructions I found and now I'm stuck staring at some boot up and recover screen. What I can't do is select any of the options give to me.
I'm starting at the following screen:
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
(However, since it's a verizon phone, I had no sim card and I left my micro SD card in place)
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 can get my phone to the option above and I can still get to download mode
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't use the “OK” key nor any other to select an action
Someone please please help me! Even if I can just reset it to where I was before, I honestly don't think I'm far along enough that I can't undo what I did, I just don't know how ...
I really really need a hand
The biggest problem of what you wrote, is you followed the instructions of the wrong phone.
The verizon fascinate is the i500 not i9000. The verizon fascinate doesnt use the phone button on odin.
Odin this file for 2.2: http://www.droidforums.net/forum/sa...roms-w-root-new-clockwork-updated-2-11-a.html
Get the Full Stock Froyo Leak+root+Froyo Clockworkmod file, and once it successfully instals, you can instal different roms.
Would you be able to shoot me a private message with instructions a little more detailed? At this point, I'm absolutely paranoid about being in WAY over my head
You can use this thread to get back to rooted 2.2.
http://forum.xda-developers.com/showthread.php?t=977493
+1 to the post above me. You will more than likely need to use heimdall. (the hardest part is installing the drivers. Once you figure out how to do that it's similar to Odin)
At this point, you are extremely lucky to still have a course of action. Rarely does flashing that many files from another device actually leave you with an easily recoverable phone.
Good luck!
Since you used pda, you might still be safe, but I doubt you will be able to recover this. You are probably out of luck after this accident.
Oh dear.... you definitely did flash firmware for the wrong phone on to your phone.
Since you can still get into download mode you *might* have a shot. Definitely try that thread linked a few posts back. Flashing the firmware for the i9000 to a i500 might have done something screwy to your phone's memory partitions. The thread here has a .pit file which should repartition your phone's memory.
Please let us know if you do bring your phone back from the dead. Best of luck.
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.
I rooted my LG recently to get rid of the crapware that was on by default. But, of course, it wasn't enough for me. I tried to flash a new ROM, and everything went to hell. Now the boot screen won't go past the LG logo. Does anyone know how to reset the device back to factory standard?
Hard reset doesn't work (home + volume down / up + power)
Windows/Linux doesn't see the plugged in device.
adb doesn't see the plugged in phone
I tried to put cyanogenmod on, which was probably a bad idea. I've heard that this problem may be irreperable, and I just want to see if there's any way to avoid having to try and deal with Verizon.
Before flashing (using rom manager), I made sure to choose the backup the current rom option. I've heard that I should be able to restore that backup, but there's no way to actually connect to the phone at the moment.
Any help would be appreciated.
EDIT: I've gained access to the SD card by plugging it into an external reader. I can see the recovery image that clockwork made. How can I get the phone to boot into it?
theevan117 said:
I rooted my LG recently to get rid of the crapware that was on by default. But, of course, it wasn't enough for me. I tried to flash a new ROM, and everything went to hell. Now the boot screen won't go past the LG logo. Does anyone know how to reset the device back to factory standard?
Hard reset doesn't work (home + volume down / up + power)
Windows/Linux doesn't see the plugged in device.
adb doesn't see the plugged in phone
I tried to put cyanogenmod on, which was probably a bad idea. I've heard that this problem may be irreperable, and I just want to see if there's any way to avoid having to try and deal with Verizon.
Before flashing (using rom manager), I made sure to choose the backup the current rom option. I've heard that I should be able to restore that backup, but there's no way to actually connect to the phone at the moment.
Any help would be appreciated.
Click to expand...
Click to collapse
LOL wow i just did the same thing ... i am "was" experimenting with the optimus v cyanogen rom and now im stucc at the skate droid screen.. any help would be nice
msg me for help got my self out of it
u got out that situation? i installed a app and my phone needed to reboot now im stuck
I need help. Vortex stuck on LG logo after i flashed a rom using rom manager!
Please Please help!
infamousr60z said:
msg me for help got my self out of it
Click to expand...
Click to collapse
Consider posting how you did it here for everyone to see.
naenee said:
Consider posting how you did it here for everyone to see.
Click to expand...
Click to collapse
Yes, please do post it. I attempted the LOL 1.4.2 rom for Optimus One and am now in this same situation. I have a working rom on my sd card if I could just get to the recovery screen.
[Solved!]
s3rvant said:
Yes, please do post it. I attempted the LOL 1.4.2 rom for Optimus One and am now in this same situation. I have a working rom on my sd card if I could just get to the recovery screen.
Click to expand...
Click to collapse
I read a few posts mentioning that they were able to reset their phone using their ac adapter, but I hadn't any luck trying it that way, until a good friend of mine used some google-fu to determine that the order in which you do things matters! Here's the steps I had to take:
Remove battery from phone
Begin holding power, volume down and home
Plug phone into ac power WITHOUT LETTING GO OF BUTTONS (wasn't easy for me either)
Phone should boot into recovery (in my case the custom recovery)
You can let go of those buttons now
Install battery
Flash your phone and rejoice!
THANK YOU! The part I wasn't getting was the plugging into A/C while holding the buttons down...you're a lifesaver!!!
This did not work for me. I tried putting the phone into recovery mode, but it still just booted up as normal. I'm running out of ideas and patience here...
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Lgtools
estoy en la misma situacion, yo cuento lgtools de Setool Box3, la cual soporta lectura y escritura de sistema de Lg vortex vs660, pero no logro que me lo detecte para cargar firmware completo, mi problema fue que flashe el recovery desde el ROM MANAGER y se queda en el logo.
I recovered my friend's phone using the following procedure
I just fixed a friends phone so I thought I would share in case it helps anyone. This is for the LG Vortex on Verizon. Might work for other carriers.
Download and install the Vortex drivers from LG's mobile support site www dot lg dot com/us/support/mc-support/mobile-phone-support.jsp
Download and install the LG Mobile Update utility www dot lg dot com/us/support/mc-support/mobile-phone-support.jsp
Run the LG Update app and make sure your phone is up to date. You can also try the Recover option if it can't update. This phone's firmware was up to date.
Install the Android SDK from google.
Access backdoor recovery through ADB
Plug phone in to laptop usb
Press and hold down the volume down key, the home key, and the power key at the same time. Keep them pressed until the screen goes black then you can release. If it goes in to some other visible recovery you can simply skip some of these steps
At this point your computer should start to recognize the phone and go through a series of driver installs
Once that is complete you should be able to go to the command line and enter the ADB shell
Follow the procedure at the following link to get the clockworkmod recovery installed
androidforums dot com/getitnowmarketing/330813-all-one-recovery-thread.html
Once you are able to boot in to clockwork, immediately do a backup. Then clear your data, cache and dalvik cache, then reboot. This won't always work, but many times it will allow you to boot a ROM that gets stuck booting (like this phone). If that doesn't work then just go back to recovery and utilize a manual ROM flashing procedure you can find on many forums.
This process worked great on this phone so hopefully someone else may have similar luck.
Sorry for cutting up the links, i'm new to the forum. Just replace the "dot"s with . obviously.
Try this worked for me
Here's a different method of unbricking your vortex V660. With limited support and methods for this device it seems to make everything more complicated in finding a soluttion around certain but complex problems. I tried to use some of the other metheds listed on android central and XDA...such as, taking the battery out, holding home, vol -/+ and power key at the the same time the phone back in while it was connected to the computer. I wasnt able to get anywhere with these methodes,I also thought qbout trying the unbutu method to unbrick it then I thouht that was to much of an effott. I read all the comments and differnt methods and decide it wasn't worth the risk, I re-woked a different method for unbricking, there's prob about a 90% possibility of it working for your LG.This just happenes to be my own solution or workaround if you find yourself screwed like i did with no type of support.
The reason this didn't work was because I didn't have cwm installled nor did the phone have the original firmware installed, my mistake, I wiped that off too, happenes when you have to much to drink lol, the hard reset buttons were a no go as well since they take you into cwm or the orignal firware from verizon {all mine did was take me to a black screen because there was nothing there for it to load.} Some how or another all was wiped clean and I was in a catch 22 while being bricked. I found the vs660 recovery firmware but I knew i really didn't need to install it so i didn'nt.The bricked happened after I installed Titanium Backup then uninstalled launcher pro so then I restarted and got to the point where the ring Fire or boot animation was trying to load ,and it just just hung there. I don't care for the app launcher pro I would rather use awd launcher, if u haven't noticed you have to pay for the pro version of launcher pro just to rezize widets, so im wondering why this app was added to the Rom Cyan7.2 in the first place. So with no cwm, no stock image, and no way to make an sdcard boot into m to unbrick it my hopes and last resort were to pray that.I had usb debugging enabled.
First thing you have to install is called jdk-7u3-windows-i586] the other file called installer_r_windows wont't allow you to install until the install of JDK is complete.It'd ok to lauch the installer-r26-windows first because it ill drnf you directly to the site to downloadthe JDK file. Install these two programs first, (google how to ADB tutoria if needed? So after downloading that you will need to download the right drivers (for the voerex) Software name (Driver_WHQL_ML_Ver_4.9.7_All_Win7_LGEAll)(Google Search It)} There's 1 other thing we to have to do before seeing if your decice is listed in ADB. We need to add a line to the Envioronment Varibles section under System Variables at the bottom. Here's how to get there in Win7, right click on my computer, advanced tab, at the bottom Environmental Variblesm, click itlook down under system variables and scrooldowm until you see something called Path and add this line to end of it, ofcourse clickit edit then copy and past his line including the semicolon ;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools now save it amd exit. The reason this is done is so we won't have to contantly navigate through cmd prompt to the directory and list commands. This is prevent you from have to navigate to the folder evertime u want to run the program or any cmds. Now that were all setup lets connect to you phone's data cable to the pc and the phone, and again make sure abd debugging is enabled. Settings, applications, development, the check in the box for debugging, if it's not enabled you will get the turn on usb feature your phone so not what we want. Now opem the cmd prompt run the cmd cd.. then cd.. now you should C:\>, you can run the cmd adb devices now hit enter and you you see a long 14 to 16 digit # then that means your devices is succesfully connected and talking to your PC.That long # should be your MEID HEX# to your phone if you dont see that and you see somethine else then go back though the guide to see if you missed something during setup. If setep properlly in the cmd prompt type adb devices and your phone will automactically show its long#, after that type the cmd adb reboot at which point through cmd promt the device will reboot itself. Here a little secret just because you don't have youtr verison's orignal firmware nor a working ROM on you phone such as froyo 2.2.1 or 2.2.2 doesn't mean anything, you are still rooted and wont have to downgrade to 2.2.1. Side note ( z4root didn't work for my lg vortex, I tried gingerbreak 1.10 and later gingerbreak 1.2 which both worked just fine, z4root just hung on my phone, sry i bounced off topic but i took me 24 hrs of troubleshooting till I got it back up and running.
This method I would say this only applies to the ones that don't have cwm installed on their internal drive it acccidently wiped the original firware off their phones and don't have anything to boot into. I don't have the orignal verizon stock installed, essentially you hit the same buttons on the phone to do a hard reset or to boot into recovery as you normally would. If you neiher on your phone then ADB is your saving grace. Another tutorial I seen was something about installing ubuntu lunux, it just seemed liked to muck work for me, plus I didn't want linux on my box anyways, not til im ready for building a linux kluster later.
let get started...go and download the Adb software which is called Android-debug-brigde...you will also have a visual demo to guide you through the setup) (ADB file) name installer_16-windows,install this this file last to the root of C:/ once done its location will look like this c:\android-sdk-windows ( this is important to make sure you extract the exe to C:/android-sdk-windows (you can take advantage of youtube's a great resourse for viual walkthroughs} or google it,.i have had to do i know's our there , well if you more of a reader search google or xda it will breakdown the core or the installing of the actual files can't post links here but you have to post a minimum if 8 tines b4 you can post links outside this site.
Once all that's setup you need to confirm that its linked properly. Phone off or on during this process I wouldn't think it matters,my devices were on, so conntect you data cable to you usb port and the other end to your phone where you normally power it. This is the time you better hope USB Degugging is enabled. If it is you will see the little Android character and something that looks like a usb icon in the status bar of your phpne, so if you pull down your status bar is will tell your if you are in use debugging mode,. in the status bar depending on where your bricked. if you are in a booploop all its going to do it make that noise of connecting and disconnting. you may have to find fifferent approach to fix it, only solution I can give you if to try home, vol +, and power down til you get a black screen and hope it hangs there there long enough to so you clear it. So it this aproach words on a bootloop let me know in the comments.
Once everything looks good open up your device manager
Just under your computer mame u should see somethig called ADB Interface
under that from the drop arrow you will see android plactform sooner single ADB Interface, click on that and you will see android plattform sooner single ADB Interface, then under modems you will see LGE Android Platform USB Modem, and last at the bottom your youw will see universal serial bus controllers, select that and you should your see LGE Android Platform Composite USB Device, If you see all that that your 100% convered
Now to get your phone out of that nasty brick and we don't need need any firware or Roms to do it...
Open cmd prompt, type cd.. then cd.. again now your in C:\>
now type cd android/sdk/system (note the CD just means change directories) now were in the folder called c:\android-sdk-windows
From this directory is where were going to run our commands since we can't do it in cwm.
type wipe system and hit enter
wipe system you will see a alot of errors like it didnt do anything but that's ok next step
type wipe data hit enter
once done pull cable reboot phone wait to it to come up to where to you have to touch the andoid like your setting up the phone for the first time again, warming u more that lickly will get an FC during setup and it will brick again on the same screen. Repeat wipe system and wipe data again, the gp though the setup on the phone again, if have have another FC one last time so again wipe system then wipe data, this time there shouldn't be anymmore FCs, I have to go through wipe system and data 3 times b4 the FC's stooped and I will able to to to the activaton screen > My phone is a refurb so if would let me past the activation screen this time as when im loading up in CM7. last issue I faced was the accivation screen, Now I did some reading on this and there are a couple of thing you can one of which worked for me., You can tap the four counrers in the clockwise direction which didn't work for me, or what did, I click activcate then entered *228 then hung up, avtivate again *228 hungup, then activate again,*228 hugnup and this time I was able to skip activation anb and was again to load cwm and flash my phone, so its not longer bricked and I dont have to worry about the avivation all though it will comes up U can stip it and It wont keep me from me phone, I have VIOP setup over my 4g LTE, any questions about this type hack just let me know, ( I have an 18 Page Paper about how it works how to set it up, its free and no download charge for the APK) and I will post it. Forwaring the paper 18 pages long and pretty in depth, I dont explain the backend of how it works but just a little, its mainly the frontend and to set it up and all the routing.
I also have video demonistrations on youtube for bypassing the registration of your Nook Color
Channel is under wudamnify
Vortex sux
Okay ... so my vortex is nothing more than a paper weight at the moment. When I turn it on, the LG screen comes on for 3 seconds, then the screen goes blank, then it starts over again. I can't turn it off after it starts its boot loop. I have tried using the recovery keys, and nothing. If I plug it into the computer it will turn on and do the loop over and over again, and i still cant power off. I have a 4gb micro with cwm recovery, but i do not know how to get this phone to boot into the cwm recovery. your help would be appreciated.
Here's what worked for me
corydespain said:
Okay ... so my vortex is nothing more than a paper weight at the moment. When I turn it on, the LG screen comes on for 3 seconds, then the screen goes blank, then it starts over again. I can't turn it off after it starts its boot loop. I have tried using the recovery keys, and nothing. If I plug it into the computer it will turn on and do the loop over and over again, and i still cant power off. I have a 4gb micro with cwm recovery, but i do not know how to get this phone to boot into the cwm recovery. your help would be appreciated.
Click to expand...
Click to collapse
I was in a similar situation and was able to get to recovery by taking out the battery, holding down the buttons required to get into recovery and then while holding down the buttons, plugging the phone into the wall charger. Once it was in recovery I put the battery back in and flashed back to a known good rom. Not sure why this worked over just turning it on normally, but it's worth a shot.