Develop Bugs

CM 11 + One+ One Conversion kit Downgrade

Hey Guys,
A few days ago, i successfully flashed CM 11 and One+ One Conversion kit and it worked fine. But i realized it's not for me so i wanted to go back to stock 4.4.2.
I got my GNote 2 on download mode and hooked it up on Odin. I also have the Stock 4.4.2 firmware. However, it doesn't seem to be doing anything and it's just stuck on sboot.bin
{
"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"
}
What's the best way to go? Am I missing anything that i need to flash first?
Thanks and looking forward.

madchanson said:
Hey Guys,
A few days ago, i successfully flashed CM 11 and One+ One Conversion kit and it worked fine. But i realized it's not for me so i wanted to go back to stock 4.4.2.
I got my GNote 2 on download mode and hooked it up on Odin. I also have the Stock 4.4.2 firmware. However, it doesn't seem to be doing anything and it's just stuck on sboot.bin
What's the best way to go? Am I missing anything that i need to flash first?
Thanks and looking forward.
Click to expand...
Click to collapse
have u tryied to make full wipe ( data , cache , dalvik ) from any recovery before u start? give it a shot

Hi Sir, Thanks for the reply. That is exactly what i did before flashing the stock firmware.

ooops forgot to reply. I actually fixed it, the problem is the USB port. Just needed to use another PC, or you can also try different ports incase you encounter this problem.

madchanson said:
ooops forgot to reply. I actually fixed it, the problem is the USB port. Just needed to use another PC, or you can also try different ports incase you encounter this problem.
Click to expand...
Click to collapse
glad u got ur problem fixed

[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.

Flashed stock rom via ODIN and now my phone thinks it is 32 GB

TLDR; Soft bricked phone trying to install TWRP, flashed stock rom on it, now phone says its 32 GB when its really 256 GB.
Hi all,
So I got a brand new Note 10+ a couple weeks ago and tried to flash TWRP onto it thinking it was easy like it used to be. Boy i was wrong. Stupid iphone user mistake.
So, I googled how to fix the soft brick. Downloaded the most recent firmware and flashed it via ODIN.
I flashed the following
BL
AP
CP
CSC (not HOME_CSC)
I setup my phone and personalised it like i had before and just now got a notification saying my phone is almost out of storage.
So i click the notification naturally being like what the hell already?
And long and behold my phone is now 32 GB instead of 256 GB.
I googled ways to fix this but all the ways say to flash the regular CSC which i already did!
Can anyone help me?
I've provided screenshots of the DF command and the storage settings.
Screenshots:
{
"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"
}

This could happen if you have flashed standalone AP file without CSC file same time.
Stock AP file must be flash with BL CP and Home_CSC at same time unless it may shrink your data.

Thank you for your response, however i flashed the AP file at the same time as everything else.
If i was to flash the AP file including everything else but change out the CSC file for the CSC_HOME will i keep my data on my phone because it was a pain to set it all back up.

No...

Is there a way to keep my data or no?

JosephShenton said:
Is there a way to keep my data or no?
Click to expand...
Click to collapse
If you use HOME_CSC_* it will not wipe data If you use CSC_* then it will wipe data. But looking to your device issue, probably you need to wipe it.

Help with MTCD_MX - A-MEDIA AUTO - PX5 on Android 6.01

Hi guys, just got an android unit for my Citroen C4L. Got it used and it came with everything including the canbus.
Before installing on my Car I wanted to test it out and upgrade to Android Pie but even after reading I have a few questions that I hope someone can help me:
- Below is the config for the unit. Its a 2GB/32GB PX5 unit.
{
"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"
}
- I already found versions 2.79 up to 2.90 for MTCE_MX but I have no clue on how to update (and if its needed for something)
EDITED: Nevermind that one, got the .img file for MX2_3.13 from May/19 and updated fine
- The unit has only one button, being the reset button. I tried holding for 15-20 second, letting it go and pressing it again in order to try to get into recovery without sucess. Any other known method?
EDITED: After having built a OTG cable and sucessfully connected to the computer I tried using the keyboard to get into recovery cause, why not. Worked perfectly (Holding Alt GR + prints scr and pressing E repeatedly)
- How can I find the version of the BT module? To be sure isnt the one that has issues with android 8/9
EDITED: When I go to factory setting is showing SD-968 but since you can change this setting Im not sure if its the correct module being showed
-The Unit had a SD card slot but when I open a File Manager, it says "SD CARD not available", and when I insert the card, I get a USB STORAGE so my guess is that the SD card slot is just an USB 3 port, meaning theres no way to upgrading android from it correct?
- Would paying the 10 Euro be most practical method for me for the upgrade? Doing that way can I downgrade back to 6.01 is something were to go wrong?
- It is possible for me to run into any incompatibility from the current canbus?
Thanks!

Well, for know I was able to full flash an OREO image with the OTG cable, and then update to the latest Hal9K release.
I noted the serial number changed. Contacted Hal to see if its possible for me to go directly to android 9.0 (paying the 10 EUR)