Just went through the adb process and added param.lfs to the phone, then pushed my new logo to the phone and works fine. But when it reboots, it only shows my new image for about a second then reverts to the stock image. Strange because that stock image doesn't exist in the directory where it reads the boot image (maybe it is in a temp directory) so I will have to push the modded image to that temp directory, anybody have any ideas that can help me? Thanks.
I'm assuming you replaced the boot logo in the param.lfs? The second "stock" may be the kernel boot image.
Sent from my cm_tenderloin using xda premium
FaultException said:
I'm assuming you replaced the boot logo in the param.lfs? The second "stock" may be the kernel boot image.
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
I think I should tell you that before I added the param.lfs thing, adb detected my device in download mode and it worked fine. However, after I rebooted it to download mode, adb didn't detect the device. I was instructed to push the new image after adding param.lfs, but since adb didn't detect it in download mode, I could only push it when the device was on.
Related
Hey guys.
I am assuming my phone is not "bricked" because I can still get to the clockworkmod interface and mount usb and things like that, but I cant get any roms to load. I followed all the instructions and multiple videos to make sure I did my 1.5 right. Seems to be find as far as root. When I logged in to my old backup i had superuser and all.
I tried to install the WARM rom, but didnt work, so i restored my backup and bought Flash Image GUI which then I loaded the WARM zip and it said it found the Kernel and went to install it. It then asked me to reboot, which I did, and then proceeded to install the rest of the ROM via clockwork install ZIP, after doing that I can no longer even restore my backup.
If i try to load WARM, it just sits at white HTC screen and never changes. If I try to load MIUI, it loads to HTC screen, makes a sound and then goes black forever with backlight on but black and buttons lit.
That is all I can currently do. My backup no longer loads or works.
Is my phone bricked? I dont think so since I can get to clockworkmod, but what can I do to try to get it back up and running?
Thanks,
M374llic4.
Your kernel is most likely the problem. When using the the flash image GUI, dont accept when it asks you to reboot, manually hold down the power button and reboot yourself. Hook up your phone to the computer and boot into fastboot usb and fastboot boot recovery.img then install the warm rom. This will ensure you have access to flash the kernel.
JayDaKissEP said:
Your kernel is most likely the problem. When using the the flash image GUI, dont accept when it asks you to reboot, manually hold down the power button and reboot yourself. Hook up your phone to the computer and boot into fastboot usb and fastboot boot recovery.img then install the warm rom. This will ensure you have access to flash the kernel.
Click to expand...
Click to collapse
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
m374llic4 said:
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
Click to expand...
Click to collapse
A friend kinda having a similiar issue with this.. but I tried this all on his computer and not sure if it's driver issues or not.. but I can't get adb to communicate with this phone.. when I use " adb device's " it doesn't show up.. but If i plug my phone it - it picks it up.. Same issue as the guy above it seems.. but when I go into the boot loader - click fastboot and it picks up the usb.. i still can't get them to talk.. any idea's?
m374llic4 said:
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
Click to expand...
Click to collapse
When you rooted your phone, you should have downloaded a folder called newevo3droot or something like that. There's adb files, fastboot..etc and this is how you would have flashed clockworl recovery. Since you are on hboot 1.5, you need to go into fastboot and connect usb so that it says fastboot-usb, then you need to run the command fastboot boot recovery.img. Recovery.img is the name of the recovery image file in that folder. I think it's something like cwm******.img
I did download that, and had some help from someone in the IRC channel and he got me back up up and running! Turns out you have to use USB fastboot on the phone along with fastboot.exe via cmd prompt on the pc with the CWM.exe to load the kernel, then once you do that, you use the phone cwm load from zip to load the rest of the rom and you are good to go!
JayDaKissEP said:
When you rooted your phone, you should have downloaded a folder called newevo3droot or something like that. There's adb files, fastboot..etc and this is how you would have flashed clockworl recovery. Since you are on hboot 1.5, you need to go into fastboot and connect usb so that it says fastboot-usb, then you need to run the command fastboot boot recovery.img. Recovery.img is the name of the recovery image file in that folder. I think it's something like cwm******.img
Click to expand...
Click to collapse
Yeah, thats what I did with some help from a fellow XDA member via IRC and it worked perfect! I was trying to do it all via the CWM on the phone side only, not via command prompt which was my issue.
Good Morning XDA
So I have a bit of a problem, it appears that my recovery is corrupt.... very similar to Brick #2, however it does not give any error. It will not boot to fastboot, and I do not have a NVFlash backup (This happened months ago, before NVFlash was out)
Brick 2: When booting up your Prime hangs at the splashscreen (the screen with "EeePad" in the middle) and tells you something about an "unrecoverable bootloader error" (happened so far to at least 4 users)
-> Please go to Option 2
Now I have noticed that while booting it tries to check for an OTA update. My question is, without CWM or TWRP can the prime still load an OTA if I were to put it on SDCard as EP201_SDUPDATE.zip as has been said in another thread? Has anyone else run into this?
I realize the chances are slim, but I thought I would ask to see if anyone has had success with this.
Are you able to go into the Power/Volume- mode where you can either wipe or continue? Unless you can get to this menu, you probably would not be able to load the E201_SDUPDATE.zip from your sdcard.
The check that you are seeing is perhaps the prime checking the /staging partition to see if any data is in that partition. The staging partition is written to in two scenarios in the stock prime.
1. OTA updates - downloads the update > writes data to staging > upon reboot the blob file in staging is broken down and written to the needed partitions.
2. E201_SDUPDATE.zip - upon entering stock recovery by powering up with Volume Down pressed, and then pressing Volume Up after the message is shown, the stock recover (RCK mode) will check the sdcard for the named file, check versions with the currently installed version, check signatures in the file, unzip the contents to /staging, and then reboot. After reboot, the prime will check the staging partition and then flash the needed partitions.
Let us know if you're able to access the Power/Volume Down menu.
kokopuphz said:
Are you able to go into the Power/Volume- mode where you can either wipe or continue? Unless you can get to this menu, you probably would not be able to load the E201_SDUPDATE.zip from your sdcard.
The check that you are seeing is perhaps the prime checking the /staging partition to see if any data is in that partition. The staging partition is written to in two scenarios in the stock prime.
1. OTA updates - downloads the update > writes data to staging > upon reboot the blob file in staging is broken down and written to the needed partitions.
2. E201_SDUPDATE.zip - upon entering stock recovery by powering up with Volume Down pressed, and then pressing Volume Up after the message is shown, the stock recover (RCK mode) will check the sdcard for the named file, check versions with the currently installed version, check signatures in the file, unzip the contents to /staging, and then reboot. After reboot, the prime will check the staging partition and then flash the needed partitions.
Let us know if you're able to access the Power/Volume Down menu.
Click to expand...
Click to collapse
Unfortunately no, it simply goes strait to trying to load recovery (which doesn't work).
Does your prime hang at the eeepad logo, or do you get the android robot on the ground?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
Does your prime hang at the eeepad logo, or do you get the android robot on the ground?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It hangs at the Eepad logo....
Averros the Ancient said:
It hangs at the Eepad logo....
Click to expand...
Click to collapse
I am guessing since you are using recovery, you have unlocked. I think you will further complicate the issue by trying to install a stock ota possibly solid bricking you tab. Basically you need to access either fastboot or the recovery in order to do anything with it. For recovery, press and hold power and volume down until you see the part about rck then release power and press voulme up. I know you probably tried this but you really do need to get to one of the 2 in order to fix it. I don't think it is bricked (yet). Fastboot would be the best then install trwp, I am not a fan of cwm as it has be flakie for me.
Ouch. I'm sorry to say, it appears you have a hard brick.
Sent from my SO-01C using xda app-developers app
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
liqdnitro said:
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
Click to expand...
Click to collapse
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Batesinc said:
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Click to expand...
Click to collapse
I Did A Lg Update Tool Fix Brought It Back To Life
Trying to figure out if I can get the view working for my friend.
We rooted it via HTCDev, flashed CWM with fastboot and tried to then flash CGRom with appropriate GApps in recovery after doing factory reset, cache wipe, dalvik cache wipe and a wipe of the /system.
Phone said all was installed correctly, and when rebooting went straight to a black screen.
Trying to power off the View would not work, it keeps booting to the recovery.
Figured out the battery was very low so we charged it fully on a battery machine.
Still would not boot.
Tried flashing another rom, which at least got us to the boot animation, but it just sits with the animation repeating over and over.
Cant flash the only RUU I found because it is older than the last firmware on the device.
Wanted to use the multitool, but it doesn't support the HBoot we're on, and requires the tablet to be fully booted for other functions....
At this point I'm stumped, and we'd be happy just to get it back working even if it was only stock.
Did you flashed the boot.IMG manually? Since you rooted the view via fastboot you need to flash the boot.img from the ROM manually every time you flash a ROM.
Sent from my HTC Flyer P512 using xda app-developers app
Manually how?
Via fast boot or recovery?
If fast boot what is the command? And I can just pull it out of the rom's zip file?
TonyTurboII said:
Manually how?
Via fast boot or recovery?
If fast boot what is the command? And I can just pull it out of the rom's zip file?
Click to expand...
Click to collapse
Ok since you chosen CGROM open the zip file. There you will find a files boot.img. Copy it to the directory where you have adb and fastboot.
Open CMD or Terminal navigate to the directory and type
Code:
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
The problem should be fixed.
Finally got back from vacation and gave this a whirl.
Worked perfectly, thank you.
Sent from my HTCONE using xda premium
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Cap'n Jazz said:
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Click to expand...
Click to collapse
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Click to expand...
Click to collapse
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
http://img854.imageshack.us/img854/6248/ismh.png
This is how far I got in cmd if I'm headed in the right direction at all..
Cap'n Jazz said:
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
This is how far I got in cmd if I'm headed in the right direction at all..
Click to expand...
Click to collapse
You start fastboot in the phone, that puts it in a mode to enter fastboot commands from a PC... You Don't do anything in the phone in fastboot, you use the fastboot command that is part of the ADB package. The same way you would have unlocked the phone on HTCdev.com to allow root or CWM to be installed.
Sent from my Nexus 4 using Tapatalk
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
mjones73 said:
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
Click to expand...
Click to collapse
Thank both of you so much! I'm sorry I had to have you completely spell it out for me, but I appreciate the help and this forum in general so much!
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Did you flash the boot.img this time? I would suggest after you get booted, trying rumrunner to go S-off... It saves sooo much time... I'm always switching between multiple ROMs because I'm s-off....
Sent from my HTC EVO 4G Running AOKP 4.2.2
Cap'n Jazz said:
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Click to expand...
Click to collapse
... you should remember one thing for sure. Because you are s-on whenever you flash any custom rom, you have to flash its corresponding boot.img file in fastboot separately otherwise you are gonna get bootloop ...
---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------
... and yeah. you should try to get s-off as you are already been suggested above ...