[Q] Any fixed e3d camera rom? - HTC EVO 3D

Ok, I've already searched the forums, both in the Evo3D section and outside, I've also have within the last week tried many different sense roms, all of which had the exact same problem: my camera does NOT work.
The closest thing to working was mike1986's Android Revolution HD (so far). The camera app boots into the window that ask to choose between Done or run the Demo Video. The Demo Video sends ye off to the internet browser. Hitting Done goes straight to my problem.
The application opens into a black screen. Sometimes the backlight is on (noticed this is a 'feature' of the newer roms that has came out/updated within the last month). That's it. After hitting home to exit the application, I have noticed I get either dimmer horizontal strips of the screen or the screen has a ghost of the lighter portions of the screen image that slowly moves to the left. After a few seconds of this strangeness, the screen reverts back to normal. A few times I got the impression that the screen's dual layers having synchronization problems.
I'm about ready to give up and go back to the stock rom, maybe I'll even try the 'cleaned' versions before trying the rooted shooter stockers. If all else fails, I'll even try to use the full OEM installer and return the phone back to stock, if this is the only option left to get a working camera. I'd prefer to use a custom rom that allows undervolting/overclocking and has the fat trimmed off, but if I have to, I'll go back to stock rooted. ...now that I think of it, I started to have problems with the camera right after I applied the HTCDev Root method. And, yes I DID follow the instructions to the letter.
This is quite frustrating as I've have as yet to find a rom that has a working camera! I've already tried the following roms:
Shooter-Rewind-3D-RLS2.1+RLS3
WTSB_Evo3d_1.91
CleanROM_2.7
CleanROM_DE_1.2
Chogardjr3D-2.3.4-Stock
Chogardjr3D-Blue-v1.3
STEAL25_inbREDedROM_2.1clock
viperROM_RC1.3
viperROM_RC2_Rebuild_Test28
Android_Revolution_HD-Evo3D_CDMA_1.1.1 (current)
I haven't tried but already downloaded:
Gerbil-6-shooter_v.2.2.4
freEVO+3D+2.1
WTSB Hydro e3d 2.3 (want to try this one, but keep having problems downloading, the server keeps on downloading a 35kb index.html instead of the rom itself)
If the above roms fails, then I going to try reloading the rooted stock rom
shooter_2.08.651.2_cleaned_v0.4.2
Else one of these two...
Shooter_2.08.651.2_deodexed_rooted
Shooter_2.08.651.2_odexed_rooted
If all these fails, sigh, I gonna start over again with the full oem install...
PG85IMG_2.08.651.2.zip
And see if the camera still broken. If so, then gonna apply all OTA updates FIRST before applying the HTCDev root method again. This is the only thing I did not do before. If this doesn't work, I dunno what else to do then.
Any suggestions, rom-wise or camera-wise? I've been reading around and found a thread in the Amaze section that suggested that the camera problem might be kernel-level. Think this may also apply to the e3d?
I've been doing sleepless nights for the past 5 days already trying roms after roms and apk after apks. I'm about reaching the end of my thread (and patience) and figured it's time to ask the pros here on xda.
Thanks in advance...
-Lance (Lanaka)

Reserved for Fixed Post.

I forgot to upload my hardware/software specs. I'm out of time as I have to go to work, so I'll edit it onto this post during a slow period at work.
K here's my hardware/software specs:
---Hardware:
------Hardware Version: .. 0002
------Processor: ............ 1.2 GHz Qualcomm MSM8660 Dual-Core
------Memory: ............... 1GB
------Display: ................ 4.3 inch QHD resolution
------Main Camera: ........ 5Mpx*2
------Front Camera: ....... 1.3Mpx
---Software:
------Android Version: ..... 2.3.4
------HTC Sense version: 3.0
------Software number: .. Android Revolution HD 1.1.1 by mike1986
------Kernel version: ...... 2.6.35.14RCMIX-ACS-EVO3D-CR-V9-g98e7362-dirty
------------------------- [email protected] #6
------------------------- SMP PREEMPT Mon Oct 24 13:13:49 CDT 2011
------Baseband version: . 0.97.10.0808
------Build number: ........ 2.08.651.2 CL130920 release-keys
------Browser version: .... WebKit/533.1
------PRI Version: .......... 1.24_003
------PRL Version: .......... 10602
Bootloader:
------SHOOTER XC SHIP S-0N RL
------HBOOT-1.50.0000
------eMMC-boot
------Aug 7 2011,10:21:40
---Recovery:
------Team Win Recovery Project (twrp) v1.0.3
------Based on Android System Recovery <2e>
Any other information you need, lemme know and where/how get it.
Mahalo Much
-Lan

Infected eternity ROM works...
Sent from my 3vo

http://infectedrom.com/showthread.php/561-ROM-Eternity™-2.3.4?p=10369
Sent from my 3vo

nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.

You might also want to try one of the many superwipes.

User error. Camera works on roms. Maybe ur phone is broken
Sent from my PG86100 using XDA App

I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Sent from my PG86100 using XDA App

fsu311 said:
Infected eternity ROM works...
Click to expand...
Click to collapse
Ok, I'll give it a try next after the ones I've already downloaded. I'm a methodical type of guy (don't like leaving thing left undone).
il Duce said:
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
Click to expand...
Click to collapse
That's what I'm figuring. I start reading the original set of posts, then randomly check out a few posts in the middle, and then read the last 10%. The roms i've picked mostly had either minor issues caused by misflashing or other user errors. A few actually said had an issue or two but nothing that'd stop me from giving the rom a try.
Yup, that's the MO I've been using as instructed in the following thread:
http://forum.xda-developers.com/showthread.php?t=1239821
I'll go thru the step-by-step process I used and you can nitpick where I went wrong,
I've placed a copy of adb.exe, AdbWinApi.dll, fastboot.exe and TWRP's recovery.img into folder c:\adb\
A little tip here, as I play with windoze XP a lot, a trick I used to eliminate the need to cd so much with cmd.exe. I did this after the 3rd ROM!
I place a shortcut link to cmd.exe into this same folder with the above files and exes. Next I open the Properties window for this shortcut, I made the following changes:
Start In: c:\adb
Comment: Starts cmd.exe in adb folder.
What happen is that cmd will open its window with the c-prompt already IN the same directory as my android files. Also, when i mouse-over the shortcut icon, it will popup a message reminding me that this link starts cmd.exe in adb folder.
Then I do the following:
I connect the phone to the laptop using the usb cable, set the phone to disk drive mode. Once Windows recognizes the volume and mounts it, I type the following:
c:\adb>adb reboot bootloader
After the e3d reboots into hboot, I then type the following:
c:\adb>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.250s]
booting... OKAY [ 0.000s]
finished. total time: 1.250s
Once TWRP loads, I then switch to the phone (WITHOUT disconnecting the phone from the laptop). Here on, I use the keys on the phone to navigate to the necessary functions. The proceedure I used mirrors what Steel25 suggested in the following thread:
http://forum.xda-developers.com/showthread.php?t=1269610
I initially thought it was an overkill, but figured probably wouldnt hurt to be safe than sorry.
If the installed rom is something I liked, I nand it first...
I then enter the Wipe Menu proceed to hitting each of the following:
Wipe Cache
Wipe Dalvik Cache
Wipe Everything (Data Factory Reset)
Wipe Battery Stats
Then I go to Advanced/Format Menu and hit each of the following:
Format SYSTEM (/system)
Format DATA (/data)
Format CACHE (/cache)
Format SD-EXT (/sd-ext)
Then I go back to top menu and enter Install Zip Menu, and first I hit:
Wipe Cache and Dalvik Cache
Then I enable:
Reboot After Successful Flash
THEN I:
Choose Zip To Flash
(Navigate to where the rom or app zip is located and select it.) Here I take a break and let TWRP does it thingy and check back on the phone in 5 minutes or so.
After recovery reboots the phone back into system, I let the phone sit on the lockscreen for 10 minutes to let the rom complete it's init process. Then I skip thru the entire initial setup prompts (altho I enter NO for Tell HTC). I reboot phone back into system, let it sit for another 5 minutes on the lockscreen before I hit the Android Market app to trigger the process of linking the phone to my google account. I then let my account sync. Once my new email icon pops up on the notification bar, I check out the camera. By the time I've hit the 3rd rom, I've had read about the camera problem possibly being a kernel level issue, I've since then added this step....
Menu/Settings/About Phone/Software information/More
Here I took note on whether the Kernel version info has changed as well. (And for the most part, yes, the kernel information DOES change with each rom).
K, now ye can start thrashing me...
-Lan

Drewmungus said:
You might also want to try one of the many superwipes.
Click to expand...
Click to collapse
I'll try that, altho I've never used it before. Even when I had my e4g, I never heard of this one until I started my current research on the e3d. Any particular one you'd (or anyone else'd) recommend?
Sigh, lotta work rooting and flashing the 1.50 e3d, compared to the good ol' e4g! >8p HTC!
Mahalo Much!
-Lan

cajones42 said:
Maybe ur phone is broken
Click to expand...
Click to collapse
Gods! I certainly HOPE NOT! It'd be a real b!atch if this proves to be the case.
Seriously, tho. I'm thinking it'd probably not be the case as I had the phone and was playing with it stock and unrooted for nearly a week and during the whole time, the phone's camera worked with nary a problem. That's why as a check value, I'm going to restore the phone back to stock unrooted state AFTER I try the last 4 roms I still have en-queued. This doesn't include the cleaned/rooted stocker, the full/rooted stocker nor the full OEM stocker.
-Lan

unCoRrUpTeD said:
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Click to expand...
Click to collapse
Ok, I'll try that next. Altho, I gonna have to read up on how to prepare the kernel for flashing separately. Am I correct in guessing that I probably could get away with making a copy of the zip file and deleting everything in it except for boot.img, then adb boot into recovery and set the flag for check sign off before flashing the custom zip I just made? If that's not correct, mind pointing me to the apropos thread? (...or tell me what I need to do for separate flashing?)
If all else doesn't work, that's what I intend with the stocker roms. SU, TI, RE. Then time for me to research on where what and how to root out all the bloat meself. I'll worry about that later cuz I no need do that IF i can get a pre-made rom and kernel to take root in me e3d!
Mahalo Much!
-Lan

You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'

SketchyStunts said:
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
Click to expand...
Click to collapse
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.

il Duce said:
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
Click to expand...
Click to collapse
Ah, didn't know that, mebbe that's why I'm having problems. I'll try reinstall one of the earlier ROM and see if there's any difference. If that doesn't fly, I'll try the kernel separately. I went with hard drive mode cuz I got actual confirmation the device was loaded. Charge only, didn't get any indication that the pc seen the e3d, sigh, noticed the sense and adb interface is rather ...crude.
Heh, wordy, that's what you get when you have an English major for a mother and an English/Japanese Translation Specialist (aka Cultural Attache in the US Army) for a grandfather...
I'll give joeykrim's flash_gui a try too. Just downloaded it. Cross fingers for luck. (roll eyes at 1.50)
Thanks dude, if I could, I'd hit yer thanks button again for good measure.
EDIT: clicked the button again...

Update: Back to work on problem...
Been a while guys. Unfortunately, work becons (or more accurately, intruded). Had to deal with a bunch of sht from my job. Things gone to the dumps there. Well, enuff of that.
In meantime, with my phone being activated and in use, I tried to tether (teeether, hehe) my e4g to my e3d and noticed I'm also having wifi issues. What rang a bell is when I noticed my wifi tether issues disappeared after I turned off 3G. It's like, heeeeey, didn't I read something like this in xda??? After doing some researching (on xda, of course ) I've learned that this is also a kernel issue, most often because the new kernel was not properly flashed in conjunction to having the correct matched kernel modules (wifi, CAMERA, 3g/4g, etc.) installed as well. On reading these, I went 'hmmm...' Looks like all of these issues others and I that have been experiencing are all kernel/module misflashes (no thanks to hboot 1.50). Where I think I hit pay dirt is when I found a xda thread that actually explains in depth Flash Image GUI, which was also mentioned earlier in THIS thread (thanks, il Duce).
So, I have downloaded the apk, installed it. Downloaded a new ROM (Olympus Trinity XE Version IV) STRAIGHT to phone...
Oh, just remembered. I've noticed another possible cause of problems. I've originally downloaded the various files from xda and then either push it to phone or more often just enable hardrive mode and drag/dropped it into the phones sdcard directly. Normally, I check the md5 hash on download, but yesterday, I ALSO checked the md5 hash again after moving it to the phone. Meaning, I downloaded ROM to pc, then checked md5 hash, all good. Copied ROM to phone and then checked md5 hash again. NOT good. Somehow, it changed during the copy process. What prompted me to check was I also downloaded Flash Image GUI to pc and copied it to phone and then had phone try install it. It failed to "parse" file correctly, which tells me that the file may have been corrupted. I downloaded Flash Image directly to phone and tried again, and success! Suspicious now, I checked the md5 hash of all three copies of the apk. The laptop downloaded and the phone downloaded copies matched the source's md5, while the COPIED version did NOT match! Whaaa Daaaa FFF(bleep!)!!! I then checked the two copies of the ROM (pc downloaded and phone copied) and they DON'T match!
Sigh. I'm in a area that has poor 3G connection, while ironically, my laptop's 4G was good.
So, I bit the bullet and endured the nearly hour long download of the ROM directly to phone and double checked the hash (which matched the pc downloaded copy, the source didn't provide a hash). THEN I used the Flash Image GUI app to pull the kernel and modules and pop it into phone. Immediately rebooted phone into recovery. Well, tried. Wished Flash Image GUI gave the option to reboot directly into recovery or bootloader, like those 4-/5-/6-1 Reboot options offered in the various ROMs. Because it just simple did a reboot back into System.
I didn't want to take chance with problems with mismatched ROM/kernels (I was on Android Revolution 1.1.1 at the time), so I quickly turned to adb on my laptop and had it reboot phone into recovery.
Once in recovery, I immediately started doing my usual ROM change process. Wiped using every wipe option (except for sdcard) in TWRP (oh btw, I also updated it to 1.1.1 earlier) in both the standard wipe and advanced wipe menus. Once I did so, I then thought, hey where did Flash Image GUI dump the kernels into? Couldn't remember whether it was DATA or SYSTEM. But decided that with Flash Image GUI it's ain't no hassle to reflash the kernel again after the ROM is installed. Besides, read somewhere that some issues was resolved after reflashing the kernel again after the ROM, so wouldn't hurt to try anyway.
Will let ye know how it goes, TWRP is installing Trinity XE as I type this. Gonna continue the SOP by letting it sit for 7-10 minutes. Skip thru init setup. Reboot. Let sit for another 7-10 minutes. Relink my google account. Let first Sync finish. (Basically let it sit again for another 7 minutes). Reboot. Hit Market and download Flash Image GUI, and pay for it, it's well worth IT!!! Flash the ROM's kernel/modules again. Reboot. And hopefully it should be a-ok!
(cross fingers ...on both hands)!
-Lance
PS: Assuming it's fixed, I'm gonna edit the second post and reflag this thread as resolved. Will put what I did to get it fixed, including all necessary links and credits as expected. I know it's premature, but THANKS, I wouldn't have gotten even this far without you guys (and gals) on XDA!
PPS: Also chris.goodman's AnthraX Kernel thread was also quite informative. Mebbe I'll try a ROM that features AnthraX. Somehow, the thought of being over-clocked to ~1.52G sounds appealing!

Related

I cannot access recovery anymore

Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.

[Q] Cannot boot into Recovery

Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.

[Q] Unable to install ROM

Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774

[Q] Is there a good documentation for all ROM flash steps?

I've been trying to understand all the steps necessary to replace the OEM ROM in my HTC Amaze 4G phone, but I can only find a disjointed set of pieces about the various steps and not one overarching document that covers all the stages of custom ROM flashing. A lot of the docs are aimed at the "insiders" of the Android developer community and few to people like me who would just like to try something better than what that ICS update did to my phone.
Having dabbled at one time with Linux from version .98 to 2.6 and being software developer most of my working life, I figure this should be easy for me. Yet, I find the documentation frustrating. I only imagine what it must be for others with less computer experience than me.
Since Android is based on Linux, I don't understand the big fuss about rooting. In Linux having the rooting privilege simply meant having a root password. Why is Android so much more complicated than that? Also, loading a new Linux kernel used to be a fairly simple process if one used compiled modules. The installation script pretty much took care of it. Android totally obscures this process and the disjointed documentation doesn't seem to help much. A lot of it assumes certain knowledge by the reader as if he/she was also an "insider" in that circle.
On my part I would like to so the following steps documented:
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
2.) How to prepare the phone for installing a new ROM
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
5.) How the flashing process would look like? Expected phases and length?
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
7.) Any special issues when booting the new ROM for the first time?
8.) How would I restore the original factory ROM saved in step 1?
Some of you might think I ask too much from guys who do the dev work as a hobby but I always thought that if one does something, might as well do it right, regardless of pay.
Well, that's my 2 cents worth for the day.
Howdy. I'll try to answer some of the questions you asked.
I would also recommend talking with @ravike14 who can easily guide you through the back up and routing and s-off process. It's not that difficult really. The most bizarre thing for me was sticking a piece of wire into a hole in the back of the phone to short out a process to achieve s-off.
With the right recovery image installed, it won't matter where you place the Rom.zip. which may be named just about anything. But it will always be a zip file.
The important one is the PH85img.zip must be placed in the root of your external sdcard. That file is loaded when you boot into the bootloader. And is for updating firmware.
Once you have root, and have made a nandroid backup, flashing is easy.
If you download viper, it is vipera1.7.2.1.zip. you can have it anywhere on you internal or external sdcard.
If you use 4ext recovery, you can select install and it will take you to a directory that you can browse to the place where the Rom, whatever name it is, is stored.
Click the Rom zip file and you will be guided thru the install process, if it has an aroma installer, or it will just install otherwise.
Then reboot and go thru the set up as if it was a brand new phone.
If you don't do the s-off thing, 4ext offers a smart flash option. If you aren't s-off you can't just flash a Rom if it contains a kernel. So smart flash will be required.
There are a few guides in the dev section and the general section on how most of this process works.
Again, talk with ravike and he'll be glad to help. Plus the more people we can keep here and happy, the longer we will be creating roms and fun stuff to play with.
Regards,
Chevy
Sent from my HTC_Amaze_4G using xda app-developers app
Is there a good documentation for all ROM flash steps?
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Your welcome!
NWsoccerfan said:
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Click to expand...
Click to collapse
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
chevycowboyusa said:
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
Click to expand...
Click to collapse
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
chevycowboyusa said:
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
Click to expand...
Click to collapse
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
chevycowboyusa said:
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
Click to expand...
Click to collapse
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
chevycowboyusa said:
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
Click to expand...
Click to collapse
Aroma? That doesn't smell too good to me.
chevycowboyusa said:
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
Click to expand...
Click to collapse
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
chevycowboyusa said:
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
Click to expand...
Click to collapse
I've got this.
chevycowboyusa said:
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
Click to expand...
Click to collapse
Thanks. I like your attitude about this.
When you get time stop by
XDA University.
I learned tons here its a great place to start and much better than trying to Google everything
http://forum.xda-developers.com/general/xda-university
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
been busy
NWsoccerfan said:
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
Aroma? That doesn't smell too good to me.
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
I've got this.
Thanks. I like your attitude about this.
Click to expand...
Click to collapse
you're welcome! I wish everyone would try to learn this
and the university is also very helpfull as freakboy noted above,
I've been busy working at bringing the comunity the next greatest romz!

[Q] Root noob questions

I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
rumpus01 said:
I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
Click to expand...
Click to collapse
Okay, first, what machine are you on? Linux,mac,xp,vista,7? You can't unlock on 8.1 drivers aren't compatible. But Yes you unlock via HTC dev, I have a tool to help for that if you want to try it it helps first time root you still have to take the info that it gives you and put it into HTC dev then put the code you get from the email you get into the folder but I don't know if you would want that I need someone to test it But continuing.
Unlock via HTC dev if you want to do it manually with the command first.
1. Open a cmd prompt where your fastboot tool is using shift+right click.
2. Boot into fastboot by pulling the battery, then holding volume down and power, then clicking on the first thing which is fastboot by clicking power.
3. Back to the computer type
Code:
fastboot devices
4. If your device is found your good to get your unlock data, if not you need to reinstall drivers/check your connection/or your on windows 8/8.1
5. Now to get your unlock token.
Code:
fastboot oem get_identifier_token
6. Copy and paste this into HTC dev starting at
Code:
<<<< Identifier Token Start >>>>
And ending with this line:
<<<<< Identifier Token End >>>>>
7. Submit the unlock token it will say if its valid or not and send you a email with it is.
8. When you get the email it will have a item called Unlock_code.bin place this item into the same folder in which your fastboot is in.
9. Initiate the command
Code:
fastboot flash unlocktoken Unlock_code.bin
10. It will then send the Unlock_code.bin to your phone, you will see a prompt saying "Unlock bootloader" Then volume up and click yes. It will wipe ALL of your data back it all up before you do anything...
11. When your phone finally reboots. If you would like a custom recovery boot back into fastboot again, (Pulling battery then volume down+power button and clicking on fastboot
12. Then once into fastboot, back to your computer download either
TWRP: http://techerrata.com/browse/twrp2/vigor
PhilZ: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/vigor <-------you must use this if using a ROM by snuzzo "aka Plain-andy or illusion ROM
CWM: Or go here http://forum.xda-developers.com/showthread.php?t=1914215 Download one of the zips, Extract it with your favorite extractor. You should get a .img in a folder, extract it and put it in your fastboot folder. This is only for CWM.
Take one of the .img's from above that you just downloaded and place it in the folder with your fastboot.
13.Back to your computer to push the recovery. Then while your phone is still in fastboot and connected to the computer make sure your device is still found.
Code:
fastboot devices
then if your device shows up, you are good to then flash the Recovery. Initiate this command.
Code:
fastboot flash recovery <name of recovery>.img
14. It should write the img successfully.
15. If you would like to go into recovery, you can either press "bootloader" In the fastboot option then click recovery and go into it from there. Or do
Code:
fastboot reboot
it will reboot your phone like normal. Then you can put your ROM and correlating GAPPS of choice onto your phone via USB Mass storage, along with SU. Put it on the root of your external SD card. Then you can reboot into recovery. After booting normal and transferring the ROM of choice you can then enable USB debugging and do
Code:
adb reboot recovery
16. It will reboot you to the recovery that you used. You might get a lot of errors on your phone. IGNORE THEM!!
17. Go to install and find SU from your external SD card. Install that. Then after that I would suggest STRONGLY making a backup (NANDroid) By clicking the backup button in any recovery, make sure you back it up to your external SD card.
18. Make sure that you have your ROM of choice on your SD card.
19. Wipe the hell out of everything once your ready to install your ROM.... EXCEPT SD CARD
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
23. Take your original <Name of ROM>.zip and extract it. Open the folder. In the folder will be a item called boot.img
24. Place this boot.img into the folder with your fastboot.
25. Again initiate the command
Code:
fastboot devices
make sure the device is found.
26. Initiate the command, this will flash the kernal aka "boot.img"
Code:
fastboot flash boot boot.img
27. Once you've confirmed that it has flashed the boot.img do
Code:
fastboot reboot
it will reboot your device. WAIT AT LEAST 20 MINUTES!!! FIRST BOOT CAN TAKE A WHILE!!!
28. Once rebooted set up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now talking about s-off, if you like to flash ROM's a lot I would suggest it, if not and your just staying on one ROM then just stay s-on. s-off allows you to write to every partition to the phone. s-off can be dangerous as if say you flash a ROM made for the S3, well your phone will flash it happily and well brick itself going down happily... But with s-on it will abort the flash or anything. That being said theres also the advantage of s-off being you can flash a ROM for your phone, flash and go, no computer. S-off can do some stuff inside the phone such as bootlogo's etc.. BUT its not needed for almost any app in the play store or any ROM... s-off just simply means you can write to every partition freely. No its not required. Now if you were to mess up and something goes corrupt on the phone and you need to return to stock for some reason......Well.... You almost kinda need s-off for that.... unless you do
Code:
fastboot oem lock
relock your bootloader and run a RUU..... But while s-off you can simply run a RUU (ROM upgrade utility I think ) But you can just run it.... This is how your would "return to stock" if anything messes up.... s-off can be EASILY obtained via rumrunner, use the universal 0.5.0 it will s-off your device http://rumrunner.us/downloads-2/
Unlike the old version of s-off which requires linux and a 22ga wire.... Hope this answers any questions!
I will post anything if i missed something, have to go, typed this real quick, please don't do this yet I think its right though....
edit: Just checked over it and made some changes... This should be exactly step by step... Or for what I did and what most others did. If I missed anything, someone else please post...
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
rumpus01 said:
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
Click to expand...
Click to collapse
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Code:
fastboot flash boot boot.img
8. Reboot phone.
If you have any questions with that. I will explain each step more in depth. But steps 1-11 were unlocking help.
Step 12-19 is pushing the recovery, making a back up, rebooting to it.
Step 20-end actually getting the device to boot after flashing ROM. If I need to explain again. I will. In a ever more simplified version. Plus the reason that there were so many steps is because the longest step literally takes like 2 minutes max. The rest is almost like 30 seconds besides actually flashing the ROM and GAPPS. I tried to do as much detail as POSSIBLE!!! Please consider rereading it, if you don't understand a step, ask and I will gladly explain. But it is a COMPLETE STEP-BY-STEP GUIDE. Hope you get your phone rooted, but if you didn't know what fastboot was....you might need some more reading..... I can write up a complete guide of what EVERYTHING means, what EVERYTHING does. But fastboot is just where you flash recovery/boot.img/etc.....any questions, please ask, I will explain or someone can beat me to it
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
rumpus01 said:
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
Click to expand...
Click to collapse
sweet. Just PM me or post here :good:
pball52998 said:
sweet. Just PM me or post here :good:
Click to expand...
Click to collapse
Alright man so after re-reading it, it's starting to make a whole lot more sense now. Initially, I was wondering why the hell there were so many steps in your first post. Now I realize you were just going step by step through the HTC unlock process as well, which I'm guessing HTC walks you through more or less but you clarified it in more detail.
Now in a broader step by step list, you said this:
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Click to expand...
Click to collapse
Now my understanding is that unlocking the bootloader wipes all data, but #4 is a backing up procedure... Is this just creating a backup of the stock ROM on my phone at the moment, without any of my apps or personal data? Then #5 would actually be wiping the stock ROM?
These few steps confuse me a little:
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
Click to expand...
Click to collapse
Are GAPPS included with the ROM download?
#21 - Are you telling me to "cache and dalvik" or is that part of the flash process that I don't have to do in separate steps? For example, are you saying
a) After a confirmed flash, you need to wipe, cache, and dalvik.
or
b) After a confirmed flash, wipe, cache, and dalvik, you need to boot into fastboot.
WTH is dalvik?
Now I think those are my only questions regarding the process for the moment; I'm going to check out some YouTube videos of some of these processes individually to get a better understanding. It sounds to me like most of this makes sense once you actually start going through the process and seeing it instead of reading about it, but I wanted to do as much homework as possible first.
Think I'll go ahead and give this a try tonight... It sounds like with S-on, I can only screw it up so much but we'll see. I did all my chores tonight so I can focus on this tomorrow all night if I wonk it out and just be without my phone during the day.
Oh one last question - Will I be able to get updates / update without flashing again?
Thanks again man!!!
Okay. So my "full" step by step makes more sense now? Good now do you see why I had so many steps? It was each individual part. Step by step. With clear detail or at least I tried
So moving onto the "unlocking wiping data" yes it will wipe every piece of data. But leaves stock. What I would suggest is putting su on your SD card and that being the first thing you flash before wiping or backing up..I've heard you can't back up bare bone stock. It must have root, or so I've heard... So put su on your sd card and flash it first (aka go to install and find it swipe to flash. Su should now flash. You now have root or should). Not very hard, just flashing it won't do any damage.
But backing up. When you back up it pulls every piece of info you have and puts it into a folder on your SD card. Like I have no stock... I accidentally erased it... But besides that. Do you see in my signature how I have 3 roms on my rezound. PAC, CM, And sense 5. See every one of those has been backed up. If I were to restore it, it would automatically restore to the point where I made the backup.
So now let's say. You have your backup of stock. It's on your EXTERNAL SD CARD. It should be about 1-3 gb backup. So now we have that backup made in twrp. Wipee we now have stock saved just incase something happens
So then we go in to the wipe button. Youre going to
factory reset 3 times
Wipe data, cache, dalvik cache, boot and system 3 times each. Don't ask why 3 I really don't know. But one isn't good enough...it's proven... So this leaves you with no OS oooo noooo. But the thing is you have your backup on your external hard SD card. And also your ROM/gapps on there. (gapps is google apps) but you must download the two separately. Both in a .zip format. Not a folder... Can't flash a folder... But there should be a need gapps button on the evervolv page? Click it and it should take you to a download for gapps. Remember all this is on the root of your external SD. So now we have 3 things on your SD card and no OS. O Lordy.... Time to hit up the install button!!! ;D now were going to choose the evervolv ROM. Bam, click add more zips, find gapps, click it. Bam, now you have two zips queed to flash. Just swipe to flash make sure you choose the rom before the gapps. so time passes (less than 5 minutes) and rom and gapps are now flashed. When it gets done flashing you should have some options. One being wipe cache/dalvik. That is where your question of the #21 is... Sooo.... Dalvik is pretty much like our java almost... It runs our apps...soon android will be changing to ART (android run time).
Blah blah blah, doesn't matter!! Lol xD so then after wiping your cache and dalvik after flashing your rom, return to the main menu of TWRP you should see a button on twrp's main menu, at the very bottom right, "reboot" when you click on that you should get 4 options, reboot system, bootloader, recovery, power off. We want to choose bootloader. This will bring us to fastboot (it will say fastboot usb in bug red letters if your in fastboot) where you flash the boot.img that you extracted earlier from the zip and placed it in the same folder as your adb/fastboot you remember? We need to open a cmd prompt and flash this boot.img "aka kernel" so were going to type in that cmd prompt: fastboot flash boot boot.img
This will flash the boot.img to your phone once confirmed, (only about 6 seconds to write it) were going to reboot the phone and hope for the best.. Do: fastboot reboot
It'll reboot your phone, remember first boot can take a while....
Also what do you mean by your last question??????
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
Hey man! I did not read your full post just now because I'm tired of thinking about this stuff, but I went through your step by step instructions and everything seemed to work out. I'm currently waiting for on my first boot; it's at the Evervol screen with the heartbeat animation going on. Everything made perfect sense once following your guide to the actual process; it just seems risky since there's no good way to practice unless you have a spare phone or something.
The only thing that tripped me up was that my SD card had all the data from my previous ROM even after everything was wiped. So I formatted it in Windows prior to copying the SU, ROM, and GAPPS zips on there.
Oh and I noticed after wiping and booting into the "clean" stock ROM, I had no service... Obviously, I didn't try to fiddle around with that since I was about to install a new ROM, but I can see that being a problem if this ROM ever loads (been about 22 mins).
I did find this info on a different thread:
1. Go to the dialer and press *#*#4636#*#*
2. Click on "Phone Information"
3. You should notice almost towards the bottom radio settings, Make sure the radio is on and change the settings from WCDMA to GSM (auto)
4. Exit out of the screen by pressing the back button
5. Reset the phone and you will have service.
Click to expand...
Click to collapse
I'll give that shot if it's no bueno!
Thanks again man, I'll post back tonight if I don't fall asleep before it's done loading, lol. Either way I'll post back tomorrow. Seriously thank you again, can't believe you typed all that out for me, even when the first 11 steps were step by step from HTC too. :good: True internet assistance!
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
I did indeed as it was listed in your steps, of course!
It's been about an hour now, so I'm guessing something went askew and it is not going to power up. What course of action should I take from here? I'm guessing go back to stock ROM via recovery (the backup I made), and then do the whole process over again, aside from unlocking and what not. I definitely installed SU before making a backup, so hopefully that works out.
Thanks again! It's never simple...
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
No, I did not... I did everything before your post about that, so I'm guessing that's the problem. I also only wiped cache, dalvik cahce, system, and internal storage. There's an option for android secure and factory reset under the wipe menu as well, but I wasn't sure about those...
I tried pulling battery and rebooting, I'm guessing it's dunzo. I am now booted into recovery mode and going to recover to the backup I made, and try the whole thing again after reading your post about wiping multiple times.
EDIT: To clarify, I am wiping everything 3 times before restoring. Then I'm going to reboot normally to see if the restore worked, and then go through the process again except wiping multiple times before installing the ROM this time.
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
Crap I already wiped everything and tried a restore, which doesn't appear to be working haha. And don't worry man, I can't believe you gave that many instructions to begin with. It's a lot of steps! Nothing happens when I boot after doing my recover install. My computer gives the sound of a USB device but says nothing, and my phone doesn't even light up in any way. I'm going to go wipe everything and try rebooting it normally again.
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
So after wiping everything, I go to "install" and all the zip files for the GAPPS and SU and ROM are on my Internal storage device... didn't I just clear that 3 times???
I cleared everything including internal storage and selected reboot, and recovery told me SU was not installed and asked if I wanted to. I chose yes and rebooted. Then wiped cache/dalvik cahce 3 times each, and now installing the ROM and GAPPS again... I think I wiped my internal SD card & system in addition to cache and dalvik cache after installing SU but before installing the ROM and GAPPS initially... I wonder if this was the main source of the problem.
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
WELL WELL, IT IS WORKING. IT blew through that Evervolv boot screen in like 2 minutes this time.
I see that my service is not working, and my computer said MTP USB Device drivers failed to install. I now see that has something to do with transferring media files to PC.
Well, whatever. I am cool with this for now, at least it is installed. Very tired, let's all go to sleep! Thanks again for all the help man, feel like I'm paying someone for remote support lol.
Lol gg man. We got it. Cheers!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF

Categories

Resources