Can i ask you for help?
I am trying to port cyanogenmod 11 to Samsung Galaxy Beam GT-I8530 (Gavini). This device is very similar to your GT-I9070 and to GT-I8160.
We don't have our device forum on xda-developers, so i'm posting this message here.
The problem is that after compiling kernel and system device doesn't boot. If i use kernel that was compiled with cyanogenmod, device failed to boot at all (It stays on Samsung GT-I8530 logo), if i use stock kernel device can boot into recovery, but when i try to boot system it stucks on ANDROID (Cyanogenmod) logo. ADB isn't working at this moment. Device isn't detected by PC, neither in Ubuntu nor in Windows 8.1 (when it is in recovery, everything is fine), so i can't get boot logs for debugging (or may be i don't know how to get them?).
In sources that i used, i modified device kernel config only (because our devices have different touchscreens and some other things). In other files i just changed janice to gavini (where i found it).
If you need i can provide any information that you request. (I haven't attached any docs now, because i don't know what files may be helpful).
Any help and ideas are welcome.
If someone can help, please write here (or PM me), because our BEAM community is very small and i9070 developers are our last hope in getting Cyanogenmod.
Related
Hey there,
I wanted to install a custom recovery on my MI8, I"m currently on MIUI Global 11.0.5.0 QEAMIXM, bootloader unlocked
I have tried several tutorials, such as:
https://www.the***********.com/how-to-root-xiaomi-mi-8-and-install-twrp-recovery/
https://www.getdroidtips.com/root-twrp-recovery-xiaomi-mi-8/
https://clickitornot.com/install-twrp-recovery-and-root-xiaomi-mi-8/
https://wiki.orangefox.tech/en/guides/installing_orangefox
https://forum.xda-developers.com/mi-8/development/official-orangefox-recovery-project-t4039531
everytime I reboot into fastboot, fastboot on my laptop doesnt recognize my phone, I mean if I type in "fastboot devices", it just isnt there, but adb recognizes my phone and also reboots into fastboot per command line....I just dont know what to do - I also used the all in one tool version 2, after reboot it just waits for my device which is already in fastboot..I just dont understand what I am doing wrong
I installed all needed USB drivers, my laptop recognizes my phone in device manager, everything is as it should be (also enabled ADB debugging on my phone)
If I type the command to flash recovery.img, it just get stuck there and nothing happens...
It is a very strange behaviour and I am sick of it right now - wasted the last three hours for this :crying:
Maybe someone could help?
Also I have several questions regarding finding the right ROM for my phone - I want MIUI 12 without any bloatware from XIAOMI, also want Viper4ANDROID if it is still a thing - also where I can read for some information regarding magisk? I never used it and I have no idea how it works, I just remember some things from my previous phones, such as Samsung Galaxy S5 or HTC EVO 3D, but this time it is all different...
I would be really thankfull, if someone could help me out
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authenticated mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
As redmi 9 is mtk based device so their is not any edl point...if you have authorized account then you can easily flash it without the device open
Just use older preloader.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
That I have an authorized account was a wrong information.
When I try to flash it with sp_tool the following error is displayed: STATUS_CRC_BROM_FAIL 0xC0060005
PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
Disable authorization and unbrick your Redmi 9
Now you can unbrick your device even if the redmi logo not coming..just go to below link and follow their steps.... https://megafon929.github.io/mtk For more information and how to do follow the below post...
forum.xda-developers.com
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.
Hi!
This phone has been given to me as broken. Yet the bootloader and fastboot work, so maybe there is something I can do? (I would love to install Ubuntu Touch on it!)
State of the phone, and approximately what I've done until now:
- fastboot works (sometimes I can access it from the PC, sometimes I can't)
- adb doesn't
- no system boot
- bootloader and fastboot only show up when phone is plugged in. If I unplug it the screen goes black.
- Can't access the recovery. Tried flashing TWRP (both official and modified found on XDA) or stock recovery, tried booting it from terminal.
- I have the dm-verity message show up ("dm-verity in not started in enforcing mode") when trying to boot. Threads I've found explaining how to disable it say it requires TWRP or adb (I think), and I can't access either
- tried modified boot.img, stock boot (can't remember exactly)
I have little hope, but maybe someone can come up with a good idea?
Thanks for reading!
After trying to flash TWRP (by following this guide: https://www.thecustomdroid.com/root-oneplus-6t-guide/ ) my device would no longer boot to the OS,but (stock) recovery and fastboot modes worked, so I tried to fix it by flashing some Android 9 roms from https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/ , and flashing a stock Android 10 boot.img (for some reason).
But my attemps at fixing it by flashing only made things worse, my current situation is as follows:
Device: Oneplus 6T (6/128)
Version (either Global or T-Mobile): Unsure
OxygenOS Version: Unsure, only know that it is Android 9
Bootloader: Unlocked
- Neither Recovery mode nor TWRP work
- Bootloader and Baseband versions show as empty
- I can only access Fastboot mode and EDL mode
- A power outage left my main pc (which had the drivers, permissions and backup i had been using, and need, to do this) a burning mess
- I´m currently using an old desktop computer i had stored (which has Windows 7), but it fails to recognize my device.
- I have installed and tried multiple versions of the Qualcomm, Oneplus, Adb and Android drivers, but it never recognizes it
- Windows doesnt allow me to manually select the drivers for the Unknown device as ¨the specified folder doesnt contain a software driver compatible with this device¨
- By searching the system and internet it always says that ¨the best software driver for this device is already installed¨
- Both of the above were tried with a disabled driver signature requirement
- When using it on the other PC, the msm download tool, it always said that the image didnt match the device, no matter which of the 13 versions I tried
- On my current PC, the msm download tool doesnt detect my device
I implore anyone that can provide any help or advise to do so, as I´ve already spent an entire week scouring the Internet (including the Oneplus and XDA forums) for any solution, but so far, nothing has worked. Have a good day and thank you for reading my post.
Hey man.
I'm a dude with no OnePlus 6T but have a OnePlus Nord N10. But I do know the really bad punch-in-the-gut feeling of not having a device work at all.
What does "fastboot reboot bootloader" show?? (Does your phone reboot to the bootloader upon that command being ran?)
Also did you try to flash the stock Android 9 boot.img that your device was updated to?
As for the MSM download tool, the last replies I've seen show that some people trying that on Win11 recently have got it working.
Also check if these work? https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
How to Unbrick Your OnePlus 6T When All Else Fails
When flashing files through TWRP, ADB, or Fastboot, there's a slight chance for things to go wrong. Whether it's user error related or something else entirely, it's always good to have a backup plan. In most cases, you'll be dealing with a semi-brick or soft-brick, which can usually be solved by...
oneplus.gadgethacks.com
Sorry if it sounds stupid but I want to try to help.
I really hope your phone gets fixed, man. Good luck!