ok so i installed [RECOVERY]SGH-I337 OUDHS Recovery - now with smart auto-loki and downloaded the miui from [ROM][PORT]MIUI for GT-I9505[21/06] it booted up just fine. i then replaced libril.so and libril-qc-qmi-1.so from a working rom to /system/lib/ but still couldnt get data working.. everything else from what i could tell worked just no mobile network so i restored nandroid.. if any1 interested in getting a working miui for us
how did u even get it to boot? i keep getting stuck on mi screen
U gota have the cwm recovery that auto lokis kernals and just flash rom and gapps
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
i think it is because i didnt flash gapps. thank you though. ill see if i can help
xwill1212 said:
i think it is because i didnt flash gapps. thank you though. ill see if i can help
Click to expand...
Click to collapse
Ive tried these steps to no luck im using ouhds auto loki recovery
Have you tried manually adding the APN settings after initial install? Only issue you'll have is needing WiFi for gapps setup and sync. Too many potential problems flashing another ROM's libs IMO.
Sent from my SGH-I337 using Tapatalk 4 Beta
Related
Trying to install viper rom on my epic and when I'm in clockwork recovery mode it gives me this error:
E:/ Cant open / cache/ recovery/log
What does this mean? What can i do to resolve this. I keep getting errors when I try to install the rom.
I believe you are in the wrong version of clockwork. For the latest viperRom the cwm needs to be Orange 3.0.0.5
Reroot your phone with one click and try again. It appears your phone has lost root. If that doesn't work their are posts in the viper rom thread that describe a process of going back to stock and working your way to viper rom 4.02b. Another alternative is if you haven't flashed viper rom 4.01 first you might try that.
Sent from my SPH-D700 using XDA App
Dont think that is the problem I cant install any ROM s right now including the stock ROM.
Reflash one click root. It will reinstall clockwork for you and that might fix your issue. If not you might have to use odin to go back to stock. The links for this stuff is in the sticky above.
Sent from my SPH-D700 using XDA App
What v. are you trying to install? Is it ext4? what color is the text (v. #) in cwm?
2sslow said:
What v. are you trying to install? Is it ext4? what color is the text (v. #) in cwm?
Click to expand...
Click to collapse
CWM v2.5.1.0. I'm looking for the how to to use odin to get back to stock now
wtam1100 said:
CWM v2.5.1.0. I'm looking for the how to to use odin to get back to stock now
Click to expand...
Click to collapse
I think where i screwed up real bad is I tried to installed the viper ext 4 b4 actually installing the DK 17 2.8.
wtam1100 said:
I think where i screwed up real bad is I tried to installed the viper ext 4 b4 actually installing the DK 17 2.8.
Click to expand...
Click to collapse
Yeah you need to instal the dk28 modem first. In the epic sticky their is a version of dk28 froyo that you can flash through odin. Try that and then one click root and then instal viper rom.
Sent from my SPH-D700 using XDA App
raylusk said:
Yeah you need to instal the dk28 modem first. In the epic sticky their is a version of dk28 froyo that you can flash through odin. Try that and then one click root and then instal viper rom.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks for the advise got it back to stock now will try again.
wtam1100 said:
Thanks for the advise got it back to stock now will try again.
Click to expand...
Click to collapse
Got that Viper installed now. Thanks for all the help from eveyone. I know so much more about the phone now. Good learning experience even thought it was very stressfull at that time.
wtam1100 said:
Got that Viper installed now. Thanks for all the help from eveyone. I know so much more about the phone now. Good learning experience even thought it was very stressfull at that time.
Click to expand...
Click to collapse
Great news. Glad it worked out for you.
Sent from my SPH-D700 using XDA App
i need help to im stuck in clockwork 3.0.0 and my fone wont turn on can somebody help
I was running cm-10 new 32gb Nexus 7 and decided to update to cm-10.1. It flashed fine but when I reboot it wont boot. If I flash again it boots fine but it doesnt matter how I flash...when I reboot it just goes into a bootloop (google black screen).
Please, any advice?
Sounds like the download is bad. Try downloading again and use adb to put it on the Nexus.
davisac said:
Sounds like the download is bad. Try downloading again and use adb to put it on the Nexus.
Click to expand...
Click to collapse
I rooted with the Tool Kit and the version was 4.1.1. After I rooted and unlocked, I flashed cm-10 stable. Used it for a while and everything was fine. Last night I flashed like 4 different ROMs with the same result...bootloop after a reboot. I noticed on the first ROM, when I finished the setup and rebooted. Should I go back to stock but with 4.2 using the Tool Kit and then root again?
Wally72 said:
I rooted with the Tool Kit and the version was 4.1.1. After I rooted and unlocked, I flashed cm-10 stable. Used it for a while and everything was fine. Last night I flashed like 4 different ROMs with the same result...bootloop after a reboot. I noticed on the first ROM, when I finished the setup and rebooted. Should I go back to stock but with 4.2 using the Tool Kit and then root again?
Click to expand...
Click to collapse
Yeah I would see if stock is doing that too. If so it sounds like something wrong with your device not the software.
Sounds like someone didn't do a factory reset between flashes....
Sent from my Nexus 7 using Tapatalk HD
davisac said:
Yeah I would see if stock is doing that too. If so it sounds like something wrong with your device not the software.
Click to expand...
Click to collapse
Pirateghost said:
Sounds like someone didn't do a factory reset between flashes....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have TWRP and this bootloop only happens on 4.2 ROMs. 4.1.2 runs fine, and I flashed it afterwards to see if it is the tablet. It Reboots fine with 4.1. As far as factory reset...I rather flash clean, so YES I did the full wipe.
Thx for your replys guys. I really appreciate it.
Wally72 said:
I have TWRP and this bootloop only happens on 4.2 ROMs. 4.1.2 runs fine, and I flashed it afterwards to see if it is the tablet. It Reboots fine with 4.1. As far as factory reset...I rather flash clean, so YES I did the full wipe.
Thx for your replys guys. I really appreciate it.
Click to expand...
Click to collapse
What version of TWRP are you using? You need to be on the latest for 4.2 roms. 2.3.3.0 I think.
davisac said:
What version of TWRP are you using? You need to be on the latest for 4.2 roms. 2.3.3.0 I think.
Click to expand...
Click to collapse
I do have 2.3.3.0, but guess what....I found the problem! I was flashing M-kernel because I read that that kernel is great for playing games. Since I have a whole bunch of games, I decided to flash it. All the ROMs I flashed...I flashed with that kernel, and it booted fine. My issue was at reboot. Every time it put me on a bootloop. I just finished flashing grouper-M1 from CM, did my setup and rebooted, and booted fine!
Imma do some more reading to see if I can find a good kernel to run with cm-10.1.
Thank you daviac!!!!!:good:
Edit to the previous post and maybe it will help others:
The problem was not the kernel...IT WAS THE BOOTLOADERS version. I had to upgrade bootloaders. With adb I flashed the image and everything is fine!
Reading is fundamental...and I've learned my lesson!
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
There is a disclaimer before installing M-Kernel or probably any other kernel, that states that you need to be on the latest bootloader version. But it's ok, its best to learn from mistakes right?
Leonhan said:
There is a disclaimer before installing M-Kernel or probably any other kernel, that states that you need to be on the latest bootloader version. But it's ok, its best to learn from mistakes right?
Click to expand...
Click to collapse
Lol...after flashing I don't know how many ROMs and getting those bootloops...I went back to that thread and that's how I decided to flash the image. And you're right...some people like me just learn the hard way!!! Currently running Dirty AOKP with M-Kernel, and love it.
Thx!:thumbup:
Sent from my SGH-T889 using Xparent SkyBlue Tapatalk 2
Wally72 said:
Edit to the previous post and maybe it will help others:
The problem was not the kernel...IT WAS THE BOOTLOADERS version. I had to upgrade bootloaders. With adb I flashed the image and everything is fine!
Reading is fundamental...and I've learned my lesson!
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Hey, I got same problem with you.
How do you upgrade bootloader? My bootloader version is 4.1.3.
Thanks before.
inex_emo**** said:
Hey, I got same problem with you.
How do you upgrade bootloader? My bootloader version is 4.1.3.
Thanks before.
Click to expand...
Click to collapse
That's the latest version.
Hi,
I am currently running N4 on AT&T network, but as soon as I install any custom roms radio stops working. Kernels work fine stock and Semaphore. I tried with PA and Purity Roms latest and for both its the same. I tried re flashing bootloader and radios 84, 48, 27, 33Hybrid and 33 but makes no difference nor does the temporary fix suggested by going to *#*#INFO#*#*. It works fine if I restore to stock rom. Please suggest what might be going wrong here.
**Update**
After restore I see in about > baseband is 33. After installing custom rom in fastboot mode I see 33 but once phone is up it comes blank. What should I do to fix it.
Thanks
It is an issue with your current recovery. Some versions of CWM and TWRP cause issues with the radio resulting in an unknown baseband. Which one are you using? From what I know CWM 6.0.3.5 And TWRP 2.5.0.0. should fix your problems.
Sent from my Nexus 4 using xda app-developers app
xperimentul said:
It is an issue with your current recovery. Some versions of CWM and TWRP cause issues with the radio resulting in an unknown baseband. Which one are you using? From what I know CWM 6.0.3.5 And TWRP 2.5.0.0. should fix your problems.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I am running recovery-clockwork-6.0.4.3-mako, should that be an issue ?
dub123 said:
Thanks, I am running recovery-clockwork-6.0.4.3-mako, should that be an issue ?
Click to expand...
Click to collapse
From what I can recall, that version of CWM is one of the versions that causes radio issues. That recovery is your problem. Downgrade to an earlier version of CWM and your radio should be fixed.
Sent from my Nexus 4 using xda app-developers app
xperimentul said:
From what I can recall, that version of CWM is one of the versions that causes radio issues. That recovery is your problem. Downgrade to an earlier version of CWM and your radio should be fixed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You sir are savior, switched to TWRP, created new recovery put in Pure Speed X and this time it works. Thanks. Someone should let them know version is broken as site still links back to it.
dub123 said:
You sir are savior, switched to TWRP, created new recovery put in Pure Speed X and this time it works. Thanks. Someone should let them know version is broken as site still links back to it.
Click to expand...
Click to collapse
Yes I'm not sure why it hasn't been addressed. Maybe it's not a widespread issue. Anyway, your're welcome and glad I was able to help.
Sent from my Nexus 4 using xda app-developers app
Hi, I flashed countless kernels for my european SM-N9005 but I can't find one that let me pass through the boot of the phone. Every time I get stuck after the samsung logo ina black screen, forcing me to reboot on recovery and do a recovery of the boot from a backup I made earlier.
I'm running the latest android kitekat aokp rom, with the latest CW bootloader.
Please help me I would like to overlcock and downclock my device.
http://forum.xda-developers.com/showthread.php?t=2439633
Sent from komsa's Air
komsa said:
http://forum.xda-developers.com/showthread.php?t=2439633
Sent from komsa's Air
Click to expand...
Click to collapse
Thanks, but I already tried from that post:
AEL Kernel
AURORA
lean kernel
Ultimate kernel
still no luck... why?
because I don't know
You have to clean dalvik and cache after flashing new kernel.......
Sent from komsa's Air
komsa said:
You have to clean dalvik and cache after flashing new kernel.......
Sent from komsa's Air
Click to expand...
Click to collapse
I tried even that, I will try againwith other two kernels to see if something change, I will post the result
komsa said:
You have to clean dalvik and cache after flashing new kernel.......
Sent from komsa's Air
Click to expand...
Click to collapse
Like I said, nothing change. Black screen and I have to recovery the boot partition.
PS seems that the phone can get through the boot process, but I can see nothing cause the screen is totally black. In fact, if I try to unlock the phone, I can hear the sound of the unlock process.
Why? How I can solve this?
Up
Some1 help please ;_;
komsa said:
You have to clean dalvik and cache after flashing new kernel.......
Sent from komsa's Air
Click to expand...
Click to collapse
No you don't. It has no effect on kernel flashing whatsoever.
UP
:crying::crying::crying::crying:
Does the stock kernel still work fine?
I mean, flashing the stock kernel will pass the boot process?
Yep, with the stock kernel of the rom all is fine, just updated to the last nightly yesterday, I will try again this weekend with other kernels
Sent from my SM-N9005 using XDA Free mobile app
I know this is off topic and I apologise, but I dont want to make a new thread...
I'm a first time rooter and have TWRP installed ...
I don't know much about kernels but I'm interested in one that works well with stock ROM, is fully stable, improved performance, improves battery and perhaps also has double tap to wake...
If anyone could recommend one, or a few options, that would be great... Thanks
--------------------------------------------
My house phone's better than your iPhone.
Senryu_91 said:
Hi, I flashed countless kernels for my european SM-N9005 but I can't find one that let me pass through the boot of the phone. Every time I get stuck after the samsung logo ina black screen, forcing me to reboot on recovery and do a recovery of the boot from a backup I made earlier.
I'm running the latest android kitekat aokp rom, with the latest CW bootloader.
Please help me I would like to overlcock and downclock my device.
Click to expand...
Click to collapse
or you have problem with BL or recovery or you don't take good version of CM kernel
I used zion and temasek without problems
make your choice http://forum.xda-developers.com/showthread.php?t=2718684
Can any one help me try to get cm11 on my verizon note 3. I have TWRP and Unlocked Bootloader with root running CM13 but I still want to run cm11 and when I tried to flash the rom, it gave me a updater 7 error. If you know a way to fix this please tell me.
lootrooter said:
Can any one help me try to get cm11 on my verizon note 3. I have TWRP and Unlocked Bootloader with root running CM13 but I still want to run cm11 and when I tried to flash the rom, it gave me a updater 7 error. If you know a way to fix this please tell me.
Click to expand...
Click to collapse
Error 7 is typically a mismatch condition between the fingerprint of the recovery in use and the model of the phone the ROM is intended for - the ROM author puts an "assert" statement in the installer script to prevent dummies from flashing a ROM from the wrong device to a phone.
Assuming you didn't make a mistake downloading the wrong cm rom for the SM-N900V Note 3 this could be a "hlte" vs "hltevzw" issue depending on which TWRP version you have installed.
You can work around this by unpacking the ROM .zip file, deleting the offending "assert" line in the installer script, and red zipping the ROM.
bftb0 said:
Error 7 is typically a mismatch condition between the fingerprint of the recovery in use and the model of the phone the ROM is intended for - the ROM author puts an "assert" statement in the installer script to prevent dummies from flashing a ROM from the wrong device to a phone.
Assuming you didn't make a mistake downloading the wrong cm rom for the SM-N900V Note 3 this could be a "hlte" vs "hltevzw" issue depending on which TWRP version you have installed.
You can work around this by unpacking the ROM .zip file, deleting the offending "assert" line in the installer script, and red zipping the ROM.
Click to expand...
Click to collapse
It was just a "hlte" vs "hltevzw" error, thanks
Did you get CM11 working?
Sent from my SM-N900V using Tapatalk
Old 4.4 rom on new vzw bootloader
bishop0114 said:
Did you get CM11 working?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I did and c-rom. Which i love. But with both of them lte data goes in and out. I've tried a bunch of things but can't figure it out. It's weird editing apns causes them to be deleted. Any ideas anyone?
how to install
themrgoats said:
I did and c-rom. Which i love. But with both of them lte data goes in and out. I've tried a bunch of things but can't figure it out. It's weird editing apns causes them to be deleted. Any ideas anyone?
Click to expand...
Click to collapse
can tell me how did u installed it? i am getting ERROR : 7 in TWRP , cm-11-20160612-NIGHTLY-hltevzw.zip (223.82 MB)
Rooted 0B6 then Unlocked Bootloader.
dat ka said:
can tell me how did u installed it? i am getting ERROR : 7 in TWRP , cm-11-20160612-NIGHTLY-hltevzw.zip (223.82 MB)
Rooted 0B6 then Unlocked Bootloader.
Click to expand...
Click to collapse
TWRP error 7 typically means you're trying to install the zip onto the wrong device.
Sent from my SM-N900V using Tapatalk
Yes if you are using the hltevzw twrp then just flash the hlte generic twrp and u can flash roms that don't require the hltevzw twrp to see the right rom is version is being flashed.
One more question , i am running JasmineRom its 5.0.x CM 11 is 4.x.x Will it work? if i install it?
dat ka said:
One more question , i am running JasmineRom its 5.0.x CM 11 is 4.x.x Will it work? if i install it?
Click to expand...
Click to collapse
I don't think so but was wondering since we have an unlocked bootloader, can we downgrade to a developer 4.4.2 rom and then install the cm11?
Sent from my SM-N900V using Tapatalk