With a 100% stock setup, how do people update to, for example, the MHC19I version without breaking/losing anything? Is there an app for this?
.psd said:
With a 100% stock setup, how do people update to, for example, the MHC19I version without breaking/losing anything? Is there an app for this?
Click to expand...
Click to collapse
If you're stock all you need to do is take the OTA that comes via the built in updater, nothing gets wiped so you don't lose anything.
you wait a day or 2 for the update to come to your phone.
otherwise, they take the time to read the Stickied guide by Heisenberg in the General Forum for 6P
I'm not sure I understand your question correctly? Are you currently stock? Is your bootloader unlocked? What version/security update are you on?
Sent from my Nexus 6P using Tapatalk
Thanks for nothing you guys suck. I can always reliably look forward to getting told to essentially figure things out on my own when I come here.
Meanwhile, after about an hour of pointless searching I found the answer, because I'm not the only one asking this question. I'll post the instructions because that's how google searching works. In the future, other people will have this exact question, and will hopefully be directed to a thread like this, as opposed so big convoluted all-in-one "official" threads.
1. Download the OTA zip
2. Follow the instructions of this reddit comment
The text of the instructions is as follows...
Install adb and fastboot. Power off phone
Power on holding power+vol down
Use volume keys to select recovery mode then hit power to select
Once the KOd droid is on the screen press and hold power and tap volume up, as soon as you see a menu popup let go of power.
Select "Apply updated from ADB"
Connect to your computer and make sure the OTA .zip is in the ADB folder.
Run command "adb sideload <filename.zip>"
.psd said:
Thanks for nothing you guys suck. I can always reliably get told to essentially figure it on my own when I come here.
Meanwhile, after about an hour of pointless searching I found the answer, because I'm not the only one asking this question:
1. Download the OTA zip
2. Follow the instructions of this reddit comment
The text of the instructions is as follows...
Install adb and fastboot. Power off phone
Power on holding power+vol down
Use volume keys to select recovery mode then hit power to select
Once the KOd droid is on the screen press and hold power and tap volume up, as soon as you see a menu popup let go of power.
Select "Apply updated from ADB"
Connect to your computer and make sure the OTA .zip is in the ADB folder.
Run command "adb sideload <filename.zip>"
Click to expand...
Click to collapse
I'm sorry what? You're *****ing because we wouldn't hold your hand and explain to you step by step? Your in the wrong forums buddy. There's plenty of guides for people like you.
Sent from my Nexus 6P using Tapatalk
superchilpil said:
I'm sorry what?
Click to expand...
Click to collapse
Name doesn't check out.
.psd said:
Thanks for nothing you guys suck. I can always reliably look forward to getting told to essentially figure things out on my own when I come here.
Meanwhile, after about an hour of pointless searching I found the answer, because I'm not the only one asking this question. I'll post the instructions because that's how google searching works. In the future, other people will have this exact question, and will hopefully be directed to a thread like this, as opposed so big convoluted all-in-one "official" threads.
1. Download the OTA zip
2. Follow the instructions of this reddit comment
The text of the instructions is as follows...
Install adb and fastboot. Power off phone
Power on holding power+vol down
Use volume keys to select recovery mode then hit power to select
Once the KOd droid is on the screen press and hold power and tap volume up, as soon as you see a menu popup let go of power.
Select "Apply updated from ADB"
Connect to your computer and make sure the OTA .zip is in the ADB folder.
Run command "adb sideload <filename.zip>"
Click to expand...
Click to collapse
Hypothetically, if you actually hadn't received any help, here's what I would have said to you:
Maybe if you had included the right information you would have gotten further. "How do I update" doesn't exactly cut it. Don't have a go at everyone else for something that is your own fault.
/hypothetical situation
But what are you on about? You did receive help. Did you not read any of the replies here? I answered you (as accurately as I could, considering the complete lack of information that you provided). So did the next member to comment, who pointed you to my detailed guide. And the third person asked for more information, that should have been provided by yourself in the first place. I really don't know what your problem is, you got more help than you probably deserved considering your one sentence request that didn't contain the right information. Then there's the fact that there's all this information all over this device section and the entire internet that would have answered your question had you actually bothered to look for it. Check yourself and lose the attitude.
{
"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"
}
Related
This is a video I made to show what happens when you mess with your phone without doing research in advance. Thought some of you might enjoy and some of you might take as a learning experience
http://www.youtube.com/watch?v=g4Ln15Al0qk
Haha I did laugh "someone help me please"
Sent from my SGH-T959 using Tapatalk
lol great video!
"Congratulations... You have successfully bricked your phone"
Can you access download mode ?!
Read this,
METHOD 2: STUCK AT VIBRANT SCREEN:
(and are not able to use vol+ vol- methods to access downloader/recovery)
You will need the samsung ADB drivers installed for your phone as well as ADB…
ACCESS DOWNLOAD MODE
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears… once it reappears, release all 3 buttons
6) Setup ODIN and get it all setup and ready… (if you are flashing your phone via odin)
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT DOWNLOAD
{
"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"
}
Your phone will reboot into the download screen… go back to ODIN – A com port should now appear for your phone…
9) Click start and wait for your phone to do its thing
ACCESS STOCK RECOVERY
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears… once it reappears, release all 3 buttons
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT RECOVERY
Your phone will reboot into the stock recovery and flash whatever update.zip you need
Click to expand...
Click to collapse
Haha.. "I don't actually know what it is called, it says Galaxy"
lmfao, i would love to have that as my startup anim and sound
That video was funny! "Somebody help please???" lol
Br1cK'd said:
lmfao, i would love to have that as my startup anim and sound
Click to expand...
Click to collapse
Me too that brick is awesome looking even a wallpaper of it would be great
Times never wasted when your getting waisted
"I wanted to make all fast.... and stuff."
Too funny.
is there an app for "I brick my phone"?
Hahaha.. this video is great. Thanks for making me LOL at work. Everyone around me was looking at me with a WTF face.
Awesome Video !!!
I too want the brick animation at start up. LMFAO !!! This made my Day Thanks Allen K
Hahaha! That made my day. Thank you for this.
"Somebody help please? Ummm..."
Allen k for governor!
Wow, just....wow. Anyway, to the OP, you should search this forum. You will find your answers. I want that as a boot up sound too. Too funny
Sent from my SGH-T959 using XDA App
rofl!!!! THAT'S AWESOME.
I don't think that you can fix that type of brick, I haven't seen it before
Ive never seen that either
Sent from my SGH-T959 using XDA App
That was amazing lol
Sexy Vibrant featuring Bionix Fusion 1.1. JAC's OC/UV kernel, FFC installed
Omg to funny, "best I can do is......ummmm....i don't know " fooking class right there
Sent from my SGH-T959 using XDA App
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
fmf.post said:
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
Click to expand...
Click to collapse
Did you install the samsung usb drivers on your pc?
fmf.post said:
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
Click to expand...
Click to collapse
This method is easy and works .
Download Mode .
Put file to PDA in Odin .
Connect cable .
Flash .
http://forum.xda-developers.com/showthread.php?t=1831173
jje
I did...
conan1600 said:
Did you install the samsung usb drivers on your pc?
Click to expand...
Click to collapse
Yes, I installed kies as per instructions.
And I see the com port and tablet detected when I plug it in without being in download mode.
Thanks for the suggestion
Thanks All
fmf.post said:
Yes, I installed kies as per instructions.
And I see the com port and tablet detected when I plug it in without being in download mode.
Thanks for the suggestion
Click to expand...
Click to collapse
Ok... so guess what?
I was just being an idiot.
Instead of power and volume down, I was doing volume up.
Now it worked perfectly.
Thanks to all for comments.
fmf.post said:
Ok... so guess what?
I was just being an idiot.
Instead of power and volume down, I was doing volume up.
Now it worked perfectly.
Thanks to all for comments.
Click to expand...
Click to collapse
Is this after doing the JB update your using this root?
Yes
domethiuos said:
Is this after doing the JB update your using this root?
Click to expand...
Click to collapse
Yes, after the update.
It works perfectly.
Really easy and straight forward.
Took about 15 seconds.
fmf.post said:
Yes, after the update.
It works perfectly.
Really easy and straight forward.
Took about 15 seconds.
Click to expand...
Click to collapse
You didnt any files specific to 4.2.1 just the ones in his zip?
Sent from my GT-N8013 using Tapatalk HD
no. ..
domethiuos said:
You didnt any files specific to 4.2.1 just the ones in his zip?
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
The third post in that thread contains the specific files for our tablet.
Make sure you use the correct one.
{
"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"
}
The first file on the first post only contains the software needed on your pc.
Let me know if you need any more help, i was really clueless the first time.
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
{
"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"
}
So I finally figured out the problem... I had to completely flah the stock image from fastboot, but my drivers were not up-to-date... so I guess it was kinda my own fault... sorry.... but let it be a cautionary tale for everyone, DRIVERS DO MATTER!!
Mancini_Rafael said:
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
View attachment 2410610
View attachment 2410611
View attachment 2410612
View attachment 2410613
Click to expand...
Click to collapse
Pm'ed you.
Sent from my Galaxy Nexus using XDA Premium HD app
I like wugfresh's Nexus Root Toolkit.
I had the same problem.
As suggested above, get the wugfresh nexus root toolkit. That has the option of flashing a stock rom from a soft-bricked device so long as you can get to the bootloader (which is where you are).
I had the same issue - I'm wondering how many others are getting this too. I'm in no way conversant with this kind of technical challenge so I had a few hours of stress thinking my tablet was knackered.
I tried mskips and wug's toolkits on my bootcamp partition in but couldnt get them to work. I tried following the manual fastboot recovery then ADB sideloading the image but that kept failing too.
In the end, I use the mac toolkits (here: http://forum.xda-developers.com/showthread.php?t=2063042) to get back to android 4.2, then let the device receive OTAs. The 4.4 OTA installed fine this way around.
I'll apologize in advance for not trading the entire 41 page thread about the update. I started to read through it and saw discussion about a lot of stuff not pertinent to the upgrade.
I just gave my daughter an S4 for Xmas and trying to update from 4.2.2 to 4.3 (AT&T) before she starts customizing (I will factory reset after the update). I've kicked off the update a few times - message has popped each time about phone being up to date in the middle of the download, but download would continue. Then it would eventually freeze.
The really weird part is that the update says it's a 728MB update, but twice I've gone beyond that size (last time was almost 900MB/125% before it died).
What the heck is going on???
I read there was an update after the original 4.3 update and thought maybe it was actually downloading 2 updates. But I also wonder if I'm downloading the 728MB update twice somehow.
Anyone have any tips/pointers/suggestions?
Thanks
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Check your Baseband number if end with MF3......follow my thread ATT-MK2-Update.zip to upgrade to Android 4.3 MK2 Firmware or there is another thread 4.3 Att official Upgrade http://forum.xda-developers.com/showthread.php?t=2498897 .....To check your Baseband number go to Menu>Settings>More>About Device .....let me know if u need more help and if i help u anyhow.....hit that thanks button......
Swyped from BlueICESense_JBE
I'm MF3
The official thread hurts my eyes, trying to sift through 1,200 posts for pertinent information to my situation.
This might be the part where I get in trouble - asking/saying things I might not supposed to on a dev site. But when you start talking about rooting, sideloading - while those are things I could probably do if I put the effort in (I have rooted and put a ROM on one of my tablets), I'm not going to at this time as I think it's ridiculous that I'm unable to update a brand new never been used phone via either OTA or Kies. I'll return the phone unused before I have to do something to it that should be available without a workaround
I'd really appreciate it if someone can comment on how/why I seem to be downloading more than the stated file size.
Thanks
Just downloaded Kies to your computer, plug it in, and update it through there.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
LZLandingZone said:
Just downloaded Kies to your computer, plug it in, and update it through there.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Tried Kies - told me that the phone version is updatable (or something like that) via Kies.
Just tried OTA updating for about the 8th time - popped up around 500MB that there's an update available and closed the window I was watching the update download on. Hit update and it acted like the download was still in process - picked up saying it was already at 500MBish. Then download went past 728MB AGAIN, and a short time after told me the phone was up to date (no forced restart to install the update). Now it just popped up that it's downloading an update again - shows 754MB/103%, and it's not increasing.
Getting pissed that I've spent about 5 hours on this thing so far today. Giving up and downloading the file Ted posted and figuring out how to flash the update, since that sounds like I won't technically be rooting or flashing a custom ROM.
I just keep getting more and more frustrated with this thing.
I went through the effort to download the Android SDK on two different machines (it wouldn't launch the SDK Manager on the first one), than had to mess with installing the Java SDK on the 2nd computer because the SDK wouldn't install without that. I finally got the SDK loaded, made sure ADB is installed and running, downloaded the update.zip from Ted's thread, and...
the freakin' phone won't let me boot into Recovery Mode?!?!?!?!?!
I *think* ADB is installed correctly and recognized the phone - I ran 'adb devices' from the command line and it listed the phone. I have tried entering the bootloader myself, and also with the ADB reboot bootloader command. The phone appears to go into the bootloader, but I don't have the ability to do anything - trying to attach a picture of the screen. At the top is just says 'Odin mode' or something.
And help/direction on how to fully get into the mode I need to in order to flash the update?
Thanks
{
"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"
}
cvail71 said:
I just keep getting more and more frustrated with this thing.
I went through the effort to download the Android SDK on two different machines (it wouldn't launch the SDK Manager on the first one), than had to mess with installing the Java SDK on the 2nd computer because the SDK wouldn't install without that. I finally got the SDK loaded, made sure ADB is installed and running, downloaded the update.zip from Ted's thread, and...
the freakin' phone won't let me boot into Recovery Mode?!?!?!?!?!
I *think* ADB is installed correctly and recognized the phone - I ran 'adb devices' from the command line and it listed the phone. I have tried entering the bootloader myself, and also with the ADB reboot bootloader command. The phone appears to go into the bootloader, but I don't have the ability to do anything - trying to attach a picture of the screen. At the top is just says 'Odin mode' or something.
And help/direction on how to fully get into the mode I need to in order to flash the update?
Thanks
Click to expand...
Click to collapse
Hold your power button for about 10 second till vibrate.....that would take u to recovery mode ...if not pull your battery off and put it back....and use combo button to go to recovery mode [hold VolumeUp+Home key+Power button] together and when it vibrate let go only power button while still holding volume up and home key.....and when u see samsung galaxy s4 splash screen and also on top left u would see small tiny blue text reboot recovery..... and let go both volume up and home key....that would take u to recovery so u can flash the update .zip files or use ADB sideload......BTW U SHOULD ENTER ADB REBOOT RECOVERY ........and u should have downloaded file inside your sd card already before u do anything.....and hit THANK button if people help u ......
ted77usa said:
Hold your power button for about 10 second till vibrate.....that would take u to recovery mode ...if not pull your battery off and put it back....and use combo button to go to recovery mode [hold VolumeUp+Home key+Power button] together and when it vibrate let go only power button while still holding volume up and home key.....and when u see samsung galaxy s4 splash screen and also on top left u would see small tiny blue text reboot recovery..... and let go both volume up and home key....that would take u to recovery so u can flash the update .zip files or use ADB sideload......BTW U SHOULD ENTER ADB REBOOT RECOVERY ........and u should have downloaded file inside your sd card already before u do anything.....and hit THANK button if people help u ......
Click to expand...
Click to collapse
Finally - after about 10 hours working on the update on xmas day, I got it to update and my daughter was able to start playing with her phone.
Thanks, Ted.
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
{
"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"
}
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
arksoother said:
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
Click to expand...
Click to collapse
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
rahimali said:
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
Click to expand...
Click to collapse
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
arksoother said:
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
Click to expand...
Click to collapse
Can you not even boot into bootloader/fastboot or TWRP/recovery?
You should be able to boot to recovery by following the steps shown here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/recovery-mode/
You could also try and boot into safe mode and try and use the magisk manager to uninstall magisk - howto here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/safe-mode/
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
arksoother said:
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
Click to expand...
Click to collapse
somebody else apparently had the same experience although on a different LG device -> https://forum.xda-developers.com/lg-spirit/help/help-fastboot-error-loading-keystore-t3430163
So it seems that fastboot commands may have been disabled which means you can't interact with the device in fastboot mode whatever you do.
If nothing else works, you could try and re-flash stock ROM if you can manage to get into download mode.
Best of luck!