Hi, so I was testing out new ROMs for fun and found lineage is 14 (from the other XDA post) and liked it. I then decided to try and duel boot two ROMs. The article said to format my SD card. I then proceeded to forgetting I had my backup on there. I now have lineage os on here which would be fine except the camera and Bluetooth don't work and I really need them. So of anyone has a backup of there's I can use, know where I can get the stock ROM or anything please help
Related
Hey guys, first post here so let me know if I'm doing anything wrong!
I was feeling ambitious today, so I went ahead and installed the Supernexus 4.0 rom on my i9305t. Install worked fine, and all was well and good until I noticed my SIM card wasn't being read.
I did the classics - rebooting, reseating the card etc.. with no success. Reinstall didn't work either, nor did an alternate version of the rom (check the linkdump).
Any ideas? I'm pretty excited about the rom, so I'd rather not have to flash stock!
links:
http://forum.xda-developers.com/showthread.php?t=2585847
http://forum.xda-developers.com/showthread.php?t=2524516<br /><br />[ROM][GT-I9305][KitKat][4.4.2]%20CyanogenMod%2011.0%20Official
Every time I trie to update to the latest ROMs I notice they specifically target the new bootloader. I have no idea what the old vs new bootloader dilemma is about but I bet my device runs the old one, I read somewhere the white LG logo on startup hints to an old bootloader,
My question is how to upgrade my bootloader or ROM directly to Kitkat the easiest way possible, I bought my handset already CMed and unrooted but I have never done it myself.
Thank you in advance, and if you could bother throw in some links to relevant threadshttp://forum.xda-developers.com/images/icons/icon8.gif
xdaCyborg said:
Every time I trie to update to the latest ROMs I notice they specifically target the new bootloader. I have no idea what the old vs new bootloader dilemma is about but I bet my device runs the old one, I read somewhere the white LG logo on startup hints to an old bootloader,
My question is how to upgrade my bootloader or ROM directly to Kitkat the easiest way possible, I bought my handset already CMed and unrooted but I have never done it myself.
Thank you in advance, and if you could bother throw in some links to relevant threadshttp://forum.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
for tonyps kitkat , the only one for daily usage workign at the moment. you need his version of twrp 2.6 or as i know the cwm version 6.0.4.7, which can be found somewhere in the development forum.
tonyps cm11 : tonyps Cm11
kowalski kernel: kowalski kernel by pengus
dl links: cm11 by tonyp and bs86
working twrp by tonyp
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
xdaCyborg said:
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
Click to expand...
Click to collapse
With that you can backup/resotre and change the bootloader and alot more AiO-Toolkit
If you change the bootloader layout, as i know all stuf will be removed. so make a nandroid backup, if your new rom is not working and make a sdcard backup(also in aio) to get appdata back if you want.
If you dont want to download all apps new after having new rom use titanium backup. the recovery is not breakable. it will always work. not important if you **** your rom
xdaCyborg said:
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
Click to expand...
Click to collapse
As you do have CM 7.1 installed, I guess you've got a custom recovery installed too? I don't think you can directly use ROM manager to install a kernel, but you can use ROM manager to boot into recovery mode and flash the zip from there Just be sure to make a nandroid backup, just in case KK isn't compatible with 7.1.
If you ever want to get tonyp's CM 11 though, the AIO toolkit, as @Zubeplanet pointed out, is really easy to use to get the new bootloader.
Happy flashing!
So I've gotten myself into a bit of a jam. I was on CM12.1 build 0411. I wanted to migrate to the latest 0425 build with f2fs support to see if some lag issues are gone, with Tangerine Kernel 1.3. I booted into Philz Touch (from XZDualRecovery), followed the instructions in the ROM Thread. I went to install the ROM but now it says it cannot mount /sdcard along with some other errors (I'll get pictures if needed).
So is my option only to go back to Stock ROM using FlashTool and .ftf?
Plus, I can't use adb sideload as it doesn't recognize the device in recovery.
BrokeDude12345 said:
So I've gotten myself into a bit of a jam. I was on CM12.1 build 0411. I wanted to migrate to the latest 0425 build with f2fs support to see if some lag issues are gone, with Tangerine Kernel 1.3. I booted into Philz Touch (from XZDualRecovery), followed the instructions in the ROM Thread. I went to install the ROM but now it says it cannot mount /sdcard along with some other errors (I'll get pictures if needed).
So is my option only to go back to Stock ROM using FlashTool and .ftf?
Plus, I can't use adb sideload as it doesn't recognize the device in recovery.
Click to expand...
Click to collapse
Hello my friend, I think you are not allone. I was on CM11 Rom (LBL) for over year - two month ago I flashed CM12 for the first time. Now the troubles begin:
Because CM12 especially 5.0 over all is still a problem (wifi, calls etc.) even for their own Nexus series.
Anyway, I had a perfect backup of CM11 and I had perfect backup of the currently running CM12 Rom.
Because I need a stable running Rom for my bisiness, I switched always again back to my CM11 Rom.
But some day last week I flashed back to CM11 and was in a full bootloop. No chance to go back to Recovery or anything else.
Reason: I don´t know why, but there is something in the scripts of Kitkat or Lollipop, that damages SD cards, when you often switsch between the two systems. The sd card was dead, only readable, but not writeable again!!!
So ith the latest backup I made in the sd card, not all data have been written on it (not a complete backup) and when i tried to restore the system, with CWM, onla parts of the recovery have been readable. Hehe, bootloop. **** happens
My tip: Save your time with experiments - install your phone from beginning with .ftf file. I did it too
Greets, reinipic
reinipic said:
Hello my friend, I think you are not allone. I was on CM11 Rom (LBL) for over year - two month ago I flashed CM12 for the first time. Now the troubles begin:
Because CM12 especially 5.0 over all is still a problem (wifi, calls etc.) even for their own Nexus series.
Anyway, I had a perfect backup of CM11 and I had perfect backup of the currently running CM12 Rom.
Because I need a stable running Rom for my bisiness, I switched always again back to my CM11 Rom.
But some day last week I flashed back to CM11 and was in a full bootloop. No chance to go back to Recovery or anything else.
Reason: I don´t know why, but there is something in the scripts of Kitkat or Lollipop, that damages SD cards, when you often switsch between the two systems. The sd card was dead, only readable, but not writeable again!!!
So ith the latest backup I made in the sd card, not all data have been written on it (not a complete backup) and when i tried to restore the system, with CWM, onla parts of the recovery have been readable. Hehe, bootloop. **** happens
My tip: Save your time with experiments - install your phone from beginning with .ftf file. I did it too
Greets, reinipic
Click to expand...
Click to collapse
Alright! And it's interesting you mention that SD Cards dying because of this. My 64GB SDXC Class10 microSD mysteriously died on me with the same symptoms. I was switching between LiquidSmooth and ParanoidAndroid while the latter has no internal memory.
Thanks, will do a .ftf flash
Do tell me, what ROM are you on now?
BrokeDude12345 said:
Alright! And it's interesting you mention that SD Cards dying because of this. My 64GB SDXC Class10 microSD mysteriously died on me with the same symptoms. I was switching between LiquidSmooth and ParanoidAndroid while the latter has no internal memory.
Thanks, will do a .ftf flash
Do tell me, what ROM are you on now?
Click to expand...
Click to collapse
Hi mate, btw. I had to buy a new sd card too. I personally think that it´s a bug since kitkat, because from this version on google only has allowed to write apps to ext. sd, which where verified by google! It´s a well known problem.
So I use this ROm http://forum.xda-developers.com/showthread.php?t=2735975
There are more excellent Roms from excellent developers. I must say I never tried another one, because this Rom for me always worked perfect - since CM10 build by bagyusz. No need to try another one :fingers-crossed:
Greets reinipic
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK https://www.youtube.com/watch?v=KBsWNrKNZzA
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
yeah, you are missing a step.
you have to format data partition.
check my guide on how to install roms: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, may I suggest EU/masik instead of stock, its a lot better
in #3 you can see that in the video data is also formated: https://youtu.be/KBsWNrKNZzA?t=190
of course i did this too....was also not working.
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
motorh3ad said:
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
Click to expand...
Click to collapse
Don't flash vendor, theirs no need, eu.miui has everything in the one zip file. Just to clarify have you formatted in twrp? The option where it requires you to type 'yes'? Everything gets wiped from your photos and apps all to the rom itself. Then just flash eu.miui and reboot. Works everytime for me without fail.
no i never formatted in TWRP wipe, only used the factory reset and swiped to wipe.
just did a format and flashed xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM _v11-10.zip
ITS BOOTING!!
first please let me thank you very much for this help, i was already quite desperate about nothing working except LINEAGE.
fingerprint in MIUI rom is working great, unbelievable!
can you please explain me why this FORMAT in WIPE is needed and what its used for? i was not aware and i can not find it in any of the howtos..
haha, glad it's working. Knew the problem was that you didn't format.
however since you posted on xda, I just assumed you knew format data is not the same as wiping data.
(literally, the most common beginners mistake for this phone)
it's cause of the encryption keys, when moving from MIUI to AOSP (and vice-versa) a format data partition is required.
I stated this in How To Change My ROM? I wanna Try them all!
section in the first post.
under there, FOR MIUI ROMS (since that is what you were trying to do)
you missed the 7th bullet point. (you can also text me on telegram)
(also, in the same guide, I inform people to flash their vendor first -4th bullet point- then in the 5th bullet point you wipe it.)
(this is cause often miui customs and some people are usually on a vendor that isnt there's. you have to be on your region vendor, then wipe it, then allow the miui custom's vendor to take over, else you will face fingerprint problems)
This is just another point most just don't follow.
Umm, if my guide needed anything to be included, or like... needed to be more easy to read and follow... I can edit that if you like.
(use can text me on telegram as well)
edit: just read the xiaomi.eu one, I'll edit it to make it more informative
motorh3ad said:
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
Click to expand...
Click to collapse
You're not installing stock ROMs. You are installing custom ROMs based on stock.
If you want to return to true stock grab a fastboot ROM from here and flash it with the Mi Flash Tool. After fully extracting the ROM delete the flash_all_lock.bat file before flashing. That way you cannot accidentally lock the bootloader.
Then choose the 'clean all' option in the Mi Flash Tool before you hit the flash button.
thank you.
my mistake, i didnt write clear. i just wanted to test a miui rom to see how the fingerprint is working there. im happy now with the custom rom based on stock.
but i also went for this solution you mentioned and noticed that on the https://www.xiaomiflash.com/ site only older xiaomi devices are mentioned as beeing compatible.
looks like this is not the point, so im happy to have this option too.
Good evening, I know it's an old model but I was forced to reset and I lost the 4.4.2 cyanogenmod rom. or tried everything but installing the recovery does not make me go to the main folder of the tablet where I save the rom. Does anyone remember the right procedure to install the rom? At least I can let the children play with it. Thanks
And if you have the rom and the recovery saved even better because the 10.1 is no longer found