{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
PROCEDURE
1) Flash a stock ROM Samsung (AP, BL and CSC) in Odin
2)Flash in AP the TWRP recovery unofficial for T510, then, once in recovery, make a format data and flash multidisabler Samsung
3)Return in Odin and flash AospExtended in AP without any wipe
4)Reboot and enjoy!
LINK
SOURCES
TREBLE DEVICE TREE: https://github.com/phhusson/device_phh_treble
MANIFEST: https://github.com/AospExtended/manifest
i wiped data and flashed it and as soon as it boots into android is keeps saying the launcher is force closing and i cant do anything because as soon as i click close it just pops back up again
Strange....for me works fine. If you start from another custom rom must reinstall first the Samsung Stock Rom. Try to reinstall stock rom (BL,CSC and AP stock) with odin, then flash in AP twrp always in odin. Once entered in TWRP make a format data and flash multidisabler, then return in odin and flash my rom in AP without wipe data, then reboot.
UPDATE: I tried with a simple format data, and also reflashing the stock rom Samsung, my rom works fine.
I enjoy trying new ROMs. Too me, that is the great thing about TWRP. I can backup my current ROM, try a new one, and if something goes wrong, just restore the backup. I've had as many as six different ROMs installed on a Tab A 2016. So, my question is, after re-installing stock and flashing yours via Odin, can I return to my Nextus 10 ROM via TWRP restore, or would I have to re-install stock again and start from scratch.
You can return to Nexus Rom by TWRP
Anyone noticing reboots at night or in the afternoon?
i like your work but 100% NOT a daily driver for this device. i cant even get ahold of my internal storage file with pc. USB DEBUGGING an FILE TRANSFER is on.
still nothing!
going back to nexus stock 10\
thank you
PopCaps1996 said:
i like your work but 100% NOT a daily driver for this device. i cant even get ahold of my internal storage file with pc. USB DEBUGGING an FILE TRANSFER is on.
still nothing!
going back to nexus stock 10\
thank you
Click to expand...
Click to collapse
you did something wrong then..
I followed OPs instructions and was up and running first try. I went further and installed gapps and magisk 20.4.
The only problem I am having is It is saying my external sd card is corrupt.. any suggestions on how to fix this? I can life without it but I dont want to wipe the ext sd since I know its not corrupted
elliwigy said:
you did something wrong then..
I followed OPs instructions and was up and running first try. I went further and installed gapps and magisk 20.4.
The only problem I am having is It is saying my external sd card is corrupt.. any suggestions on how to fix this? I can life without it but I dont want to wipe the ext sd since I know its not corrupted
Click to expand...
Click to collapse
If I remember right it's because it isn't the right format or what u would call it. U will have to format the SD card for it to be the right one. Put ur stuff on the laptop via ur phones SD slot or if ur laptop got a SD reader
DKzVeNgEnS said:
If I remember right it's because it isn't the right format or what u would call it. U will have to format the SD card for it to be the right one. Put ur stuff on the laptop via ur phones SD slot or if ur laptop got a SD reader
Click to expand...
Click to collapse
does aospextended use a different format that stock firmware? or is it a difference between pie and q?
elliwigy said:
does aospextended use a different format that stock firmware? or is it a difference between pie and q?
Click to expand...
Click to collapse
All aosp use a different one than stock oneui but the ones aosp use also supported by oneui so u only have to do it once
Hey there,
I'd very much like to try out your aospextended build and have two questions:
Was this build on the November or March update? I'm unfortunately running March and can't install anything from November
Is this a 64bit or 32bit rom? I'm urgently looking for a 64bit one.
Chaosghoul said:
Hey there,
I'd very much like to try out your aospextended build and have two questions:
Was this build on the November or March update? I'm unfortunately running March and can't install anything from November
Is this a 64bit or 32bit rom? I'm urgently looking for a 64bit one.
Click to expand...
Click to collapse
its based on treble/gsi so it doesnt matter what month firmware you have
elliwigy said:
its based on treble/gsi so it doesnt matter what month firmware you have
Click to expand...
Click to collapse
Ah cool, thanks.
Do you also know if this is a 32bit or 64bit rom by any chance?
Thanks and kind regards
Jakob
Anyone have a link to stock ROMs as per the instructions?
-BoneZ- said:
Anyone have a link to stock ROMs as per the instructions?
Click to expand...
Click to collapse
If you google "SM-T510 stock rom" there are quite a few pages
Chaosghoul said:
Ah cool, thanks.
Do you also know if this is a 32bit or 64bit rom by any chance?
Thanks and kind regards
Jakob
Click to expand...
Click to collapse
Hello!
Im also on the March Firmware. Have you flashed this rom already? I ask because the instructions say to install twrp... and you cant install twrp because its based on the old Firmware...?
Related
Hello my friends,
I think I've done a real disaster: I tried to update my Hd2 using the official update from Htc web site but after the update the phone self reboot and got stuck at the boot loader screen; I followed a suggestion on a site and did the HSPL with hard spl by bepe & cotulla but after doing this I'm now stuck at the boot screen and I can't flash neither it's original rom or any cooked rom; I also tried the Task29 trick with no luck and also tried to flash my phone through the SD card...no luck at all...
Help me 'cause I really don't know what else can do.
Thanks for any help
Your gonna need to post some info about your phone and what you were trying to flash before anyone can help buddy.............
I can post the boot screen capture: is enough?
What kind of HD2 is it......
Which rom were you running before this happened.......
What was the rom you were trying to flash.......
Sure post the bootloader screen too........
It had the original rom, it's an Htc Hd2 from Tim Italy, it's not the 1024 mb ram version, and I was trying to flash the latest official htc rom.
I would post also the image of the bootloader but since I am a new member I can't post link :-(
Ok, I was expecting you to say it was a tmous model and that you'd flashed the wrong radio........
Im not sure why it wouldnt let you flash to that rom........
Are there any error messages when you try to flash again?
From your first post it sounds like youve tried everything I could suggest......
conantroutman said:
From your first post it sounds like youve tried everything I could suggest......
Click to expand...
Click to collapse
and you are absolutely right :-(
When I flash a Rom or else I get "ERROR 328 (Invalid Command - This Update Utility cannot be used for your PDA Phone)"
This is the boot image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note the signs in the upper left corner: what do they mean? A corrupt hspl maybe?
tisinpower said:
and you are absolutely right :-(
When I flash a Rom or else I get "ERROR 328 (Invalid Command - This Update Utility cannot be used for your PDA Phone)"
This is the link to view the boot:
h**p://184.72.239.143/mu/5d29e6f9-8cce-14e9.jpg
(sorry but I can't insert images yet)
Click to expand...
Click to collapse
Ok im running out of time to help you im afraid, gotta go to work
I think it might be something to do with your phone being network branded.....
Try looking in the rom development section stickies to find a carrier branded rom from your network provider and see if you can flash that.........
Im sure someone with more knowledge than me will jump in and help you out eventually......
also try googling for the error message that you get.......
conantroutman said:
also try googling for the error message that you get.......
Click to expand...
Click to collapse
I did a search and find out a possible solution in editing the rom image nbh file with an hex editor to set it to a higher version, since the problem could be my hspl version too low, but also this didn't work...
Thank you for your interest
in your screen shot the modelcode (or whatever it is) in the upper left looks corrupted. I'm not sure but i've seen people post before with corrupted bootscreens.
i would get hspl2 and try changing to say 1.66, anything, really, in the hope it fixes it, but i don't hold much hope.
samsamuel said:
in your screen shot the modelcode (or whatever it is) in the upper left looks corrupted. I'm not sure but i've seen people post before with corrupted bootscreens.
i would get hspl2 and try changing to say 1.66, anything, really, in the hope it fixes it, but i don't hold much hope.
Click to expand...
Click to collapse
I supposed it was corrupted too, and I tried to flash hspl again but it does stop at 19% with any version... I don't know what to do
I know you mentioned before but if you do a forced installation from your SD card I don't see a problem on that.
***Preparing of your SD
-Format your SD with "FAT32"
- Download the original Rom from HTC following your SN N°
- Extract the .exe file with Win-Zip
- Move the RUU_signed.nbh to your SD
- Rename the RUU_signed.nbh to leoimg.nbh
- Reset the device while pressing the volume down button.
- Follow the instructions fore installation
kurt-willems said:
I know you mentioned before but if you do a forced installation from your SD card I don't see a problem on that.
***Preparing of your SD
-Format your SD with "FAT32"
- Download the original Rom from HTC following your SN N°
- Extract the .exe file with Win-Zip
- Move the RUU_signed.nbh to your SD
- Rename the RUU_signed.nbh to leoimg.nbh
- Reset the device while pressing the volume down button.
- Follow the instructions fore installation
Click to expand...
Click to collapse
Unfortunately it does not work: it says "installing", then quit and self boot and return to the boot screen.
I also sent it to the service and they returned it as "not serviceable" since I modded the spl.
Is possible that is only rubbish now?
Well...check my topic. I have a corrupt bootloader as well. My phone is dead, I tried everything but without any results.
You can pull out the battery for a couple of hours (16-20), then go directly to the bootloader and flash an original ROM through USB. That helped for me 2 months ago. But unfortunately this time it is fatal and have to call the insurance company
Delete HSPL and flash original carrier ROM
Hi Tisinpower,
I don´t know, but since you´ve tried just about everything, and the service people told you "unserviceable" due to HSPL, have you tried to delete the HSPL and "install/reboot" with an original carrier ROM?
Sheikmans said:
Well...check my topic. I have a corrupt bootloader as well. My phone is dead, I tried everything but without any results.
You can pull out the battery for a couple of hours (16-20), then go directly to the bootloader and flash an original ROM through USB. That helped for me 2 months ago....
Click to expand...
Click to collapse
Good luck
BHS Interceptor said:
Hi Tisinpower,
I don´t know, but since you´ve tried just about everything, and the service people told you "unserviceable" due to HSPL, have you tried to delete the HSPL and "install/reboot" with an original carrier ROM?
Good luck
Click to expand...
Click to collapse
Yes, I did, and obviously didn't work.
I think I'm going to sell it as is on eBay and buy another htc, I don't know what to do anymore to restore this damned hspl...
now i'm no noob, i've odined plenty of times. but ever since i flashed eugenes 2.2.1 the first update, my phone has went crazy. i had to flash back to bionix and it worked but everytime my phone rebooted or i turned it off then on i wouldn't get service because flight mode was always active for some reason, but bionix was the only one after i unchecked it i would get service, because i flashed tons of 2.2.1 roms and other 2.2 roms and flight mode would always be checked after boot. even though bionix still worked it was acting funky sometimes so i just odined and i used the true firmware 2.1 from eugene instead of froyo but i doubt thats the deal, now after a successful odin , it passed, it keeps coming on and i flight mode is still checked but after the second media sd card scan it boot loops, everytime... the phone won't stay on past the sd card scans.. wtffffffff help pretty please
which recovery do you have? root it, get clockwork, format system, data, cache, reflash to jfd, mini kies to kb5. I just did this from a borked voodoo recovery.
Lol its been rooted. Im not a noob man. I just odined eugenes 2.2 official jk2 stock. Now phone boots and works fine. But when I reboot flight mode is always on... and some apps keep fcing over unistalled and re installed bunch of times same result. I did two odins wtf is wrong wit my phone
BTW something I forgot to mention, ever since flashing eugenes 2.2.1 under about phone my baseband version always says unknown, even after the odin twice it still says that on every rom. Everything was alwaya fine until I flashed that rom. Odins didn't fix so idk wut is up.
Sorry not to spam but ever since I flashed dead horse and the rom my IMEI always shows up as unknown, even after odin, on any rom.
Couple of things if you odin back t ostock and you still have issues then try
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Reboot Enjoy!
Or try clearing the cache, reset phone in recovery and clear dalvik
oka1 said:
Couple of things if you odin back t ostock and you still have issues then try
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Reboot Enjoy!
Or try clearing the cache, reset phone in recovery and clear dalvik
Click to expand...
Click to collapse
I do this before every rom flash :/
Where did you get the pit/tar for jfd?
Did you check the md5 sum?
Try my Alt Method in the noob guide (signature, bottom of post one)
Which recovery do you have?
s15274n said:
Where did you get the pit/tar for jfd?
Did you check the md5 sum?
Try my Alt Method in the noob guide (signature, bottom of post one)
Click to expand...
Click to collapse
I got the pit and pda from the eugene does not brick thread then I used the true stock 2.1 firmware after flashing eugenes does not brick. Phone turned on but after media scanning finished it went into boot loot doing the same thing. I then odined the stock official jk2 and phone works again. BUT the reasons I odined in the first place is still there. In about phone no matter what rom or modem I flash it always says unknown under baseband version , and it says unknown on my imei number too, and when I reboot the phone no matter wut rom flight mode is always on so I don't get service untill I turn it off. None of this ever happened until I flashed eugenes newest 2.2.1 rom and even after two odins it still is affected from it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
get clockwork and flash kb5 modem. then save all bytes from the sd card (internal) and wipe it. whatever is causing your problems is persistent through a full \system, \data, \sys, \etc, etc wipe, so it must be on the internal memory.
I am about to do the same to my phone right now...
1freedude said:
get clockwork and flash kb5 modem. then save all bytes from the sd card (internal) and wipe it. whatever is causing your problems is persistent through a full \system, \data, \sys, \etc, etc wipe, so it must be on the internal memory.
I am about to do the same to my phone right now...
Click to expand...
Click to collapse
Let me know of it works for u
worked
everything copied over fine except the hong kong stock rom, so i deleted it. the phone rebuilt the necessary folders and files (Android, dcim, external_sd, lost.dir, and sd).
So does it no longer say unknown for all of those things under about phone?
i didn't have that problem, i ****ed up my kernel/recovery. worse than boot loop, couldn't mount internal, voodoo wouldn't mount \system. my saving grace...odin back to stock.
firtst, i went back to ji6, but didn't have a data connection (probably had the same issue as you have now, i didn't bother to dig deeper), then tried mini kies to get updates, but kies didnt do anything so, i flashed to jfd, (im trying to find it now for you) this got me back to a shipped straight from the box state. with data.
kies (pita) updated to kb5 on its own, went wonderbar. fast data, really smooth ui, i thought it was a tweaked rom. i think i m gonna root it and keep the stock rom...
so, the moral of the story? install mini kies if you don't have it already, wait for the link when i find the jfd i used, flash it, and then upgrasde through mini kies. ou, then put the personal stuff back onto internal
here, i found it
http://www.multiupload.com/IFSJECTS3L
or this is from the source
http://forum.xda-developers.com/showpost.php?p=10871041&postcount=234
I have clockwork recovery installed.
my question is
is there *anything special* i need to do to go from this to the new ICS or JB Roms??
thanks in advance!
Yes. Make sure you flash Gingerbread bootloader. There is an easy to follow guide available. Search for Vibrant Custom GB Bootloader on Google and it should take you directly to the thread here.
It's a simple guide to follow, just follow it carefully. *a misstep can hard brick you*
After you have that you can find a suitable 4.0.4 ICS to flash. Just follow the directions in the OP and you should be fine.
Or, you could flash a JB ROM. In that case I would recommend (because I had to) flash cm9 nightly FIRST, then go to JB from there. Would probably make your life easier
As my buddy Woodrube says: read, read, read. When you've read enough, read more.
I still sit back and read about an hours worth of old solved threads and new ones alike on an everyday basis.
Note: if you for choose an ICS ROM, please read the threads titled EU bug, and Encryption Unsuccessful. It may not ever affect you, but you should become familiar with it.
You don't need to flash Gingerbread bootloaders.
theexel said:
You know, everyone always says to go to CM7 then CM10.
I ODIN'ed back to stock today, no idea why, I got bored. xD
Note: Skip steps 1, 3, 4 if you already have a custom recovery, which you do, you're running Bionix and don't want to ODIN back to stock for a complete clean install.
These are the steps I use to go to CM10 coming from stock:
1. ODIN to stock, wipe everything, you know.. clean install.
2. Download all the zips you need. (CM10, JB GAPPS, CM10 FFC support zip, update.zip that has clockworkmod recovery.) and put them on your phone.
3. Reboot into recovery, install 'update.zip' it'll reboot, do it again.
4. It should boot into CWM now, the old version.
5. Flash CM10, it should reboot or get stuck.
6. Boot into recovery (Should be new recovery from now on.), wipe data/factory reset.
7. Boot into recovery, flash twice before rebooting.
8. Reboot system and wait for it to boot up, if it doesn't boot up, flash again.
9. Once it boots, flash GAAPS.
10. Flash CM10 FFC support.
Enjoy?
Click to expand...
Click to collapse
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Woodrube said:
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Click to expand...
Click to collapse
so i need to install CM7 before installing these roms(ICS)? (the guide says skip to the CM7 part). is CM7 required??
if so, how to go about installing the CM7 in place of the Froyo bionix build??
and is there a custom CWR for ICS roms that I need to install?
sorry for the dumb questions. ive been knee deep in my sgs4g and havent kept up with vibrant...
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
theexel said:
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
Click to expand...
Click to collapse
Ive been looking for the JB GAAPS file to dl for vibrant and I cant find it any where
http://goo.im/gapps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
theexel said:
http://goo.im/gapps
Click to expand...
Click to collapse
No wonder I couldnt find it, I was spelling it wrong ffs I feel like a a dip**** now lol
---------- Post added at 11:55 PM ---------- Previous post was at 11:40 PM ----------
Just trying to be thorough here. On step 7 it says "7. Boot into recovery, flash twice before rebooting." What exactly should I be flashing 2x here? Never mind I figured it out
The ROM, but you figured it out.
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
FC3SRedSuns said:
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
Click to expand...
Click to collapse
I had already flashed 2 other ROMs before going to CM10, 1 successful on not so successful. This time it went flawlessly. Im loving CM10 so far. I see why this is so addicting now haha
Now you guys see what I mean about steps before leaps?
If you have a bad flash on 2.2 or 2.3.x, they are fairly easy to recover from and start over. Sometimes a bad flash on ICS can cause irreparable damage, al'a EU bug. I've also seen motherboards borked, USB/PC unconnectivity and the worst of all a bootloader bad flash, hardbrick.
But yes, I as well as almost everyone here will agree, it is very addicting.
So here I am again, after a while.
Have changed like hundred of ROMs about year ago on Galaxy S III and Galaxy S II, it was still time when newest android version was 4.1.2 i think.
So now i have a problem, big one. I bought Galaxy S II again, and wanted to flash new rom, because version that i had was 4.1.2.
It was horrible, i effd up my phone big time and flashed stock rom trough Odin, now its 4.0.3. It's old like my granny, but it's very fast. I'm spending like only 38% of my RAM.
But still i wanted to change ROM, and put on the new 4.4.2, but only that kind which don't takes more than 50% of ram.
Adding Screenie, so you can check out what kernel am I using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using as stock rom - I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5 (file name)
and as root - CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5 (file name)
I Have tried to flash any of the ROMs trough CMW recovery with the kernel i have now, but still i got Failed to install update. Some kind of e:emmc (Status 7 error), i tried to fix it, fixed. But now I had Status 6 error. It seems that i can't open the update (ROM).
So i'm asking for help. Maybe some1, could give me the right ROM, right KERNEL and RECOVERY. and step-by-step guide to avoid those errors and fails.
I'm sorry if i'm posting new thread, but i can't really find and answer to my question and problem. I would be greatful if someone could just help me and guide trough this problem, if not here, then maybe in PM.
NEzverins said:
But still i wanted to change ROM, and put on the new 4.4.2, but only that kind which don't takes more than 50% of ram.
I Have tried to flash any of the ROMs trough CMW recovery with the kernel i have now, but still i got Failed to install update. Some kind of e:emmc (Status 7 error), i tried to fix it, fixed. But now I had Status 6 error. It seems that i can't open the update (ROM).
Click to expand...
Click to collapse
You don't need a step to step guide. Just flash a kitkat compatible CWM (search for it), before flashing a kitkat rom. Everything else goes the same.
NEzverins said:
So here I am again, after a while.
Have changed like hundred of ROMs about year ago on Galaxy S III and Galaxy S II, it was still time when newest android version was 4.1.2 i think.
So now i have a problem, big one. I bought Galaxy S II again, and wanted to flash new rom, because version that i had was 4.1.2.
It was horrible, i effd up my phone big time and flashed stock rom trough Odin, now its 4.0.3. It's old like my granny, but it's very fast. I'm spending like only 38% of my RAM.
But still i wanted to change ROM, and put on the new 4.4.2, but only that kind which don't takes more than 50% of ram.
Adding Screenie, so you can check out what kernel am I using.
using as stock rom - I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5 (file name)
and as root - CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5 (file name)
I Have tried to flash any of the ROMs trough CMW recovery with the kernel i have now, but still i got Failed to install update. Some kind of e:emmc (Status 7 error), i tried to fix it, fixed. But now I had Status 6 error. It seems that i can't open the update (ROM).
So i'm asking for help. Maybe some1, could give me the right ROM, right KERNEL and RECOVERY. and step-by-step guide to avoid those errors and fails.
I'm sorry if i'm posting new thread, but i can't really find and answer to my question and problem. I would be greatful if someone could just help me and guide trough this problem, if not here, then maybe in PM.
Click to expand...
Click to collapse
Hi
As long as your phone is rooted and have custom cwm
You can flash this kernel
Then dont reboot the system
Reboot to recovery
Full wipe
Flash kk rom zip
Flash gapps
Sent from my GT-I9100 using Tapatalk 2
Thankyou very much both of you. Seems to me i just had old CMW. I installed new one, and sucessfully flashed rom and gapps.
The problem now is that file transfering, deleting and folder opening when connected USB is really slow or folders won't even open. So i really can't transfer any files from my PC.
Thanks.
NEzverins said:
Thankyou very much both of you. Seems to me i just had old CMW. I installed new one, and sucessfully flashed rom and gapps.
The problem now is that file transfering, deleting and folder opening when connected USB is really slow or folders won't even open. So i really can't transfer any files from my PC.
Thanks.
Click to expand...
Click to collapse
Make sure the screen is on and the phone is unlocked and try a different usb transferring modus.
cwm 6.0.4.5 can't open kitkat rom
Hi,
classic intro i guess, i'm new to the forum, was going to open a new thread, when in fact this one seems perfect. Still, if i shouldn't be doing it, i apologies in advance, please let me know....
Now,
as i said the original topic replicates almost exactly the issue i'm facing.
i have Galaxy S2 i9001, i had rooted it, then tried to flash a rom, failed that, found a guide which got me to have rooted stock (i assume it is a stock rom) version 4.0.3, similar kernel version listed in the original post (i hope is ok to list below the file names? this is the file i used to get there: I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5)
I flashed CWM version 6.0.4.5, which, reading from this thread, should be compatible with KK roms.
i didn't manage to install the newer version listed in that thread as inside the zip there is no .tar file for odin to read, so not sure how i would do that. same for the other "philz" file listed. i'm a noob after all....
So, with CWM 6.0.4.5 on, i downloaded into external SD card a few different ROMs
pa_i9100-4.3-BETA6-20140523.zip
aokp_i9100_kitkat_unofficial_2014-04-14.zip
Resurrection_Remix_KK_v5.1.1-20140507-i9100.zip
rebooter into recovery, followed the wipes listed in the ROMs threads then tried to "install zip" and for each file i get the same messages:
Installing: /PATH
Finding update package
Opening update package
Can't open /PATH
i hope someone could help me understand what it is that i'm doing wrong?
any help would be really appreciated, please!!:fingers-crossed:
Hi everyone,
I have a Samsung Galaxy Note 3 (SM-N900P) on Sprint and am currently running the latest Cyanogenmod.
I absolutely NEED for both Wi-Fi Teather AND GPS to work on my phone and so far, the Wi-Fi Teathering works perfect on Cyanogenmod, but GPS will not work no matter what workaround I try on the phone.
So, I thought I'd come here to ask you all for recommendations on the best and stable ROM that BOTH Wi-Fo Teathering and GPS work on without a doubt.
If I need to go to a ROM that is extremely close to Stock, then so be it. I just need to be sure that these two things work without issues.
Any suggestions are GREATLY appreciated!!
Best,
Jason
I use stock rooted touchwiz and they both absolutely work for me! :good:
inkmachine said:
Hi everyone,
I have a Samsung Galaxy Note 3 (SM-N900P) on Sprint and am currently running the latest Cyanogenmod.
I absolutely NEED for both Wi-Fi Teather AND GPS to work on my phone and so far, the Wi-Fi Teathering works perfect on Cyanogenmod, but GPS will not work no matter what workaround I try on the phone.
So, I thought I'd come here to ask you all for recommendations on the best and stable ROM that BOTH Wi-Fo Teathering and GPS work on without a doubt.
If I need to go to a ROM that is extremely close to Stock, then so be it. I just need to be sure that these two things work without issues.
Any suggestions are GREATLY appreciated!!
Best,
Jason
Click to expand...
Click to collapse
Stick to stock or stock based ROMs. Asking what's the "best" is always relative here and often meaningless. If you are looking for a non-TW based ROM for all of this then a 1000 factors come into play. Did they flash the ROM clean or dirty? If dirty from what ROM? Was these things working before flashing? If they got GPS working...did they have to do something more? Does that work for everyone? Are they calling the ROM the BEST because they like the color? How many have they tried?
Another thought is, has anyone gotten GPS to work on CM? If so, have you tried the same methods? If it worked for them and not for you, that should tell you something about trying to find another non-TW ROM where it does work. There are variances from phone to phone causing something to work on one and not another.
With all that said, if you are not heading to a TW ROM, the trial and error may be in your hands to work this out, not someone's opinion.
FreddyFredFred said:
I use stock rooted touchwiz and they both absolutely work for me! :good:
Click to expand...
Click to collapse
Can you provide a link to that stock rooted touchwiz that you use? Just want to make sure I get the correct one lol.
inkmachine said:
Can you provide a link to that stock rooted touchwiz that you use? Just want to make sure I get the correct one lol.
Click to expand...
Click to collapse
If you are new to the note 3 my thread linked here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 will give you step by step how to root your device. There is no magic pill, it takes about a hour or less to do. All stock roms on the Note 3 are touchwiz, so it does matter what version of KitKat is on your phone i.e. 4.3 NAB, 4.4.2 NC5 or 4.4.4 NH7, when you root your device it will become stock rooted touchwiz.
jimzweb1 said:
If you are new to the note 3 my thread linked here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 will give you step by step how to root your device. There is no magic pill, it takes about a hour or less to do. All stock roms on the Note 3 are touchwiz, so it does matter what version of KitKat is on your phone i.e. 4.3 NAB, 4.4.2 NC5 or 4.4.4 NH7, when you root your device it will become stock rooted touchwiz.
Click to expand...
Click to collapse
Hi!
Thanks for the info! I'm going to read through it after work today.
I'm already currently rooted with CWM based Recovery v6.0.4.7
compiled by Xiaolu (20140125)
My current and only ROM on the phone is the most current version of CyanogenMod.
I hope none of the above causes any problems for me when trying to go to the rooted stock touchwiz!!
inkmachine said:
Hi!
Thanks for the info! I'm going to read through it after work today.
I'm already currently rooted with CWM based Recovery v6.0.4.7
compiled by Xiaolu (20140125)
My current and only ROM on the phone is the most current version of CyanogenMod.
I hope none of the above causes any problems for me when trying to go to the rooted stock touchwiz!!
Click to expand...
Click to collapse
I'm going to assume you received the phone that way. First I would make a backup of the Cyanogen rom on the device, "you know that one works", to an external sd card, or use the internal sd card, and then copy and paste the back up file you just made to the desktop of your PC via USB cable. Now the with phone connected to your PC go to the internal sd card, copy and paste the DCIM, music, and any other data you want to keep to the desktop of you PC. Then go to settings/general/Backup and reset/Factory Data reset/reset basically you are going to do a factory reset. That should take you back to unrooted stock. It will delete all your data, like the device was new. Now, you need to go to settings/general/about device and see what version of KitKat you have. Then you need to go to download mode ( press the power button, volume down button, and home button at the same time a screen will come up then push the volume up button) it should look like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If both lines are not OFFICIAL the you need to flash a fresh copy of what ever stock version of KitKat 4.3, 4.4.2, 4.4.4 you want with odin. Check out the thread I listed above to do that, and get to stock, then follow the steps to stock rooted touchwiz. Make a backup of the stock rooted TW rom that way you can always get back to square one it's like system restore on your PC.
Ok, with the stock rooted TW rom up and running get the device connected to the PC, and copy and paste the data files on your PC desktop back on the internal sd card. Get the device to the point of a daily user, then make a backup. Now one more twist and your done, if and when you try to restore that Cyanogen rom first backup you made, the md5 will not match your new stock rooted rom. Here is the fix, first try and restore the Cyanogen backup maybe you will get lucky. If not download a root file manager like Root Explorer, go to the Cyanogen backup that failed and click on it all the files that make the OS will come up. Find the file named "nandroid.md5" and delete it. Now use root explorer and create a new file and install in the same place, check permissions should be rwxrwx--- . Then go ahead and restore the Cyanogen backup again, this time the system will ignore the empty nandroid.md5 file and install the Cyanogen backup. I know this looks tough but you can do it, and be a flashaholic like the rest of us !!! Lol