My viewpad 7 is boot-looping, it is restarting before reaching the launcher screen, and also stuck while booting into cw recovery mode. I changed font files of the root before this happened. Any way to restore it's rom without using cw recovery mode? Is it possible to boot from sd card?
Can you boot your VPAD7 into CW Recovery Mode ? (Hold down Vol. UP and Vol. Down buttons and press Power at the same time to get into recovery mode)
Anyway, you most likely need to flash a stock ROM first using the SUTL3_v1.7.9 utility available from Viewsonic and then one of the FM6*.nb0 files - it might not recognize or "see" the device, keep trying & reset/reboot and use that small "reset" button on the bottom if necessary.
Check your FTM (Factory Test Mode) for your Hardware & Software build info - and try to match the closest *.nb0 file for flashing. Hold down Vol. Down while pressing Power to start & run FTM, use tiny pin hole to press & reset device/exit this mode.
I haven't done this in a while, but it will most likely change the device back to unrooted, stock form. And, you will lose all your custom app settings - but it should come to life after a successful flash, restart & give it 5 to 10 minutes to complete initial install & setup - and, you should see your original screen again.
Then, follow steps to get it rooted again, do a NAND backup & set it aside for safe keeping, then reflash your choice of custom Rom, etc. Detailed directions are here on XDA - good luck & let us know if we can be of further help ....
I was making the root to my viewpad 7, and during the process, I took out the cable by accident. And now it's impossible for me that the process finish, it always stuck. Some ideas, please?
luisete123 said:
making root .... and during the process .... took out the cable .... And now it's stuck. Some ideas, please?
Click to expand...
Click to collapse
OMG, okay - relax & take a deep breath ....
It should be recoverable, I think - you will just need to flash the "proper" factory stock ROM first, get it working again & then repeat the rooting process.
First, check your hardware/software version in the FTM mode (it's for diagnostic, flash & download to ROM, etc. ....) & safe to do - hold down the left Volume Down key on top while pressing the Power button with the device off. If necessary, get someone to reset the device (use the smallest pin hole on the bottom of the device.) A pin works best but small paper clip will do.
In a few moment, it will show "Enter FTM Mode" and then display the VPAD7's info -
SWVer=3.410 or whatever is on yours
Model: FM6-0001 or whatever yours say
HWVer: 107 (106, 103 or whatever)
What to do with this info - it will help you select the correct or closest factory ROM to flash & restore your Vpad7 to stock condition, unrooted.
You will need one of the SULT3 or for oldest ROM, maybe SULT2 is better - download & save to PC, unzip the SULT* - and follow onscreen prompt & instructions to select your *.nb0 file.
Another suggestions, since you cannot get into Recovery Mode to wipe dalvik, cache & full system/data first, it might help to flash the *.nb0 file twice - it will take a bit of time, maybe 10 minutes or so and a few more minutes to do its initial boot-up configuration. Be patient - and write down any error messages, etc. if you run into problem.
It's best to take out any SIM card and even mSD card from your device, not required but recommended. When you can boot up again & get pass the Android activation wizard/screen, you can power down - put the mSD card back in and reboot again.
http://vsg.viewsonic.com/ViewPad7/
Good luck - there's a wealth of helpful info posted here, please set aside & take time to read it first & refer to those notes. Good Luck & Cheers - let us know if you succeed ....
A thousand of thanks Letitride!!
Before continue making mistakes, I want to ask if there is any problem to use SULT3 (because I read u posted it before) instead of SULT2, because yesterday, before post my question, I already installed SULT3_v1.7.9...
When I enter FTM Mode, the display shows:
SWVer=3.16R
Model: FM6-0001
HWVer: 106
So now I dont understand. I am a little bit lost, but I think I must to download something else from the viewsonic web that u posted (I can't repeat the link because I am new), isn't it?
Thanks again for your help. I know there are lots of help already posted, but about my problem I didnt find anything, that's why I asked. Thanks!!
Ok, I will explain what I tried, and the next error:
As I said, I already installed SUTL3_v1.7.9, so I used it. I downlodes for the viewsonic web that you posted FM6-316Q-0-1008-A01.nb0, and this is the error that the program said me:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
Maybe I need to uninstall SUTL3_v1.7.9 and try with SUTL2.1_v1.8.4? During the process I don't need to select nothing in the ViewPad screen, do I?
Thanks again!
EDIT:
I installed the SUTL2.1_v1.8.4 (without unistall the SUTL3_v1.7.9, and there is the next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
luisete123 said:
Ok, I will explain what I tried, and the next error:
I installed SUTL3_v1.7.9, FM6-316Q-0-1008-A01.nb0, the error:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
EDIT:I installed SUTL2.1_v1.8.4 (without SUTL3_v1.7.9, and next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
Click to expand...
Click to collapse
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Letitride said:
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Click to expand...
Click to collapse
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I think it was a problem while I was downloading yesterday, because I don't know why, the speed was very very low. Otherwise I can't understand, because in this other laptop that I tried, the Windows is not original, and in mine it is...
So now, as I understand, I can root it without any problems, can't I? I will wait untill tomorrow, because I am on hurry now, and I dont wan't to do any more mistake
I am really greatful Letitride, thanks again!
luisete123 said:
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I can root it without any problems, can't I?
Click to expand...
Click to collapse
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Letitride said:
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Click to expand...
Click to collapse
I am again really thank you! But, I still have the same problem... I am trying to use SuperOneClick v1.7 program, and again get stuck...
I will try with GingerBreak, but I was reading here another post about this program and I will need to read it again, in order not to make another stupid mistake!!
Cheers anyways!!
Related
UPDATE REGARDING FLASHING OF HARDSPL - Specifically the error message "we have detected that you appear to already have unlocked another device"
- contact with the creators of HSPL has been established.
- If you have EVER used HardSPL before (on any phone BUT the one you're trying to flash) you will need to request another "license"
- OliNex will provide up to 2 or 3 licenses, but more than that is deemed commercial and you will have to purchase them thereafter.
- If you are sure you have NEVER flashed HardSPL before, then please standby until I get more information from OliNex, regarding steps we can take to resolve any conflicts.
- more to come.
Dear all,
i mentioned to some people a while back that I could send them detailed instructions via PM, helping them install their first custom ROM (available from our many fine cooks and chefs here: http://forum.xda-developers.com/forumdisplay.php?f=486)
Now, quite a few have been pm'ing me since, asking for help, so i thought i'd make a public post for all those who are wanting to flash their phones, but are scared or uncertain of making that first step.
SO, in as simple a way as possible, here we go:
INSTALLING HARDSPL 1.83:
(note: YOU CAN NOT INSTALL HardSPL via SD Card!!!! YOU HAVE TO USE ACTIVESYNC via USB!)
- Make sure your phone is fully charged and your data backed up!!!
- Download HardSPL 1.83 from here: http://forum.xda-developers.com/showthread.php?t=520312
- the page i linked does contain instructions, but i'll summarise:
1) connect your phone to your pc using ActiveSync (NOT the DiskDrive connection)
2) Make sure you have an active internet connection
3) run Topaz-HardSPL_V5_00R5.exe from your PC and follow the steps HardSPL prompts you with (incase your antivirus says something, trust me, there is no virus)
4) Press OK when asked to wait
5) everything will continue automatically (if an error pops up, STOP and mail me with your error)
6) you will see your phone jump to a tri coloured screen eventually. anything displayed on screen will be automated (again, any errors here...well let's hope you don't get any)
7) Your device will automatically reboot and you have HardSPL 1.83
Now, let's make sure it installed correctly!
- switch off your phone.
- hold down the Volume - button (minus/volume down) and press the power button. This will take you to the famous Bootloader mode. Here you should see the word Olinex somewhere. If you do, YAY, softreset your phone (the little red button under the battery cover)
- if NOT: send me a message
!!!IMPORTANT!!! You only have to do the HardSPL installation ONCE After completing the above, you can simply proceed with the following steps from now on.
OK! Now you have the means to install the ROM you want!
Step ZERO: - Connect your phone via activesync -> open My Computer -> double click on your diamond 2 -> You will now see two folders. One is internal memory, the other is your storage card -> right click on your storage card -> properties -> look for the words FAT 32 -> If it says that, proceed with "Choose your ROM!!!" below.
If it DOESN'T say FAT 32, then do the following:
- close that window and right click on your storage card again. Now click format (REMEMBER TO BACKUP)
- select FAT 32 as your File System (NOT NTFS) and then click format
- once that is complete, you may proceed with the next steps below.
Choose your ROM!!!! (I am a Dutty fan, so that's the first one i'm going to recommend...however, the method of flashing stays the same)
Once you have downloaded your chosen ROM, make sure you have the following files: TOPAIMG.nbh and TopazRUUWrapper.exe
there are TWO ways of flashing: (again, please make sure your phone is fully charged)
Method one:
- Copy the TOPAIMG.nbh file into the ROOT directory of your storage card (NOT onto your phone). (Root directory means as soon as you double click on the storage card, THAT place, that's the root directory...some people call it base directory)
- switch off your phone and enter bootloader mode (read how to in the HardSPL section above)
- You will now come to a white screen with blue writing.
- It should tell you that you can continue flashing by pressing the power button.
Once that is pressed, you sit back and wait till your phone is flashed!
watch this for help: http://www.youtube.com/watch?v=FbRboNeo2XE
(credit to wadialdoor)
Method 2:
ALTERNATIVE WAY OF FLASHING YOUR ROM WITH RUU.exe
- Turn off your device by using the Power Button
- Go to Boot loader mode. Push and hold Vol. Down and press the Power button.
- Connect your device to PC (with activesync, yes it works even if your phone is not "fully" on)
- Run the TopazRUUWrapper.exe and follow the screen instructions.
Whichever method you choose, once you get the message that everything was successful, open your battery cover and press the red reset button once. THEN, as soon as you have entered your pin code and your phone is on, switch it off
Now hold volume up (+) AND volume down (-) and press the power button. You are thereby doing a "Hard Reset".
Once that is done, CONGRATULATIONS! your new ROM is ready to go!!!
I hope this proves useful to some!
-Simon
Good and Clear
Thanks for including some missing points which some of our members missed/or/got questions during flshing (first flash ).
Thanks.
great job. it will be very helpful for the first time flashers
Sorry for the double post dont know what hapend!
great job. it will be very helpful for the first time flashers
Another tip fort first-time flashers:
Do not forget your silk underwear and trenchcoat!
Seriously though, this is a great simple guide for newbies like me. I'm still in the process of exploring the standard WinMo 6.5 as well as Manila, trying to decide what I want as it is and what I want differently.
Hey guys, if you are having trouble with some of the content in this guide, please check out my other "pre-guide guide" over here: http://forum.xda-developers.com/showthread.php?p=4963913#post4963913
also, if you have any questions, you can post them THERE (above link) as i would like to use that post as a Q and A place (and not my inbox )
Thanks for all the help, ive sucessfully installed my first ROM
Very helpful, The pre-guide and this.. both helped a LOT.
Thanks
One more thing, do i have to do the HardSPL 1.83 flashing part everytime i want to install a new ROM, or is that enough if its done once, and then only do the RUU.exe from the pc?
Drag-On said:
Once you have downloaded your chosen ROM, make sure you have the following files: TOPAIMG.nbh and TopazRUUWrapper.exe
there are TWO ways of flashing: (again, please make sure your phone is fully charged)
Method one:
- Copy the TOPAIMG.nbh file into the ROOT directory of your storage card (NOT onto your phone). (Root directory means as soon as you double click on the storage card, THAT place, that's the root directory...some people call it base directory)
- switch off your phone and enter bootloader mode (read how to in the HardSPL section above)
- You will now come to a white screen with blue writing.
- It should tell you that you can continue flashing by pressing the power button.
Once that is pressed, you sit back and wait till your phone is flashed!
watch this for help: http://www.youtube.com/watch?v=FbRboNeo2XE
(credit to wadialdoor)
-Simon
Click to expand...
Click to collapse
Only one thing, the SD must be formatted in FAT 32
htcdiamond8 said:
Thanks for all the help, ive sucessfully installed my first ROM
Very helpful, The pre-guide and this.. both helped a LOT.
Thanks
One more thing, do i have to do the HardSPL 1.83 flashing part everytime i want to install a new ROM, or is that enough if its done once, and then only do the RUU.exe from the pc?
Click to expand...
Click to collapse
I am very glad you managed to get it all working!
the answer to your question: NO HardSPL is done and over with, you only have to do it once. I will update this in the guide, to reflect the once off HardSPL'ing.
Also, thanks rspillo:
rspillo said:
Only one thing, the SD must be formatted in FAT 32
Click to expand...
Click to collapse
i will update this too.
Excellent guide, I wish I have seen it before flashing my first ROM, it is always comforting to have a step-by-step guide to follow even if the process is quite simple.
After some research on xda, I have followed the same steps you mention, and the ROMS are working perfectly, so I guess I have done it right....still there was some anxiousness at the end of the flash that is not mentioned in your guide: HardSPL stop telling flashing the ROM went OK, but never reboot....basically, to reboot it i am forced to use the soft reset button behind the back cover, all the hardware buttons including power button are not responsive. This is worrying for a first timer and should be mentioned somewhere (or is it just me, the normal behavior is auto-reboot?)
Other thing worth mentioning in your guide is the hard reset after a flash: you may add that it s advisable to do, and explain how to do it (power off, then power up while holding volume-up AND volume-down pressed simultaneously). This has taken me 2 customs ROM to figure out ;-)
gkai said:
Other thing worth mentioning in your guide is the hard reset after a flash: you may add that it s advisable to do, and explain how to do it (power off, then power up while holding volume-up AND volume-down pressed simultaneously). This has taken me 2 customs ROM to figure out ;-)
Click to expand...
Click to collapse
I did not know this thanks for this
not all custom ROMs require a hard reset. i've almost never had to do it.
but i digress. i will update as recommend by all
Drag-On said:
not all custom ROMs require a hard reset. i've almost never had to do it.
but i digress. i will update as recommend by all
Click to expand...
Click to collapse
Performing an immediate hard reset upon completing the initial flash is something I almost never do. However, I continue to recommend it to people who flash my ROMs since I have had it solve some issues in the past.
-Edit-
I'm gonna move this thread to ROM Development since it centers around flashing ROMs. I have "stuck" your roll-up thread leading here.
Successfully Flashed my First ROM
Drag-on.. thank you so much for ur guide that helped me out in successfully flashing Dutty holy grail R3 ROM on my HTC Touch Diamond2..
Thread Stuck.
P.S.
You requested this thread sticking also : http://forum.xda-developers.com/showthread.php?t=585457
I suggest it might be easier to add this to the first line of the first post - as a "If you are very new to this - read here" sort of thing.
Regards,
Dave
Hi all,
I will be a new htc owner next week and i'm trying to enter this htc world to be ready as soon as i get my toy (topaz)
My topaz is not blocked to any operator and my question is: Do i need to use Hard SPL 1.83 to flash for the first time considering the device is unlocked???
Thanks
PS: i'm sorry for this questions but i really didn't find any docs for beginners!!
Have a device blocked to an operator means that you only can use a SIM from that operator, it's not related with unlock to flash cooked roms, or HTC roms not provided thru Serial Number download from HTC Site
HardSPl is allways required to flash any other rom, please read the 1st posts where an explanation is stated, and as no relation at all with SIM Block
Happy flashing
Pisca said:
Have a device blocked to an operator means that you only can use a SIM from that operator, it's not related with unlock to flash cooked roms, or HTC roms not provided thru Serial Number download from HTC Site
HardSPl is allways required to flash any other rom, please read the 1st posts where an explanation is stated, and as no relation at all with SIM Block
Happy flashing
Click to expand...
Click to collapse
Thank you for your answer, i was confused with so many threads and information. It is in fact a little bit difficult to enter in a world like this. I own an Asus P750 and in related websites of Asus sometimes after a mouth no new posts if you now what i mean
So here it is the opposite, it's good but i have some years in disadvantage to update.
If i will post some stupid questions, so be it!! It's my beginning!!
Again thanks to reply.
Zimaia said:
If i will post some stupid questions, so be it!! It's my beginning!!
Click to expand...
Click to collapse
There are no stupid questions, only stupid answers, feel free and enjoy your new device
Thanks bros for your introduction on flashing a ROM (this is particularly useful for newbie like me in reducing the problem encounter~)
1 more question..i knew that hardreset will rest all the things and revert my phone like it is released from the factory, so what is the initiative to have it hardreset after i flash a new ROM? will my newly flashed ROM got "flushed" away after this hardreset?
Thanks again!!
h9922293, doing a Hard Reset will only reset the ROM you currently have installed. It doesn't (and can't) reset to your original ROM that the phone came with, because that ROM is long gone.
Think of it as switching your pc off, then turning it on again, to find all your programs and settings have gone back to original, but your modified windows xp/vista/7 is still there.
that make sense?
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
[email protected] said:
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
Click to expand...
Click to collapse
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is here. Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
jojojohnson7410 said:
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
Click to expand...
Click to collapse
When I touched the screen above the search button, I see the source of the error is "/system/app/swype.apk
so I imagine it is due to updating swype cuple of times and as far as I remember, in the first update i had to remove 2 system files to make it work.
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Eddie Bombay said:
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Click to expand...
Click to collapse
This did it for me. Left the SD card update on my SD card and as soon as it rebooted to clean 183 it found the update and installed it!
Thanks
Ok the web just glitched on me so this is the second time of me writing this novel and patience has grown very thin. First i would never be asking for this help if i didnt already do my 5 days of research and exhaust all solutions i can see. And since this is my second time writing this im sorry but im going to give the short version. I did the fatal mistake of lg style reset while i was rooted i know its a rookie mistake i thought i was completely unrooted and didnt double check it before i continued. i cant boot into recovery at all or if i can its just a black screen. when i boot normally it goes to the lg logo then to a black screen. i can access emergency mode however i cant get my pc ( running xp sp3 ) to recognize the device. I can get it to be recognized when i boot it normally to the black screen and even gain acces to root through adb, When in emergency i get nothing though and i have attempted recovery and flashing through adb, kdz, romtools, lgmdp and a few more randoms i could find in the forums ( i have done a lot of research ) when i do establish root though i cant seem to push or pull files, flash, mount or anything besides adb shell, the rest is filled with error: 0's and sbin/sh "whatever" not found, etc. since i can establish root it leads me to believe this can be fixed. THANK YOU in advance for any help you can throw my way and I'm sorry if this post is vague, poorly written ( like i said second time going through this ) or gets under your skin i know better that you veterans hate reading these posts and im only asking for help because now i am at my wits end. Thank you again
hey it would be nice if you could tell something about lg style reset and that rooted thing..... I don't have any info. about bricking the device like this.... ;-)
just wanted to know as a word of caution....
Sent from my LG-P500 using xda premium
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
fundoozzz said:
hey it would be nice if you could tell something about lg style reset and that rooted thing..... I don't have any info. about bricking the device like this.... ;-)
just wanted to know as a word of caution....
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Rooting is the process of essentially gaining Administrator rights to your phone ( So you can access files and gain privilages you wouldn't normally have ) Think of it like a computer and your signed in as a guest when you root your signed in as the Admin, Hope that helps. LG style reset is the factory reset of the phone from the recovery menu to restore the phone to its original state, Which is a huge no no while rooted or a custom recovery is installed.
mak.3736 said:
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
Click to expand...
Click to collapse
I attempted that and its a no go. The main problem being i can not get my phone to be recognized by the computer while it is emergency mode and i can not even select an image or anything. I booted it normally ( into the black screen i get after LG logo ) And i dont recieve a pop up with image and i recieve a error everytime i attempt to backup my nv its doesnt seem to be found, Nothing, but the device does get recognized at least.
AbattoirX said:
I attempted that and its a no go. The main problem being i can not get my phone to be recognized by the computer while it is emergency mode and i can not even select an image or anything. I booted it normally ( into the black screen i get after LG logo ) And i dont recieve a pop up with image and i recieve a error everytime i attempt to backup my nv its doesnt seem to be found, Nothing, but the device does get recognized at least.
Click to expand...
Click to collapse
Are you able to connect to phone from lgmdp when booted normally ( into the black screen you get after LG logo ).
If yes then
dont back up nv
no need the pop up window, press on "select image" in lgmdp and browse to recovery extracted folder for "image folder"
then press "start or download"
fix-black-screen-custom-recovery-custom-roms
I'd've posted it here on xda, too, but it's quite enough manainance dealing with it in one forum already.
the problem is that lg started shipping the optimus v with cheaper hitachi screens instead of the novatek screen it was released with. so the older custom recoveries and roms use a kernel that isn't configured to use the hitachi screen and you only get to see the backlight with no display.
edit:
mak.3736 said:
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
Click to expand...
Click to collapse
the p500 kernel is incompatible (different chipset.) so the recovery won't work even it the mtd map is the same.
bummer, as that's be a nice easy fix.
Mak Thank you for the progress i have made so far i did manage to get the phone connected through lgmpd as i have before however this was the first time when connected it went straight to emergency ready ( in the lgmpd screen ) I am going ahead to assume that is good i was never able to get it that far. The problem i face now when i press the "select image" button nothing happens, as long as the button is pushed down the word ready in the bottom left disappears and when released the word reappears, However i dont recieve the option to browse any menu for the image. Is there a specific folder i should have extracted to? I'll continue my research too if i find out the problem i wil post it immediately, Thank you again for your help i'm not there yet but definately making progress.
Squid, I knew about that topic too i remember reading it during my research, It must of slipped my mind before i even though about posting this. I'm Sorry ill be more careful about making these posts in the future
Also Squid since the chipsets are different i assume thats a no go, Would it still hurt to try? i'm running on hopes and dreams at the moment. Also when booted normally to my black screen i can obtain root access via adb leading me to believe if i can do that a fix is present somewhere
AbattoirX said:
...snip
Also Squid since the chipsets are different i assume thats a no go, Would it still hurt to try? i'm running on hopes and dreams at the moment. Also when booted normally to my black screen i can obtain root access via adb leading me to believe if i can do that a fix is present somewhere
Click to expand...
Click to collapse
yes, a no-go. when I flashed a p500 kernel to my v for experimental purposes, it wouldn't boot right for a day even after putting a working kernel back on it. it had to sit with the battery pulled for a few minutes between boots or it would just freeze on the lg logo.
if you follow the adb instructions to install a compatible recovery (currently, BobZhome IHO recovery is advised) in the thread I linked to, you should be fine.
AbattoirX said:
Mak Thank you for the progress i have made so far i did manage to get the phone connected through lgmpd as i have before however this was the first time when connected it went straight to emergency ready ( in the lgmpd screen ) I am going ahead to assume that is good i was never able to get it that far. The problem i face now when i press the "select image" button nothing happens, as long as the button is pushed down the word ready in the bottom left disappears and when released the word reappears, However i dont recieve the option to browse any menu for the image. Is there a specific folder i should have extracted to? I'll continue my research too if i find out the problem i wil post it immediately, Thank you again for your help i'm not there yet but definately making progress.
Click to expand...
Click to collapse
yes, as long as pressing the "select image" button ready in the bottom left disappears. But when you release button you should get a window poped up to select image folder.
Try again to connect in emergency mode and see.
AbattoirX said:
when i do establish root though i cant seem to push or pull files, flash, mount or anything besides adb shell, the rest is filled with error: 0's and sbin/sh "whatever" not found, etc.
Click to expand...
Click to collapse
I did follow those instructions previously ( 2 days ago i believe ) When i attempted that i was not able to push the needed files to my sd card unfortunately and i did try multiple times using Xionia recovery. I understand user error so I'll try again with a fresh mind just to be certain and get back to all of you.
AbattoirX said:
Rooting is the process of essentially gaining Administrator rights to your phone ( So you can access files and gain privilages you wouldn't normally have ) Think of it like a computer and your signed in as a guest when you root your signed in as the Admin, Hope that helps. LG style reset is the factory reset of the phone from the recovery menu to restore the phone to its original state, Which is a huge no no while rooted or a custom recovery is installed
Click to expand...
Click to collapse
I know what rooting is....infact I myself is on CM 6.5.8
what I didn't knew was that factory reset with custom recovery can brick our device..
but I feel this is not true as many people had done factory reset when they had problems after restoring nandroid backup....
I know a corrupted /system partition will cause the 'system/bin/sh not found' with adb if you're booting into the rom, I hadn't seen that booting into recovery.
if you have an older optimus v (2.2.1 froyo original, pv5 baseband) you can
Code:
adb reboot bootloader
to get to the bootloader and use fastboot to flash the recovery or even the whole system.
2.2.2 optimus v with pv7 firmware has the bootloader locked, so trying to reboot into the bootloader just tries to boot to the normal ROM.
My apologies Fundoozzz i was not insulting your intelligence just covering all basis, And from what i understand when you choose lg style reset from recovery it is the same as perform the factory reset from the settings menu which i guess your not suppose to. I by no means am not an expert on any of this obviously, I'm just simply relaying the information i have read on these and android forums as well as my personal experience.
Squid, I purchased this in the beginning of sept. and as i understand the revamped the Optimus in August?? So yes im running the later version and to double back on the posts I tried to push files again and attempted fastboot before still with the sbin/sh not found error....I am still hopeful that this is not a paper wieght however it very well could be thank you both again
have you tried booting into the blacked recovery before using adb?
(hold home+vol down while pressing power until lg logo goes black)
it sounds like your rom was corrupted (so adb is fairly useless there,) and recovery might be working but you just can't see it if you do have a newer OV.
to force reboot to recovery without the button-smashing,
adb reboot recovery
while you're booted normally.
then try adb again.
please cut/paste the errors you're getting with the commands you're using, here in this thread..
Well all be cheese and crackers, Thank you Squid it did the trick to actually push the image to my sd card here are the commands that I used....
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>cd c:\android\platform-tools
C:\Android\platform-tools>reboot recovery
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\platform-tools>adb shell
~ # reboot recovery
reboot recovery
C:\Android\platform-tools>adb push vm670nh_recovery.img /sdcard/
2608 KB/s (4200448 bytes in 1.572s)
C:\Android\platform-tools>
Now before i move further just to humor me all i need to do is push the flash_image and reboot to recovery and i should be good from there to flash a new rom. I ask only so i dont mess this up any worse than i have
if you're in the recovery, flash_image is already in the PATH.
Code:
adb shell
flash_image recovery /sdcard/vm670nh_recovery.img
exit
adb reboot recovery
then you should be ready to see your recovery.
format cache, data, and system.
install the rom.zip as usual.
THANK YOU VERY MUCH, How I wasn't able to obtain this I'm not too sure lack of knowledge or user errors possibly regardless I am now in CWM recovery and will format and flash my new rom. Any suggestions by the way? I was considering CM7 but i heard mixed reviews about it on the Optimus v. Oh well I'll do some research Thank you again Squid if i can repay this debt let me know, Lets face the facts in reality you just saved me over a hundred dollars and countless more headaches. Thank you again to everyone, much appreciated!
AbattoirX said:
THANK YOU VERY MUCH, How I wasn't able to obtain this I'm not too sure lack of knowledge or user errors possibly regardless I am now in CWM recovery and will format and flash my new rom. Any suggestions by the way? I was considering CM7 but i heard mixed reviews about it on the Optimus v. Oh well I'll do some research
Click to expand...
Click to collapse
I really enjoy the IHO cm7 flavors, all of them.
I advise giving one a whirl, froyo just doesn't compare to gingerbread for my personal use.
They use more battery than harmonia, but the features! the features!
Thank you again Squid if i can repay this debt let me know, Lets face the facts in reality you just saved me over a hundred dollars and countless more headaches. Thank you again to everyone, much appreciated!
Click to expand...
Click to collapse
if you're financially solvent, I have a donate button in the sidebar... I like to help people out, but my woman really appreciates it when I get more from helping than warm fuzzies.
the thanks are appreciated, though, and if your income is like mine, don't send any money
Well if a promise is worth anything in this day and age, when I am slightly more financially stable I'll send enough for a six pack your way or some flowers so your girl won't mind you helping us for a while longer Thanks again and I'll load up CM7 now
Well easy come and easy go back to a new LG screen. So after managing to get the recovery working i went to flash CM7 on the Optimus using information here http://androidforums.com/optimus-v-all-things-root/366620-cm7-installation-my-optimus-v.html Anyway I am now experiencing this problem, I get stuck back at the lg screen again. I did wipe the cache data system 3 times to be safe before flashing the rom and i only have access to emergency mode and this screen ( regular boot and recovery mode come up and end the exact same way ). I'll explain what i see step by step...
1. The black and silver LG Logo
2. A green Android guy next to a box with arrow coming out and these words come up on the screen. " with out the numbers of course "
(1) Android Recovery
(2) Do Not Pull Battery
(3) Formatting Data:...
(4) Formatting cache:...
(5) Factory Reset...
(6) Rebooting...
3. Then reboots back to the black and silver LG Logo screen.
4. Finally stops and freeze's up on the screen with a pinkish/reddish LG symbol with LG next to it and www.lgmobile.com written underneath it.
Question being is this some sort of recovery boot loop? And if it is what can be done about it? Furthermore many if not all files on the phone so far seem to be " read only " .... well i guess I'm ready for round two!