I'm sure most of you are familiar with the "2 white bars when booting into recovery issue" so I have a favor to ask. I'm running the 2.5.0.5 recovery on my HTC incredible and needed to do some stuff from recovery. It seems like recovery is working, I just cant see the menu options. Can someone post the menu items (and order of course) so I can use it blind? I just need the main menu and partitions menu. Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just go to rom manager, all recoveies and install the new one. I think it adresses the slcd screen problem
Awesome, thanks. Can you also show me the mounts and storage menu?
RLKirk said:
just go to rom manager, all recoveies and install the new one. I think it adresses the slcd screen problem
Click to expand...
Click to collapse
Unfortunately this didn't work for me. With 2.5.1.1 The screen just went nuts and flashed a bunch of colors. 2.5.1.0 and 2.5.0.1 both had white bars. At some point I had an older version of the recovery mod that worked but then when I installed ROM manager it forced me to install the recovery mod which caused the white bars problem.
SOLUTION
It turns out the recovery is fully functional, you just can't see it on the screen. So, you can do all the mounting from adb. The best part is you don't even have to know the paths to mount. If you type
Code:
mount -a
from an adb shell it mounts all the partitions (except the sdcard for some reason).
adprice said:
It turns out the recovery is fully functional, you just can't see it on the screen. So, you can do all the mounting from adb. The best part is you don't even have to know the paths to mount. If you type
Code:
mount -a
from an adb shell it mounts all the partitions (except the sdcard for some reason).
Click to expand...
Click to collapse
Nice to know. Thanks
Sounds like you have a slcd screen. I had the same problem. Go to this link. Once you flash through Hboot it works perfectly. Better than messing around with it in the dark! Hope that helps.
http://forum.xda-developers.com/showthread.php?t=816273
Related
My old evo decided to commit suicide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway got a new evo in, trying to get it rooted. Got as far as getting S-OFF which seems to be important:
Supersonic EVT2-3 SHIP S-OFF
Hboot 2.02.0000
Click to expand...
Click to collapse
Flash MISC, run the pc36img. Everything seems sane, then i do the rageagainstthecage exploit again, load on a recovery image. as soon as i reboot to recovery my /system/ partition size gets cut in half and then i can never boot again because random files are missing. Also flashing images fails because half the files dont copy. same with nandroid restores.
results from df before:
/system: 358400K total, 270140K used, 88260K available (block size 4096)
results from df inside recovery after mount -a
/dev/block/mtdblock4 179200 131460 47740 73%
Click to expand...
Click to collapse
I cant seem to find anyone else with this problem, ive tried it several times with different recovery images. WTF am i missing?
Have you tried unrevokeds unrooter? I used it when i got my second evo with 2.2 on it and i had no problems. Maybe the root method is causing the problems.
I had the same problem. I ran RUU using fastboot and it restored me to stock.
Same issue...
I was able to get su with hboot Super one click.. I can post a place to download if needed. My issue is with the crappy quality of this hardware ver (003) my wife has the original and i love it.
also
I also cannot get any roms to load... I used the traditonal push with no success... Although i have noticed on significant thing that seems to keep happening.... its always fails with the boot.img. I tried loading Fresh through the Rom manager and all it would do is kick me to recovery.... try to do it manually and all roms fail on the boot img.
im currently running cm-7.2.0-RC0-marvel-KANG and im on US Cellular. Everything works except:
wifi and internet
Need some help please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
help
vansrootedandroid said:
im currently running cm-7.2.0-RC0-marvel-KANG and im on US Cellular. Everything works except:
wifi and internet
Need some help please
Click to expand...
Click to collapse
You [and all cdma variants (like me even)] will have to wait for kernel development as alquez states in his OP of that thread.
or
Restore your nandroid backup of stock (easiest fix).
Regards,
Rob
insink71 said:
You [and all cdma variants (like me even)] will have to wait for kernel development as alquez states in his OP of that thread.
or
Restore your nandroid backup of stock (easiest fix).
Regards,
Rob
Click to expand...
Click to collapse
Hope it comes soon...I forgot to make a backup before i went to cm7....however I do have a second Wildfire S thats rooted but for some reason i cant get into recovery to back up that ROM....it gets stuck on the white HTC screen....any ideas?
ideas
Can you boot to hboot [on second phone]? If not you are either semi-bricked or bricked. Still assuming you cannot get into hboot, go download the htc sync drivers, set up your environment [Google has a guide that walks you through it], then with the phone connected to your computer [and on] type "adb devices" If you get a return that looks like a short serial, it can be fixed... If no devices found... well, it will take someone smarter than me If you can boot to hboot, it can be fixed no problemo... Hit me back with results [via pm] I can't follow every thread I respond to.
Regards,
Rob
PS it sounds like the 2nd phone has had either a bad recovery or wrong boot.img flashed to it w/o knowing more
I've always used CWM but I see everyone basically recommending it. I've tried it in the past and I've never had it work probably, they just updated it to 2.4.2.0, so I figured I'd give it a shot. The time zone is set, time never is correct, battery is no where near correct, that doesn't bother me, however, I cannot make a backup. I CAN and do, but once I reboot and enter recovery again, it doesn't show up under restore. The backup is still in my phone though via root explorer. I usually fast boot flash the .IMG file, but I also used goo manager to just see if somehow it got corrupt. To be honest the only two features I like are being able to name your backups, and multi zip flashing is neat. What the ****?
TL;DR
Toro user
TWRP doesn't keep backups, date and battery info are incorrect.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Pretty sure this phone didn't exist in '99)
Sent from my MMuZZY'D SCH-i515
backups should be in /data/media/0/TWRP/...
because the virtual sdcard is in /data/media/0/ for android 4.2 and above
andQlimax said:
backups should be in /data/media/0/TWRP/...
because the virtual sdcard is in /data/media/0/ for android 4.2 and above
Click to expand...
Click to collapse
That's just a redirect.
Just how like that's the same for:
/storage/emulated/0
/storage/emulated/legacy
/storage/sdcard0
/sdcard/
Are all the same directory, same files.
REGARDLESS, twrp should account for the 4.2 filesystem as you needed to update your recovery going to 4.2 to have these issues corrected and my clockwork touch recovery works fine, and I've used the newest twrp, so it makes no sense, I've even backed up my storage, deleted /data/media while doing a full cleanup to have twrp and my ROM create the correct directories for 4.2 and it still doesn't work.
If it wasn't the correct version it would keep creating /x/0/0/0 everytime I flashed a new ROM which it doesn't.
I'm over it as twrp only has those two features which doesn't bother me and the interface is ugly IMHO.
Sent from my MMuZZY'D SCH-i515
andQlimax said:
backups should be in /data/media/0/TWRP/...
because the virtual sdcard is in /data/media/0/ for android 4.2 and above
Click to expand...
Click to collapse
notstevek said:
That's just a redirect.
Click to expand...
Click to collapse
It's not a redirect. /data/media/0 is the physical location of the data. The other locations are either fuse mounts or symlinks that point back to this location.
Hello everyone and have a Merry Christmas,
I'm trying to update my TWRP recovery because I want to go 100% stock. I'm still running TWRP 2.7.0.2. The most recent version of TWRP is 2.8.3.0.
I downloaded the TWRP manager app from the Play store and easily selected the last available version of the recovery to install.
After downloading the .img file, I get a pop up that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The pop up says: "Be sure that the listed path is correct for your device. An uncorrect check may result in bricking your device. You can't flash a recovery directly on Android on some devices. If you can't flash through Android, please choose a different method".
It looks like a "routine" alert, but nonetheless it sounds very alarming. How can I say if the listed path is the correct one for my device (HTC One M8 unbranded GSM international version)?
Thank you for helping.
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Because the procedure to go stock requires some flashing and it was adviced to have the latest version running.
I'm not such an expert, I'm more the type who tries to read as much as possible before trying anything, and upgrading TWRP was a sort of "pre-step".
Also I'm not very keen to use fastboot: I got that it is great, but it is not very straightfoward for beginners.
The tool from the Play store seemed to do the job pretty good and easily.
Mr Hofs said:
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Click to expand...
Click to collapse
What if I flash a custom recovery over a custom recovery? Is it possible to simply flash it and overwrite an already existing custom recovery?
there is no other way, the recovery will always overwrite the old one. its impossible to run 2 recoveries
After a bunch of research I finally decided to take the plunge to try and move to Lineage OS.
Phone is a Google unlocked 128GB 2 XL.
I was able to get through the unlock portion but after that all the guides went different directions. I was following the process from TWRP and at one point had the TWRP recovery app showing via fastboot but now all I get is the "device is corrupt" warning which then ends up in the white screen with Google logo and small unlocked icon.
Any chance I can get back to scratch or press forward to LineageOS/other ROM or is this thing a brick?
*Update* Not sure what key combination I used but I can get to the following TWRP screen. However the touchscreen does not respond and after the screen hibernates any key returns it to this state:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Strephon Alkhalikoi said:
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Click to expand...
Click to collapse
Not sure how I can do that.
I can get to the default green START option. If I selection that the system boot to a white screen adn stops.
If I select BOOTLOADER the device pops back to the green START.
If I select RECOVERY it gets to the TWRP screen but the touchscreen nor buttons work.
I've tried connecting the phone via USB to my PC but no matter what mode I put it in ADB never detects it.
The "green Start" is where you want to be here. That's the bootloader. You need to make sure the driver - assuming Windows - is set to ADB Bootloader Interface in Device Manager as well as make sure you have the latest version of the ADB / Fastboot package.