Develop Bugs

[Q] [REQUEST] Working ROM for US Cellular

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

Unable to root stock Rom

Hi,
I've got some trouble to get a proper root mod on my phone. After i used some of the hints which can be found in this forum i didn't managed to get it running.
History of my mod-trys:
I got it running until i patched my stock Rom to the latest version via fota. (the feature pack for German roms)
Then i tried to go back to a stock Rom here at the forum - but with little success. I installed it but important not able to get the root mod running without errors.
This is a screenshot of superuser:
{
"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"
}
If i try to update i am getting an error.
Sadly i don't know what to do now to get this fixed. Iused many fresh installs / cleanup etc but everytime i install the update.zip via recovery - its messed up.
gesendet mit Tapatalk 2

try to flash CWM with ODIN.. do not use adb shell because it needs root.. the try flash another ROM.. IT'S VERY RISKY.. I'M NOT RESPONSIBLE IF YOUR PHONE BRICKED

i've got cwm at the moment installed. As far as i understood the "root / unroot" thread it's not recommended to use this while rooting via recovery.
i used cwm to create a backup of my system and i rolled back it many times - so - thats working fine.
But my problem is that i don't find a suiteable custom rom for me - because it has to be "as stock as possbile". Meaning - i'm doing much development and testing with that phone - so it's not good if the mod can do things which i can't do with a stock rom. (Rooting is ok - i can handle that "mod" - if it works )
But i'm not firm enough with android core development to fix the root problem right now. Are there any manuals to use the "USB Debugging" Shell? I'm able to use that, too.
OR - if exsists - is there any _german_ stock rom out including the "value pack" addon? I just found a stock rom which is missing that. I guess there's coming with the value pack that causes rooting via update.zip going mad

i cant also root mine and i also have the value pack update but before i had the value pack i can still root my phone :CC

Reset back to stock

I recently got a Epic 4G Touch from a friend who was upgrading. After messing around with it, I decided to try get CyanogenMod running on it. To make a long story short, I can no longer get the phone to boot, but I do have access to the AGAT custom recovery. I know I could use OdinExecution, but the phone is no longer recognized by Windows when plugging in USB - probably after flashing the kernel.
My question is what should I do from here? The only other way to get data onto the phone would be microSD, unless I can get USB working (I doubt). I was pretty foolish to go into this without more reading, and for that I apologize.

Ringle said:
I recently got a Epic 4G Touch from a friend who was upgrading. After messing around with it, I decided to try get CyanogenMod running on it. To make a long story short, I can no longer get the phone to boot, but I do have access to the AGAT custom recovery. I know I could use OdinExecution, but the phone is no longer recognized by Windows when plugging in USB - probably after flashing the kernel.
My question is what should I do from here? The only other way to get data onto the phone would be microSD, unless I can get USB working (I doubt). I was pretty foolish to go into this without more reading, and for that I apologize.
Click to expand...
Click to collapse
If you can get into recovery, I would try going here and flashing one of the zips found there.
http://forum.xda-developers.com/showthread.php?p=31961585
If by chance you can get into download mode and if the links are not working you can always use this
http://www.sammobile.com/firmwares/3/?download=12947

BIGSAMDA1ST said:
If you can get into recovery, I would try going here and flashing one of the zips found there.
http://forum.xda-developers.com/showthread.php?p=31961585
If by chance you can get into download mode and if the links are not working you can always use this
http://www.sammobile.com/firmwares/3/?download=12947
Click to expand...
Click to collapse
Thanks for the reply,
I managed to get a custom ROM installed, so at least I'm able to use the phone. Now I need to figure out how to get USB working again. I took a snapshot of the device screen:
{
"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"
}
Is there perhaps a compatible kernel I can try?

[Q] TWRP Update path for One M8

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

unable to install or launch TWRP

Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma

Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.

Facing the same issue. Tried everything but no success.