So I bought a Flyer already rooted. I checked what was on it, and I have this information:
Rooted
S-Off
Hboot
Revolutionary recovery CWM
Superuser installed
I believe it has a custom rom already installed because it has the model number of p510e and it is just a Flyer 16gb Wifi only.
I want to put leedroid on it, but I don't want to accidentally brick my system. Most instructions start at step one and work there way from there. I still am missing some information.
Let me know if you need radio information or what not. I just want to get leedroid on it asap as I keep installing programs on the included rom and that is wasted time and effort.
So the question is, to be clear, how do I get Leedroid on it properly? I am unaware what rom is currently on it.
Love this website. I searched for an answer for hours, so I hope I am not repeating!
I went for Dexters Jelly Bean ROM rather than LeeDroid: http://forum.xda-developers.com/showthread.php?t=1795342
Seems very stable, quick as I need and ticks boxes for me.
Hboots for Gingerbread is different from Honeycomb. So if the tablet is on GB, and you want to flash any HC, ICS, or JB ROMs, you need to upgrade the Hboot as per the guide here.
Otherwise, if its already on Gingerbread, and you want to flash LeeDroid GB, just put the ROM on the SD, go into recovery, make a nandroid, wipe data/cache/Dalvik, and flash the ROM.
Likewise, if the Flyer is already on HC, and you want to flash LeeDroid HC (or any other HC, ICS, or JB ROMs) just put the ROM on the SD, go into recovery, make a nandroid, wipe data/cache/Dalvik, and flash the ROM.
Thanks
Wow, redpoint73 you could not have made that any easier for me. I am now on Leedroid, but I think my radio is wrong. Does wifi only US version have a different radio then 3g? I am unable to get GPS to work. When I click on Phone options in settings, it crashes. I was hoping to have a dialer for VOIP.
I only tried LeeDroid for a short time. But I don't recall having any issues with the radio (mine is also WiFi only). But I don't use GPS on my Flyer really.
I'm still not clear, are you on the HC LeeDroid? HC has GPS issues.
Honeycomb,yes
Yes, I have Honeycomb. However, I just put honeysense on because, leedroid was acting weird. Who knows. I'll keep trying until I find the right one. Honestly, the one that came installed (don't know if it was stock, unfortunately) was pretty good. I did nandroid it, so worse comes to worse, I can go back to it. But it didn't have hard buttons or the dialer, both of which I want. Thanks again for your help.
Related
Hello folks,
I got my GTab a couple of weeks ago and the first thing i did was follow the awesome guide to flash the 'Flashback' Honeycomb rom. I've been running it for 2 weeks and have also updated to the latest alpha release. I love the HC overall but since there are a couple of basic issues in all HC roms, i've decided to move back to Gingerbread.
I've searched around but haven't found the method to go back to GB from HC. I understand that I can't just flash it from CWM as it gives some errors.
I flashed HC throught NVFlash so I'm guessing there's got to be some other way of moving to GB, maybe repartitioning?
I would really appreciate if someone here can point me to a guide to flash GB from HC, including the partitioning requirements.
I will check out the GB roms and their functionality but i might move back to HC once some stable roms are out, so i would like to keep that door open.
Thanks for your help in advance!
are you trying to go from a 1.2 bootloader HC rom to a 1.1 bootloader GB rom?
Visit the Gtablet for dummies website. You can download the 1.1 bootloader NVFlash and use it to get back to stock 3588. I suggest you get the one with CWM built in. Once there, you can flash any GB rom you want.
If you're staying on the 1.2 bootloader, just flash the Rom from CWM, and make sure that you wipe Dalvik cache, and a wipe data/factory reset in CWM and it should work fine.
problems arise when jumping bootloaders, using different versions of CWM...they don't play well with eachother.
A couple weeks ago, I decided it was time to root my phone, since I missed running the custom ROMs on my Droid. So I unlocked it and rooted it and everything went all fine and dandy. I decided for my first ROM, I would flash Xtreme Outcast's ICS ROM (v2.0, I think). When I first flashed it, my data worked fine (however downloading apps from the market gave me some issues, but I think that was another problem..). However, before long, like later that day, the 4g and 3g stopped working. After it stopped working, I decided to try to restore my nandroid stock ROM, but when I went back to it, not only did the 4g and 3g not work, the wifi just said 'error' when I tried to turn it on. So after that, I tried to flash the GB OTA RUU, but that gave me some issues, but I've figured out where that went wrong (mainver error).
Anyway, what I'm trying to figure out is what I can do to try to fix the issue. My mobile data IS on, the battery cover IS on, and the SIM card is inserted and, to my knowledge, working just fine. Would flashing an RUU help? Am I just having bad luck with this ROM and need to flash a different one? Should I update to the new RUU? Any help would be fantastic, and I'd award you 456789876435974 awesome points!
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
woodyt74 said:
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
Click to expand...
Click to collapse
Thanks for the response, but do you think it was just a bad flash if it affected the stock nandroid backup too? I will try flashing a new ROM soon either way, though. Is it possible to download an older version of CleanRom? I can't find a link on the first page of the thread, though I might have just overlooked it. I'm just not sure if I want to update to the new RUU right now, but if there are no other options, I might just pull the trigger on it.
Go to Scott's ROMs web site and you can download ISCE 3.7 which is still on the old firmware so no RUU needed. His roms are pretty slick and he provides great support.
Good point on the nandroid so I'm not sure what's going on. Hopefully the new ROM flash helps.
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
CollinswithanS said:
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
Click to expand...
Click to collapse
It is just easiest to install and ICS new firmware ROM that is already rooted.
There is however a couple of thread in the development forum on rooting and there is an ICS root tool there
I installed the CLEANrom tapped edition rom after wiping everything as instructed. It boots and initially I had issues with wifi working, but that seems to be working after flashing a stock kernel. Now if I try to play anything with sound or change the volume using rockers or in the phone itself it forces a reboot.
Any ideas?
Thanks
You are probably on old firmware and need to flash the patch
http://www.myandroidfiles.com/Downloads/Rezound/3.14.605.5/GB%20Firmware%20Patch.zip
Sent from my Rezound
Still having issues
Thanks for the reply. I actually ended up flashing it back to the rom that I had. I also made sure I flashed it to the original recovery as well which is amon ra. The rom I flashed it back to was the clean rom standard 4.4.
Unfortunately, I'm having the same problem no. If I go into the dialer and hit a number it freezes and force reboots. If I hit the volume rocker, it freezes and force reboots. It just force reboots for almost everything except for texting and going into apps.
any thoughts? The 4.4 worked fine on the firmware that's on here, and I did do the wipe and reset before I installed back. Maybe I bricked it?
Definitely not bricked. You wouldn't be able to even boot if bricked. What firmware are you on?
Here is some information
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Mr. Lando said:
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
Even though your on ics, it looks like your on gb firmware. Search for the gb patch for ics and flash in recovery and problem solved
2.11 hboot is gb firmware, 2.21 or up is ics firmware
Mr. Lando said:
The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
It runs just great on the correct firmware lulz
Correct Process for Updating firmware
Hello,
You stated that 2.11 in the hboot indicates gb firmware. Do you know a link to the correct thread that would give me the appropriate process for updating the FW one that will work with the CLEANrom 1.4 dev version? I got the wifi working again after flashing the "old firmware patch" and then reloading CLEANrom 4.4 everything went back to normal. However, I hate sense and I would like something without it which is what the dev version provides, but if I cannot get wifi working then it's kind of useless. When I say "if I cannot get wifi working" what I am indicating is that when I try to run the cleanrom dev version 1.4 WIFI gets stuck on "turning on" but never turns on and eventually just says "error" with no further details. I searched through forum feeds and found a few forums that hinted on steps, but many people have seemed to be confused by this issue in the past and perhaps it is related to firmware as you said.
Thanks
i would wipe everything again, reflash the rom, and then immediately the patch. that should fix everything. key thing is flash the patch before booting the rom. ive flashed the patch after rebooting before and had things go haywire. not a promise that it will work, just letting you know what ive run into
Scosler has everything listed in the op for the rom, and all files are there as well. There's a bunch of different instructions for however your phone is set up.
Sent from my Rezound
Continuing...
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
If s on and on 2.11 hboot Method 4:
-Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
-Reboot to recovery
-wipe data / Factory Reset
-Flash ROM
-Flash GB Fimrware Patch
-Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
-Reboot
-Profit!
Based on what you typed you didn't flash the firmware fix...
Mr. Lando said:
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
Click to expand...
Click to collapse
If i were you i would either s-off or flash one of the ics leak ruu's. that will help. there are many ways to solve your problem but those are your best bets
My issue is resolved. Thanks for all of your help and insight.
Sent from my ADR6425LVW using XDA
Care to share what you did? I am having exact same issue . . .
nvm - resolved: applied GB Patch right after ICS ROM flash (who would have known - I was kind of ignoring those GB patch instructions, since they did not apply to ICS).
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
Dunno if I'm risking flaming but here goes...
Had my Rez from day one, the phone is HTC unlocked but S-ON. I am still running a stock, rooted and debloated GB rom (based on the very first OTA update we got way back when). The rom has run great for me and so I never really had much reason to update...
The ONLY persistent issue I've had is with 4G cutting out, usually whenever trying to watch vids on Youtube, or trying to use Google Maps. Works fine on 3G. Way back when, someone had posted a thread where a lot of people mentioned they were having this exact same issue, so I figured that it was not an issue with my particular phone or even the rom/firmware. Even non-Rezound Verizon customers were complaining that they were having the same issues at the time (early last summer) so it seemed to be a network issue.
Fast forward a year and no one seems to be complaining about this issue anymore, and my wife has a Galaxy S3 that does not exhibit the problem... so I'm assuming that one of the OTA's that bumped the Rez up to ICS and updated the radios/firmware fixed this issue as well, so I would like to finally update to the latest and hopefully be done with this issue.
I have been reading threads and I think I know what steps I need to take, and wanted to run it by you guys and make sure I'm not missing something or doing something I shouldn't be, and that I have them in the right order... so here's my understanding:
1. Make a nandroid and titanium backups
2. Backup everything on the internal and external SD card
3. Relock device
4. Do I need to flash back to the stock GB OTA (to restore stock bloat apps that I've removed) or can I go straight to next step??
5. Flash latest RUU (can I do this from a PH98IMG.zip or does it have to be an RUU.exe run from my computer? I strongly prefer the PH98IMG method if possible)
6. Unlock device
7. Flash recovery
8. Root device
I don't really have any interest in S-Off or any custom roms, so I have left those steps off. Even back with the Incredible and now with the Rez, I've always been happy with the stock Sense rom just with bloatware removed, and that's my end goal here as well. So, do I have everything covered?
Points 1 & 4
1. Use MyBackup root instead of Titanium.
4. It will do a complete wipe also in the process, not needed.
PH98IMG will work, I highly and strongly suggest contemplating s-off NOW(if you really want to, not needed) versus doing it after. The PH98IMG you might want to look at is 3.14.605.12. If it's of any help, there was a few OTA's on top of that, which VZW may ask if you want to take through an OTA on the Rez's rom.
cool thank you for the tips. I was able to get onto the latest global OTA and firmware without issue.