Hello, I apologize for my English, I use the translator.
Would anyone find someone willing, and ppmohl me?
I bought for ali for myself and my friend two radio isudar with android 7.1.1, 2gb ram, 16gb rom.
I tried to both radio in my car.
Both of them were normally released, but after a while they were stuck and restarted, started, but after a while they jammed and restarted, then jammed when booting the system.
It happened several times in a row, eventually it does not turn on at all, the other sometimes starts, but gets stuck when the system starts.
The seller sent me an update as well as instructions on how to do it, but one of my radio will not run at all and the boot loader will not start on the other, and will boot into the system.
The update process sent by the manufacturer does not work.
I have already bought several pieces of radio by ISUDAR, always with a system of wince, they all work. I tried even the android, another little one. Did it work well?
Will anyone advise? Thank you very much
Related
I got this tablet as a gift yesterday. Booted up fine, I updated all apps. Also rooted the tab which went through smoothly. The problem started after I installed Titanium Backup and froze/uninstalled a lot of system apps. Now the tablet has gone into a boot loop. It starts up, boots fully into the OS, and then restarts after around 10 seconds!
I have tried going into Recovery to do a factory reset, but YouTube videos showing the procedure show a menu which I am just not able to get to.
I have also downloaded the latest official firmware file from ASUS directly. Tried putting that on a MicroSD card and then booting up the tablet, but it does not recognise even that!
Basically, I'm screwed for now! And since it is a gift from the US, I cannot even send it in to ASUS for warranty recovery/replacement etc.
Please HELP!! :crying::crying:
Never mind. I've sorted everything out.
Alrighty folks, it's time for me to give up and ask the community (probably what I should've done in the first place. lol)
This basically all started when I tried to update my GPE Rom to lollipop. I flashed it using TWRP from my external SD card. Then it wouldn't boot. Just kept showing the screen with the "google" logo and an unlocked padlock at the bottom.
Skip forward a day and some change and I managed to screw up the recovery. Same thing happens as when I tried to boot into the Rom. I'm now trying to get the stock RUU to work as I'd be happy with anything right about now. I keep getting an error 159. So, I committed the mortal sin, I didn't read enough and somehow, playing with fire, I got burnt.
Now I'm turning to you kind people to help me solve this issue and hopefully teach me a few things in the process
Just let me know what you need and I'll do my best to be not a dumb.
Thanks in advance.
applehusky said:
Alrighty folks, it's time for me to give up and ask the community (probably what I should've done in the first place. lol)
This basically all started when I tried to update my GPE Rom to lollipop. I flashed it using TWRP from my external SD card. Then it wouldn't boot. Just kept showing the screen with the "google" logo and an unlocked padlock at the bottom.
Skip forward a day and some change and I managed to screw up the recovery. Same thing happens as when I tried to boot into the Rom. I'm now trying to get the stock RUU to work as I'd be happy with anything right about now. I keep getting an error 159. So, I committed the mortal sin, I didn't read enough and somehow, playing with fire, I got burnt.
Now I'm turning to you kind people to help me solve this issue and hopefully teach me a few things in the process
Just let me know what you need and I'll do my best to be not a dumb.
Thanks in advance.
Click to expand...
Click to collapse
Have you tried reflashing your recovery? Also I had the same problem with being stuck at the splash screen for lollipop, it just takes a really long time to boot and doesn't show a boot logo.
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
HELP PLEASE.Is there a way to flash or root AT&T Note 5,stuck in boot loop mode???
Hi to all
I'm member on XDA for a long time,but I really am a newbie considering rooting,flashing and messing with the phones.
Yesterday ,my At&t Samsung galaxy NOTE 5 restarted by itself and started doing that constantly.Maybe because the memory was almost full so the firmware didn't have enough space to run correctly ,I don't really know.
So I decided to do a FACTORY RESET in order to refresh the phone.I backed all up (it did restart few time while I did that but I managed to finish it).
After I did the factory reset and wiped the cache,I rebooted the phone and that is when the boot loop started.
Once or three times came back and started the phone up to the first settings (I managed to put in my google username e.t.c. but after a minute maybe it freezes and restarted by itself again)
I tried again another factory reset but the boot loop continues.I tried many time to turn it off,it restarted up to INSTALLING UPDATE......then tried to turn it off completely (Volume down+Power+Home button) and somehow I managed to turn it off.
I thought that I can come here and find the instructions on how to FLASH it with ODIN,but I couldn't find the stock firmware for AT&t Note 5.
Then I remembered (and read on internet) that the bootloader on AT&T phones is locked !!!!!
I searched some threads here for at least how to root it ,but I can't find anything clearly.
So I'm asking you for help: IS THERE ANY SAFE WAY THAT I CAN DO FLASH OR ROOT MY AT&T SAMSUNG NOTE 5 (EXPLAINED STEP BY STEP) IN ORDER TO MAKE MY PHONE WORK AGAIN????
I have never before messed with the phone.It has the original stock firmware Android 7.0 Nougat.
And the phone is bought in USA,but I live in EUROPE and have unlocked it ,by buying some code online, few years ago.It was working fine until yesterday.
Thank you in advance guys I hope that someone might help me.
Juno 106
Guys I found here some older version (few months older) of Android 7 for my Note 5 and I managed to do a flash. The flashing went OK I went through settings and after few minutes the phone freezes again and restarts. And then again the same,it works fine for a few minutes,freezes and restarts (I can here the camera working inside sometimes too)...........CAN ANYONE HELP ME REPAIR MY PHONE ,PLEASE ???
Hi again
I don't know why no one is replying to me???
Today I managed to make the settings and power up the phone,restored the back up....the phone is working,BUT the PROBLEM is that it constantly freezes and reboots by itself.Sometimes it works for few minutes and reboots,sometimes it works for 30min and then it reboots,sometimes longer...
What might be the problem? Is it some hardware problem processor ,memory or maybe bad battery? It is older model and I have noticed with Accu Battery that most likely the battery haslowered it's capacity.It drains faster,sometimes when it comes to 15% it drains very fast...
Can anyone help me diagnose the problem?
Thank you in advance
Try booting into Download Mode & flash a new stock firmware if all else fails, assuming u tried a factory reset first with no satisfaction. Guides are everywhere. I HTH
PiMPSoFT said:
Try booting into Download Mode & flash a new stock firmware if all else fails, assuming u tried a factory reset first with no satisfaction. Guides are everywhere. I HTH
Click to expand...
Click to collapse
Thank you for your reply
I managed to flash the firmware few times,but the phone keeps freezing after some time and restarts.Sometimes it is stuck in the bootloop,sometimes it starts up to some point,freezes and restarts.
Could it be BAD BATTERY or is it something else?
If it is the battery problem,I will replace it,but I'm afraid that it might be someting else wrong.
What is your opinion?
Hello Samsung Galaxy A70 users!
I come to you with a request for help. Well, a few days ago I got my hands on a Samsung Galaxy A70, which for some time did not want to start the system when trying to boot, but only turned on and off over and over again every 20 seconds. He also often stopped at the Samsung Galaxy A70 logo and did not attempt to boot the system at all. So I figured I'd reinstall the latest software by Odin. The previously described problems still occur after correctly uploading a clean system.
Anyone know what I should do to solve the problem of the phone rebooting itself and its reluctance to boot the system? From myself I will only add that the OEM is blocked, because I have no chance to get into the operating system and to be able to disable this lock.
You can add more information, like the software version you have flashed, which spftware the phone worked previously on, a picture from your bootloader (so we can figure out what may have happened to the phone that made it useless).
Stock recovery logs are useful too, but you gotta read it on your own.