how comparable is 2.3.1 and 2.3.3 and how similar would the cwm be? I ask because I have a cheap dopo md-702 tablet that I would like to try working with. It has 2.3.1 and I was wondering how to get cwm to work with the tablet. It has a rockchip rk2918 so any ideas on where to start digging?
jaycush said:
how comparable is 2.3.1 and 2.3.3 and how similar would the cwm be? I ask because I have a cheap dopo md-702 tablet that I would like to try working with. It has 2.3.1 and I was wondering how to get cwm to work with the tablet. It has a rockchip rk2918 so any ideas on where to start digging?
Click to expand...
Click to collapse
Most cheap tablets cannot have cwm due to the lack of recovery menu. Cheap tablets are already rooted. Just install superuser and do whatever you want with. But once again. Due to lack of recovery you have to be careful with what you do.
XjokiX7 said:
Most cheap tablets cannot have cwm due to the lack of recovery menu. Cheap tablets are already rooted. Just install superuser and do whatever you want with. But once again. Due to lack of recovery you have to be careful with what you do.
Click to expand...
Click to collapse
In a very interesting sort of way the tablet has a recovery mode but it takes multiple steps to get to it. The long and short I used quick boot app to boot to recovery (which looked similar to a download mode) and then had to try different key presses to get into the actual recovery mode. I can run an update.zip from the menu but nothing else. It looks so similar to what the modded cwm is for our phones that I wonder if there was a way to look at the codes and compare. Also note worthy after I used Titanium Backup to unistall the phone (bad idea) I had to hit the reset button to see if I could start it back up, and it booted back to just the basic apps but still had the google play app (this tablet did not come with google play originally). There are just so many little nuances that I'm not sure what is going on with this tablet. I need to have some time to connect it to my PC so I can see if there is a way to look at the tablet through the computer similar to what I used to do with my windows phone.
There is also an upgraded model of the tablet that has 4.0, with a 1.2Ghz instead of 1Ghz processor. Is the OS (android 4.0) a part of the firmware? If I have the firmware from the newer model what are the chances it would work with the older model?
I want to copy this post over to the tablet thread and hopefully get some hits over there.
jaycush said:
In a very interesting sort of way the tablet has a recovery mode but it takes multiple steps to get to it. The long and short I used quick boot app to boot to recovery (which looked similar to a download mode) and then had to try different key presses to get into the actual recovery mode. I can run an update.zip from the menu but nothing else. It looks so similar to what the modded cwm is for our phones that I wonder if there was a way to look at the codes and compare. Also note worthy after I used Titanium Backup to unistall the phone (bad idea) I had to hit the reset button to see if I could start it back up, and it booted back to just the basic apps but still had the google play app (this tablet did not come with google play originally). There are just so many little nuances that I'm not sure what is going on with this tablet. I need to have some time to connect it to my PC so I can see if there is a way to look at the tablet through the computer similar to what I used to do with my windows phone.
There is also an upgraded model of the tablet that has 4.0, with a 1.2Ghz instead of 1Ghz processor. Is the OS (android 4.0) a part of the firmware? If I have the firmware from the newer model what are the chances it would work with the older model?
I want to copy this post over to the tablet thread and hopefully get some hits over there.
Click to expand...
Click to collapse
As long as you have a way to get to recovery from boot up you shouldn't have much of a problem. And Android and Windows work differently on many things. But android is more open. *you can do whatever with it* and if I'm not mistaken you can upgrade your firmware to 4.0 through recovery. Some tablets you can upgrade by downloading the firmware on the tablet's site.. Try that if it doesn't have the option to do a system update in the settings.
Right now I'm bricked, used the firmware from the upgraded model but worried that because there a gig of additional memory, but the rest of the hardware specs are identical, so right will not boot. Fuzzy lines, going to try and drain battery then charge and boot into recovery.
Let me clarify, I used the firmware from the manufacturer for the upgraded model. So I thought out would work. I've not given up but not optimistic. If I'm lucky someone can pull the original firmware and I can miraculously get it into download mode again for a reflash, that is if I can't get a factory reset.
UPDATE: I can power on to the first animation, the infamous penguin. Going to see if either computer will notice it tomorrow. If neither will, I'm not sure I can do any thing more.
UPDATE: it will connect but windows doesn't recognize it. I'm thinking I have options but will take time.
Sent through the stargate
I had a somewhat small problem with this tablet - the virtual keyboard was not as fast as i'd exected to be. So I wanted to reinstall the OS by reflashing the rom/tool provided at http://www.needrom.com/download/chuwi-vi8/ .
It went well, the OS installed but at the end, that tool updated the uefi firmware too. I expected that, i kinda knew what I was doing. At about 80% of uefi flashing, the device went blackscreen and today it's still like that, Maybe battery was too low or it was simply the wrong Bios-uefi This is the first device I permanently broke.... It cannot be connected to a PC simply because it's a PC by its own... Or is it? There is no info on flashing dead win8.1 tablets on google.... Please help me out!
Sam.1211 said:
I had a somewhat small problem with this tablet - the virtual keyboard was not as fast as i'd exected to be. So I wanted to reinstall the OS by reflashing the rom/tool provided at http://www.needrom.com/download/chuwi-vi8/ .
It went well, the OS installed but at the end, that tool updated the uefi firmware too. I expected that, i kinda knew what I was doing. At about 80% of uefi flashing, the device went blackscreen and today it's still like that, Maybe battery was too low or it was simply the wrong Bios-uefi This is the first device I permanently broke.... It cannot be connected to a PC simply because it's a PC by its own... Or is it? There is no info on flashing dead win8.1 tablets on google.... Please help me out!
Click to expand...
Click to collapse
Because there is not a specific forum for your device, this thread will be moved to Windows 8 General
reply
did you find solution ?? I have the same issue.
thanks to share if there is any way to repair it
So im thinking of purchasing one of these when the come out here and i was wondering about an android to windows os hack. Will there be one in the immediate future and will dual booting be an option?
The hardware is exactly the same.
There must be a way to dual boot, hopefully others on this forum can figure out how to do this if Lenovo doesn't facilitate dual boot themselves
Best
I believe there's a different BIOS for Win vs Android. Could have sworn I saw the Windows BIOS posted on the Lenovo support site prior to the Oct 17 launch. It seems gone now though, unless I'm missing something or went to the wrong link? Unlikely you can install Win without a different BIOS.
There is some clear hardware differences with the Android and Windows tablets. Specifically, 2 different physical layouts for the halo keyboard, where the windows one has defined left and right mouse click buttons. There doesn't seem to be any way of accessing the BIOS on the Android tablet, and it does have the usual Android power + volume up, power + volume down recovery options, so it looks like it boot directly to the boot loader.
The Bios is still there ... but how would you flash it?
http://support.lenovo.com/de/de/products/Tablets/Yoga-Series/YOGA-Book/downloads/DS119182
ok so there is also android open source code available in their site, any chance of making a custom rom?
I wonder if we could flash the Chuwi 12 roms onto this given that Chuwi12 has dual boot already?
This is reallly really stupid to me, why not provide dual boot in the first place? I would not mind shelling out $100 more for a dual boot version. Now if I want the windows version I will need to spend another $550 to get another OS with the same device. I will end up having 2 same devices, but that is so anti-mobile really. Do I have to carry 2 hardware devices so i can have 2 OSes at the same time?
Lenovo get some grip please and provide a dual OS version.
win 10 driver
Today, the windos 10 drivers are online..
The drivers you get with levono support with input of the serial number
It must now be possible to build a dual system
Tastertur chipset audio and more .
igelelf said:
Today, the windos 10 drivers are online..
The drivers you get with levono support with input of the serial number
It must now be possible to build a dual system
Tastertur chipset audio and more .
Click to expand...
Click to collapse
Could you post the link for the windows 10 drivers? also any idea on how to unlock the bootloader?
Hi,
earthCallingAngela did unlock the bootlader. .
My background knowledge about booting is very low. But I think there are huge differences between Android and Windows. I think If a system can boot via PC-Bios or Android-Boot-Loader is "on the chip". If this is correct you would need a Android-Boot-Loader that does boot into a windows ... IMO this is no "easy to do". May be the guys who did create Remix OS found a way to do that ...?
Can we use Chuwi 12's disk image somehow? It comes with dual boot.
hajkan said:
Can we use Chuwi 12's disk image somehow? It comes with dual boot.
Click to expand...
Click to collapse
Are the two the same hardware? My understanding is that unless the hardware is very similar, you can't use other ROMs without a *TON* of work.
so i was able to install android x86 6.0 on my yoga book, unfortunately i managed to do it over my windows install so now i just need to reinstall windows lol.....
---------- Post added at 06:35 PM ---------- Previous post was at 05:54 PM ----------
decided to install 7.0 over my 6.0 install i just made and messed everything up. now im back to just trying to get gparted to run so i can reformat and start over.
bisharat said:
Could you post the link for the windows 10 drivers? also any idea on how to unlock the bootloader?
Click to expand...
Click to collapse
http://support.lenovo.com/kr/en/pro... and Software|Drivers and Software&beta=false
you can download yogabook win10(64bit) driver here.
edited--
you should change operating system dropdown menu from android to windows10
Hi & Happy New Year
Now it's possible to get root with android version
I have a YogaBook with Windows version ; Someone can make a backup Android version?
Maybe it's possible to create a dual boot with the windows version I cross the fingers :fingers-crossed:
Where and how?
ThomasHardy said:
Hi & Happy New Year
Now it's possible to get root with android version
Click to expand...
Click to collapse
someone can said me, where i found an android image? (original yoga book, of course) i try to install Remix OS and Android-x86 6.0-r1 released from Android-x86.org but, its can't run. graphics issues and reboot.
i install in a MicroSD and boot it booting yogabook hold volume up + power boton and select boot menu, but it fail on boot.
i have yoga book windows. any idea?
thanks
sorry for my english..
I'm exploring this as well.
Since the BIOS and drivers available (just tested with my serial#), it does seem like it would be relatively easy to dual-boot, provided you can get past the loader issue.
I've done many dual-boot setups, just not since the Win7 days, with the Win8 and forward it's gotten quite a bit trickier, the loader does a bunch of "extra" stuff, boot timing and such, to protect itself.
I've also never done an Android/Windows dual-boot, mostly just Win/Win or Win/Unix.
I think you'd have to figure out how to bootstrap these, so the custom loader can take over, and load from there, but this is a bit beyond my Android capabilities.
Has anyone even tried this? I assume the power/volume keys must work, to get at the loader?
Hi there !
I've just unlocked my Yoga Book's android bootloader and made a backup. I'm trying to install Windows 10 and replace Android with it. The problem is that I don't know how to boot the device from the USB drive.
Does anyone know how to do that ? Even if rooting is required ?
P.S. : I can't google it as all results link to "how to boot a PC from android device", which is the reverse...
Totjoss said:
Hi there !
I've just unlocked my Yoga Book's android bootloader and made a backup. I'm trying to install Windows 10 and replace Android with it. The problem is that I don't know how to boot the device from the USB drive.
Does anyone know how to do that ? Even if rooting is required ?
P.S. : I can't google it as all results link to "how to boot a PC from android device", which is the reverse...
Click to expand...
Click to collapse
simple...you can't do that! it's not possible to boot usb from android bootloader or recovery.
What would be the PC equivalent of Custom Recovery software like TWRP?
Would it be something like Acronis TrueImage ?
Also, would it make sense to say that a locked bootloader in a phone (PS: Notice I won't say 'Android Device', because the bootloader comes into play BEFORE the Android OS) is the equivalent of having 'secure boot' enabled in UEFI in a Windows PC? Thereby implying that the process of disabling Secure Boot in UEFI in a PC is the same as unlocking the bootloader in phones?
BIG_BADASS said:
What would be the PC equivalent of Custom Recovery software like TWRP?
Would it be something like Acronis TrueImage ?
Also, would it make sense to say that a locked bootloader in a phone (PS: Notice I won't say 'Android Device', because the bootloader comes into play BEFORE the Android OS) is the equivalent of having 'secure boot' enabled in UEFI in a Windows PC? Thereby implying that the process of disabling Secure Boot in UEFI in a PC is the same as unlocking the bootloader in phones?
Click to expand...
Click to collapse
I really don't think you get how phones work bro. Unlocking a bootloader can only be done by manufacturing or through more aggressive means when possible. The H812 still hasn't had its bootloader unlocked by lg and at this point probably never will
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
I really don't think you get how phones work bro. Unlocking a bootloader can only be done by manufacturing or through more aggressive means when possible. The H812 still hasn't had its bootloader unlocked by lg and at this point probably never will
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
That doesn't answer my question. I asked the theoretical side, not practical.
Before you do anything, you must understand the FULL boot sequence and structure of Smartphone with ARM chipset, and compare it to Intel x86 Chipset..... and know the relationships well... THEN only you can safely say "I know this" ... THEN only you can safely play around and tinker with the smart phones.....
I thought I knew alot.. but turns out I know NOTHING.... so I go back to square 1 and learn EVERYTHING from scratch again.....
Before I do anything, I must familiarize WHAT is TWRP.. You can say "TWRP is custom recovery", okay, 'WHAT IS CUSTOM RECOVERY' ? You must be able to clearly explain what it is, what parts of the boot sequence it affects.... what is the equivalent in an Intel x86 PC of TWRP or custom recovery????
WHat is a ROM? We all know ROM in smartphone world is more than just the operating system... So what other components does it replace besides the operating system???
We have to think like this and analyze EVERYTHING, all the relationships between all the entities.....
I am now learning about EMBEDDED LINUX ... and the boot sequence of it... as smartphone is just another version of embedded linux......
This is what I'm doing now... when I am familiar with EVERYTHING.... then I will tinker....
BIG_BADASS said:
That doesn't answer my question. I asked the theoretical side, not practical.
Click to expand...
Click to collapse
Secure boot on windows acts as a UEFI (modernized motherboard BIOS meant to work better and faster with x64 and newer systems)
Locker to prevent UEFI from booting into unsigned/unrecognized system images (as far as I know, anybody feel free to correct me)
Bootloaders on smartphones would be the equivalent of a UEFI for the arm architecture. Meant to guide the system into booting from a specified mount. Bootloaders are coded by the manufacturer, either locked or unlocked. Unlocked bootloaders provide a way for users to enter recovery mode and potentially flash unsigned/custom images. If the manufacturer decides to lock the bootloader, the only options are wait for a way to unlock from manufacturer or find a way to crack it if you have the know how
Some manufacturers use the same bootloader for all or most variants of one phone, or can use a different bootloader for each variety of a phone, choosing which bootloaders to unlock or leave locked
For example with the Lg G4, the international variant H815 I believe is unlocked, while the H812 is still to this day locked, while unfortunately their has not been enough interest in trying to reverse engineer or find a loophole if even possible
SpyderAByte said:
Secure boot on windows acts as a UEFI (modernized motherboard BIOS meant to work better and faster with x64 and newer systems)
Locker to prevent UEFI from booting into unsigned/unrecognized system images (as far as I know, anybody feel free to correct me)
Bootloaders on smartphones would be the equivalent of a UEFI for the arm architecture. Meant to guide the system into booting from a specified mount. Bootloaders are coded by the manufacturer, either locked or unlocked. Unlocked bootloaders provide a way for users to enter recovery mode and potentially flash unsigned/custom images. If the manufacturer decides to lock the bootloader, the only options are wait for a way to unlock from manufacturer or find a way to crack it if you have the know how
Some manufacturers use the same bootloader for all or most variants of one phone, or can use a different bootloader for each variety of a phone, choosing which bootloaders to unlock or leave locked
For example with the Lg G4, the international variant H815 I believe is unlocked, while the H812 is still to this day locked, while unfortunately their has not been enough interest in trying to reverse engineer or find a loophole if even possible
Click to expand...
Click to collapse
Thank you bro... now we're getting somewhere....
So PCs also have a bootloader.... but the way I understand, "Bootloader" in the smartphone is a combination of BIOS and MBR in the pc world, right? It is all combined into one entity called "Bootloader"...
Also, the MBR usually has a Stage 1 bootloader, which points to a stage 2 bootloader, which is installed somewhere in the permanent memory (hard disk in PC).... but this structure is not the same in smartphone I believe?
The arm architecture is completely different than the x86 or x64 architectures.
As Asus and MSI and acer etc have their own bios,
Samsung, lg, HTC Huawei Google etc have their own bootloaders. Twrp for example is a custom open source bootloader that anybody can get the source and add to. Phone companies do not give out the source code for their bootloaders usually and it is in their own power to lock and unlock them
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
Maybe just get an unlocked international variant of your next phone and let the big boys do the work for you
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
Yes, that would be the easy way around...
I have the H815 now which I got in exchange for H812... anyways.... if I didn't have it the hard way, I wouldn't learn anything..... If I had the unlockable H815 from day 1, I wouldn't be this curious... therefore I wouldn't learn.. I'd just be living in ignorance thinking I know everything there is to know .....
Why don't you start by finding the twrp out for the h815 and tinkering with it, making it your own. Try finding a stock ROM and tinkering with that building your own. Plenty of guides around the internet. Learn java and take flight bud
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
The arm architecture is completely different than the x86 or x64 architectures.
As Asus and MSI and acer etc have their own bios,
Samsung, lg, HTC Huawei Google etc have their own bootloaders. Twrp for example is a custom open source bootloader that anybody can get the source and add to. Phone companies do not give out the source code for their bootloaders usually and it is in their own power to lock and unlock them
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
SpyderAByte said:
The arm architecture is completely different than the x86 or x64 architectures.
As Asus and MSI and acer etc have their own bios,
Samsung, lg, HTC Huawei Google etc have their own bootloaders. Twrp for example is a custom open source bootloader that anybody can get the source and add to. Phone companies do not give out the source code for their bootloaders usually and it is in their own power to lock and unlock them
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
Yes, in the x86 world they do have different motherboard architectures, hence different BIOS's ... but the rest of the boot sequence follows the same order......
So that brings me to my next question... why is it that we can hard brick a phone, but not a PC? I mean.. technically it is possible to brick a PC if you screw up a bios flash.... but that just leads me to believe a "ROM" in smartphone world actually consists of BIOS + OS ...
So that leads me to wonder.. what else has combined functionality? What is the BIOS equivalent in Android? I mean.. technically it is possible to brick a PC if you screw up a bios flash.... but that just leads me to believe a "ROM" in smartphone world actually consists of BIOS + OS ...
So that leads me to wonder.. what else has combined functionality? What is the BIOS equivalent in Android?
The bootloader partition/iso and the data/android partition/ROM are 2 different things
You can independently swap your recovery if it's unlocked and keep your data. Or you can independently change ROMs and keep your bootloader. You don't seem to understand this pretty basic concept
You can brick a phone flashing the bootloader incorrectly or by flashing the ROM incorrectly
Likewise on a PC if you flash the bios/UEFI incorrectly you can brick your motherboard, and corrupting your OS installation can cause issues
The reason you've bricked phones more than you've bricked computers - when was the last time you tried flashing a custom bios or UEFI? Or a version of Linux/windows that your bios won't allow
Computers are usually pretty plug and play so you can swap HDDs/ram/processors and simply upgrade needed drivers to works
Smartphones are greasy and closed source and the manufacturer usually wants it their way, that's why you see them blocking root access and custom roms
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
The bootloader partition/iso and the data/android partition/ROM are 2 different things
You can independently swap your recovery if it's unlocked and keep your data. Or you can independently change ROMs and keep your bootloader. You don't seem to understand this pretty basic concept
You can brick a phone flashing the bootloader incorrectly or by flashing the ROM incorrectly
Likewise on a PC if you flash the bios/UEFI incorrectly you can brick your motherboard, and corrupting your OS installation can cause issues
The reason you've bricked phones more than you've bricked computers - when was the last time you tried flashing a custom bios or UEFI? Or a version of Linux/windows that your bios won't allow
Computers are usually pretty plug and play so you can swap HDDs/ram/processors and simply upgrade needed drivers to works
Smartphones are greasy and closed source and the manufacturer usually wants it their way, that's why you see them blocking root access and custom roms
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
So basically, the ROM is more than just the operating system, no? Flashing a rom in smartphone is NOT exactly the same as installing Ubuntu or Debian in a PC, right? There's something else you're replacing, am I right?
Also.. the way I understand... Bootloader is the very first software that runs once you power on the smartphone? (equivalent of BIOS) ?
BIG_BADASS said:
So basically, the ROM is more than just the operating system, no?
Click to expand...
Click to collapse
The ROM is the operating system, the included apps and packages and any other information that android needs to run after the bootloader
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
The ROM is the operating system, the included apps and packages and any other information that android needs to run after the bootloader
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
So when you flash a rom, you're not replacing the original bootloader? Or BIOS?
No as I stated in my previous post. You can use your bootloader or a PC through fastboot to flash ROMs as long as your bootloader is unlocked
On a galaxy for instance you could first install twrp if possible leaving your stock touchWiz ROM perfectly intact but now you have twrp
Then later you can use twrp to install paranoid Android or CM for instance, replacing your stock touchWiz ROM, but leaving your newly installed twrp untouched
I used to have a galaxy s4 Canadian variant, and the bootloader was locked and still is to this day. The only way to flash a custom ROM was to bypass the stock bootloader using a method found by someone experienced with Samsung bootloaders (a rogue Samsung employee iirc)
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
Bootloaders on smartphones would be the equivalent of a UEFI for the arm architecture. Meant to guide the system into booting from a specified mount. Bootloaders are coded by the manufacturer, either locked or unlocked. Unlocked bootloaders provide a way for users to enter recovery mode and potentially flash unsigned/custom images. If the manufacturer decides to lock the bootloader, the only options are wait for a way to unlock from manufacturer or find a way to crack it if you have the know how
Click to expand...
Click to collapse
The final outcome is the same, yes, but bootloader and BIOS/UEFI are completely separate, right? X86 PCs have a bootloader called NTLDR and it comes into play after the BIOS has finished POST and given control to the MBR....
BIOS > MBR (contains stage 1 bootloader) > Stage 1 bootloader points to Stage 2 bootloader in the HDD
Or is the functionality of bootloader and bios combined into one unit in the smartphone?
---------- Post added at 07:09 AM ---------- Previous post was at 07:05 AM ----------
SpyderAByte said:
No as I stated in my previous post. You can use your bootloader or a PC through fastboot to flash ROMs as long as your bootloader is unlocked
On a galaxy for instance you could first install twrp if possible leaving your stock touchWiz ROM perfectly intact but now you have twrp
Then later you can use twrp to install paranoid Android or CM for instance, replacing your stock touchWiz ROM, but leaving your newly installed twrp untouched
I used to have a galaxy s4 Canadian variant, and the bootloader was locked and still is to this day. The only way to flash a custom ROM was to bypass the stock bootloader using a method found by someone experienced with Samsung bootloaders (a rogue Samsung employee iirc)
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
So TWRP comes into play before the operating system is loaded, correct? Meaning if you flash a corrupt operating system, you can still format the drive, because TWRP is on a lower layer?
So you can think of TWRP as those Windows Recovery disks?
Do you understand how partitions work? (Not attacking, honest question)
Your bootloader would sit on one partition of the phone emmc(like a small solid state drive/kind of like an sd card chip)
So your partition table would look kind of like this
Emmc1 - /boot (bootloader tells android to boot into recovery, download, fastboot, or android rom
Emmc2 - /recovery (recovery partition. User interface of twrp for example)
Emmc3 - /download mode (used to flash zips)
Emmc4 - /data (android rom that you install
Emmc5 - / (the root folder of your phone, where your storage starts
If you remember getting a 16gb iPhone or iPod and wondering why you only got 9-11gb when you have 100% free space, it's because the emmc is rated for 16gb but the data/ROM uses 5-7gb
Sent from my LG-H812 using Tapatalk
SpyderAByte said:
Do you understand how partitions work? (Not attacking, honest question)
Your bootloader would sit on one partition of the phone emmc(like a small solid state drive/kind of like an sd card chip)
So your partition table would look kind of like this
Emmc1 - /boot (bootloader tells android to boot into recovery, download, fastboot, or android rom
Emmc2 - /recovery (recovery partition. User interface of twrp for example)
Emmc3 - /download mode (used to flash zips)
Emmc4 - /data (android rom that you install
Emmc5 - / (the root folder of your phone, where your storage starts
If you remember getting a 16gb iPhone or iPod and wondering why you only got 9-11gb when you have 100% free space, it's because the emmc is rated for 16gb but the data/ROM uses 5-7gb
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
Sorry man, I'm from the PC world.. this makes no sense to me.... please relate all the functionality to it's PC equivalent...
Also, what is the boot sequence of the smartphone? Does it have a BIOS? MBR? Hard Drive? RAM?
If smartphone doesn't have all these parts, then what part of the phone does the job of the BIOS, MBR, Hard drive, RAM, bootloader, etc?
---------- Post added at 07:27 AM ---------- Previous post was at 07:20 AM ----------
Maybe my approach here is wrong, maybe I shouldn't try to relate everything 1 to 1 ?
---------- Post added at 07:48 AM ---------- Previous post was at 07:27 AM ----------
SpyderAByte said:
Do you understand how partitions work? (Not attacking, honest question)
Your bootloader would sit on one partition of the phone emmc(like a small solid state drive/kind of like an sd card chip)
So your partition table would look kind of like this
Emmc1 - /boot (bootloader tells android to boot into recovery, download, fastboot, or android rom
Emmc2 - /recovery (recovery partition. User interface of twrp for example)
Emmc3 - /download mode (used to flash zips)
Emmc4 - /data (android rom that you install
Emmc5 - / (the root folder of your phone, where your storage starts
If you remember getting a 16gb iPhone or iPod and wondering why you only got 9-11gb when you have 100% free space, it's because the emmc is rated for 16gb but the data/ROM uses 5-7gb
Sent from my LG-H812 using Tapatalk
Click to expand...
Click to collapse
Also, lets say you format the entire memory of the phone, and reinstall Android.... will it automatically create all these partitions?
Holy **** man you say you know computers but it's almost the same as Linux. Android uses Linux at its absolute core so alot of it is pretty close. Look up a healthy Linux partiton setup and compare to my half assed partition table above and you'll see it's almost identical.
A HDD, SSD, or a memory block (phone internals, usb drives, sd cards) all can have seperate "partitions" which are basically seperate simulated drives, and all have a master boot record telling the device where to start.
There is a boot partition on the memory block which holds the core bootloader files and tells the phone what to do first.
If you hold down the recovery button it will tell the phone to boot to the recovery partition. If you hold down the download buttons it will tell the phone to boot into the download partition. If you allow the phone to boot regularly it will tell the phone to boot to the android /system partition which is where the android operating system is held
I can't explain how this works compared to windows because windows does its own thing in regarding to booting and it is not in my spectrum
The paranoidAndroid.iso file system you would try to flash for example would hold the
/system(android os)
/Data (user data and apps)
/ Or /root (main read/write accessable storage for user)
/Root would require root access to be able to get into and from there you can access the /system and /data mountpoints to modify system files, without root access you are usually not even able to view these folders
SpyderAByte said:
Holy **** man you say you know computers but it's almost the same as Linux. Android uses Linux at its absolute core so alot of it is pretty close. Look up a healthy Linux partiton setup and compare to my half assed partition table above and you'll see it's almost identical.
A HDD, SSD, or a memory block (phone internals, usb drives, sd cards) all can have seperate "partitions" which are basically seperate simulated drives, and all have a master boot record telling the device where to start.
There is a boot partition on the memory block which holds the core bootloader files and tells the phone what to do first.
If you hold down the recovery button it will tell the phone to boot to the recovery partition. If you hold down the download buttons it will tell the phone to boot into the download partition. If you allow the phone to boot regularly it will tell the phone to boot to the android /system partition which is where the android operating system is held
I can't explain how this works compared to windows because windows does its own thing in regarding to booting and it is not in my spectrum
The paranoidAndroid.iso file system you would try to flash for example would hold the
/system(android os)
/Data (user data and apps)
/ Or /root (main read/write accessable storage for user)
/Root would require root access to be able to get into and from there you can access the /system and /data mountpoints to modify system files, without root access you are usually not even able to view these folders
Click to expand...
Click to collapse
Yes I know Linux... but there is a HUGE difference between Embedded Linux and GNU/Linux you run on PC.....
If you were to completely wipe the phones internal memory, formatting each seperate partition into one blank one. You would need to find a way to recreate the partition table, install the bootloader onto its proper partition
Then you would use the bootloader to either recreate the partitions for the android rom, OR the ROM could self unpack and create it's needed /system, /data, and /root partitions
Hello,
I'm new here and I registered because now after searching, reading and trying different things I'm a bit confused
And: Most information is quite old...
I was donated a LG device that gives me these informations about itself:
Modellnummer: LG-K350n
Android-Version: 6.0
Android Sicherheitspatch-Level: 2018-04-01
Kernel-Version: 3.18.19
Build-Nummer: MRA58K
Software-Version: V10k-EUR-XX
My initial idea was to have postmarketOS on it and use it as kind of a small tablet - e.g. to read/write eMails, take pictures, have video-conversations via tox, use it as a music-player and maybe use it as a GPS-device (offline, just via GPS). Connections should only be made via WiFi. No SIM should be required - to make calls and SMS I have a separate feature phone, so I don't need the telephony-module.
After a while I befriended myself with lineageOS or even replicant. In such a case maybe I would even use it as cellphone and keep my feature-phone just as a back-up.
My main aspect is to have a device I control - not someone else (e.g. google).
I know that it would be easier just to use stock android and maybe fiddle a bit around, but I don't trust android/google/...
I don't need google-applications, facebook/What's-App, some cloud-based-stuff... - never did and never will. (I prefer to stay away from things that require these - if something has it mandatory then I will not use it.)
What I did until today: Following gottlasz' guide Friendly root method for lg k8 and k10 but got stuck without a version of TWRP that fits on my firmware. I found one that clamied to be OK for my firmware (https://www.cyanogenmods.org/downloads/twrp-recovery-for-lg-k8/). Booted into it, then I installed rce_univ.zip, supersu and rce_univ.zip again. But then the phone was in a bootloop saying that it was corrupted before it tried to boot itself again. With the help of a friend I restored the stock-ROM with LG Bridge (he has Windows10 on his laptop) - that took about 10 hours because here we don't have fast internet-connections...
I'm willing to put effort in this project and try to build/compile all kinds of things myself. But I need help in the way someone could guide me with what are the steps to be taken next. My PC (amd64) is running linux (gentoo to be precisely) and in a VirtualBox I have a copy of Window$ XP SP3 (32-bit).
After this toying around I found it hard to get up-to-date informations on what is possible today. And I don't want get stuck again like I was (and of course I don't want to brick it completely ).
So, please help me on my way to free my phone, I'd be glad to offer further information if needed.
Thanks a lot!
Quick answer, forget about it not going to happen.
I have k350nds with same hardware but it's dual sim and long time ago I was trying to build rom from lineage sources since there is mt6735 device tree for ex cyanogenOS and I didn't succeed because lack of knowledge and computing power, however even if I did succeeded I won't be able to flash it because nothing can be flashed, not even twrp it can be only booted from fastboot, because of some 'security' measures, it may be reverse engineered and some with knowledge can make a rom but it won't happen since device isn't so populated etc. And therefore you can only use this phone as is, I think at this point it cannot even be rooted. I received update of 11mb which didn't update patch level or anything else that I notice.
Professor Woland said:
Quick answer, forget about it not going to happen.
(...)
Click to expand...
Click to collapse
Hello Professor Woland,
thats' a pity! But thanks for your answer anyway!