hi i am a long time lurker, first time poster and i have been stalking the forums for a while looking for an answer too my problem, but so far i think i may be the only one to pull this **** up
i was unlocked bootloader
running twrp 3.1.1 open kirin edition
openkirin os
i didnt get on with the percieved lag soo unrooted restored official os and removed twrp and locked up the bootloader
after first boot i realised my 2nd sim slot is not working after it was functiuonal before :/
ive been hunting about and think it might have something to do with the 3dmodem.app but when i extract orr use the update.zip it always skips it. does anybody know how i managed this? :/
also a way to restore 2nd sim functionality would be appreciated
This is the first time I see this issue.
However, if you are on complete stock now, do a rollback to marshmallow and see if it works.
Goddamnitnappa99 said:
hi i am a long time lurker, first time poster and i have been stalking the forums for a while looking for an answer too my problem, but so far i think i may be the only one to pull this **** up
i was unlocked bootloader
running twrp 3.1.1 open kirin edition
openkirin os
i didnt get on with the percieved lag soo unrooted restored official os and removed twrp and locked up the bootloader
after first boot i realised my 2nd sim slot is not working after it was functiuonal before :/
ive been hunting about and think it might have something to do with the 3dmodem.app but when i extract orr use the update.zip it always skips it. does anybody know how i managed this? :/
also a way to restore 2nd sim functionality would be appreciated
Click to expand...
Click to collapse
Can u tell me if u messup anything with modem and system files?
Nailed IT!
hey guys, last night literally moments after posting this i bit the bullet and
unlocked bootloader
re installed twrp
used an update.app
flashed thrrough twrp
first boot
rooted
and 2nd sim is back again! and also it now says i am entitled to the 389update
when i first used it i was stuck at 360 so i have a feeling when i bought the phone it had been played with internally then sold, but not completely cleaned if you know what i mean, thanks for offering to help though guys !
Goddamnitnappa99 said:
hey guys, last night literally moments after posting this i bit the bullet and
unlocked bootloader
re installed twrp
used an update.app
flashed thrrough twrp
first boot
rooted
and 2nd sim is back again! and also it now says i am entitled to the 389update
when i first used it i was stuck at 360 so i have a feeling when i bought the phone it had been played with internally then sold, but not completely cleaned if you know what i mean, thanks for offering to help though guys !
Click to expand...
Click to collapse
It is good to hear :highfive:
Related
currently on 10.6.1.15.3 WW version and wanting to restore to the same version, i am having a massive blank spot in my brain right now..
I want to restore this version back to normal, long story short.. im rooted but NOT unlocked and have some modifications to the system folders id like to revert back to original before i attempt to upgrade to the latest version that came out this week (tho re rooting first of course).. last time i tried to update with changes made this things screwed up and it locked up hard so hard i had to get a replacement.. so id rather not go through that again....
so ya.. how the heck do i do this again.. ive got TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip and a micro SDHC card but im failing to remember and my search fu is failing hard tonight as all im seeing are methods for unlocked devices to go backwards.
*edit*
http://forum.xda-developers.com/showthread.php?t=2277955 turned out to be the correct method.
Ashcunak said:
currently on 10.6.1.15.3 WW version and wanting to restore to the same version, i am having a massive blank spot in my brain right now..
I want to restore this version back to normal, long story short.. im rooted but NOT unlocked and have some modifications to the system folders id like to revert back to original before i attempt to upgrade to the latest version that came out this week (tho re rooting first of course).. last time i tried to update with changes made this things screwed up and it locked up hard so hard i had to get a replacement.. so id rather not go through that again....
so ya.. how the heck do i do this again.. ive got TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip and a micro SDHC card but im failing to remember and my search fu is failing hard tonight as all im seeing are methods for unlocked devices to go backwards.
*edit*
http://forum.xda-developers.com/showthread.php?t=2277955 turned out to be the correct method.
Click to expand...
Click to collapse
Im really not sure, do you have access to fastboot if your bootloader's still locked? if so you'd download the firmware from asus and zip it, flash the system.blob with fastboot flash system *blobname*
If you don't have fastboot im not sure its possible
JoinTheRealms said:
Im really not sure, do you have access to fastboot if your bootloader's still locked? if so you'd download the firmware from asus and zip it, flash the system.blob with fastboot flash system *blobname*
If you don't have fastboot im not sure its possible
Click to expand...
Click to collapse
sorry, check after the *edit* i put, followed that exactly including renaming the file on the micro sd and boom worked just fine/perfectly... fully locked tablet and was able to re root aftewards and upgrade to the latest with no issues. didnt need to use fastboot in the end..
Hi guys, I'm pretty new to rooting so tell me if i need to give more info etc cause I know i can be a bit vague.
So I rooted my phone no problem via the all in one kit thing and installed cyanogen, but this was right before the big android update so I wanted to switch back and update to that, but somewhere along the line i got rid of all the Roms (I think)
The stage it's at now: I can boot normally but the startup wizard fails, I assume this is because the stock operating system isnt hooked up to run, regardless I can't find a copy or figure out how to run it. (before my TWRP seemed to stop running on startup)
Bootloader: I don't know how it ended up relocked after I'd unlocked it but am guessing that is why i cant access the custom recovery at the moment (twrp)
If anyone is able could you walk me through, or point me to a guide to show:
How to unlock a relocked phone,
How to get a Stock version of Android (anything after 4.0 I guess because it will auto update?) running on there
Tell me if I'm being dumb in any part of this (apart from pissing about with things I don't understand, haha)
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Redijedeye said:
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Click to expand...
Click to collapse
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
sd_shadow said:
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
Click to expand...
Click to collapse
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Redijedeye said:
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Click to expand...
Click to collapse
No, I don't.
I consider this [Completed] and have thread closed.
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.
First of all let me say that i am not new to the android development world, ive done rooting process, flashing etc in several phones and this is the first time ive been stuck clueless.
So this is what happened, I have the Xperia Z5 Premium (E6853), after succesfully unlocking the bootloader i inmediately started the root process and that is were it all went wrong, i followed the root process from this link: technosamigos.com/root-xperia-z5-phone/ I did everything it says, but when rebooted all i got was an unresponsive black screen, the sony logo doesnt appear nor the animation, no bootaudio either, the leds work fine, i can still acces flash and bootloader mode but i cant seem to restore my phone to its previous state any help would be greatly appreciated, thanks in advance.
Are you on lollipop or marhmallow, because supersu 2.46 won't work on marhsmallow.
L33Tgod said:
Are you on lollipop or marhmallow, because supersu 2.46 won't work on marhsmallow.
Click to expand...
Click to collapse
I was just able to unbrick the phone my friend, i was in marshmallow, the problem is that the guy who uploaded the tutorial made a mistake in the version of the kernel, so instead of installing a kernel compatible with my phone (E6853) i installed a kernel for another version (E6653), so i just reinstalled a custom kernel for my version and bam just like that my phone is alive again, thank you anyways man, i really appreciate the fact you were trying to help me out. :good:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/