Related
Hey guys, even though I don't post here much, I've done my share of rooting, unlocking, and flashing roms. This post is going to very general, philosophical, long, and technical, and I've tried to research these things myself to no avail, so I really hope someone can put me on the right track. I have a few questions to ask, and if you want you can skip to the TLDR, but first I have a little background on my questions:
Pretty much any guide you can find on rooting, unlocking, and flashing devices here on XDA comes with the warning that you can "brick" your device and void your warranty. Before I started hacking Android devices, I was installing various Linux distros on all sorts of PCs, and I didn't once hear anything about the possibility of bricking your PC, or loosing your warranty from installing Linux on it. The reason why, is because no matter what you do to the software on your PC, there is always the option of installing another operating system, and usually restoring the software to a factory state, because messing with software does nothing to affect your PC's BIOS. However, on most Android devices, we run into trouble flashing custom operating systems on our phone because the bootloader isn't typically as open as a PC's BIOS.
I recently purchased a refurbished Nexus 7, and I've really enjoyed it, because the flashing process has been similar to my experience installing Linux distros on various PCs, at least in terms of "openness"; I can always relock the bootloader, and I can always flash back the stock rom without having to worry about bricking my device (I don't mess with overvolting or overclocking, because that actually does prove a potential hardware danger to your device). My first Android device was a Motorola Atrix 4g, which I rooted and unlocked, but I was sad to find out that the device doesn't have a bootloader that you can re-lock, which means for any warranty purposes, I was screwed. After learning this about the Atrix, I started researching more about the bootloader on Android devices, and even after some extensive Google searching, and looking at XDA posts, I was still confused. So, TLDR; here are my questions:
1. Where is the bootloader on Android typically stored? Is it on the same flash storage as the rest of the OS, a PROM, EPROM, or EEPROM?
2. Along the lines of question one, is fastboot (on devices that have it) part of the bootloader?
3. On a device with an EEPROM bootloader, shouldn't it be possible to restore the bootloader to it's original factory state even if a command like "fastboot oem lock" doesn't work with the device? I realize that if possible, this process could brick your device if anything goes wrong, just like flashing the BIOS on your PC could brick it if something goes wrong, but the idea is that you could do this if you needed to return the device for warranty purposes and you've unlocked the bootloader.
4. Shouldn't flashing ROMs and rooting a phone with an unocked bootloader with fastboot enabled be just as safe as installing a Linux distro on a PC as long as you have a copy of the stock ROM of the device?
5. What devices come with a fully open bootloader? (I define this as a device that can boot into fastboot mode, and can be trivially unlocked, or locked with the commands "fastboot oem unlock" and "fastboot oem lock") All the Nexus devices (at least the new ones anyway) are like this, and apparently the Motorola Xoom is too, but I don't know of any other devices like this, and it would be helpful to have a list, because I like the idea of always being able to completely restore the device to it's factory state. Is there a better term for what I define here as a "fully open bootloader"?
6. What devices come with a bootloader that is unlocked by default? I believe the Nokia N900 is like this, (in fact, I've heard Nokia encouraged flashing as a standard update method for the N900) but I'm not sure about any others.
7. Why is getting new/custom Android images working on different mobile devices so difficult? To explain this more, I'll go back to the analogy of installing an os on a PC: When you download a Linux distro to be installed on a PC, you don't have to download a specific one for your device, you just have to choose the right architecture and things generally work right out of the box. I know there are driver issues sometimes, but it's still different than developing an alternate mobile OS; you usually have to deploy images for specific devices, and even then oftentimes a lot of the features don't work. Is this because mobile device drivers are not yet as standardized as device drivers for PCs are, because OEMs don't usually release the source code for their device's hardware, a combination of the two, or something completely different?
bump
Mostly about your fastboot question. Flashing it from a hard bricked state requires special tools and most of all access physically or though the USB port. If the bootloader is gone and there is no low level initial driver or boot component it may be impossible to re-flash. APX mode is one example of a mode you can access on the original N7 but the bootloader has a specific Secure Boot Key (SBK) unique to each device which is why those people who hadhard bricked their N7's could not restore through APX but some other Asus devices worked with APX and nvflash software.
I am thinking APX mode was some type of port to the Tegra 3 Arm SoC to access low level diagnostics commands not to far off from JTAG at the processor level!!
I would also like to know more about fastboot and from a recent risky test I performed link below:
http://forum.xda-developers.com/showthread.php?t=2391072
My conclusion is the fastboot on the N7's must be some type of eeprom unlike that one found on a PC Motherboard BIOS or an AppleMAC Main Board called EFIbios. Even new PC motherboards are now coming with EFI Bios chips like Gigabyte and Asus. Even USB flash drives have a rom with some boot code in them. These are probably also flash-able with the right tools.
The fastboot bootloader can also be programmed just like that on a PC or MAC Motherboard with a specific tool, fastboot, while the android is in fastboot mode using a fastboot command, like fastboot flash bootloader 4.23-grouper.img for example. So there are fastboot updates for this chip.
I don't think this part of the bootloader can be part of the flash ram as the OS partitions are on android devices. Some will say it has an area on the ram nand memory but I am starting to feel it resides on a chip of its own such as the newer SPI or I2C EEPROM memory chips which I have programmed myself using Microchip PICKIT 2 and PICKIT 3 developmental boards and using Microchip's MPLAB IDE software to write the programs.
I am trying to see if there is a second chip just for the bootloader by viewing the schematics of the N7 original model 2012 since I cannot find the new model FHD 2013.
Check this pdf out it mentions different bootloader's used and fastboot is mentioned in that document!!
http://www.ti.com/lit/an/spraag0e/spraag0e.pdf
If someone can point us to some white paper or PDF on this it would be great because my exhaustive google search could not dig up anything!!
Found Schematic check out the iROM boot code chip. That's probably where the fastboot code resides.
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10 bought from T-Mobile.
As this is a carrier specific MSM, it will only work with BE2028 model with build tag BE88CB
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
OnePlus for the device and OS
Reserved
I need this for the T-Mobile Variant.
- Works great! Thanks.
I learned a ton of hard lessons with this device. My maiden voyage of custom ROM and hackery. Now, unfortunately, I have to resort to a power greater than my own mind to restore my little N10 5G to sanity. Thank you for this post, and wish me luck,
Click to expand...
Click to collapse
Will the above work on the TMobile varent?
mbl1979 said:
Will the above work on the TMobile varent?
Click to expand...
Click to collapse
Duh
una ar oem aluna solucion
Can i use this to downgrade from 11 to 10..?
Fr4n©\<y said:
Can i use this to downgrade from 11 to 10..?
Click to expand...
Click to collapse
Yes. Moreover when boot to Android 10 and connect to WiFi it can be updated back to Android 11 ( through native update interface, did not check but got a prompt )
@Some_Random_Username
What if I have Unlocked Bootloader + TWRP + patched boot - will unbrick flashing restore these partitions to factory defaults ?
Will I lose bootloader unlock after flashing ?
Thank you
.
Testing
Would this also work on the Metro version?
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2025 model with build tag BE88CF
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
OnePlus for the device and OS
Reserved
Thank you.
I used it yesterday after I screwed up my Nord N10 5g. I hadn't used msn since last year on another device I sold, so had to be real careful getting back in the saddle.
It worked fine - no issues - except it took 500 seconds not just 300 - lol.
So I got everything downloaded and installed once I get the nord in edl mode it shows as bulk driver I tried to install the cab through driver update and my pc doesn't see it what can I do to fix that
The URL with links to files doesnt seem to have the current version of BE2028 - T-Mobile - 11.0.1.BE88CB
D:
the problem i encountered was it showing up as unknown usb device (device descriptor request failed) in device manager
Hi, I have bricked my Nord N10 Metro PCS while installing magisk patched boot. The phone is stuck in fastboot mode. Kindly assists. Do you have the T Mobile Android 11 Firmware? I was on Android 11 with August security patch
umaga2012 said:
Hi, I have bricked my Nord N10 Metro PCS while installing magisk patched boot. The phone is stuck in fastboot mode. Kindly assists. Do you have the T Mobile Android 11 Firmware? I was on Android 11 with August security patch
Click to expand...
Click to collapse
If you bricked it, then you have to unbrick using the provided tool here, it's only android 10, though. Afterwards you must do OTA.
andreas__ said:
If you bricked it, then you have to unbrick using the provided tool here, it's only android 10, though. Afterwards you must do OTA.
Click to expand...
Click to collapse
You've saved my life brother. The tool has worked perfectly. I am able to update to A11 via OTA
Some_Random_Username said:
Reserved
Click to expand...
Click to collapse
Bro on behalf on all us dumbasses slash semi noobs I thank you
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2025 model with build tag BE88CF
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
Hello. I have OnePlus Nord N10 5G model BE2029 and cannot get it unbricked. MSMTool fails with error "Param failed". Can you point me to the right ROM, I have been struggling whole day and still no luck.
My friend, I don't know how to thank you for this. After the update that I did on my phone about 1 month ago, I have been going crazy with having problems sending texts and making calls whether on 5G or 4G. I got together with oneplus customer service today to revert back the OS, for me and it was no help. This has been perfect!!!! thank you so much!!!
My OPN105G is forever stuck on "waiting for device" in both status of communication and status of last communication... i tried like over 20 times. the device manager shows it fine as 9008.
Hello quick question,,, will this lock my bootloader?
Nathan1616 said:
Hello quick question,,, will this lock my bootloader?
Click to expand...
Click to collapse
Yes. It puts you back to default stock.
As long as you have your unlock.bin file, you can unlock your bootloader again though.
Spent four hours trying volume buttons and adb method. Nope... Don't waste your time. This works for I'm assuming 1 out of every nobody on planet Earth.
Your browser is not able to display this video.
MSM has readback function which can grab stock boot for patching
works likea charm much love and thanks from barberton . ohio
Hello to all! Thank you for taking the time to read my post and questions!
While I'm quite PC savvy, I've never had the extra funds to invest in mobile devices such as tablets, but as luck would have it a buddy found a handful of old G Pad 8.3 (aka LG V510) tablets at a local dump early last year and dropped them off to me to play with. I successfully unlocked and rooted them all and was able to use the LG Flash tool to flash the proper 4.4.4 stock ROM to them, as well as using the mobile support tool (which is now defunct) at one point in mid 2021 to do updates from LG itself.
Not long after getting the tablets running I became sidetracked with other must do projects for months and these tablets languished here. Recently I pulled them back out, as I have more time to investigate uses for them at present.
The first tablet I moded allowed me to run Ubuntu and log into it from my desktop with VNC. No problems there. I can even install my mail server on it now that Linux is more exposed.
The next tablet I tried to mod I accidentally flashed the wrong firmware to... Bricked..... No power, no noise, no vibrate. All that I can see for any sort of response from the tablet is seeing Quallcomms 9008 mode in the Windows device manager, or Qualcomm, Inc. Gobi Wireless Modem (QDL mode) in Linux. Holding the power button for 15 secs will make the port reset but it doesn't change in any other way. the CPU is running as it stays warm until I disconnect the battery.
I have spent over 2 months trying to resolve this issue, using both Windows 7 & 10, as well as Linux, and so far no luck. I've downloaded MANY gigs of files. With Qfil and other similar tools, its constant sahara errors or firehose errors, despite having what appears to be the proper files for the firehose. The LG Flash tool tries to read it but then says the device is "differente", giving an F0000002 error, so I'd presume the wrong firmware flashed caused a change to the version number somewhere... So now the proper version won't flash with that tool...
On Linux, the only halfway encouraging responses I get is using a tool called EMMC_Recover. That tool on Linux has allowed me to send some partitions to the bricked device over USB, but certain partitions such as boot.bin, and a couple other needed partitions, EMMC_Recover responds back with a 256 error, which is an I/O error, so I would assume something is locked or not rooted proper any more on the bricked device after flashing the wrong firmware?
I have a good copy of a backup of one of the working tablets with stock ROM at 4.4.4, but have not been successful in getting the files all back onto the bricked device so it will boot.
I have also tried booting from an SD card, setting the card up a few diff ways as instructed online, but it made no difference. Button combinations combined with battery disconnects and reconnects while connecting the USB cable seem to make zero difference in its behavior. it's just plain dead other than the few things I could do with EMMC_Recover.
Other things I have tried included making up a 910k cable, which made no noticeable difference. Shorting the D+ to GND, no difference. Making sure the battery was fully charged on a working tablet, since it will not charged on a bricked tablet, but again no difference.
I realize that some devices have test points that need to be jumpered to flash them but where the device is already in 9008 mode I dont see the need, nor could I find any info what so ever about test points on the G Pad 8.3. The most I could find is a boot config setting in the service manual for this device, but the points are unclear in that manual and would take some time to trace out, if even possible short of removing the CPU/EMMC from the mother board.
I also read last night that while these devices can show as 9008 mode, that sometimes its not fully in that mode, but I cant confirm that myself. Does anyone know for sure?
JTAG sounds like its been an option for some bricked devices, but I dont have funds to risk on buying a box that may or may not work. The JTAG port pads are exposed on the edge of the board with no connector soldered on, but the chances of getting wires soldered onto that spot effectively and have the pads not tear away from the board are slim.
I'm also not sure what software would be used if I was to make my own JTAG device using something like a Pro-Micro ATMEL device. The JTAG hardware can be made, but I dont have the knowledge needed as to what to flash and where and how, and an extensive search really didn't answer those questions...
I'm not usually one to bother others with hardware or software issues, as I can usually work it out myself over enough time, but I seem to of run out of viable options after a couple hundred hrs of extensive reading and trial and error, so I am hoping someone here might have some other suggestions to try. Any help would be greatly appreciated.
Thanks to all for what you all do to help many people in need each and every day here!
So after making a few more attempts at various methods of de-bricking this tablet from Qualcomm 9008 mode, I've decided that I'm going to attempt to get 6 wires soldered onto the Jtag port, to see if i can program it with a stm32 "blue pill" that is flashed to be a Jtag programmer. Whether this works or not, and whether i can get the few wires soldered on the tiny pads or not, remains to be seen. I dont see any other viable way to fix this short of removing the cpu / ram stack, but I dont have a proper socket or programmer for that anyway.
I also dont have a hot air soldering tool, so putting a tiny socket on the Jtag pads is out of the question. Though I am game at some point to build such a tool. I was hoping to find attaching points away from those pads that are easier to solder to, but after probng with the meter only 1 is available at an alternate spot, the rest appear to go directly to the CPU.
AS far as the SD card boot method goes, clearly something does try to happen. I did set up a card with the full image and partitions from a working tablet, and edited the fstab and other files to reflect where the files were located, then repacked the boot and recovery loaders. I Then booted the patched boot image to a working tablet with the SD card in. It boot and ran either normal Android mode or TWRP recovery with no hesitation.
However, when I tried the same thing in the bricked tablet, it still didn't boot. It was clear that certain key combinations made a difference in how warm the processor runs, when the SD card was installed, but it ran cooler with the SD card out, so it does attempt to do something, but I have no idea what it is doing... So that method for now is a fail short of someone having another suggestion to try.
I have a question. Has anyone here on this forum succeeded or failed at Jtagging one of these tablets, or knows of anyone who has tried Jtagging one before? I really hate to put hrs into trying to get wires soldered on only to find that the Jtag port isn't enabled, or doesn't work proper unless some other step is taken, so any advice would be very welcome
Thanks again to all of you who took the time to read my initial post. I didn't expect to get so many views with such an old but very viable device, which I really would hate to throw away if it can be salvaged!! Thanks again for your time!!
I tried to write GSI properly and bricked it. I did a full backup with TWRP just in case, but it only starts in EDL mode. (Of course ADB does not respond).
The information I wanted was not available there, as it was done with a minor device called C330 (Rakuten mini) from Tinno mobile, which is sold only in Japan. What should I do?