Related
Immediately after rooting my phone my wireless was permanently disabled. When trying to re-enable, the gui displayed "error" and nothing else.
I'm not new to linux and have successfully gotten adb and fastboot working under gentoo.
I have all the apks I need to root, but I erased my boot and recovery images when I tried to install the cyanogen mod. The cyanogen mod loops at the mytouch animated logo when I flash it to boot.
I have three simple questions:
First, has anyone successfully resolved the wifi "error" message? When I looked (yesterday) there were tons of confirmations about the problem, but not a single fix I could find.
Second, has anyone gotten cyanogen or clockworkrecovery working on the mt4g? It was very frustrating trying to get out-of-band access to the android market. It makes no sense to me whatsoever that access to free software should be controlled in any way by google. Have they been deliberately uncooperative in letting apks be downloaded to pcs?
Third, would anyone be willing to mail me copies of their boot.img or recovery.img? As I was unable to get clockwork recovery, I didn't backup my roms before trying to flash an attempted fix.
Help would be greatly appreciated.
Google hosts the market and the Market app itself is not open source, which if why they can and do prevent distribution of it. There's no restrictions of people distributing apks (license notwithstanding) through other means.
I think there's an alternate method to installing clockworkmod via fastboot. I reinstalled stock recovery this way, though I don't think that helps you without a signed system image.
There's also an ruu available but I don't think I've heard of anyone trying to user it yet.
Sent from my HTC Glacier using XDA App
poseidon1157 said:
Immediately after rooting my phone my wireless was permanently disabled. When trying to re-enable, the gui displayed "error" and nothing else.
I'm not new to linux and have successfully gotten adb and fastboot working under gentoo.
I have all the apks I need to root, but I erased my boot and recovery images when I tried to install the cyanogen mod. The cyanogen mod loops at the mytouch animated logo when I flash it to boot.
I have three simple questions:
First, has anyone successfully resolved the wifi "error" message? When I looked (yesterday) there were tons of confirmations about the problem, but not a single fix I could find.
Second, has anyone gotten cyanogen or clockworkrecovery working on the mt4g? It was very frustrating trying to get out-of-band access to the android market. It makes no sense to me whatsoever that access to free software should be controlled in any way by google. Have they been deliberately uncooperative in letting apks be downloaded to pcs?
Third, would anyone be willing to mail me copies of their boot.img or recovery.img? As I was unable to get clockwork recovery, I didn't backup my roms before trying to flash an attempted fix.
Help would be greatly appreciated.
Click to expand...
Click to collapse
the reason it's not working is because, I'm assuming, you followed the guide about forcing your update. When you did this it patches the kernel, but does not update the bcm4329.ko kernel module. There are a bunch of guides on how to root in the dev section. It looks to me like you started following my guide. If you look at my guide (entitled forcing update 2.2.1 and rerooting) it will give you the steps to complete the process with all files linked.
There are a bunch of us in IRC who would be willing to help.
Please post questions in Q&A section.
Hello everyone, First off I would like to thank all of those that have posted on this site and contribute to it.
Now to my problem. Let me share a little history of how everything started.
I first rooted my MT4G about a year ago, Tried to use IcedGlacier but it was not loading properly so I used cyanogenmod 6 I believe? I wanted to try IcedGlacier but It still was not loading properly. Then when I tried to restore it would not restore properly. At this point it appeared to be bricked but bootloader still worked but the PD15img file was not found. So after some researched I downloaded it and it restored my phone back to factory condition. Now I want to try other roms again because I'm getting bored of stock and attempting to load different kernels but this is where my issues are beginning.
As you can see in the attached photo that is what the bootloader looks like. I thought it was weird that next to hboot it says "HBOOT-0.85.2007 (PD1510000)".
(I tried to post the image but since I'm a noob I and unable. If you want to see the screen shot of my bootloader just message me.
I was thinking maybe this is a reason as to why now No other rom but the stock one will load. Also what is weird is that when it goes into bootloader it still says PD15img is not found but the phone will start up fine with the stock rom.
The phone remains rooted but No Rom or Kernel will Load and fully install.
When It loads roms it goes to install it shuts off and reboots into stock rom.
I tried to Use the PD15IMG.zip on the SD card to see maybe if it didn't load properly but it will begin to load with the blue bar in the corner but then after it goes all the way up nothing else happens.
I have been trying to look for answers but haven't found any real answers that help me fix my problem.
So if someone can help me I would greatly appreciate it.
The "no PD15IMG.zip" message is supposed to appear. When the bootloader loads, it checks the root of your SD for that file, and if it's not there, you'll get that message. Nothing wrong with that.
Since you're perm-rooted and running the engineering boatloader, you just need to make sure your recovery image is good. If you haven't already, download ROM Manager from the Market and use that to install a fresh copy of ClockworkMod recovery. From there you should be good to flash any ROM you want.
Thanks, I did what you said plus I realized when I was downloading the roms using a Mac and my Mac would unzip the file automatically and trying to compress it back to a zip doesn't work at all. But thanks alot for the help!
If the PD15IMG.zip doesnt work you probably dont have the part7-xxxxxxxxxx.zip file on your sdcard
Sent from my HTC Glacier using XDA Premium App
[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?
I just got a brand new K1. Fresh out of the box with 3-3 pre-installed, I downloaded and used TimmyDean's permanent root tool, flashing a rooted 2-2 firmware. I then enabled the backdoor and ran all the OTA updates up to 14-14. This took several hours in all. I then ran the BusyBox and SU Tools install script. Everything was looking okay. I selected the choice to exit the script with reboot. The K1 turned off and came back on with the Lenovo logo, but, at the top of the screen was red writing:
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002).
It stops there and goes no further. No bootup.
Attempting to research the error, it seems this is not an error too many people encounter or know about, so my guess is that my only way of fixing this problem is to flash the whole thing over again from the beginning. (Unless someone here knows something about this problem. That would be tremendously helpful.)
Having already experienced what it took to go from 2-2 to 14-14 the first time with the permanent root package, I'd certainly like to shortcut it however possible. In this thread, http://forum.xda-developers.com/showthread.php?t=1404351 , TimmyDean posted a rooted 13-13 that we can start from. However, the link to the download file for it is Multiupload.com, and Multiupload.com does not seem to be up for me. Does anyone know where else I can go to try and download a copy?
I'd have posted directly in that Development thread, but, since I am an XDA noob, the forum system only allows me to post in this General section.
After experimenting with the "permanent root" package several times now, each time ending up with the "Unsupported menu option selected: 1" error after any OTA update, I have to believe there is an incompatibility between the K1 I have and the bootloader files in the "permanent root" package. I do not know if my K1 is recently manufactured and they are now doing something different with them that causes this incompatibility or what, but I felt I should warn you all that flashing the "permanent root" package could cause your K1 to not take official updates or to otherwise brick it with the "unsupported menu option" error. Perhaps the 13-13 package, which I don't have and can't test, didn't have this problem.
My serial number is CB1245XXXX. Manufacture date is "11/11/27."
I have now given up on getting root on my K1 and would just be happy to get it back to a working condition that can take Lenovo's OTA updates without bricking. I am currently trying these instructions and will update as to whether or not that resolves the problem: rootzwiki.com/topic/13877-guide-ideapad-k1-restore-to-mostly-stock-with-ota-updates/ (The forum software will not allow me to post hot links, so copy and paste that to browser.)
The rootzwiki procedure did not work to correct the problem. After any update, the tablet is bricked with the error. There are a few threads on the Lenovo support forum on this issue now, and there is no solution.
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Unrecoverable-Boot-Loader-Error/td-p/683633
I believe these old bootloader files will not work and will brick newer K1's, so my warning is:
DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
This might only apply to more recently manufactured K1's, but, since we do not know when this problem begins, it is not possible to know beforehand whether or not you will brick yours.
To be on the safe side, DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
Unfortunately, there was no backup option in the rooting packages, so I could not get a copy of the stock bootloader or any other files, if they are indeed of a different and newer variety. If someone has a recently manufactured K1, perhaps you can get those files and share them, because a lot of people are starting to see this problem now.
I have one with sn#1250xxxx, mfg dt 11/11/29. I wasn't even trying to root the thing. I happened during an OTA update. I tried probably all the recovery/rooting option out there. None of them worked. I have the tablet booting at lenovo screen. But I think you are right about the bootloader. If we can get the correct bootloader, we might be able to the the tablet back to life.
fix?
Has anyone come out with the fix for your issue.. I have the same issue . Used TImmy Dean's method.. and anything updating past the 02_02 (loaded from the tool I get the error... Anyone here have access to contact JimmyDean to ask him for help?
I see that he updated the tool to K1_A301_13_13_111209_US and maybe K1_A301_14_14_111209_US but all the links are dead.. anyone have a good place to download the files?
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
those are just OTs.. not image files.. If you don't have a compatable boot loader, you can't load those files.. We don't have a compatable bootloader.. so this is why we need ver 13 of timmy dean..
rezapatel said:
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
Click to expand...
Click to collapse
Can someone who's getting this bootloader error send me a pm. I put together a stock 120109 update that may work around the issue and I need someone to test.
Was this issue ever resolved, I didnt attempt to root mine, only attempted to wipe it clean and got this..
No, no real resolution. What I ended up doing was NVFlashing one of khanning's ROMs, like this one: http://forum.xda-developers.com/showthread.php?t=1560441
I don't know what's going to happen when I have to update again, such as the upcoming Ice Cream Sandwich update promised by Lenovo.
Hey guys, I've been trying out ROMs for the past couple weeks and finally decided I wanted to replace my stock ROM with the energy rom to save space. I wiped all files from my stock ROM and then tried to flash the energy rom. I got an error so decided just to leave it for another day and created a second partition for the energy rom. Forgetting to flash my recovery back to my stock slot, I booted in to the energy rom. Now my recovery buttons don't work, probably due to the fact that they were installed on the stock rom. I don't have any way of getting in to the recovery and that kind of worries me. I've been reading up on fastboot, but don't know were to be begin or get ahold of rsdlite since all of the links send me to spam. Any help would be greatly appreciated!
I am currently using Safestrap 3.1.2 and do have a backup image of my stock ROM on my external SD card (at least I was smart enough to remember that).
Figured it out
Figured it out! Just in case anybody else has this problem, use RSD to fastboot the stock image to your phone. I know everything I read was talking about this, but I couldn't find detailed instructions anywhere. Most time consuming part for me was editing the xml file due to "oem" command lines that weren't recongnizable. There is a fixed xml file on droidrazr forums for those who need it!
Please help same issue
bgregs514 said:
Figured it out! Just in case anybody else has this problem, use RSD to fastboot the stock image to your phone. I know everything I read was talking about this, but I couldn't find detailed instructions anywhere. Most time consuming part for me was editing the xml file due to "oem" command lines that weren't recongnizable. There is a fixed xml file on droidrazr forums for those who need it!
Click to expand...
Click to collapse
PLEASE HELP ME
I am in the same trouble you were in here is my thread.
Hello,
I'm looking for help. I wish I could ask on the development page, but I don't have access to do so because of my low post count.
I've had a problem with my HTC Bolt screen. I made a video of the problem and put it on youtube:
https://www.youtube.com/watch?v=1eR5NFDcnvU
I thought it may be a problem with the firmware/stock rom that is loaded with bloatware, so I decided to tinker with rooting, etc...
First thing I did was gain root using this method:
https://forum.xda-developers.com/bolt/how-to/root-supersu-v2-78-sr5-s-off-sunshine-t3513048
Then I downloaded and ran Sunshing to get S-off.
I then tried to install a new Rom, but it wouldn't install, giving the " E:footer is wrong .. E: signature failed" on the android recover.
The phone on my screen continued to glitch, so I tried to go back to stock using the RUU as described here:
https://forum.xda-developers.com/bo...t-htc-bolt-1-17-651-11-updated-t3502778/page4
but the process hung when trying to install a new rom using the RUU . I assume this happens because of the same "E:footer is wrong .. E: signature failed" problem when I try to flash a ROM.
Please help. I can't boot up into the system and am new to this. Also, if you can point my problem to the developers, that would be great.
recovery screen shows this:
*** Software status: Official ***
*** Unlocked ***
*** S-Off ***
This looks good to me to give me access to flashing, but the error keeps getting in the way.
Thanks,
Marc
what recovery are you using?
when you reboot to download mode and use fastboot, type fastboot devices. Does the serial number and fastboot show up?
what method are you using to RUU?
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
marcram said:
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
Click to expand...
Click to collapse
Is the screen always black, or intermitting?
in download mode
fastboot oem lock( it will say relocked and not Locked though)
OK, thanks. Maybe some chmod can solve it. Sprint is charging since it is more than 20 days old. Going to HTC instead since under their warranty.
The problem is intermittent, but is getting worse with each hour. Others are having the same issue.
I've been seeing the same issue with the display not waking since the .22 update...it's very intermittent on mine though, maybe 10% of the time...I haven't been able to narrow it down.
did u flash twrp recovery before flashing a ROM?
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
marcram said:
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
Click to expand...
Click to collapse
no, twrp is best installed by flashing it in download mode, u cannot flash a ROM via stock recovery, only custom recovery(twrp)...https://forum.xda-developers.com/devdb/project/?id=18340#downloads
Thanks, twrp did the trick. But with 3 different roms, I'm still having screen blackout issues. Going to need help getting back to locked and s on after RUU. Guess I'll start a new thread for that.